Training Preparation -- What 100 Attendees Dislike About Software Development

Least favorite thing about dev
Broken or difficult to use tooling, ever changing requirements, unrealistic schedules
Show
Working with legacy code that uses abbreviations, no comments/descriptions, not very readable.
Show

Show
The amount of time it takes to do things such as documentation and unit testing.
Show
Too many abstraction layers that I don't understand
Show
Bugs and unit-testing nested if statements...
Show
- slow deployment/testing
Show
It can feel like a grind sometimes
Show
N/A
Show
So many options to accomplish the same thing.
Show
In medical -- the long time it takes to develop a few lines of code.
Show
Overhead of pushing code to a joint repository
Show
Sometimes it takes very long time to see the results - medical industry...
Show
Writing unit tests
Show
Spending more of my time working with machines instead of with people.
Show
iteration takes long time.
Show
Lack of documentation/requirements
Show
Unnecessary complicated code, and arch, left by devs trying to be clever.
Show
Waiting for long builds or tool runs.
Show
It can be frustrating.
Show
Banging my head against a wall chasing down bugs for hours at a time.
Show
Hard to find bugs.
Show
All the documentation to go along with it. And UL.
Show
no
Show
i hate debugging, and getting sucked into writing a bunch of code at once, instead of incrementally
Show
That I eventually get tired and have to stop.
Show
pressure to deliver bug-free software within short time frame.
Show
debugging
Show
Testing. Solitary. Long time in a chair. low interaction with other people.
Show
I don't enjoy working within a codebase that doesn't apply software development best practices.
Show
Debugging
Show
context switching
Show
Debugging is fine, but doing it under time pressure is awful (which is normally the case)
Show
Slow development environment, tedious tasks (boring debugging included)
Show
I like
Show
Not getting enough time for research or improving solution.
Show
Nothing really. Perhaps fighting with tools that doesn't work or slows down your work
Show
My code from last year backwards. I will think the same next year
Show
Complex and emergent behaviors
Show
When the code gets way to complicated and hard to debug.
Show
Bugs and writing lots of documentation, usually.
Show
Not knowing how to structure the code. Writing buggy code and do not know where to start fixing it.
Show
when it is not working or badly
Show
Understanding 20 year old > 1000 line functions and the fear of others that improving it breaks it
Show
Working on low quality software that behaves erratically. Chaos that ensues when requirements change
Show
Unit test takes a while to write
Show
Overall when you lose track during debugging.
Show
Useless meetings Explain manager implementing a feature is not just some line of codes Meetings
Show
It's somewhat detached from the physical world.
Show
Burnout
Show
Having to deal with legacy code with awkward formatting/standard/architecture.
Show
solving puzzles
Show
Needless complexity. Design decisions being made by unqualified individuals.
Show
Having to do it in a hurry because of deadlines
Show
interruptions when in flow
Show
unit testing :)
Show
Figuring out what a gigantic ancient piece of code does with no available written doc at all.
Show
Debugging extremely hard to find bugs
Show
Legacy code, bad documentation, unclear errors
Show
Testing
Show
Hidden errors that show up when truly don't need them to show up
Show
When the code is so complicated.
Show
Lack of documentation... when learning something new.. sometimes the documentation is lacking.
Show
Often requirements change
Show
how some simple tasks can be complicated
Show
Maintain certain bad-structured without test code, uncertainty of some development tasks.
Show
It gets frustrating when the code does not work, I there is no logical reason
Show
The time required to test changes.
Show
Rigid enforcement of every possible design pattern that can be forced into an implementation
Show
When its not working
Show
N/A
Show
Realizing you've made a mistake in your design
Show
Debugging can be time consuming
Show
Huge dependencies that touch many aspects of the code base.
Show

Show
Not clear about requirements.
Show
there are a lot of things to think about all at once sometimes when looking maintance of code
Show
It never works the first time.
Show
everything
Show
documentation
Show
Working in big teams with a lot of red tape
Show
When code breaks from something super small and it takes an hour or more to find it
Show
Unclear requirements that cause rework Finding evidence for very elusive bugs
Show
Unclear requirements that cause rework Finding evidence for very elusive bugs
Show
Tests take longer to write than code
Show
Reading other peoples code
Show
It can be very frustrating when you do not understand why your code is not behaving as expected.
Show
When everything doesnt work
Show
Constantly wrestling with IT
Show
Tracking down bugs.
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and are stuck for too long figuring out why
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and you can't figure out why
Show
When it doesn't work and you can't figure out why
Show
I don't like how debugging can be difficult at times.
Show
Getting stuck on something
Show