This is unfortunately very much true. Was only a matter of time I guess. The "grass is greener" effect is indeed the most likely reason.

An advice I often give, it's nice to see the theory behind it well laid out like that.

Now this is a well balanced piece about estimates. Starting from the "why" to decide how you approach the estimates and the level of details is just very good advice.

Couple of interesting tips. I like how it challenges the usual mythical man-month quote. Indeed sometimes adding people might help, if the conditions are right.

It feels a bit like cumulating aphorisms and "laws" to prove the point. Still it's nice to know them at least for the general culture.

Interesting set of metrics indeed. As usual the danger lies in how/if you set targets and potentially fuzzy definitions of some of the terms.

Interesting take as usual. Utilization doesn't matter, throughput is what you need to keep in mind.

This is a good piece. Killing all planning is indeed not a good thing. Setting plans in stone wasn't a good thing either, it's no reason to go to the other extreme.

Interesting musing on how different types of companies manage their projects. I'm glad to see there's less cargo-cult Scrum than I expected. I also find funny that Scrum is perceived as "heavy weight". :-D

This is a sane approach and a good list of steps for estimating at large scale.

Excellent advises on project planning and management. It explains pretty well why being optimist in those areas will just drive your project through a wall.

Last part about estimates. Plenty of very good advises again on how to deal not meeting a deadline. Communicating the bad news early is key.

Another nice piece about estimates. This time for the tough times when you're asked a quick ballpark number. The best piece of advises in there: know when you shouldn't do it at all, and, if you go for it sound vague.

I'd even add "you can never be to vague". Even if you go for "a few weeks, maybe two or three" very often people here "two weeks". Don't hesitate to hammer down the uncertainty in all this.

I got a slightly different view on the topic. To me there's value in the process of estimating, the estimation itself less so. The process often helps you refine both your understanding of the technical domain but also of the business domain.