832
reason enough to fail the interview (lemmy.world)
submitted 2 months ago by to c/programmer_humor@programming.dev
121 comments fedilink hide all child comments
 
A picture of Edsger Dijkstra with a concerned face and the following text on top: How software engineers look at your code when you solve the problem using two tables — instead of using the Maxwell-Ross-Karmakar algorithm, which is marginally optimal in ordered sets bijectable to the exponential curve
you are viewing a single comment's thread
view the rest of the comments
[–] 87 points 2 months ago (5 children)

Ha. I had a convo with a programmer in the 90s. He was explaining a complex problem and the steps to solve in the code, to adjust things based on user choices and parameters.

And I said why wouldn't you presolve all of them and then provide a lookup to go get the solution from a list. And he just looked stunned and walked away.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 17 points 2 months ago

    Ah my prior manager suggested something similar... Dynamic views that would adjust based on user set parameters... We set up canned views and called it a day.

    He was let go, but always pushed for the art of the possible (even if it would take a few extra sprints to wrap)

  • permalink
  • fedilink
  • source
  • parent
  • [+] -12 points 2 months ago (2 children)

    why is this upvoted

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 10 points 2 months ago

    Because he hadn't thought of what I suggested and it was much easier than what he was trying to program. I wasn't suggesting he write the program, solve it and table it; it was more like empirical knowledge/common sense stuff to narrow options, then fill the rest in based on what made sense. Then its just a horizontal or vertical intersection to find the outputs required instead of a complex calculation every time

  • permalink
  • fedilink
  • source
  • parent