DEV Community

Cover image for What’s the most annoying part of your job?
Ben Halpern Subscriber 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.

Oldest comments (33)

Collapse
 
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.

Collapse
 
brunoj profile image
Bruno

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

Collapse
 
edalonzoh profile image
Daniel Alonzo

speak in english :(

Collapse
 
aryank21 profile image
Aryan Kaushik

Back to back MS teams beep beep beep beep beep

Collapse
 
asimdahall profile image
Asim Dahal

lol I can relate

Collapse
 
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.

Collapse
 
nombrekeff profile image
Keff

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

Collapse
 
tutrinh profile image
Tu Trinh

100% on your side

Collapse
 
dendihandian profile image
Dendi Handian

learning a tech that rarely used by people

Collapse
 
ratcat profile image
RatCat

6 working days.

Collapse
 
dbkooper51 profile image
CodeKooper

Yeah i agree. Working from office sucks.

Collapse
 
frikishaan profile image
Ishaan Sheikh • Edited

Unnecessary calls and timesheets.

Collapse
 
frontwires profile image
frontwires

Content writing.

Collapse
 
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.