DEV Community

Cover image for What is the most frustrating part of software development?
Ben Halpern
Ben Halpern

Posted on

What is the most frustrating part of software development?

Latest comments (50)

Collapse
 
steveblue profile image
Stephen Belovarich

Interviewing at most companies.

Collapse
 
k_penguin_sato profile image
K-Sato

Imposter syndrome....😰😰

Collapse
 
Sloan, the sloth mascot
Comment deleted
Collapse
 
tuwang profile image
TuWang

fending my code - don't touch my garbage!

Collapse
 
atvfool profile image
atvfool

i feel it changes job to job. in the past its been management/ownership or customer who don't know what they want. more recently its been supporting a "high priority" application which involves essentially being on call for a period of time. my time is my time

Collapse
 
fnh profile image
Fabian Holzer

Avoidable waste of effort caused by people without skin in the game.

Collapse
 
fyodorio profile image
Fyodor

Business. It dictates everything. No matter how cool and ambitious your ideas are, if you cannot sell them properly, they’re useless. No matter how sure you are that doing “A” is wrong, if it’s requested by a major customer, just do it silently.

But no matter what, this industry is the best ❤️

Collapse
 
fyodorio profile image
Fyodor

It’s actually the most frustrating part of like everything

Collapse
 
aarone4 profile image
Aaron Reese

2 things.
Naming variables,
Scoping variables,
Off by one errors

Collapse
 
jankapunkt profile image
Jan Küster • Edited

Working with colleagues that don't like to share knowledge.

Edit: I don't do right know but I did work with that kind of colleagues and it was awful.

Collapse
 
liviufromendtest profile image
Liviu Lupei

Checking if the software works as expected, also known as Software Testing.

Since I'm a Solutions Architect at Endtest, I get to talk to a lot of customers and I hear their stories.

The typical situation I hear about is that the devs from a company started using all sorts of libraries and 3rd party components in the last years (React, Tailwind, Gatsby, etc).

And they didn't really follow the best practices when it comes to Software Testing (there a reason why the ISTQB certificate exists).

And at some point, they realize that they can't really predict what will break, and the only solution is to have functional automated tests (from the perspective of a real users, in real browsers).

And no one really wants to write code for tests, so using our platform is the easiest way for them to get cross-browser automated tests up and running in a few hours.

But if someone wants to build a career out of writing code for automated tests, they just go for Selenium or Playwright.

P.S. Even we had cross-browser issues, Safari is unpredictable, wrote a blog post about one of those issues:
What Happens when You Don't Test in Safari

Collapse
 
muthandir profile image
muthandir
Collapse
 
nombrekeff profile image
Keff

for me it's dealing with clients who don't know what they want! And of course time estimates...

Collapse
 
pp profile image
Paweł Ludwiczak

Collapse
 
codemouse92 profile image
Jason C. McDonald

The humans.