It's not as much about how many hours you work so much as how much of your life revolves around your job. Ask yourself this: if things aren't going well in your job, what happens? If your life revolves around one thing and that thing goes badly, it affects your whole life. Having more things outside of work helps a great deal.
AA still has its place. A lot of people like its philosophy. Plus, some people just don't respond to anything else other than its "tough love" philosophy.
> Well yeah... it's completely delusional to think a 3 month developer should earn the median income for programmers.
$75k is not the median income for programmers. $75k is the median income for anyone in SF. Which is exactly my point. To expect engineers to live in SF, you have to be willing to pay exorbitant salaries just to break even. If you want to pay a good salary, you pretty much have to pay 6 figures. Don't like it? Move to Cleveland or Detroit. I'm pretty sure $75k would be considered a great salary there. Just don't complain that developers cost too much and then require them to live somewhere with such a high cost of living.
Yeah, but you know what? The cost of living has also skyrocketed dramatically in Silicon Valley. I mean, you make it sound like engineers here are on a gravy train where we spend 3 months learning a language and can suddenly move to San Francisco where we just let the money roll in. The truth is it costs a lot to live in the Bay Area these days, and that means that if companies want people to move here they need to pony up and pay a good salary.
That $130k starting salary you mention is enough for a person to afford a studio in the Tenderloin these days?
Not only is this an issue of residential codes. The other problem is that they're doing manufacturing in a residential neighborhood that's not zoned for manufacturing. And it's disturbing the neighbors in the area with noise and even sewage spillover.
Well, there are still cases where object pooling might make sense. Some games on mobile devices still use object pooling. I suppose I could also see the need to use object pooling for a very busy server or a very large hadoop job.
At most private companies, stock options aren't worth the paper they're written on. Unless of course the company sells, in which case they're worth slightly more than the paper they're written on. And besides that, to exercise them you usually have to pay a pretty hefty sum. I generally don't consider equity as a part of my compensation package when I work for a private company.
Correct me if I'm wrong, but it would seem like Ocean Acidification would be less prone to "Climate Commitment" than regular climate change. Meaning, if we just stopped emitting greenhouse gases, OA would stop increasing. The rest of Climate change would still keep continuing for a few decades.
Blah. Yet another "new-fangled technologies have no place" post. Granted, there's a grain of truth to the core thought. As I've become more experienced, I've seen more frameworks and libraries that re-invent the wheel and solve problems that have already been solved long ago, albeit in a trendier manner.
But at the end of the day, software engineers are technologists. Our job is to create and consume technology. Being afraid of new technology is counter-productive.
For better or worse, this is life for top executives. Example: the president of the US's popularity is correlated with the economy in spite of the fact that they have very little control over it. It's not uncommon for one executive to do something totally reasonable under hard circumstances only to get ousted anyway while the next person gets the credit for their actions.
What he took was proprietary infrastructure-related code that didn't involve any of Goldman's trading algorithms. His claim is that it was so tangled up with the open source code he wanted that he had to take it out to get it.