Unless by that you mean listening to her complain about her day while rubbing her feet, this is a different model of "marriage" than any of the rest of us are familiar with.
Not necessarily. Or rather - yes, that may be true, but on the other hand, my native language is American-accented English, I know that "needful" isn't a word, and I'm awake the same hours you are. I do charge a bit more, though.
Sort of - but somehow, in spite of the "high" demand, mainframe programmers don't command much pay. As in, I have about 5 years of mainframe (COBOL, JCL, Adabas Natural) programming experience, but I clawed my way out of it into desktop C++ programming just so I could make enough money to actually afford a car payment. If I went back to it now (from my current "enterprise Java" role), I'd probably take a 50% pay cut.
The grass isn't always greener. I did take that advice, and I did get a job maintaining decrepit mainframe-based COBOL for the U.S. government (I was making about $25K/yr). Then when I graduated, I proudly put that _real world_ experience on my resume. And found out that the only people who would talk to me were the people who were looking for COBOL programmers, and were paying half what they were paying C++ programmers. So you may have missed out on a summer of slightly-above-minimum-wage employment, but you also skipped over five years of climbing out of "experience COBOL programmer" hell.
Yeah, but be careful... replace too many jobs, and you'll be flagged as a "job hopper" and suddenly find it way harder to replace a job. The system will squeeze you every way it can.
Open offices, too. But the fact that they're so popular suggests that the people who are making the decisions really just don't care about the consequences; they're just hanging on until retirement.
Yeah, that's the thing I think gets missed here: you don't need a college degree to be a programmer. You don't need a college degree to do any job. But the people who do the job best are the people who've been studying it their whole lives.
You're being (ironically) an asshole, but you're probably right - not the way you mean (which is just to be a spiteful, petty, vindictive prick) but that he had probably built himself a reputation of being "difficult" to work with. That's easy to do when you're the go-to guy for a dozen different things - everybody's demanding 100% of your time, all the time, relying on you to dig them out of the hole they've dug themselves into - you have to turn some people away. Especially when you're already working 12 hour days to meet some insane deadline - you just don't have time to deal with all the people who aren't carrying their own weight.
Slashdot Mirror
it'd probably be for some loving.
Unless by that you mean listening to her complain about her day while rubbing her feet, this is a different model of "marriage" than any of the rest of us are familiar with.
If you think I can't procrastinate in the office, you've seriously underestimated my procrastination skills. Like right now, for instance...
Not necessarily. Or rather - yes, that may be true, but on the other hand, my native language is American-accented English, I know that "needful" isn't a word, and I'm awake the same hours you are. I do charge a bit more, though.
One reason I avoid working from home is that I trust my coworkers in the office to let me work more than I trust my wife and my kids to let me work.
Just because taxes could be higher, and just because they are even higher for somebody else, doesn't mean they aren't high.
... is that the so-called "gender pay gap" is actually due to life decisions, not rampant sexism?
mainframe programmers were in high demand
Sort of - but somehow, in spite of the "high" demand, mainframe programmers don't command much pay. As in, I have about 5 years of mainframe (COBOL, JCL, Adabas Natural) programming experience, but I clawed my way out of it into desktop C++ programming just so I could make enough money to actually afford a car payment. If I went back to it now (from my current "enterprise Java" role), I'd probably take a 50% pay cut.
The grass isn't always greener. I did take that advice, and I did get a job maintaining decrepit mainframe-based COBOL for the U.S. government (I was making about $25K/yr). Then when I graduated, I proudly put that _real world_ experience on my resume. And found out that the only people who would talk to me were the people who were looking for COBOL programmers, and were paying half what they were paying C++ programmers. So you may have missed out on a summer of slightly-above-minimum-wage employment, but you also skipped over five years of climbing out of "experience COBOL programmer" hell.
Nobody's willing to pay experienced COBOL programmers all that much, even though they're demonstrably scarce.
I'm curious, but haven't had a chance to read it myself. Is it worthwhile?
"The Art of Computer Programming, Volume 2", by Donald Knuth. 'Tis a rewarding but frustrating experience.
I realize you're just trying to be a jerk, but you missed that almost all of the (five star) reviews on Amazon of this book were written by women.
you're not doing it right...
Funny how much "agile" apologists have in common with communism apologists.
a .25hr scrum daily meeting
Wait until you're "matrixed" into multiple projects. Then you can attend three or four daily (one or two hour) "standup" meetings!
Well, the can't pay you in money, but you should see the stock options they offer!
Me: 'So can this job!
Yeah, but be careful... replace too many jobs, and you'll be flagged as a "job hopper" and suddenly find it way harder to replace a job. The system will squeeze you every way it can.
Open offices, too. But the fact that they're so popular suggests that the people who are making the decisions really just don't care about the consequences; they're just hanging on until retirement.
Title: Why More Tech Companies Are Hiring People Without Degrees. Body: "... or recently graduated from community colleges"
So... community college degrees aren't even considered degrees at all now?
Yeah, that's the thing I think gets missed here: you don't need a college degree to be a programmer. You don't need a college degree to do any job. But the people who do the job best are the people who've been studying it their whole lives.
Tech workers have been saying the best talent is self trained
That definitely is the slashdot mantra, anyway...
Or possibly any degree at all, as long as they fill some diversity quota. Very comforting.
How much do you want to bet the solution is going to be to start paying male programmers less?
Well, he wasn't water.
Unfortunately, until we all (collectively) grow a pair and start doing this as a unified group, these sorts of abuses will continue.
the problem is that you're an asshole
You're being (ironically) an asshole, but you're probably right - not the way you mean (which is just to be a spiteful, petty, vindictive prick) but that he had probably built himself a reputation of being "difficult" to work with. That's easy to do when you're the go-to guy for a dozen different things - everybody's demanding 100% of your time, all the time, relying on you to dig them out of the hole they've dug themselves into - you have to turn some people away. Especially when you're already working 12 hour days to meet some insane deadline - you just don't have time to deal with all the people who aren't carrying their own weight.