These comments are pretty depressing. How many of you have ever used those government services? You are paying for them you know. This article should be encouraging. It worked. They payed in, they needed the help and got it, and now they are back on their feet.
Thank you. No kidding. I grew up on food stamps, and I remind myself that when I realize I'm now well into the 1%. This shit matters and most of the people on these programs aren't on them just so they can be lazy, they're on them because they have limited options.
The glibness of the comments here really rubs me the wrong way. A lot of software people - you know, arguably the MOST employable people on the planet - have no hesitation tut-tuting about what The Poors should do while pushing buttons in a comfy chair in an AC office with the knowledge that if anything were to happen, they'd be OK.
News flash, being poor SUCKS, and it means you work your ass of just to get by every day, always in constant fear of the next unexpected event - your car breaks down or you get sick, then you miss a day of work, then you get fired, then you can't find another job, then you're homeless.
It's almost like a bunch of you ready the article and missed the point.
>It's almost like a bunch of you read the article and missed the point.
What is the point of the article? I mean besides the we-can-sell-ads-ginning-up-outrage-(which-may-or-maynot-be-misplaced). I'd like to see a "The Last Psychiatrist" like take on it:
This part sums up why I quit using OS X for my personal projects: "And if your software crashed, you didn’t make excuses. You just made damn sure that particular scenario didn’t happen again. Ever."
In making sure nothing ever crashes, Apple has moved more and more to an OS that is too restrictive for my taste.
I fail to see how making sure your code doesn't crash is related to OS X being restrictive. We've just experienced Heartbleed, a prime example of a poorly-reviewed piece of software, in one of the most entrenched OSS libraries. I'd certainly appreciate a stricter process of code review and testing, considering the cost of patching it.
You being not a fan of OS X apparently clouds your judgement in this case.
Although I too switched away from OS X, this is irrelevant. The point of the story is not about Apple's idiosyncracies. It's about a man whose story is fragmented. It's about a man who was intriguing, cryptic, and unpredictable. It's another story in a bucket of stories of about him.
Actually, I don't see how it is an important story, though it was interesting to read, and I enjoyed it. As you said, it's one more story in a long list of stories.
If the stress is overwhelming you, then you should see if there is a solution to remove the stress. If not, then you should probably quit. It isn't worth what stress can do to your health and relationships.
If they need you to do more work beyond your 40 hour week, to the point that they threaten to fire you, then your supervisor likely realizes they need you.
If you find that at 5pm that you are twenty minuets away from finishing something up, then you should consider doing that from time to time, just to show you're on the team.
I am lucky enough to be in a position that I am on salary, but I am still paid overtime if the work load moves beyond 40 hours a week. If I need to work an extra 15 to 30 minutes to finish up what I'm working on, I don't count that as overtime. If I get a ticket that needs addressed, but there isn't time to do it in the normal work day, that counts as overtime.
Maybe consider proposing something similar. If what they really need is a little more help, but don't want to hire a new dev, they may be willing to come up with a compromise.
My mother was insistent that my siblings and I knew Santa wasn't real. She was very naive as a child, and when she was 16 someone at school made a joke about kids that believe in Santa. She got in an argument with them, herself believing that Santa was real. Kids were cruel, as they are, and I guess it followed her for the rest of her school days.
My own children are young right now, so I let them enjoy it. I'll just make sure when they get a little older they know who's really buying those presents.
I figure the best thing to do if kids are getting older and still appear to fully believe is to start dropping hints. For example, Santa is usually last to go after things like the Tooth Fairy and the Easter Bunny, so you could mention them together. Eventually the kid will figure it out on their own, which is a lot more pleasant than just being told one day.
I've found NetBeans to feel less resource hungry than Eclipse, or IntelliJ IDEA, on my linux box. It also feels more intelligent than Eclipse when offering suggestions or code completion. I've, overall, been extremely pleased with it. I also prefer it aesthetically over Eclipse, for what that's worth.
The transition from Eclipse is really smooth, and there are many helpful FAQ's on the subject if you need it. I've been recommending it to friends since I made the switch a few months back.
