Tag Archives: Lessons Learned

Trauma Points (part 2) – Dealing with and treating trauma

In part 1, we talked about “what trauma points are”, where they come from, why you only see them in maintenance programming. What to expect and what do about it? So, trauma points. If your team is using this term/concept … Continue reading

Posted in IT Horror Stories, IT Psychology, Lessons Learned, Maintenance, planning, Professionalism, Team | Tagged , , , , , , | Leave a comment

What’s not on my resume

I don’t put everything-I’ve-done on my resume anymore. A few times I’ve had people complain about it being too-wordy, or even say something like “Look at all of this stuff. You must be a jack-of-all trades and master of none”. … Continue reading

Posted in Career, Education, IT Psychology, Professionalism, Team | Tagged , , , | Leave a comment

Cheap vs Good

Disclaimer: This is not about my current project. It is about all projects, everywhere. Kernighan once said “debugging is inherently twice as difficult as writing code in the first place. Therefore, if you have written an app as cleverly as … Continue reading

Posted in Lessons Learned, Maintenance, Programming | Tagged , , , , | Leave a comment

Why panicked fixes are dangerous

A few months ago, I had a blog post about “panicked fixes“. I said they were bad, but I guess I wasn’t quite clear enough about why. Ironically, I’m the kind of guy who, if you tell me “Don’t do … Continue reading

Posted in IT Horror Stories, Lessons Learned | Tagged , , , | Leave a comment

It is what it is

A buddy of mine says he hates this saying because it is pretty stupid.  “Of course it is what it is, what else could it be?”, he says.  “Could it be [not what it is] or is it [something similar … Continue reading

Posted in IT Horror Stories, Lessons Learned, Professionalism | Tagged , , , | Leave a comment