> reversable or traditional computing

o.O ...

No man I'm saying a very simple and non-controversial thing: just because someone does a tut, has an elementary understanding, knows the basics, doesn't mean I'm going to let them build/maintain/own mission critical systems.

It's not that deep.

I see. But your point is then orthogonal. So it's $400/h not $100/h per SWE as you need experienced good people anyway.

But the question really is: what solution minimises tbe number of those hours? Formal or informal?

If I can build something in 100 hours paying 100$/hour, or 33 hours paying 400$/hour, I may well choose the 100 hours version. Which is why we hire interns in the first place, rather than only hiring senior architects for our companies.

Where do you work that you're paying interns 100$/hr and seniors 400$/hr, and are you hiring?

Some places do run on 2x overhead, which means if company is paying $100/hour, that intern is taking $68k/year... Pretty normal in a lot of places.

I'm just copying the numbers from the above comment.