Training Preparation -- What 100 Attendees Dislike About Software Development

Least favorite thing about dev
Debugging. Human error. Dealing with other people's bad code.
Show
Debugging. Human error. Dealing with other people's bad code.
Show
unstructured projects and badly written code
Show
The overwhelm that occurs when you haven't broken down a problem into manageable chunks.
Show
Tracking down bugs that are hard to reproduce.
Show
It consumes a lot of life energy. That is why I am here: for optimizing this energy consumption.
Show
Often, work-life-balance is hard to have since you can always log in and work from home at anytime.
Show
Varied platforms/configurations that it eventually runs on, bringing multitude of use cases
Show
Reading other's code.
Show
inefficient of writing code; takes a large amount of code to accomplish a seemingly simple task
Show
Finding critical bugs!
Show
N/A
Show
Having to use old legacy code and coding standards that don't make sense or limit functionality.
Show
Legacy code hard to understand. Unclear/changing requirements. Bad product management.
Show
Writing documentation, Writing tests.
Show
Bit tedious job to design the software application architecture that gives flexibility to enhance.
Show
Bad tools/vendor support
Show
We still can't/won't estimate accurately (or truthfully?)
Show
Working with poorly thought out legacy code.
Show
can't thinkg of anything.
Show
Software that's too hardware dependent. Software that's not readily reusable.
Show
Debug tools that don't cooperate
Show
Tracking down and plugging memory-leaks when they occur
Show
-
Show
deadlines :)
Show
I did it for decades
Show
debug
Show
Sometimes with oversight we take more time for small issues in the code.
Show
When the complexity of the code increases, it becomes difficult and time consuming to resolve bugs
Show
N/a
Show
Dealing with intermittent issues/bugs in code.
Show

Show
Debugging
Show
When people who don't know the sw, make decisions about it :-)
Show
Unrealistic deadlines
Show
testing when there's UX or hardware involved
Show
Menial and repetitive tasks that can be hardly automated.
Show
Debugging!
Show
Solving bugs, understanding other people's code
Show
debugging for hours, only to find a simple logic error
Show
repetitive task
Show
Looking at the monitor for too long, hurts my eyes. :(
Show
Tool chain bringup and quirks
Show
Not sure
Show
- Testing - Always strugling how/where to start
Show
Nothing.
Show
Dealing with poorly written legacy code, missing documentations.
Show
Those intractable portions of frameworks that are ill-documented and/or do not work as they should.
Show
Waiting for hardware.
Show
Making significant changes to existing code that is not clear and understandable.
Show
The tedious nature of cryptic syntax and deciphering convoluted or ambiguous code.
Show
It can become frustrating to deal with code that is convoluted.
Show
I don't like manually testing code.
Show
Legacy code touched by many engineers who btw no longer work at the company...
Show
To work on poorly designed code and you realize it's too late to redesign every thing.
Show
Debugging critical bugs
Show
documentation of code
Show
Testing the stuff which cannot be unit tested unless specific HW or SW requirements met.
Show
long duration of unit testing
Show
NA
Show
The long debug sessions :)
Show
Debugging corner case issues which are not seen during complete test cycle.
Show
Documentation
Show
The amount of time it takes to write a complex code.
Show
Debugging someone else's code which is not very well documented
Show
Nothing
Show
The bugs
Show
Less efficient tools for editing and debugging. Language selection also matters.
Show
-
Show
N/A
Show
Having to use legacy IDEs such as CodeWarrior 5.1
Show
Working individually
Show
Paper work, and customer moving the goal posts.
Show
time consumption
Show
Documentation.
Show
Today it is so complex that it is impossible to understand/wrap your head around everythig
Show
As usual, chasing bugs and debugging
Show
Having to fix other people's mistakes in code.
Show
there are so many different ways to do a task. Decision paralysis is a real thing!
Show
Solitary work
Show
getting caught up in legacy bugs.
Show
Writing unit tests
Show
Testing
Show
Delivery time pressures and the lack of budgets to get things done.
Show
When I'm stalled out by problems with my tools
Show
- fixing anomalies on customer systems
Show
Struggling with the tooling to even more forward.
Show
Maintaining old code, repeated work.
Show
it is sometimes stressful, e.g. when finalizing the code close to release date.
Show
Usually I don't like writing code when it's too much repetitive and hard to maintain and understand.
Show
"management", competitive instead of collaborative environment, lack of long term vision
Show
I don't really enjoy having to spend much time figuring out what code written by somebody else does.
Show
Fixing bugs
Show
Feature creep, the idea that 'software is cheap/free'
Show
The suspicion that the whole codebase is a sandcastle.
Show
As usual, chasing bugs and debugging
Show
As usual, chasing bugs and debugging
Show
I hate having to worry about formatting. I love code beautifiers for that so i dont have to worry.
Show
Debugging
Show
The ease of not being rigourous and the multitude of tools/methods applicable.
Show