1091

Please dont take this seriously guys its just a dumb meme I haven't written a single line of code in half of these languages

you are viewing a single comment's thread
view the rest of the comments
[-] NocturnalMorning@lemmy.world 42 points 4 months ago

Python one is accurate. Most of our problems are solved by importing a library and writing the line, librarySolver.importedFunction.SolveMyProblem()

def main(): Print('thanks librarySolver')

[-] SpeakinTelnet@sh.itjust.works 14 points 4 months ago

Advent of code 2023 day 24 part 2. Z3 solver saved the day on that one.

Now I have PTSD every time I see an hailstorm.

[-] ornery_chemist@mander.xyz 6 points 4 months ago* (last edited 3 months ago)

So many solver solutions that day, either Z3 or Gauss-Jordan lol. I got a little obsessed about doing it without solvers or (god forbid) manually solving the system and eventually found a relatively simple way to find the intersection with just lines and planes:

  1. Translate all hailstones and their velocities to a reference frame in which one stone is stationary at 0,0,0 (origin).
  2. Take another arbitrary hailstone (A) and cross its (rereferenced) velocity and position vectors. This gives the normal vector of a plane containing the origin and the trajectory of A, both of which the thrown stone must intersect. So, the trajectory of the thrown stone lies in that plane somewhere.
  3. Take two more arbitrary hailstones B and C and find the points and times that they intersect the plane. The thrown stone must strike B and C at those points, so those points are coordinates on the line representing the thrown stone. The velocity of the thrown stone is calculated by dividing the displacement between the two points by the difference of the time points of the intersections.
  4. Use the velocity of the thrown stone and the time and position info the intersection of B or C to determine the position of the thrown stone at t = 0
  5. Translate that position and velocity back to the original reference frame.

It's a suboptimal solution in that it uses 4 hailstones instead of the theoretical minimum of 3, but was a lot easier to wrap my head around. Incidentally, it is not too hard to adapt the above algorithm to not need C (i.e., to use only 3 hailstones) by using line intersections. Such a solution is not much more complicated than what I gave and still has a simple geometric interpretation, but I'll leave that as an exercise for the reader :)

[-] SpeakinTelnet@sh.itjust.works 2 points 4 months ago

That is a great explanation of how you solved it, thanks! I should go back to it and conquer that puzzle properly without a solver. Or at least try.

this post was submitted on 12 Mar 2024
1091 points (95.7% liked)

Programmer Humor

31314 readers
26 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 4 years ago
MODERATORS