Hacker News new | ask | show | jobs
by bradlys 1518 days ago
> 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.

1 comments

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.