Programming, what makes you lose time?
The subject above seems to me a good one to test the 'thought' blog possibility
From experience with C under OS4.1.4, i noted the lack of a good working debugger as one of the main problems. The only thing i can use it for, is to set it for one breakpoint and have the backtrace information, giving me some info. If this breakpoint is reached first in a non-buggy piece of the SW, this info is not worth much though.
I tried to use Debug 101 but the interface confused me. I don't really know how good it is.
An other point is my keyboard, with worn-out keys. Keyboards are cheap but should you throw them away just for that sake? Replacement stickers for the keys seem to cost more than a new low-cost keyboard.
Maybe the most time consuming part is searching through the OS system documentation (including Amiga Development CD 2.1). Time and time again i do only find a small part of what i really need, start trying, do come to the conclusion that i miss some other info...
There is no substitute for understanding, but a better organised documentation structure would help.
If i ask how you tackle these problems, where you do lose time this would maybe some usefull threads. Then the question arises if the forum should not include those sections
- development tools
Submitted by JosDuchIt on Tue, 2012-02-21 17:25