Hacker News new | ask | show | jobs
by mdp2021 1771 days ago
So this friend of mine receives a call from the Director about to evaluate his work, and is told "Clearly you are brilliant, but other colleagues are faster than you... For example, yesterday I asked about X, and see how A was fast in replying?"

It was not easy to express that A gave a quick response with a largely false content.

It is called rushing, it came from a culture of stopping well before decent quality, and it should not be a value.

2 comments

This great story is only half told!

Is the director the hero, who gave clear feedback to her employees then listened to the response and corrected the course?

Or is the director a lizard who demanded the impossible received junk in reply and didn’t recognize it even when courageously told?

These things, in different forms, happen frequently, unfortunately.

It would be interesting to know how many times the outcome is "hero" and how many "lizard", under which conditions, in which contexts etc.

"Agile"/Scrum plannings is one example of rushing with design decisions in order to assign the tasks to developers.

Of course you can assign the design tasks, but the rest of the tasks are depend on the outcome of it, so it doesn't work in practice.

Waterfall on the other side, does overly encourages overthinking.