3 ms·
For me, a problem eats at me when I can't solve it immediately. Or say it's not that I haven't solved the problem but I have to write all the gold plating code
by S_A_P 13y ago
For me, a problem eats at me when I can't solve it immediately. Or say it's not that I haven't solved the problem but I have to write all the gold plating code to polish everything up and I don't have time. Or I have to demo a feature with known bugs. It's an incredibly stressful feeling. I think it boils down to what I want to finish and the time I have allotted. This can be defeating and depressing. For me I have way more ideas than time. I love designing Apis and architecting projects but hate the last 10% that takes 90% of the time to get right. This sort of thing is what depresses me regarding programming.
I don't need accolades or recognition. The reward is the resulting awesome code for me. Knowing I built something useful is really all I need.
*edit autocorrect error
- sirmarksalot 13y agoCouple that with a situation where you do have a solution, and you manage to implement it, and then later on somebody takes over your codebase, rips the solution out because they can't be bothered to integrate their new idea into your architecture, and all the bugs that you thought you'd solved "once and for all" come right back.
- noisy_boy 13y agoI remember a period when I was transitioning from my development role to a hitherto unknown role within the company. Granted my development role involved basically 50% business analyst work + 50% development (which mainly consisted of a Shell/Perl/SQL etc). During that period all could do basically surf news sites until someone needed help in some large volume data processing. Just the opportunity to write some scripts again was such an uplifting feeling - at the end of the day, I felt that I got something done (and that was independent of the resulting appreciation).