|
Show
|
-
|
Show
|
- Hardware dependence.
- If software was tightly coupled. makes refactoring a nightmare.
|
Show
|
All the documentation or processes surrounding the code.
|
Show
|
Ambiguous requirements and unrealistic expectations
|
Show
|
Any churn around boiler plate.
|
Show
|
At times post-development issues are difficult to analyze to establish root cause
|
Show
|
Bad docs between teams, unclear requirements
|
Show
|
Bug fixing
|
Show
|
Bugs !!
Especially bugs that aren't caught and make it to customers.
|
Show
|
Build issues. Getting stuck debugging when no solution can be found.
|
Show
|
Build times and having to wait between testing.
|
Show
|
Can be a bit tedious at times
|
Show
|
Code not working due to opaque infrastructure bugs
|
Show
|
Code reviews, waiting for builds, vague/misleading build errors.
|
Show
|
Constant changing of scope and requirements.
|
Show
|
Deadline pressure, poor documentation, and people who don't care.
|
Show
|
Dependencies between software modules.
|
Show
|
Design keep Changing frequently
|
Show
|
Errors
|
Show
|
Experiencing non deterministic bug that arise very seldom after quite a very long time to reproduce.
|
Show
|
Explosive growth/ const disruption in every aspect - can't master all, one isn't enough!
|
Show
|
Fighting archaic, clunky IDEs.
|
Show
|
Finding very niche unreproducible edge case bugs!
|
Show
|
Getting bogged down in I.T. world.
|
Show
|
Getting stuck in a bubble alone while the team is testing
|
Show
|
Hard-coded unit tests.
|
Show
|
Having to figure out what the issue is related to bugs.
|
Show
|
Having to make sure the environment is all set up correctly. And also staring at a screen.
|
Show
|
Hype cycles.
|
Show
|
I am forced to use AI
Some issues take longer to debug than others
|
Show
|
I don't like managing complex dependencies and debugging issues or waiting for long build times.
|
Show
|
I don't like when one small bug drives me insane because I enjoy the creating something part more
|
Show
|
I don't usually like writing tests.
|
Show
|
I like it
|
Show
|
In an RTOS environment, I struggle to debug where specifically a race condition / fatal error begins
|
Show
|
Inconsistent standards
|
Show
|
It's difficult to find a job in an area you really love.
|
Show
|
Lack of flexibility. Lack of separation of concerns.
|
Show
|
Lagging tools (C++ was stale for too long), debugging, memory corruption ...
|
Show
|
Legacy Code without comments or documentation. Maintaining Libraries for Legacy Hardware
|
Show
|
Long lead times to make minor changes
|
Show
|
Maintaining legacy code without clear documentation.
|
Show
|
Maintenance and debug issues related to changes that could have been addressed with better testing
|
Show
|
Making the documentation for a user level and managing requirement could be difficult to handled.
|
Show
|
Management over-promising then pushing us to the brink, not consulting us on time needed to deliver.
|
Show
|
Managing constantly shifting priorities while trying to debug a bunch of loosely documented code
|
Show
|
Nonsensical directives being forced on a design, without justification.
|
Show
|
Not making progress. Boilerplate.
|
Show
|
Not much.
|
Show
|
Nothing about the actual development; around development there is bureaucracy and hierarchy
|
Show
|
Nothing glaring stands out in particular.
|
Show
|
Nothing off the top of my head! I don't like writing bad code, or not knowing what best practice is
|
Show
|
Nothing... ok, I don't like code reviews and long planning meetings.
|
Show
|
Paperwork, wrangling infrastructure, strict processes
|
Show
|
Poor tooling, cargo culting, fanboyism, unrealistic deadlines, ship it anyway, obsession
|
Show
|
Poorly scoped definition of done.
|
Show
|
Pretty much like it all
|
Show
|
Probably mostly the documentation part
|
Show
|
Random problems such as builds randomly failing due to unrelated issues
|
Show
|
Resolving/investigating extremely long linker dependency chains.
|
Show
|
STM IDE bugs
|
Show
|
Setting up a new dev environment and forgetting all your macros, keybinds, etc.
|
Show
|
Shifting priorities caused by poor planning or lack of focus/commitment from the business.
|
Show
|
Short term thinking, fragility, and recently the "AI" push
|
Show
|
Some issues are not easy to debug, some problems are seen rarely or intermittently.
|
Show
|
Sometimes there is too much bureaucracy involved in making a change.
|
Show
|
Spending hours debugging just to find the error was a tiny typo—so frustrating!
|
Show
|
Testing
|
Show
|
Testing
|
Show
|
The finnicky moment of turning an idea you know should work into paper. Reproducing complex bugs.
|
Show
|
The grind - looking for hours to try to find a problem in code that is needlessly complicated.
|
Show
|
The occasional bureaucracy. I enjoy being solo, breaking things to find the best way.
|
Show
|
The overhead time not used for coding. The testing, reviewing, etc
|
Show
|
Trying to get 3rd party things working and fighting with their documentation or code.
|
Show
|
Unclear legacy code, Bad Debug tools, Environment setup/issues
Really debugging unexpected issues
|
Show
|
Unclear requirements can be challenging
|
Show
|
Using debuguer to understand the issue.
|
Show
|
When it starts to be mechanical work. No thinking.
|
Show
|
When you spend days and days looking for a bug you could have avoided
|
Show
|
Writing tests. Having to figure out undocumented code where the intention isn't clear.
|
Show
|
a lot of repetitive tasks, creating design documents and maintaining documentation
|
Show
|
bad architecture might have a cost during the development or in project (e.g., limited reusability)
|
Show
|
debugging
|
Show
|
debugging issues
|
Show
|
debugging issues
|
Show
|
debugging, refactoring
|
Show
|
difficult bugs and customers
|
Show
|
documentation
|
Show
|
manual testing of the same features when the testing should have been automated.
|
Show
|
n/a
|
Show
|
sitting on my chair too long, back posture issues mainly
|
Show
|
stepping through code to troubleshoot
|
Show
|
tedious stuff and busywork sometimes. AI has been helping with this.
|
Show
|
too many bugs
|
Show
|
trying to manually check compliance with coding rules
writing documentation
|
Show
|
typing
|
Show
|
unclear requirments
|
Show
|
unexpected failure that may be caused because of untested corner case or unknown behavior.
|
Show
|
wasted development and broken code as a result of not understanding the whole complicated system
|
Show
|