788 karma · joined March 3, 2012
Those are just two companies, ran by the same guy. I think finding even a couple dozen more examples would be very difficult.
The justification in Europe is that governments want to encourage entrepreneurship (and contracting counts as entrepreneurship), hence lower taxes. I wonder what's the logic behind the US situation.
From what I've read, the Japanese public debt is mostly domestic, so it wasn't actually foreign money that was fueling the growth.
I think people change during the course of their life. While greed will not probably motivate you enough to rise to the top (you need other drivers such as ambition), if you've already made it to the top (and there's nowhere else to go, you're already #1 by your own metrics), you can slowly morph into a greedy bastard.
The biggest problem with that is that a lot of companies don't like to contract out management, so you're options may be somewhat limited (and if you choose full-time employment instead, you go straight into the maw of 40% taxation).
I think nothing in Europe beats London. Of course, the rents are insane, but if you don't have a family and are willing to live in a shitty place (maybe with flatmates) with a commute, it doesn't affect you as much.
Out of curiosity, when making a total comp of $300k in Silicon Valley, what kind of take home pay (after taxes) can you expect - including pension contributions?
Getting easily bored was helpful?
IMO the fifties in the US were a total anomaly and they're not coming back ever. It was a time where (more than?) half of the world was taken out of competition due to idiotic economic system of communism, and Europe, the only potential competitor to the US, was still in shambles after the war. The US were a sole economic superpower, no wonder people had it great back then.
I agree that it sucks, but I'm not sure if it's unsustainable. There are plenty of worse situations in the world that pretty long-lasting.
I am specifically interested in that part :) If I'm withdrawing the money myself from the fund, then I have to take into account the small possibility of me living until I'm 90-100, and thus split money into portions that will last that long.
A company could pool a lot of people's money and take advantage of the law of big numbers (i.e. the average lifspan of their clients can be predicted with actuarial math) and portion my money as if I'm going to die when the stats predict me to die (sooner than 90-100 years old), making my monthly withdrawals bigger. That's what state pension funds do in a lot of countries at the moment, incl. my country Poland, but I don't trust the government with my money.
As for the project size, (all other things equal) the bigger the better obviously (since software complexity/difficulty raises non-linearly with problem size), but that's not the most important concern - you can for example produce two separate projects instead of a singular big one if you think it will allow you to learn and showcase more.
The first route would probably make more sense (there aren't that many people like you I guess), but it would require you to move (the market for such skills is small) - maybe even to another continent.
If, on the other hand, you want to be a "generic" SE (that can work anywhere in the world and maybe has a shot at remote work), you need to pick a specialty and prove employers that you can deliver within it. That's worth more (although less fun) than cute CS projects you've listed. Just select area/technology/stack you like and start learning about it and eventually build something non-entirely-trivial with it. If you want to see what's hot, take a look at monthly "Who's hiring" threads posted here - they give a good overview of what tech is currently in demand and/or trending up.
There is no academia (as in academic career track) - I am only asking about programmers, not researchers. If you work in academia as a programmer (say implement stuff at CERN), you can answer according to the nature of your job - ex. if you help scientists write simulations, you select "scientific/numeric", if you mainly work on massive data pipelines, you select "big data" etc.
As for coming up with a list - I compiled it myself, trying to bundle together work that seems close enough in nature. For me, desktop programming looks similar to systems programming - i.e. it's mostly C++/C/other compiled languages, working against OS APIs, no garbage collection, expectation of reasonably low latency.