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
|
Running into an issue that takes a long time to resolve.
|
Show
|
Inconsistent failures and edge cases.
|
Show
|
Testing
|
Show
|
Trying to figure out how to actually solve a problem
|
Show
|
none
|
Show
|
Pain of something not working or breaking intermittently and not knowing why, esp. under time pres.
|
Show
|
Digging through poorly documented code to fix a bug.
|
Show
|
Finding and fixing syntax errors
|
Show
|
when things don't can't follow a simple structure, and it get complex.
|
Show
|
Focus has always been in hardware/manufacturing/Design which knowing coding processes will help me.
|
Show
|
Pressure to plan and complete a project with dynamic requirements and scope on a rigid schedule.
|
Show
|
Estimating development times. Schedules.
|
Show
|
Tedium
|
Show
|
Bugs
|
Show
|
Setting up the development environment.
|
Show
|
When the user decides the original specification isn't actually what they wanted.
|
Show
|
Technical Debt
|
Show
|
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
|