5

For you, what's the most stressful thing about being a developer?

Comments
  • 3
    Being confident
  • 0
    Home issues
  • 1
    Not staying on task
  • 6
    Meeting percieved expectations.
    They're always like six times higher than the real ones.
  • 4
    Other people
  • 2
    Explain non-techie people (often managers) why their expectations are not working because of techie stuff
  • 3
    *Having* to keep up with new shit. Some of which will die out, but some of which will stick around, so in order to not become a senior dev being ranted about on here, we need to keep learning. Sometimes we need a break though, and after two weeks, there's already three new shits out that you need to at least have heard of.

    I'm not even talking about JS frameworks.
  • 1
    Designers who think they know how to code.
  • 0
    Clients?
  • 3
    @theMaintainer Dealing with that one right now.

    * The controller action is in the wrong controller.
    * The syntax is ancient, redundant, and (nitpick) in the wrong order.
    * The view doesn't define a Rails form, just a form tag with some controls.
    * The controls don't have proper names
    * There is no model
    * There is no database table at all to store the user response
    * The css is in the wrong stylesheet
    * Hardcoded options
    * Hardcoded contact information

    But yep.
    "It's basically done"
    "Just wire it up"

    K, I'll let you know when I rebuild this in its entirety.
  • 2
    @tkdmatze Same :

    Talking to people. Specially thinking fast on "How the fuck I can explain that to someone who has 0 technological background?"
  • 1
    @Root Such stupidity should be a crime.

    At least converse with the one who structured the system in the first place (granted that person is available)
  • 0
    Deadlines. Asking you: can you do this today or tomorrow. Lots of things to learn and practice. Doing unpaid overtimes just to get the job done.
  • 0
    @NoToJavaScript i am pretty good in explaining things to non techies

    Explaining why "their ideas" will not work is the hard thing

    You can't call the idea stupid, although it is, to not make them freak out
  • 0
    In no specific order:
    - working on a terrible codebase
    - a bad development pipeline which requires you to remember arbitrary details
    - APIs that are acting different from their documentation (with a goddamn wrong WSDL)
    - unreasonable deadlines
    - being interrupted while in the zone
    - pointless meetings
    - perfectionism
    - working on boring/unfulfilling projects
  • 0
  • 0
    Unclear expectations
Add Comment