I read the other day on Kent Beck's blog some wise advice that he was both simultaneously giving and breaking at the same time.
Even though I had read this wise advice, I too did not follow it. The advice was to never blog when you're mad. It was never anything that I had thought about, but upon seeing it in writing it made perfect sense. Why? It just looks bad. You'll say things in the heat of the moment that you'll regret. And you just don't want the whole world to see your temper tantrum do you?
Why did I not follow this advice that I had not even one day earlier stumbled upon? Because I was mad of course. And I wanted to express that... to get it out of me... so that I no longer held onto it. But after having my minor rant exposed on the web for a short duration of time... his advice kept ringing over and over in my head. "Never blog when you're mad... never blog when you're mad... never blog when you're mad...".
And now that post is digital trash... I deleted it. There are more constructive things to write about or do. Such as this... passing on the advice... never blog when you're mad. Lesson learned.
Cory, I tend to agree with the point in general, but the post to which I think you are making a reference is actually a series of interesting points. Sure the post reads as pure frustration, but why should software development have to be frustrating.
ReplyDeleteYou have every right to air your views - it is your blog - there is nothing wrong with constructive criticism.
Keep up the good work!
Hi Andrew,
ReplyDeleteYour encouragement is very much appreciated!
I absolutely agree with your point that there is nothing wrong with constructive criticism. I guess that when I went back and re-read the post there were a couple of items in it that read a little "whiny" to me. Perhaps I'll post a very slightly modified version back up here soon. There were definitely some points in the post that I feel very strongly about.