2024 Stack Overflow Survey Results
No space and time for creativity or “doing it right”, just do it fast, like yesterday also that feature we talked about three months ago? yeah, client also needs this added …
Or even better: this is what up to 20 years of technical debt does to people
Also we don’t make anything cool: just soulless corpo widgets for counting other widgets
Hey I’ll have you know I create tech debt all the time … Oh you said cool
This is gonna be my new answer to “What do you do?”
I’ve been on my project for 23 years. I haven’t written production code for ten of those years. There are still commits in the production branch with my name on them. Is both gratifying and mortifying.
I was talking with two other “old-timers” today about our inability to pay off tech debt because our teams are never given the time to do it
Thank you for writing this. You make me feel better about my lack of writing code.
never given the time to do it
It’s easier to ask for forgiveness than to get permission.
I see we work at the same company
You could say you’re in good company
Or the quantitative “x bugs per week” KPI…
It’s easier to fix bugs that you just introduced to be able to cover that KPI, too 🌚
Well, we’re getting laid off en masse, while our employers report record quarterly earnings. So there’s that.
Yeah absolutely.
I would go a step further and point to how a lot of companies these days supplement their workforce with low skill contractors from places like India who are like 13 hours ahead, do not have any actual investment/commitment to the project/company.
Why pay high prices for competent developers that can work alongside each other when you can have a just few competent ones and outsource the rest for those competent workers to corral, right? 🙄
Generally this results in more work for the full time devs. When you ask for senior developers and get a team of ”seniors” that write code like juniors…. That’s just more work for the full time devs. Ask me how I know.
Maybe I just need to stop working for Fortune 500s
TFW half my development time is stolen by helping this guy who I strongly suspect is just an interface for chat gpt.
deleted by creator
A part of it is horrible practices and a work culture which incentivizes them.
Who can be happy when the code doesn’t work half the time, deployments are manual and happen after work hours, and devs are forced to be “on-call”?
Introduce Test-Driven Development, Domain-Driven Design, Continuous Deployment with Feature Flags, Mutation Testing and actual agile practices (as described in the Agile Manifesto, not the pathetic attempt to rebrand waterfall we have in most companies) to the project and see how happiness rises, along with the project’s reliability and maintainability.
Oh, and throw in a 4 day work week, because no one can be mentally productive for that long.
IMO the biggest problem in the industry is that most developers have never seen a project actually following best practices and middle management is invested in making sure it never happens.
Oh, and throw in a 4 day work week, because no one can be mentally productive for that long.
Personally i’d go with a 5-day week of shorter hours, but if my company wants 4 days (they won’t) then i’m game. Bonus points for full remote.
IMO the biggest problem in the industry is that most developers have never seen a project actually following best practices and middle management is invested in making sure it never happens.
Managers, like most animals, strive for self-preservation.
I’m hoping for a 4-day 6-hour work week in my lifetime, but it seems the world isn’t ready for that quite yet, even though I’m 100% convinced productivity would not be impacted in any significant way, at least when it comes to software dev.
even if it impacts productivity, who gives a rat’s ass? companies are making obscene profit, they can damn well eat that lowered productivity. CEOs will have to live with the horrors of only affording 15 yachts.
Fair point!
I’m 100% convinced productivity would not be impacted in any significant way, at least when it comes to software dev.
I agree 100%.
Out of interest, do you think that this would be a natural occurrence in the industry if a company were to say “right, no more managers, you self-manage and build this ting, and if it doesn’t work we go bust”, would software engineers look to build the best possible thing to their knowledge?
It’s something I occasionally think about, because various companies like Valve and Fog Creek a decade or so ago did try similar stuff - and they had some great success with some absolute duds.
I think that would depend on the skill of the developers and the resources they are given.
A lot of us are only ever taught to be code monkeys and those would probably not naturally gravitate towards true agile practices (which most, I would argue, have never actually seen in a real project).
Another problem is a lack of access to domain experts, which is also crucial.
However, my current project doesn’t have any managers, or even business analysts, there’s only the developers and the Product Owner. We have access to some domain experts and we work with them to build the right thing.
It’s going great and the only problems we are facing are a lack of access to the right domain experts sometimes, as well as some mismanagement in the company around things we can’t do ourselves (like the company Sonarqube not working and us not being allowed to host our own due to budget constraints).
In conclusion, I think part of the problem is educating software developers - what true agile is and what the industry best practices are (some mentioned in my previous comment). Then you give them full access to domain experts. Then you let them self-organize. Basically, make sure you have great devs, then follow the 12 Principles of the Agile Manifesto to the letter and you’ve got a recipe for success.
Otherwise, results may vary a bit, as I think many would tend to continue doing the Fake Agile they were taught and continue producing the poor quality, untested code they were taught to produce.
You point to Valve as a success story, but the “pick the work you want” also lead to less deliverables and focus and they had to refocus that approach. Free pick and experimentation is fine until you get to a point where you want to get something out the door - when it’s a bigger thing, and you need more and focused people, to bring it to the finish line.
I can’t speak how it would be elsewhere and everywhere, but I can speak from personal experience how my workplace is set up.
We’re relatively small, work for various customers, some continuous and some contract-scoped. Developers work and speak either directly to and with customers, or have at most one person “in between” that is part of usually our team.
We have an agile and collaborative mindset, and often guide our customers into productive workflows.
Being on relatively small teams, with opportunity for high personal impact, and with agency, I was able to take initiative and work in a way I am very satisfied with. I am able to prioritize myself, collaborate with my customer to understand their needs, understandings, and priorities, and then make my decisions - explicitly or implicitly. Two-week plannings give good checkpoints to review and reassess intended priorities - which are only guides. Stuff comes up that takes priority anyway, be it from the customer, or improving code when you stumble upon it.
I’m glad to be on my current team where the customer pays monthly for how much we worked, so no repeated contract work estimation. I can and do decide on what makes sense, and we communicate on priorities, planning, and consequences. Either I decide or we discuss whether one or another solution makes more sense considering effort, significance, and degree of solution or acceptableness. One person from the customer is our direct gate to them, participates in meetings, planning, tickets, prioritization. They block all of their requests to us, and communicate to and with us on what they deem important enough. And they are our gateway to asking the customers roles and people regarding usage, functionality, needs, etc.
For me, this environment is perfect. It allows me to collaborate with the customers to match their long term needs.
I think it needs good enough developers though. There’s those that are mindful and actively invested, but also people who are not. Some become great productive workers with guidance and experience, but it doesn’t always fit. I feel like a lack of proactive good development given the environment and agency isn’t a given, but I don’t think “management” improves that. You’re putting a manager on top in hopes they’re a person like that. But why couldn’t that be a team member in the first place?
Managers and more strict role splitting becomes more necessary or efficient the bigger you scale. I feel like smaller projects and teams are more efficient and satisfactory. You have less people and communication interfaces. And as a developer, you probably know that interfaces [between systems] are one of the biggest issue causers.
For context, I am Lead Developer (became when we introduced those roles explicitly), and our team size was 2 for a long time, but has now been 4 for a while, and is now 3 developers +1 now in semi-retirement working only half of the year.
It would probably start to look a lot like Lisp programming, as in how Crash Bandicoot was made.
He’s just stating the obvious.
Our jobs have no meaning. I didn’t become a software engineer to work on some bloated piece of crap software implementing shoddy code just to make a company manager happy do the CEO can make more money.
I wanted to work in open source and democratize software for the masses.
Hey man wanna start a coop?
… as in fuck off into the woods and farm chickens?
Shit… I meant a co-op. But also free range chicken farm… Train them to attack on command.
Knowing chickens, it’s more like training them not to attack except on command.
Also works tbh
$ chicken -attacki see potential there…
So, do I ssh into the chicken or…
Neuralink? Sure why not!!
A software dev co-op would be sick 👀
Yes
It is truly impossible to be motivated in a fortune 500 commercial insurance company. My tech lead gets absolutely heated about issues and I end up in meetings wondering how anyone can feel any emotion at all about middleware APIs in a gigantic corporation
I’ve actually taken up to doodling in my notebook. I’ve learned to describe what I’m imagining using words instead of drawing actual pictures so at a glance it passes inspection.
Sometimes you just need to get yourself into it to survive
I first worked in construction, then I worked in electrical engineering, now I do software, and there’s things about software that I find inherently dissatisfying. There’s little physical movement or location variety, your code is published quickly but often deleted quickly, there’s little interaction with coworkers outside of your very specific domain, and the entire field of software has more money than they actually deserve to have based on how hard they work or actual value your code provides to society. Some companies produce very necessary products that do very necessary things for all of society to function, most of the software jobs are instead working on bullshit marketing apps that waste people’s time or just enrich some financial services company or other societal middle man that doesn’t actually need to be any better or richer.
The main upsides are the immediate return (some buildings take like a decade to build, most code is published that month), the remote work / hours flexibility, and the aforementioned undeserved pay and benefits.
I’ve written it countless times before, but software engineering desperately needs to do some engineering.
What you’re describing is absolutely true, but compare the way you’re working with an actual engineer. No sane engineer would start investigating the production process of a steel beam just to build a regular old warehouse. The steel beam has certain characteristics and unless you have very good reasons, you don’t need to question that.
We are software developers however need to know a lot of our steel beams and can’t rely on many of them. That means even simple stuff takes forever and we tie ourselves to it way more than we should.
Again, I used to work doing actual electrical engineering, working at an architecture firm designing bridges and buildings, and what you’re describing as “actual engineering” is the whole reason I went into software.
Because if the actual engineering you’re doing is just combining a lot of well defined parts to fit certain acceptance criteria, then you don’t really need a person doing that, software can do it.
But that’s exactly what’s holding us back.
Let’s divide the problem sphere very broadly into business and technical. The business problem is “I want to store an order” the technical problem is “We need to connect to a database and map our data onto the table structure”.
What we should be doing is solving the technical problem once, and then map thousands of business problems onto that. But instead, the same technical problems are solved again and again, even though there is a technical solution, because that solution is too leaky for us to rely on.
I don’t want to write the 200th iteration of basically the simple problem again and again. I want to solve the actually hard problems. Yes, software can do the simple stuff, that’s what’s the entire point of our profession. Every developer should try to make themself obsolete.
I don’t want to sound harsh, but your sentiment reminds me a lot of the “back when men were men and wrote their own mouse drivers” comments from ye olde time. But that’s not what our job is about.
Quite frankly I don’t really know what you’re complaining about. You’re literally describing how we reuse standard database technologies like SQL, or standard patterns like REST, or standard application and data access frameworks, which we do literally all the time.
Quite frankly, I think you don’t understand what I mean.
Don’t kid yourself, “patterns” are boiler-plates so common they have a name. Yes, SQL makes things much faster, but that’s just the beginning. As soon as you venture out of the almost trivial cases, things get ugly fast. Think about something as simple as a form. That’s a standard problem. But I can’t just write down a “form-spec” and have a frontend and backend for that. No, I need a bunch of libraries that don’t quite work together and need a lot of persuasion to work together.
Or think of Rest-APIs. How many times could you really just ingest a spec and have everything working as expected? That’s very rare. Some libraries are plain weird, some don’t support certain aspects of what you want, etc. etc. etc.
A simple CRUD app should not require a single line of code. Yet, 80% of us are essentially doing exactly that.
Think about something as simple as a form. That’s a standard problem. But I can’t just write down a “form-spec” and have a frontend and backend for that. No, I need a bunch of libraries that don’t quite work together and need a lot of persuasion to work together.
Honestly, what are you talking about.
You can just spin up a Next.js project complete with API calls and ready to go forms. Pick a full stack framework and go with it, there are several.
The larger reason that there is separation between front and back end though is that there is intentional decoupling between them because the backend might also be responding to requests from native applications, or other servers.
Hell, what you’re describing with Gui based application builders also exist everywhere. That’s basically airtable or salesforce or flutterflow, and guess what, those applications all kind of suck because a form is not as standard as you think. In a good application, there will always be customized design, flow and logic that happens to capture user input on the frontend, and on the backend there are a myriad of reasons to optimize different databases for different things. Look at the limitations you run into with Salesforce and Airtable databases because every database needs to have a whole plethora of features just to support the frontend Gui interface to manipulate them.
You’re not crazy or harsh. This is a very real problem. I have been stuck doing business development at every company I’ve worked for. There’s always some shitty load-bearing Django app whose schema determines what the business is capable of doing, and somebody’s gotta maintain it. It’s gotten to the point where I assume that any interesting things I do will be outside of work and not for pay.
This is still a business problem. The truth is, we solved basically all the technical problems that could be practically solved by the 2010s. We have all the technology, we know what people want and need. We could, and should, build a lifetime personal computer (phone form factor) for every person on Earth that provides for their communication needs, acts as a personal assistant and organizer, and more. And we’ve had those, dozens if times.
But how do you keep selling people stuff once you’ve met all their needs? You tear it all down and keep rebuilding and reselling it. You enshittify to squeeze money out, customers flee, so you encircle them with another capitalist enclosure and rebuild the same shit again. Repeat.
Software devs should basically all be making games and trying to teach AI to be smarter but instead we’re replacing internet search (a problem we solved in the 90s!) with LLM enabled advertising engines that literally can’t find info for you so they make it up. And we’re iterating on the 10 thousandth version of an e-commerce site because all internet shopping is part of a giant global MLM now. Seriously, “drop shipping” is the latest iteration of the same old scam they used to run on diet pills and knives and magazine subscriptions.
But every college student with a fresh business degree can set up a Wix site to resell sunset lamps. It’s uber for scams. The reseller takes on all the risk, sets up the e-commerce site with a builder, firehoses ads all over their social media, and does all the work. There are multiple industries now entirely supported on conning desperate people into being your salesforce, workforce, advertisers, and customers all at the same time.
Not even just bullshit marketing, rather on making someone rich a smidge richer. For weeks and weeks of figuring out how to solve a problem that the client could solve by just not insisting they can export every single view to excel and re-import from excel “because that’s what I’m used to”.
There’s little physical movement or location variety
That’s the main reason I switched from computer science to electrical engineering with a focus on embedded software. Programming microcontrollers to achieve something tangible is a lot more satisfying for me than writing some application that only runs on my pc to shuffle some bits around
I’m glad I work on software that has value, where I control the entire ecosystem, and where my contributions are significant.
Yeah, it was a great feeling when I had it for the first year and a bit of my career working on architecture software. I had it again recently when working on back end auth systems for a major automotive company but then we lost the contract and I had to rotate off. Now I work building software that is necessary, but the parts that are prioritized for development aren’t the parts that make the average workers’ life easier (which would increase overall efficiency when measured on a time basis) but the parts that enrich management because that’s easier to sell.
They make billions, we make thousands
I noticed that, as well.
Yeah sure, but that’s true of every job. Would you rather be a waiter or a cashier or a cleaner or a teacher or a nurse or…?
The level of entitlement here is insane.
Because they keep putting Javascript in things.
It would be interesting to see if there is difference between countries with proper labor laws and countries like USA
How does this compare to average human happiness? Aren’t humans famously dissatisfied?
My dissatisfaction is legendary.
Yeah, the previous iteration of the matrix wouldn’t cut it.
We’re all always dissatisfied with something
fr the system is in such a deep terminal crisis that talking to people in their 20s feels like talking to pensioners since in countries like the US or UK the life expectancy is declining due to not being able to afford healthy food, stressful and precarious work, mental health crisis and addictions, worsening healthcare, climate change, moldy cramped housing, proliferation of larger and thus more dangerous cars, new zoonoses etc. etc.
Private equity ownership sucks balls… publicly traded companies are only marginally better.
Government work doesn’t pay as well but I can literally say the stuff I make makes my local area a bit better. It’s a new feeling. I used to work in healthcare. It kills your soul.
Does it have anything to do with the fact that most useful code that will be written has been written and most of the hard problems are now security related?
In addition, they’ve been telling people to learn to code long enough the upper hand devs used to have for salary negotiation is largely gone.
Am I the only one who read the title as “Youtube is the reason 80% programmers are not happy”?
I mean… Not YouTube specifically but YouTube is representative of why us programmers are unhappy. The era of feeling like the tech industry and the internet are making the world better is over. All of them media platforms exist to co-opt our social interactions and replace them with ads for microwavable meals. They’re spying on us, and for what? They control major elements of how we live out lives, and WHAT THE FUCK DO THEY EVEN GAIN? A lot of them are going bankrupt because it wasn’t profitable. Their ads are less effective than the oldest forms of advertising. Ultimately, these platforms were about control, not about… Any other stated goal. And us programmer? We got tricked into thinking we were developing platforms to connect people and create a global culture of interconnectedness. Turns out we were building the infrastructure to implement genocide
Replace Youtube with Meetings, and it’s spot on!
No surprise there. What are we even doing? I haven’t written something important at work since the beginning of my career. It is/was a learning experience for sure - I’m not dumber for it, but nothing I wrote had to be written. The world could’ve done without any product I helped develop.
GNU Guix seems quite important to me.
I’m so tired…
I’ll watch it
