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
[–] 4 points 4 weeks ago (3 children)

The hash question is just something from the top of my head. I normally fit it to the situation.

I absolutely take nervousness into account, as I can relate to it.

The thing is, I need to know if the person can push back in some way. it's a hard thing to do in interviews, but also the first point for me to check how a person reacts

I've been bitten too many times, with dev coworkers who don't give at least a little resistance when vague or stupid tasks show up. Only to notice hours or days later, when something was done completely the wrong way

  • source
  • parent
  • hideshow 3 child comments
  • [–] 9 points 4 weeks ago (2 children)

    Sounds like you need to fire the person handing out vague and undefined tasks to everyone 😂

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 4 weeks ago

    Every task starts out as a vague idea that, at some point, needs to be narrowed down to something specific and actionable.

    If you’re at a sufficiently large organization and you get lucky, that happens before it makes it to a developer. For the rest of us, it’s an important skill to be able to take a task, ask clarifying questions, and narrow it down to something actionable.

  • source
  • parent