[starbeast]

I made the mistake of showing the 'hammock driven development' talk to an employer of mine. He got annoyed by it and said he thought that it was just providing programmers with an excuse for staying away from the computer when they should be writing code.

[gavinpc]

It is kind of heartbreaking.

But, although my current manager is excellent at supporting his team and would never think such a thing, let alone say it, the truth is that, unless you're a professional researcher, you really do have to do the hammock-driven thing on your own time, either by working it into your routine or by taking a long sabbatical (as Rich did). It's something I struggle with, even at a very good workplace.

"Nothing is more precious" than the chance to think through a problem over a long term, and as things stand, the best tool for thinking is still the mind, not the keyboard. I can see how that takes a leap of faith when your chief deliverable is code.

Anyway, maybe a better introduction for your typical manager is,

> The most expensive problems are problems of misconception.

[kamaal]

>>it was just providing programmers with an excuse for staying away from the computer when they should be writing code.

That would be code as carpentry development model. Often encouraged by career managers.

There are plenty of those in the industry, people who have had rapid promotions before they could do non-trivial engineering work.

[raspasov]

Has he ever written code that was used in production and he was in charge of the project?

[starbeast]

He became a project manager when he found he wasn't good at writing code after becoming a coder when he found he wasn't a good physics researcher.