DEV Community

Cover image for What are your top three everyday pain points as a developer?
Ben Halpern Subscriber for The DEV Team

Posted on

15 3

What are your top three everyday pain points as a developer?

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

Be as detailed as you like when answering this question.

Top comments (16)

Collapse
 
bascodes profile image
Bas Steins
  1. Missing Documentation
  2. Meetings that should have been an emai
  3. misused JIRA

Plus, depending on the client:

  1. restricted environments (proxies, VPNs, ...) that just standing in the way rather than provide extra security
Collapse
 
ben profile image
Ben Halpern

I'm curious about specifics regarding misued JIRA.

Collapse
 
bascodes profile image
Bas Steins

Well, I've seen any sorts of this in the wild:

  • Tickets are not really tickets, but a trash can for ideas
  • Overcomplicated workflow configuration
  • Tickets referencing documents elsewhere ("I've posted that in slack" - "sure you did, but when and where?")
  • misconfigured integrations with deployment pipelines
  • ...
Collapse
 
keik_remoteit profile image
Kei Koyama

I'm curious about the restricted environments. What specific issues have you run into? Are they all client-side?

Collapse
 
lucassperez profile image
Lucas Perez

Back, head and wrist.

Collapse
 
miguelmj profile image
MiguelMJ
  1. Undocumented code
  2. Unclear priorities
  3. Dealing with non technical problems like burocracy or users that don't read the manual
Collapse
 
jrop profile image
Jonathan Apodaca
  1. Not prioritizing developer experience
  2. Premature optimization
  3. Code that is not strongly typed
Collapse
 
shreddie75 profile image
Edmund Gomes

Bio Freeze... Spray it on pain is gone!! Its magic(I should trade mark that lol)... This is obviously a quick fix and doesn't cure the root issue... sitting in the same position for hours on end.. you have to move and stretch

Collapse
 
benbenlol profile image
benbenlol

To be honest, I know very well what health problems are. My joints and muscles often hurt. So I started looking for something that could help me and came across cbd roll on 1000mg and started using this product and it really helps me. So, read the article and try this hemp CBD oil. I think things will get better.

Collapse
 
devfranpr profile image
DevFranPR
  1. Working on projects with deprecated software/technologies.
  2. Not having enough things automated.
  3. Being forced to use Windows as work OS.
Collapse
 
booboboston profile image
Bobo Brussels
  1. Flakey tests
  2. Dependencies
  3. Meetings
Collapse
 
andrewbaisden profile image
Andrew Baisden
  1. Too many meetings (distractions)
  2. Unclear briefs that lack details
  3. Short deadlines that leads to poor code quality and lack of test coverage
Collapse
 
arikaturika profile image
Arika O

Back pain x 3 😂

DEV is built on open source software called Forem!

GitHub logo forem / forem

For empowering community 🌱


Forem 🌱

For Empowering Community

Build Status Build Status GitHub commit activity GitHub issues ready for dev GitPod badge

Welcome to the Forem codebase, the platform that powersdev.to. We are so excited to have you. With your help, we canbuild out Forem’s usability, scalability, and stability to better serve ourcommunities.

What is Forem?

Forem is open source software for building communities. Communities for yourpeers, customers, fanbases, families, friends, and any other time and spacewhere people need to come together to be part of a collectiveSee our announcement postfor a high-level overview of what Forem is.

dev.to (or just DEV) is hosted by Forem. It is a community ofsoftware developers who write articles, take part in discussions, and buildtheir professional profiles. We value supportive and constructive dialogue inthe pursuit of great code and career growth for all members. The ecosystem spansfrom beginner to advanced developers, and all are welcome to find their place…

👋 Kindness is contagious

Engage with a sea of insights in this enlightening article, highly esteemed within the encouraging DEV Community. Programmers of every skill level are invited to participate and enrich our shared knowledge.

A simple "thank you" can uplift someone's spirits. Express your appreciation in the comments section!

On DEV, sharing knowledge smooths our journey and strengthens our community bonds. Found this useful? A brief thank you to the author can mean a lot.

Okay