This is the third post of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.
This is the third post of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.
For further actions, you may consider blocking this person and/or reporting abuse
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.
Could not agree more, it's exactly what I was going to add!!!
100% on your side
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.
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
Back to back MS teams beep beep beep beep beep
lol I can relate
Fixing a bug in production yet I did not face it during development.
Unnecessary calls and timesheets.
speak in english :(
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! ❤️
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.
Changing 15 files by hand to make a tiny fix. 🥲
Whatever I'm about to have to do after saying "Well, I mean... technically we can do that"
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.
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.
6 working days.
Yeah i agree. Working from office sucks.
The context switching. It can take from 15minutes - 1hour+ just to really get to the heart of the task.
learning a tech that rarely used by people
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
When I have to repeat things to people.
New lib updates making old code redundant.
I cannot stand to be forced to work 8 hours a day when most days I’m done much earlier.
That slack notification whenever I'm occupied
Linting wars.
Reaching consensus on PR discussions or big technical choices. Very time consuming and feels like overhead relative to working alone.
Context switching between multiple companies and projects within companies
"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...
Get blamed before deployment to production, because we've never included in meeting or grooming features.
dealing with cunning co-workers
Two DAY sprint? Wow.
Content writing.