That's good advice, regardless of how much you earn (but it might need a 'save your money when you can').
Spending money when you don't actually have to is a bad strategy when you're young and you can still materially alter you later-in-life situation with relatively little funds.
That's why I hate student debt of any form, it saddles those that would benefit the most from some savings with debt so they can't start to save until they're in their mid 30's or even later.
Also, $150 /hr is a pretty low rate even in the leanest of times.
EDIT: Really surprised at the down votes on this. What I'm saying is hardly radical. There seems to be a lot of sour grapes in this thread sadly.
My tip: don't envy those doing better than you, learn from them.
Around here in the midwest, under those long-term circumstances, many contractors don't hit the three figures. A whole lot of senior devs around here are slumming it at a $50-$80/hr range.
That was my point about how $150 isn't some insane amount of money. Depending on the length of contract, it may be almost nothing at all with the overhead factored in.
Out of curiosity are those senior devs keeping their skills up, or are they programming in Java/.NET or something similar?
At those rates I'd definitely be interested in taking a look at their CVs since I often need to hire developers. It's WAY below market.
There's a lot of folks like me who program on older, non-sexy, maintenance roles on established systems which use older technologies. Outside of big cities, these positions don't generally command a big wage.
That's my point. As a developer (especially a contractor) you must always be learning new things and technology. It also helps to specialize in a field/domain.
If you're a senior developer you could absolutely make double $60/hr as a contractor by just focusing on the business side of contracting a bit more.
I've been paid $109k a year for work on Smalltalk. And yes, it was this century, in Houston. (As of this writing, 4th largest city in the US.)
Those two things aren't mutually exclusive. There is very good money to be made consulting at the enterprise level doing Java/.NET or something similar, but you also have to keep your skills up.
I am reminded of that lovely remark once made by Boris Johnson's, London's blond bombshell of a mayor, when asked about his £250,000 a year contract to write a column for The Daily Telegraph: "It's chicken feed."
$150 /hr is basically the least you're going to want to charge. Realistically you're going to be looking at 90-120k /year depending on how much work you land at that rate.
For highly skilled intellectual work, that's not very much money.
It is not what you "want to charge", it is what they are willing to pay you, that counts.
What happened to contractor pay in 2000?
My experience is most of these people will leave the industry. Very few have the skillset to become an independent contractor because of all the sales and marketing involved (in addition to the tech skill set you're actually selling).
> What happened to contractor pay in 2000?
I have no official data, but I was contracting at the time and continued to raise my rate a reasonable amount at semi-regular intervals (every year or two). During that time, people needed to get work done but they wanted one super contractor to do the work that a team of middling engineers used to do, for 1/5 the cost.
The best advice for those of you getting paid $150+ an hour is save your money and don't take on long term liabilities.