DEV Community

Cover image for What irritates you the most as a developer? πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»
Nilohit Singh Kanwar for XenoX

Posted on

What irritates you the most as a developer? πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

The week has just begun. A dozen more deadlines have probably been tossed at you already. So, let's detox a little today.

What's the one thing that really bugs the developer in you?

Vent out in the comments below. πŸ’†β€β™€οΈπŸ’†β€β™‚οΈ

Top comments (76)

Collapse
 
rachelagnihotri profile image
Rachel

This sums it up accurately for most developers I guess:

image

Collapse
 
itsasine profile image
ItsASine (Kayla)

I think this sums up why I don't mind being a QA :P

Collapse
 
adam_cyclones profile image
Adam Crockett πŸŒ€

This sums up why I'm frightened of QAs πŸ˜…

Collapse
 
perpetual_education profile image
perpetual . education

This situation can mostly be solved by changing the design process. But - they'll always be things that don't work... and that's a mind-shift. TDD can help / and early prototypes of feature too. But - yeah... so many things to take into account!

Collapse
 
patarapolw profile image
Pacharapol Withayasakpunt • Edited

What's the difference between a feature and a bug?

Isn't butterfly a bug?

Collapse
 
a92gerasimov profile image
Andrei Gerasimov

You want the feature to be noticed.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao

Unnecessary meetings for the sake of meeting.

Collapse
 
stereoplegic profile image
Mike Bybee • Edited

Just posted this on LinkedIn...

In response to the "intimacy" argument for Zoom:

I'm failing to [frozen video] how [glitchy stutter] [movement] [frozen again, with Aphex Twin sound stretch effect] [blank screen] intimacy.

Collapse
 
aneeqakhan profile image
Aneeqa Khan

