[devoply]

There may be a few exceptions, but by and large a young inexperienced programmer's 80 hours will be worth an experienced programmer's 40 hours... plus the cost of the fact that the inexperienced programmer will make mistakes which will cause your code to quickly become unmanageable without oversight. Churning out code is quite a bit different than churning out good code.

[javier2]

I am 27 and am fighting those same 24-year olds that want to code before they think.

They call it refactoring, I call it fixing a design issue. The code is no longer fit to fulfill the requirements of it's task and must be altered.

Of course hacks are fine, but they must be reserved for when the fan is blowing shit. It's not for cramming in just one more meaningless task into the sprint.

[LoSboccacc]

on the other hand, I'm fine with hacks and shortcuts as long as they're hidden behind a sane, non-leaky interface. Not everything needs to be utmost perfection, especially on the outer layers of the app