[LoSboccacc]

A: you hire young one that have no idea what they're doing and jump into problems both feet without thinking a path ahead

and for every programmer claims to work that much, you also get two of them complaining on the costant shit the overworked one produces and have to fix strange bug half their time

eventually the software becomes a mess of tangled issues and advancement grinds to an halt irregardless of amount of time spent

[Sorreah]

My last job was exactly that. I was dropped in as an almost-30 year old, working with young 20 year olds still in school.

I was fired a few months later, with the main reason being that I usually left the office 9 or 10 hours after coming in and only occasionally worked the 12+ hour days that the rest did.

With a small codebase and self contained projects, I can't really say quality suffered. Only the employees.

[coldtea]

>I was fired a few months later, with the main reason being that I usually left the office 9 or 10 hours after coming in and only occasionally worked the 12+ hour days that the rest did.

Such practices are illegal (or at least frowned upon) in most of the civilized world.

[rhapsodic]

> Such practices are illegal (or at least frowned upon) in most of the civilized world.

It's called "employment-at-will", and it's not that uncommon.

[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