News for hackers. Stuff that matters.
Re:How to set junior employees up for success in remote by greatpostman on Monday June 27, 2022 @12:03PM (#31896511)
The software is way too complex to gauge how long something will take. It’s also extremely risky to make a mistake in production. Projects slated for three months can take two years.

If you’re engineers are constantly hitting deadlines, probably it’s greenfield development or the problem space is simple

Re:How to set junior employees up for success in remote by bumby on Monday June 27, 2022 @12:16PM (#31896710)
I agree. But if we don't manage it well at scale, that underscores that we don't really understand the complexity of the problem. Can you call someone a "top performer" when they don't understand the complexity of the problem?

We can write complex code with minimal errors[1].

"the last three versions of the program — each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors."

But I worry when we facilely normalize sub-optimal behavior because we've normalized it. Especially as FAANG and adjacent companies work on safety-critical software and when that attitude pervades other domains.

[1] https://www.fastcompany.com/28121/they-write-right-stuff