Ok, here it is. I love errors.
Query append errors, SQL errors, web-server errors, you name it- I can’t get enough of them. Now, if I may, I will qualify this unhealthy love of errors.
I like errors WHEN:
- I have time for them
- They don’t cripple a mission critical application
- I have the tools and resources to fix them
So basically that excludes about 99% of the errors “regular” IT folks have, right? I love the errors because many times it helps me “get back in touch” with my applications. How many times have you built something only to abandon it for months, and stop further development? Yeah, sure, it works. What about if you tweaked this process, added some reports and maybe some auto-feedback here…and now you have a complete set of upgrade plans. I love jumping into the guts of one of my systems or perhaps a new system and filling documentation holes(I smell a blog post…), or sometimes documenting for the first time. There’s something deeply satisfying to mapping out an entire application by hand and surveying the process only to immediately pinpoint the problem, AND ways to make your app better.