[chadanon]

I like Uncle Bob's lecture on what it means to be a professional. We have to make time to mold code and recaftor it without buy in - make that time built in to the estimates you give.

Another thought... At some point there's going to be a software caused disaster with very large human cost of life such that the governments of the world will demand and force regulation and certification. Software "Engineer" will have the same hoops and red tape every other engineering profession has to deal with and over the long run we may all be better off if it's not to late. If the transhumanists give birth to free willed laser-beams-for-eyes robot hybrids... probably too late. As dark as this sounds I hope a software disaster comes sooner than later.

[bradlys]

> We have to make time to mold code and recaftor it without buy in - make that time built in to the estimates you give.

The problem is that often management has been technical at some point in the past and will want a full breakdown of why something costs more time than they think to implement. Soon as you detail having to refactor X or do some other “non-essential” thing then it gets put on the cutting room floor.

I’ve experienced this a lot. It’s often people who have escaped having to write code that are the biggest backstabbers.

[TheCoelacanth]

It's often a principal-agent problem.

It's usually in the manager's best interest to deliver a feature faster even if it results in future features taking longer, because their bonus/promotion is dependent on delivering the current feature, not on the long-term impact.