DEV Community

Cover image for What’s the most annoying part of your job?
Ben Halpern for The DEV Team

Posted on

What’s the most annoying part of your job?

This is the third post of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.

Top comments (38)

mdor profile image
Marco Antonio Dominguez

Unreal expectations, as a developer a common issue is to listen to people expecting you to finish something in record time, regardless of the lack of resources, lack of time, lack of clarity on requirements, and non-sense policies.

nombrekeff profile image

Could not agree more, it's exactly what I was going to add!!!

tutrinh profile image
Tu Trinh

100% on your side

manuartero profile image
Manuel Artero Anguita 🟨 • Edited

I'd say... the never-ending feeling. You take one task, you do it. Then you take another. Do it. Another. Again.

Don't get me wrong I do like my job, I'm extremely grateful to my profession; but I think that dealing with the never-ending cycle is the hardest part.

jeremyf profile image
Jeremy Friesen

There is infinite work, which is a function of "knowledge" work. I'm glad you at least recognize it. For myself, accepting that reality became quite liberating; because in infinity most anything can wait, so be clear what's important.

guithomas profile image
Guilherme Thomas

I guess that's true for a lot of professions. Before development, I was doing tech support for POS machines. Never ended, same errors everyday, visiting the same cities. Can be exhausting

aryank21 profile image
Aryan Kaushik

Back to back MS teams beep beep beep beep beep

asimdahall profile image
Asim Dahal

lol I can relate

evansifyke profile image
Melbite blogging Platform

Fixing a bug in production yet I did not face it during development.

frikishaan profile image
Ishaan Sheikh • Edited

Unnecessary calls and timesheets.

edalonzoh profile image
Daniel Alonzo

speak in english :(

sherrydays profile image
Sherry Day

Any time I know how I could solve a problem, but cannot go about solving it because of circumstance.

Circumstances such as not being on the team that is supposed to solve the problem. I know sometimes I am missing context about what is making the problem so tough to solve, but sometimes I know it's just annoyingly circumstantial that I can't just fix the thing I have technical access to and knowledge of the system it would take.

brunoj profile image

Changing 15 files by hand to make a tiny fix. 🥲

michaeltharrington profile image
Michael Tharrington

Haha, I think spam fighting takes the cake here.

Props to @carolineschettler, @itscasey, and all the awesome trusted users who put in the work daily to help us scrape the spam off of DEV. Not to mention @ben and our engineers who have created automated spam fighting features for us as well. 🙌

Bonus props to community members who report spam as they see it! Thank you! ❤️

terabytetiger profile image
Tyler V. (he/him)

Whatever I'm about to have to do after saying "Well, I mean... technically we can do that"

devoskar profile image
Oskar Pietrucha

Missing authorizations where clearly you should have them (no security flaws), but "corporation logic" :)
Forcing usage of stack A instead of stack B, because somebody doesn't know stack B.

mellen profile image
Matt Ellen

For me it's simply getting all the people necessary to review documentation changes prior to a release. For some reasons deadlines never take this into account and we're left scrabbling for sign off at the last minute, which doens't work because the compliance team actually read the documentation, so we end up out of time.

ratcat profile image

6 working days.

dbkooper51 profile image

Yeah i agree. Working from office sucks.

theklr profile image
Kevin R

The context switching. It can take from 15minutes - 1hour+ just to really get to the heart of the task.

dendihandian profile image
Dendi Handian

learning a tech that rarely used by people