My dad went the other route - he had an MIT Ph.D in nuclear chemistry and gave up his career to be a dad. He was always, always there to play LEGO with me or take me to the playground or drive me around to after school activities. And I really, really appreciated that - I probably appreciate it more now that I'm grown and he's dead.
The thing is - he still had something to prove, and because he had given up his professional life for me, he transferred that need to prove something onto me. And so for most of my childhood, I felt like I had to do well in school, and when I grew up it was up to me to win that Nobel Prize that he never had a shot at. And it went like that until I was in around middle school, at which point I basically said "Fuck that shit" and started sabotaging myself just to prove to everyone that I wasn't this super-genius who was destined to change the world.
And that wasn't really fair to me either.
I don't think it's really a matter of outcomes, of affording the big mansion in a gated community. I think that every kid deserves to have a dad who can be proud of who he is and what he's accomplished in life. If you can honestly feel that you're not giving up anything to be with your kids, but rather gaining something, then you should do it. But if you would otherwise be bitter and resentful for what you couldn't accomplish in life - it's better to have an absent dad than a bitter one.
I founded a startup at age 25. Worked my ass off on it for a year and a half. It failed and went nowhere, as many startups do.
But I felt that in many ways, the experience set me free. I'd kinda coasted through school, college, and my first job half-assing whatever work I felt like, because I figured that at some indefinite point in the future, I'd found a startup and become a millionaire, and so nothing I did really mattered. Whenever things didn't work out, there was always some reason - "The material wasn't challenging" or "The professor didn't like me" or "It's not what I want to do anyway" or "We're using the wrong technology stack" to explain it away.
When it was just me & my cofounder though, the material was challenging, it was what I wanted to do, there was nobody else to blame, and if we were using the wrong technology stack, I damn well better change it.
So even though it didn't work out, I felt that I gave it my best effort and made a sincere shot at it. And that set me free to give my best effort on other things, because really, the consequences of it not working out were pretty minor (I got hired by Google). It wasn't the outcome that mattered, it was the process of figuring out what I was capable of when I really put my mind to it.
I'd much rather figure that out at 27, when I'm single, living like a college student, and have my whole career ahead of me, than when I'm 40 with a couple kids, a mortgage, and a string of dead-end jobs behind me. And I'd much rather figure it out at 40 than when I'm dead.
After 2 years of my crazy commute for a higher paycheck, the paycheck doesn't quite feel as justified.
Wow, and I thought my 3 1/2-4hour commute was bad. If you live anywhere near a big city I suggest switching jobs. If you're a programmer the market is amazing out there. It has two weeks of very lazy job hunting and have found a new job that is closer, more pay, way better benefits and environment.
Though I am working on going out on my own, since I don't plan to keep the commute up long term.
You don't, your family is 2.5 hours away from where you spend most of your day.
I think it's quite hard to see the damage a commute like that is doing at the time, when you look back at it later you will wonder why you put up with it so long.
We could move close to SF, save maybe an hour or so commute each way, pay more for a smaller house, and then my kids no longer see their cousins and grandparents every weekend and we no longer get last minute babysitters.
Trust me, I analyzed my situation before and during this commute. It is very different from the outside looking in than when you are in the middle of it. And a few comments on a site like HN is missing a whole lot of context about a multi-faceted issue.
Or try to find a way to work from home. Then you'd have it made.
If anyone needs an awesome Unix Devops guy that is also a kickass backend Ruby engineer, hire Ken and let him work from home so he can have more time with his kids.