15 ms·
On the Unhappiness of Software Developers (2017)
- belter 4y agohttps://news.ycombinator.com/item?id=14459004 https://news.ycombinator.com/item?id=14459004 - 5 years ago - 140 comments
- ipnon 4y agoRemote work alleviated all my software development unhappiness, because suddenly I was free to develop software.
- deepzn 4y agoA lot of office/corporate routines and rote weight is taken off the shoulders with remote work. For young people, it might be a challenge to engage in social activities, but if they take the initiative, for e.g. travel around and work, they can find plenty of social events, activities to meet and engage with people or just enjoy themselves.
- A4ET8a8uTh0 4y agoThere is that, but, and I am saying this as an ardent remote supporter, in person appears to have an edge over remote in terms of training ( there are definitely things I would not put in official training materials or even in recorded zoom/teams/we call ). I recently joined a new team and even with previous experience of how things actually work, it was an adjustment how this new ( to me ) corporate structure really operates. It is the little things that can surprise a complete newbie. In person advice can be invaluable.
- regularfry 4y agoDiscovery of other teams is also somewhere in-person has the edge. Once you've had the contact and made the connection it's less critical, but you can't (yet) beat physical serendipity for getting to know useful other parts of the organisation.
- comfypotato 4y agoI think this comes down to the newbie taking initiative to seek help. In person, it’s easier for others to help a newbie that doesn’t know when to seek help (they can “see” them struggling). As long as the struggling new person seeks help, remote work is superior for the actual help to be administered. Screen sharing, meeting time synchronization, etc. all make it easier to help someone remotely.
- ThePadawan 4y agoOn a smaller scale, my work life also improved significantly by going from "a 60 minute meeting where no decisions are made because everyone just shouts at each other so you leave with a headache" to "a 60 minute meeting where no decisions are made because everyone just shouts at each other but you can turn down the volume on Zoom" It sounds really stupid, but that literally helped make a giant difference.
- tifik 4y agoTo me the main difference is that you can still focus on work while showing up. I wouldn't be able to just bring my laptop to an in-person meeting, zone out and clank away on your keyboard. This largely removes the main issue I had with most meetings - that I have to stop doing useful work.
- pronlover723 4y agoRemote work aggravated my unhappiness since it means I have very little social interactions. This last week was the funnest in a long time. A colleague who works at an office 7000 miles away flew in the for the week so everyone on team locally came into the office this week. First time in over 2 years I've seen everyone there. It was really fun.
- shetill 4y agoRemote made me very isolated, and especially in a team where we are 3 people and everyone else is 15 years older than me with kids and I have nothing in common with them. I could go do random meetups outside work but that's usually weekends as I live further away from bigger city, so that means that at least 5 days of the week I stay home barely talking to anyone.
- agumonkey 4y agoI just tried remote and it's a strange blend. No commute makes the morning a lot lighter. I can operate as I want without having to tag along others (lots of pauses or chit chat usually..) but it also makes me more stressed (I plan to do 20min walks outside to replenish). I don't get along with most my colleagues either but my main one is cool enough.
- pojzon 4y agoKeep in mind remote work is not for everyone. If you need other ppl company to fill the emotional emptiness - dont work remotely. Its more for the ppl who work task based or hourly based consulting and are free to do something else after.
- ItsMonkk 4y agoI think this is just a temporary phase until society figures out how to adjust to the new environment. Nothing about remote work enforces isolation. You can work from a coffee shop, you can work from the beach, you can work from a library, you can work from your friend's house, and yes, you can work from home. If home isn't fitting for you, try anywhere else on Earth. There are probably new environments that are possible that have not yet been created. Let's explore those. It's very likely that the office isn't the single best place on Earth.
- photochemsyn 4y agoThis looks like one of those BS ridiculous-syntax fraud-publications submitted to academic journals with the deliberate intention of showing them (the journal and its editors, and perhaps the whole scientific establishment) to be a pack of creduolous wankers, basically. Kind of obvious here: > "The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners..." 'Recent research in software engineering...' now, what does software engineering research have to do with emotional psychology, again?
- tgv 4y ago> what does software engineering research have to do with emotional psychology, again? Psychology of labor is a thing, and has been for ages. The idea behind it is simple: it's people with a mind that do the labor, so their psychological state has influence on the work done. Is it software engineering? No, but the article purports to identify factors that influence the psychological state during software development. That said, I do believe such studies to be of minimal value. Voluntary surveys are absolute bottom of the barrel. Identifying 219 factors from such a study seems like analysis gone mad. The extensive discussion of the non-normality of the central happiness statistic seems a point in case: it's trivially visible, it's not interesting, and doesn't play a role in any further analysis or conclusion. They do remark that the mean value they find is higher than in other studies, but can't explain it. Not that they need to, because nothing would change in the paper if the value had been lower. Basically, this looks like an experiment from a starting PhD, who needs to push out one paper per year. Sadly, it isn't. The authors are senior researchers, who seem to have little idea of psychology.
- PedroBatista 4y agoWhile I’m sure the scientific establishment is full of “credulous wankers” as opposed to our industry where everyone is tip-top-magoo, wouldn’t you agree there are more factors for you to accept or quit a job other than money? And those factors are mostly between your ears?
- hayst4ck 4y agoFrom the paper: Freq Cause 186 Being stuck in problem solving 152 Time pressure 107 Bad code quality and coding practice 71 Under-performing colleague 63 Feel inadequate with work 60 Mundane or repetitive task 57 Unexplained broken code 42 Bad decision making 40 Imposed limitation on development 39 Personal issues
- ge96 4y agoI'm doing the mundane stuff now, for a couple months actually. Stand up repo, pipeline, sem versioning, tests.. haven't actually written code yet/built something. Just copying configs/duplicating stuff.
- hayst4ck 4y agoI personally don't think happiness is very different from motivation. Happiness is the state of being motivated. Unhappiness is the state of having no motivation. The 3 key ingredients to motivation are: autonomy, mastery, and purpose. Nearly every time I've been unhappy writing software it has been because of a deprivation of autonomy, mastery, or purpose. I've been ordered (deprivation of autonomy) to work on things I didn't think mattered (deprivation of purpose) with a language I wasn't familiar with in a context I wasn't familiar with, in a way I thought was wrong (deprivation of mastery and autonomy) for political rather than technical reasons (deprivation of purpose). I have never been unhappier and less motivated than that.
- lawgimenez 4y agoAutonomy for sure is my main source of development happiness. It means that my employer trusts me that I don’t burn their business to the ground
- nine_k 4y agoI think there is a stark difference between motivation and happiness. There exists negative motivation. If you have $50k in credit card debt, you are very motivated to pay off that debt, but you are neither happy to have the debt nor happy to pay. You just plan to be more happy when it's over. This kind of motivation can also be present on the workplace, along with positive motivation (when you are happy about something and want more of it).
- wwarner 4y agoAlmost had an outburst when I read this. I don’t want to live in a bubble of happiness, I want to work hard, learn a lot and make the team/company wildly successful. To me that’s fun.
- onion2k 4y agoSo you don't want to live in a bubble of happiness, you just want to do exactly what you find fun?
- wwarner 4y agoI guess I did say that… Would delete it, but can’t so I’ll clarify instead. I just think that “happiness” is sort of a banal goal in life and at work. However, the study’s definition of happiness included meaningful work, and I have to admit my comment was reacting to something that was not said.
- peterkelly 4y agoSomewhere out there, a project manager is going through this paper and adding JIRA tickets for each of the highlighted problems.
- BlargMcLarg 4y agoThen they'll be discussed in a retrospective, into an endless discussion causing the meeting to drag on, only to be concluded that taking on the issue takes too much time in the face of endless feature requests and bug reports. Half a year later, it will be discussed again. The odds of the issue being picked up are higher, but still not high enough. The same song and dance is performed, only for the issue to be put all the way down on the backlog, the place where issues go to sleep forever.
- nly 4y agoDevOps. I didn't become a software engineer to write yaml or negotiate K8s resource allocation.
- shetill 4y agoat least your interview LC questions are easy
- ehnto 4y agoYes, it's also the part of the process that has the most "Arbitrary bullshit" in it. You can't logic your way through it, you have to know the Special Arcane Knowledge in order to configure it all correctly. I also argue that we're probably fucking it up a lot, causing it to be more painful than it needs to be, but that's because we consistently get our developers to do infrastructure work. A corollary to this, locally running the code AND integrations is essential. If you don't have the ability to replicate the full system locally, your devs are hamstrung and will take much longer to solve what could be very easy problems if only they could have debugged it locally and quickly. This is related because if your infrastructure is shooting for the moon in complexity, your devs have little hope of replicating it locally.
- highwaylights 4y agoSo much this. The perversion of it is that it comes across that I’m against DevOps. I’m absolutely the opposite. I’m against attaching bullshit marketing labels to good practices and making them a cancer on the project (cough devops, agile cough). I’ve dealt with this recently. The “DevOps guy” was a toxic, condescending gatekeeper who wouldn’t co-operate with the engineers at all, but had the ear of the management. He had a bunch of servers and builds he was really pleased with that were not at all documented and completely useless to everyone, because no-one understood it and couldn’t ask questions. Good ops should be utterly transparent and utterly out of the way. Not hidden magic, just so easy to understand that it ticks over doing what it does without interrupting your workflow. And always reproducible locally. Give a prick even the slightest chance to poison your company and they will is about the only 100% reliable piece of advice I could give anyone in this industry.
- jakobnissen 4y agoIt's absolutely hilarious that the underlying assumption is that the purpose of living a happy life is to increase work productivity. Absurd.
- comfypotato 4y agoI didn’t get this interpretation at all? Why do you say this? I much more understood the “happiness” to be constrained to how you feel about work. There’s no mention of happiness outside of work.
- mgrund 4y agoI’m surprised that reward misalignment is not making the list. Seems to me like in many places, career success is mostly driven by metrics that are not related to good software engineering practices (specifically showmanship). Normally I would expect success to be measured primarily on metrics closer to the actual professional skillset. Not arguing for or against, just surprised not to see it in the list.
- regularfry 4y agoThere are very few metrics you can usefully apply on the individual level which don't turn into hideously misaligned incentives when you tie them to career outcomes. It's different at the team level, but nobody's really cracked it for individuals yet that I'm aware of.
- revskill 4y ago80% of developers are unhappy, they include: - Junior developers who can't get their code pass code review process - Senior developers who don't know what's going wrong in a microservice products. Rabbit holes are everywhere where you don't know where, who, how to fix the bug in a strange service. - PM who can't write clear JIRA tickets
- black_13 4y ago
- blooalien 4y ago"stuck in problem solving"? Hell, that's like half the reason I chose a career in computer related stuff. That's like a huge part of the "fun" of it.
- synu 4y agoThere was a big switch at one point to people doing the career for money, which is totally understandable. They may have never played with or fixed computers for the fun of it.
- dilyevsky 4y agoI think the key word here is “stuck” as in “unable to make headway”
- locallost 4y agoThat's true, but there are various jobs. Problem solving can be fun, but it can also be trying to fit something that's easy on paper into a badly designed or incomplete system, for the nth time.
- delusional 4y agoTo me "stuck in problem solving" doesn't mean what it sounds like. Stuck in problem solving means putting out fires. You're constantly in a losing fight against the decay of the current system and therefore you never get to actually solve any of its problems. You're stuck in the solving phase, and never get to the execution phase where you get to interrogate product market fit and the needs of your users. You're forever "solving" the same problem but the solution is never implemented and in 6 months you'll be asked to solve it again.
- synu 4y agoThey quoted some people who described what they meant: > “I feel negative when I get really stuck on something and cannot get around it”. Another respondent elaborated: “I also thought of situations where I’m debugging some issue with the code and I can’t figure out why it isn’t working – when it seems like everything should work, but it just doesn’t. This is definitely one of the biggest gumption traps I encounter”.
- mkl95 4y agoAll of these issues are mismanagement symptoms in my experience. Complicated tasks that are described with one line in broken English. Cryptic bug reports. The list goes on and on.
- cantfindfreeone 4y agoB-b-b-ut if we limit developer burnout, who is going to work weekends to deliver on everything we overpromised to the customers? :(
- fxtentacle 4y ago"The happy-productive worker thesis states that happy workers are more productive" Yes, but that's not because I am happy all the time while working. It's because I have a purpose in life and a family that keeps me happy. Trying to optimize work to be a place to increase happiness sounds equally promising as breeding dogs whose shit smells like flowers. "Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers" I fully agree there, too. I've fired highly profitable clients in the past, simply because their behavior (mostly too emotional, too chaotic, bad management, no time planning skills) was making our entire team unhappy. Quote from the paper: "I also thought of situations where I’m debugging some issue with the code and I can’t figure out why it isn’t working – when it seems like everything should work, but it just doesn’t. This is definitely one of the biggest gumption traps I encounter" I totally don't get that one. For me, the path towards finally figuring out a challenging problem is the single most exciting thing in my job. This is precisely WHY I became a software developer. I'm truly surprised to hear that, apparently, many of my peers despise this aspect of the job.
- matkoniecz 4y ago2017 psychology research? Given replication crisis it is utterly worthless without confirmed replications. Has anyone tried to replicate that results, with preregistration of study? What was the outcome?
- loydb 4y agoOf the 219 factors causing unhappiness, I'm guessing 218 of them are 'constantly changing requirements' :) The last one is 'nobody refilled the coffee machine.' edit: speeling
- amelius 4y agoSo at what place are software developers on the professions scale of happiness?
- noisy_boy 4y ago> 186 Being stuck in problem solving > 152 Time pressure I can deal with the 1st as long as the 2nd doesn't become 1st.
- ricardobayes 4y agoNeeding to buy a certain make of a computer because they have a proprietary browser which doesn't run on any other machine.
- amelius 4y agoI think software development can be a great escape from life issues. And there lies its problem.
- bob1029 4y agoThe #1 source of unhappiness for me today is lack of clear and direct communication. We are a fully remote team, so this is quite a problem. I am honestly not sure how to improve matters at this point. I tried to lead by example to little avail. E.g. "look at how I documented that kind of issue here as a guideline moving forward". We tried issue templates that are effectively a checklist of required information, but not every problem fits into a round hole. Many (most?) are actually quite odd-shaped once you apply nuance and context. There are also those really annoying interactions in Teams where someone will type out "you have a minute?" instead of just describing what they need someone's attention for up front. At some levels, I wonder if I might have the wrong team for this kind of job. How does HN deal with team members who have trouble slowing down and communicating their thoughts well?
- dangerface 4y ago> How does HN deal with team members who have trouble slowing down and communicating their thoughts well? At my work we have these "catch up" meetings where theres no agenda, time limits or minutes for our meetings. Every one in the team puts down tools and we take turns ranting about what ever is on our mind at that point, after 2-3 hours the meeting is over and we all go back to work with less time or understanding.
- Test0129 4y agoBeing stuck is part of the job. Most of my unhappiness stems from a few things: 1. Time pressure. I can't develop code that works right. I am not talking about perfect performant portfolio work but as a backend developer many times I can't even hit the minimum standard of code quality because everything always needs to be done yesterday. Then I am responsible for it, and all the problems caused by deadlines are my problem, and every manager forgets they assigned me the deadline. 2. Pagerduty. Absolute worst thing to ever be perpetrated on development teams. It allows the C-levels to run "lean" teams because 4-8 developers rotate minimum 12/5 shifts, usually 24/5. 30 years ago this might have been necessary. We have been able to stagger timezones for the last decade now easily. 3. The work. It took me 10 years to land (by chance) a company with work that is interesting to me. My bar for interesting is so low at this point that on a scale of boring to life changing something that even remotely has me write other than boilerplate scores pretty high. Even now, I am responsible not only for the software but also for the devops (this is not a small company) which inevitably gets blocked to death by SREs, code review on another 2 repos for deployment, my own QA, etc. I do, effectively, the work of 4 different positions. I am paid for being a developer. Either raise my salary 40% or I will start dropping tasks. Remote work has been an absolute boon to me. I am unsure how anyone could take a negative stance on it. Sure I don't talk to people often but I don't honestly care. Work has always been work to me. Coworkers are not your friends and honestly they probably shouldn't be. Find meaning in your life elsewhere. With remote work I can actually do my job (program) instead of being in meeting after meeting where a PM waxes poetic on whatever is important to them in order to justify their meager existence at the company. I no longer have to listen to the CEO go on for hours about how good the company is, or feel like I have to join in for beers instead of going to do what I actually want, etc. Fuck everything about the office. I am fully convinced this is not an "extrovert" vs. "introvert" battle, but rather a battle of people who have actually woken up the realities of being a serf vs. the people who remain asleep suffering from stockholm syndrome.