This. Do this and one of the other strategies. Just save some freaking money. I know far to many people who are up-to-their-eyes in debt and have almost no savings.
Especially these days with people waiting longer to have kids, the 40-year-old employability cutoff is a problem.
Bay area housing costs seem to make saving very difficult. I'm not sure I'll be able to retire before 40
I spent a year in the Bay area, but moved back to Ohio for family reasons. That helped, because things are so much less expensive out here. (Bear in mind, though, you can work in the Bay Area and then retire somewhere cheaper ;)
http://www.mrmoneymustache.com/ has some great articles on how to save money while still enjoying life.
My top piece of advice is: do not buy a brand new car. Don't buy any car if you can manage it, but if you must own one, get something that's a few years old and half as expensive. And even then, try to ride a bicycle when possible.
Yes but, while working in the Bay Area you have to live in the Bay Area (assuming you aren't remote). I'm just super curious how we're supposed to save enough to be safe by 40.
* Don't spend more than about 8K on a car. Drive it till it dies. (I drove a $2140 15 year old Saturn without AC or working windows for 7 years).
* Learn how to save money while still in college.
* Read "The Idiot's Guide to Getting Rich". Ridiculous title, but plenty of sound advice throughout the book.
* Use Excel or C to figure out what your savings will be by age N if you save X/mo with whatever inflation/investment rate. You're a programmer so this should be straightforward.
* Take those results and save X/mo. Stick it into an index fund with automatic reinvestment. Set it up to withdraw X/mo from your bank account every month. This last part is probably the most important part! It forces you to live like your salary is $Salary-X, and eventually you just come to accept that.
* Monitor those numbers and watch it go up. Discover you prefer doing that to buying things. Increase X.
* Travel! Okay this is odd advice. But when you take time off work to travel a bit you really learn how to stretch every penny. I spent three years overseas sometimes working odd jobs and it was worth every second.
* Don't incur "bad" debt (duh), and pay high interest rates off ASAP. Low interest rates 3% or so you don't have to worry about so much.
* Don't play the lottery. Don't expect that there's a "trick" to building wealth. It's just a long arduous boring process of living below your means.
* Read "The Idiot's Guide to Getting Rich". Ridiculous title, but plenty of sound advice throughout the book. Yes I said it twice.
As I mentioned in the other comment, my savings rate has been trending upward for a while, and I now save about ~40-45% of my take-home pay.
But, even when I lived in the bay area, earned less money, and paid twice my current mortgage in rent, I was still saving ~15% of my income.
I don't consider myself deprived: we eat out, buy fancy phones, etc. We have a separate bank account just for giving that gets some money automatically transferred in each month. Our car is a 15-year-old civic that looks terible, but we don't drive that much and it still runs great. We'll probably replace it soon, but I kind of want to see how long it will go at this point ;)
Like I mentioned in my other comment, http://www.mrmoneymustache.com/ has a lot of great advice. There's a few sites like that one, but MMM is my favorite.
What you're doing sounds like what I want to shoot for. I'm almost 30 now, and for the last 2 years I've REALLY ramped up my savings. My goal, is to retire sometime in my mid 40s, so that I can work full time on my own projects. Lofty goal to say the least. I also realize that to do that, I'll need to find a cheap home.
Been reading up on mrmoneymustache, some great tips there. Thanks for the link!
Whatever nfriedly's situation may be ... you won't get to the latter until you understand the former. In other words: You can't "save an incredible amount of money", without first "saving some money".
Professional reputation is a big deal. If you have a good enough reputation you can basically negotiate for your own salary.
Younger Engineers (i.e fresh from university) do not get to work on the large projects and especially not in any kind of lead role. Mostly they work under other more senior engineers. Typically you'll work your way up until you get given lead on a small project. Eventually you will move onto managing medium to large projects.
Senior engineers (i.e 40's and 50's) are hugely valued. These are the people with professional reputations, contacts etc. Clients will know these Engineers by name and will often request them specifically.
What I've seen typically happen is for engineers in the 50-60 age range to semi-retire and move into consulting or Academia. Many Engineering lecturers at universities are retired former practicing engineers.
Several senior engineers I used to work with have moved into consulting and they get paid an obscene amount of money- more than I make in a years for a 3 month consulting gig in a country like Brazil, India, China etc.
We have a diversity problems for sure but it is gender not age.
In my 20's and early 30's every job I got was through contacts.
Since then I've been working solo projects at small companies for a number of years. Fun work, but suddenly it's dried up. I don't have any good recent contacts in the tech sector. So I'm competing with 22 year olds, with little to back me up.
So don't do that. Try to keep in touch with former colleagues, and try to be widely-known in your company for doing good work and being easy to work with.
If you're 33, you might get a job using a recommendation from someone who managed you a decade ago. If you're 53, that same person retired years ago and doesn't have any pull to offer. And someone who worked for you 10 years ago can't recommend you easily, because it's hard to "recommend up" to a position above your own.
It's a subtle sort of thing, it's not direct ageism but it's obviously a big hurdle for an older worker.
Stick with big companies. Yes by working at a small co you gain experience picking tech stacks, working on all areas of software, etc. But the ceiling is lower at small companies (only the very hottest couple startups each year notwithstanding). And the experience you gain there (mostly writing simple CRUD apps in various languages) isn't so applicable to larger companies where performance and scalability are the main things they want. So when you hit the glass ceiling of the "small co" sector, you're essentially starting all over when you move to the "big co" sector. That's where I am and it's almost like a career change.
Compare this to a career path at a large co, where you move into senior engineering and the skills you gain are immediately useful when you apply to other large companies. You get free networking and visibility at big companies too, an underestimated fringe benefit.
Also, pick your battles wisely when doing the "keep current on technology" thing. Avoid cute stuff that doesn't have a ton of use outside a very narrow segment (e.g. Haskell, logic programming, blockchain, marginally CUDA), unless you really want to devote your career to it. Also avoid overly-trendy stuff that will be obsolete in five years (JS frameworks, MongoDB). Stick with things that solve real problems that real companies have. To that end, search job boards and see what other large companies are hiring for.
I'm doing the small(er) company thing, and I don't regret it, but I've slowly shifted to larger groups and I definitely feel the difference. Getting exposure to lots of different things is good, but at a certain point being in charge of maintaining the website while you're also building an actual product is just a distraction.
The "current tech" thing is obviously a constant battle for everyone, and it's an important one. Narrow tools can be trouble, flash-in-the-pan frameworks are ugly, and even things like Go can be chancy if you master something valuable but scarcely employed. At the very least, it's obvious to me even early in my career that I need to maintain a couple of mainstream, in-demand skills no matter what I specialize in.
The only advantage of broken comb is that you potentially have lots of middling positions you can apply to. But even for those, you may be rejected as "overqualified" because you know so much other stuff. Besides, who wants to send lots of resumes and do lots of interviews in the pursuit of a middling job? Especially when you know you're way better than the people that you're competing against and losing to.
So, don't fan too far out. Find a concentration that's reasonably mainstream for the foreseeable future and expand your skillset to supplement that. Maybe not as renaissance-man as the typical above-average programmer would hope for, but likely the best career path.
The few that were, I got discriminated against because of my age.
Doh!
[1] They tell me. I can't get too far from the code or its no fun, but I prefer to build teams and work at a high level than to be constantly coding all the time.
Mechanical/chemical/electrical engineers have a similar problem that 30 years experience isn't much more useful than 10, wages tend to top out early and you're vulnerable to being laid off and never hired again in your 40s/50s. One advantage over software is that the skills change perhaps less frequently but that is offset by lower overall demand.
While you're in your 20's think about what you're going to do at the end of your 20 year window. Are you moving up to management? Have extensive business knowledge to add to tech skills? Have a second career planned? Or saved enough money to retire or semi-retire? Of course you can actively stay up to date with latest technology but that is much tougher than it sounds. You need to have thought a lot about this before you hit 40.
For all the young guys out there. Don't think it wont happen to you. If you just follow day by day one day you'll wake up with a big mortgage, a couple of expensive kids, maybe a divorce and a bunch of recruiters that never return your phone calls. You need to avoid that place.