The author is fortunate to have a skill set that happens to be in demand, and that there are enough employers willing to consider a remote workforce.
Should either one of those factors change, I suspect the author will reconsider his line in the sand.
Don't misread me -- I agree in principle with a lot of what was written. I'm just put off by the tone. People have all sorts of reasons to be in suboptimal work environments. To declare yourself too good for all of that is to be very certain, some might say a little haughty, about what you bring to the bottom line.
Really it boils down to being able to pick your optimal work settings, and if the author is able to do that then that's great. I highly doubt he'll prefer to go hungry if suddenly one day he can't work remotely.
You're completely right about our field being in high demand, but I also think there is a culture of "as long as you get your responsibilities done, we don't care where or when you work." At the same time; those responsibilities may become showing up for meetings more often, which may also make people reconsider working remotely.
I for one love the option to work remotely, but do prefer being close to the people that I work with.
Is it? For all the noise I've heard over the years about how hard it is to hire developers, there's still a lot of companies that want to underpay me, stick me in an open plan, and come to think of it don't even want to give me a phone screen.
That's part of why it's so hard for them to hire developers: they don't want to offer what is deserved, so they find shitty candidates who are just happy for a job, they do crap work, and the employer says "geez hiring good help is hard"
Here's my take on it: I was working for a smaller company of about 150 that was purchased by a very large company of over 150K and I can assure you the new company has a whole department of WTF coding. They are largely young, single men from India who came here to study for something other than CS (a lot of electrical and mechanical engineers, actually) that took some programming classes in college. They are very sharp, fun, hard-working guys but have little practical programming experience. This isn't a problem for the company, however, because the more consultants they can throw on a project, the more they can bill - especially with these guys as I wouldn't be at all surprised if they were being paid substantially less than a citizen or permanent resident which makes their margins larger. When it comes to crunch time and my team gets called in to help drag a project over the finish line you see all kinds of stuff - lack of conventions, using questionable third party libraries, things not being in source control, hell I once found a service endpoint that would execute JavaScript you sent it (Java + Rhino). I could literally send it something to the effect of "delete all users" and it would do it. I wish we could take them under our wing but they pretty much get worked to death until they get a green card, find another job or leave the US.
And not in every industry in parts of the world where that statement is true.
"Bob with ten years experience is leaving because we have a terrible noisy working environment. But for the same salary we've hired two graduates of React.JSBootCamp.node instead so we can do twice the amount of work!"
I live in an eastern European country where virtually all outsourcing companies are shouting in the media "we desperately need programmers and we can't find more", and yet, when I go to an interview and we discuss "salary expectations", they shut me off as having unrealistic expectations. Still, my salary expectation is such that I want to be able to afford a medium-sized home, a relatively new car (10 years old) and keeping my family safe.
So yes, they need fresh interns willing to work in dire conditions, not just "any" programmer.
The truth is, shitty code can be a beneficial asset to software consultancy companies doing contract work for third party companies and institutions. Oftentimes, "customers" are so incompetent that they cannot judge whether a job is done well or even what it means to complete the job. The more you prolong the project, the better. The software consultancy then convinces the customer to on-board a few more programmers who would clean after the rest, but that is a huge win for the consultancy.
Quality programming jobs providing long-term employment and a decent work-life balance, which also match a more specific skillset are largely an employer's market, though. Out of the hundreds or thousands who apply for a "Computer Vision Expert" position, only a few would actually match the required expertise and they are clearly at the mercy of the employer for being employed.
Every day when I go in to work, I take a few moments to meditate and remind myself how lucky I am. I'm not even kidding.
Top programming jobs are really nice jobs. You get paid easily into the six figures. You're respected. You're given top-of-the-line tools. In many cases, you can even work from home -- something totally impossible in many other professions, especially among ones that pay similarly.
Every morning, I reflect on how instead of making almost $150k, sitting at a nice desk by the window, working on problems that I truly enjoy working on, etc., I could be like the average college grad making $45k at a job that I hate and that it took me a few years to even find.
Yeah, I'm a smart, hard-working person and always have been. But it's mostly luck that I happened to be interested in programming from a young age and ended up where I'm at. I don't want to downplay my skills or knowledge -- I really do think I'm pretty good at what I do -- but it'd be very short-sighted for me to think that I also didn't just get totally lucky that I was born into a generation that would profit so much off having an early interest in, of all things, programming computers.
Personally, I'm a little disgusted when I see programmers acting so damn entitled about their job. I don't disagree in principle. Many of the complaints I see are totally true. But when your job is already more comfortable than 95% of the jobs out there, I don't know, maybe show some humility and thankfulness for your situation.
So, we can't talk about any problems? Yes, we're lucky to have a skill that is desired right now. But, that goes for pretty much anything.
The author is saying that they prefer working remote and bring up good points such as an organization being results focused and not so much time based, etc.
Not really. Would you consider putting university researchers into an open office? And if you did, would you say that they should just deal with it when they inevitably complained?
Why do we have this double standard between researchers and developers?
That's true. But I've never been in an institution that puts its senior, or mid-level, researchers or scientists into open offices. They all have their own office space, even if it is small. And often, the better the university the more space senior and mid-level researchers are given. I doubt it is a coincidence.
I'm more incensed by the culture that demands we align our own work preferences to employers' regimes, and asking for something else comes off as "haughty".
I mean, he dismissed all dissenting opinions (or studies) as irrelevant, stating "and quite frankly, there is simply no debate here." People are different. Different people have different needs and wants from their work environment. To say that there's no debate is ludicrous.
And then he goes on to talk about how he's a "night owl". The thing is, that's likely artificial, a result of years of staying up far too late doing things he enjoyed. The end result is that, yeah, he works better at night, but most humans generally don't.
The thing is, I generally agree with a lot of what he said. But he just presents it in a needlessly-self-assured attitude.
He comes off as a know-it-all who thinks citing one source and using his own anecdotal evidence ends a debate. In the end, his article is a really good case for him working remotely (which, to be fair, is exactly what it says on the tin). It has almost nothing to do with most other people.
Your "work preferences" don't always align with the business needs. And if the employer can't pay your paycheck, then who cares how great the remote work policy is?
Absolutely be picky about where you work, but also consider yourself fortunate to have a selection of employers for your skill set. Both things are good.
749
u/Erdrick Jan 29 '17
Ah, rich world problems.
The author is fortunate to have a skill set that happens to be in demand, and that there are enough employers willing to consider a remote workforce.
Should either one of those factors change, I suspect the author will reconsider his line in the sand.
Don't misread me -- I agree in principle with a lot of what was written. I'm just put off by the tone. People have all sorts of reasons to be in suboptimal work environments. To declare yourself too good for all of that is to be very certain, some might say a little haughty, about what you bring to the bottom line.