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.

Discussion (38)

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
natescode profile image
Nathan Hedglin

Dido!!! Left so many jobs because of this. Two day sprints that weren't working or spending weeks trying to get requirements.

Collapse
ky1e_s profile image
Kyle Stephens

Two DAY sprint? Wow.

Thread Thread
natescode profile image
Nathan Hedglin

They called it "1 week" .

Monday & Tuesday = development
Wednesday = QA
Thursday = UAT & deployment
Friday = planning

It was hell. But they had a scrum "guru".

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
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
manuartero profile image
Manuel Artero Anguita • Edited on

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.

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

Collapse
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

Collapse
sheikh_ishaan profile image
Ishaan Sheikh • Edited on

Unnecessary calls and timesheets.

Collapse
evansifyke profile image
Melbite blogging Platform

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

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
edalonzoh profile image
Daniel Alonzo

speak in english :(

Collapse
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! ❤️

Collapse
brunoj profile image
Bruno

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

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.

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

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

Collapse
theklr profile image
Kevin R

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

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
jeremyf profile image
Jeremy Friesen

All of these questions my boss keeps asking. (Just kidding I don't report to Ben and love these questions as well as most other questions I get asked at work).

Right now the hardest part is balancing managing, individual coding, and helping open source contributors. The good news is we're looking to hire a dedicated manager to take away one of the hats.

Don't get me wrong, most of the time I love managing; in particular meeting people where they're at and helping equipment them for further successes along the success pathway that they want to go.

Heavy is the head that wears too many hats.

Collapse
nombrekeff profile image
Keff • Edited on

Bureaucracy, I don't think I should add anything else, If you've been there you will know...
And dealing with clients and their expectations

Collapse
dbkooper51 profile image
CodeKooper

New lib updates making old code redundant.

Collapse
mikcat profile image
mikcat

When I have to repeat things to people.

Collapse
raccode profile image
Raccode

I cannot stand to be forced to work 8 hours a day when most days I’m done much earlier.

Collapse
arndom profile image
Nabil Alamin

That slack notification whenever I'm occupied

Collapse
miketalbot profile image
Mike Talbot

Linting wars.

Collapse
codewander profile image
codewander

Reaching consensus on PR discussions or big technical choices. Very time consuming and feels like overhead relative to working alone.

Collapse
adam_cyclones profile image
Adam Crockett

Context switching between multiple companies and projects within companies

Collapse
tandrieu profile image
Thibaut Andrieu • Edited on

"Sorry, I don't have time to..."
I've always been amazed that people who never have time to do anything are usually those who don't have much to do...

Collapse
mono13th profile image
Moch. Sudharmono

Get blamed before deployment to production, because we've never included in meeting or grooming features.

Collapse
adrianchong profile image
Adrian Chong

dealing with cunning co-workers

Collapse
frontwires profile image
frontwires

Content writing.