i spent the last couple of days working on a bug at work. Actually, several. Turns out, it was a pretty substantial bug, and regardless of who's to blame for creating it originally, it's my responsibility to fix. i'm fine with that.
More importantly though, i'm trying to figure out a way for folks to let me know when things aren't working quite right. i know that most folks don't read, so anything too subtle won't work. i know that i'm going to get a number of folks upset with me because something completely out of my control to fix is broken and i'm not fixing it for them. Still, there's a significant percentage of folks that are interested in trying to fix something that i want to make sure get in touch with me. i can't figure out absolutely everything that can possibly go wrong ever, but when things do break, i need those folks to help me fix it.
It's just interesting to think about how to do that. Granted, i want to let folks know who might have been hit by this bug that "No, it wasn't you. Yes we do suck. Please try it again or let us know if it's still broken.", but it's that last part that's the hardest. i don't want to band-aid a fix, i want to provide a solution.
Yeah, fixing things is easy. Correcting things isn't. I prefer to correct things since that makes it better for all, but it's still a challenge.
Save This Page
i see a lot of "baid-aid" or hack type fixes in my group and i really dislike it. i always ask devel to provide a proper fix in a timely fashion instead of a quick hack. hacks never EVER get taken out and usually are left in place forever.