we are team of 6 developers, I face this issue alot :(

Collapse
 
calag4n profile image
calag4n

Human beings

Collapse
 
jouo profile image
Jashua

I'm aware that it's part of the hustle... but my answer would be, having to make changes to something they swore was completely finished last week :'D

Collapse
 
chuksokwuenu profile image
Chuks Okwuenu

yh. i totally agree with you.. most annoying thing ever

Collapse
 
zilti_500 profile image
Daniel Ziltener

Especially when you literally talked with them about that exact scenario, and let them confirm twice that that won't ever be needed.

Collapse
 
nilohit_kanwar profile image
Nilohit Singh Kanwar

This hurts.

Collapse
 
flavienlefebvre profile image
Flavien Lefebvre

I'll get a lot of hate for that but there are two things that irritates me the most :

  • Not using the right tools for a use case, like using JavaScript to create desktop apps
  • Sacrificing app quality for money, like calling a web view an app or using bad cross platform tooling instead of the native frameworks. The UI/UX quality gets so much worse when you don't follow each platform principles
Collapse
 
rad_val_ profile image
Valentin Radu

Re 2: that's because you have the mindset of a dedicated developer. Which is of course good for a dev, however, on the business side sometimes it's more important to deliver and make $$ then slowly solve issues (if you ever solve them) than make it perfect from the start.

Personally I think the best solution is a compromise, don't 100% mess the code just for easy gains, but do find suitable shortcuts when possible (and yes, non-native apps can be suitable shortcuts in some cases)

Collapse
 
lexlohr profile image
Alex Lohr

First of all, I don't really hate you or your answer, but I'd like to transcend its sentiment.

Development is all about the compromises you make - and you will make them, consciously or not. For example, by adhering to a "use the right tools" workflow, you compromise on the ability to use tools you deem "wrong" to greater effect, which especially for prototyping can be a bad choice.

Which brings us to your second point: when we are aware of the compromises, we should also know the consequences and make them transparent. Using electron for an UI means that you trade consistency with the platform with consistency over platforms.

If you make this choice, it should be a conscious one - just like all of the other compromises you make all the time on a daily basis. However, that does not mean that you sacrifice app quality - and how much money you spend on what is not the choice of the developer, but of the manager. The developer's task here is to make the consequences of each choice transparent.

Collapse
 
jdforsythe profile image
Jeremy Forsythe

Or you can use something like Ionic with Capacitor and get native plus web stack

Collapse
 
derek profile image
derek

Ignored warnings... that typically go like:

Me: β€œThat’s a bad idea... you may not want to do it because of X, Y, and Z.”

Other: β€œIt works now, it’ll be fine”

Me: πŸ‘ŒπŸ½

A few weeks later... πŸ”₯

Other: β€œIt broke because of X, Y, Z! Why didn’t you say anything?!”

Me: πŸ€¦πŸ½β€β™‚οΈ

Collapse
 
iampaoloxd profile image
Paolo

i feel you :D. i don't tell my colleague what to do. rather i gave suggestion if he want to consider, and later on everybody has to jump in coz he did not consider the suggestion :D

Collapse
 
ben profile image
Ben Halpern

Having a good idea and not having the capacity or energy to properly articulate it.

Like: I think I'm on to something, but I just can't entirely explain the philosophy.

Collapse
 
pj profile image
Paul Johnson

The immaturity of the Node/Typescript ecosystem and the amount of fiddling around with the environment it requires to get basic things going. I actually think someone could make a career as a Node BS wrangler, at least for the next few years.

I think if I was going to do a bog standard website project I would revisit using Rails.

Collapse
 
zilti_500 profile image
Daniel Ziltener

Why people are even considering in the first place to use JavaScript engines server side is beyond me...

Collapse
 
pj profile image
Paul Johnson

There's parts of the ecosystem I like, on it's own I think Typescript is pretty good and at least in theory the massive amount of investment that browser vendors make on Javascript VMs should benefit performance vs say Python.

I think it's more the problem of combining the existing Node JS module system, es6 modules, bundling for the frontend etc.

But yeah, things like lack of proper integer and float types is pretty dumb πŸ˜ƒ.

Collapse
 
jdforsythe profile image
Jeremy Forsythe

JS is actually very good on the server. Ask Netflix.

Thread Thread
 
zilti_500 profile image
Daniel Ziltener

Ahh yes, that must be why the language they use the most is Java instead of JS

Thread Thread
 
jdforsythe profile image
Jeremy Forsythe • Edited

While it's true that they still run a lot of Java code, all of their web stack is JS. Or as they put it, everything a user sees is written in JS.

In another case, PayPal found that an app rewritten from Java to JS was more performance, serving double the req/sec one one core as the Java app did on 5 cores, so they made the switch.

Thread Thread
 
zilti_500 profile image
Daniel Ziltener

PayPal has (or at least had) reportedly such a horribly awful code base, they could've rewritten it in BASIC for an interpreter and still get a 5-time performance increase, lol! Really they had to rewrite their stuff anyways. Java still is the most performant bytecode VM out there, let alone speaking of the performance of tech like GraalVM... (plus it is multithreading capable, unlike Node)

Collapse
 
jdforsythe profile image
Jeremy Forsythe • Edited

If you think the TS ecosystem is immature, try cloning the DefinitelyTyped repo.

TS + Node is easy to set up nowadays. ts-node allows you to debug it directly, no transpiling. We only run tsc when we're ready to ship. We write TS microservices daily with no issue. We clone a setup repo and start writing code.

github.com/jdforsythe/typescript-n... has what you need to start writing code immediately

But if I were making a blog I would use an SSG like hugo, not TS or Rails.

Collapse
 
aneeqakhan profile image
Aneeqa Khan

backend developers thinking that frontend is easy πŸ˜›

Collapse
 
juanfrank77 profile image
Juan F Gonzalez

I think this is my Biggest pet peeve of all

Collapse
 
willtrout profile image
Matt Willtrout

Apparently it has been Decreed that front end is women's work. This means (I am told) that it is both very easy, and Real Men would rather handle a sanitary napkin.

So sexist incel dudebros.

Collapse
 
sleepybuildings profile image
AMFan • Edited

Clients that think that they are important enough for a (interrupting) call. Unless a server is burning, send a mail, I’ll check when I have time.

5 projects in a day... context switching is killing.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.