Category Archives: Methodology

Tech debt, rewriting the whole thing

If you’ve ever looked at a messy program, you might think “we should just rewrite this. It would take less time than fixing this mess”. The logic on it seems flawless, right. You are awesome and your ninja moves are … Continue reading

Posted in Lessons Learned, Methodology | Tagged , , , | Leave a comment

Requirements for Waterfall, Agile and Cowboy

Once again, I am comparing these three approaches to software development. It might seem funny that I could treat “cowboy” like it is a real methodology, but there is some reality to it and I would like to explain how … Continue reading

Posted in Methodology | Tagged , , | Leave a comment

Performance Testing – 201

In my career, I’ve done a few performance studies. (more than just a few). (I’m trying to be humble, but it’s not working). (Sorry). I’ve had some good mentors along the way, and I’ve done a lot of studying to … Continue reading

Posted in Optimization, Review, Testing | Tagged , , , | Leave a comment

Emerging from technical bankruptcy

The process for emerging from technical bankruptcy is actually similar to financial bankruptcy.  If you decide to pay-down the technical debt, instead of starting over, it means you need to change your current practices.  You have been living beyond your … Continue reading

Posted in Methodology | Tagged , , | Leave a comment

Management will prefer more tech debt (in so-many words)

Disclaimer: This is not about my current project or company. It is about all projects and companies, everywhere. If you are familiar with “technical debt”, I’m sure you would acknowledge: tech debt is bad, and if you allow it, you … Continue reading

Posted in IT Psychology, Lessons Learned, planning | Tagged , | Leave a comment

Why your projects don’t seem to get “done” (part 3)

Okay, so let’s say that you are a shrewd manager, and you are certain that your requirements are crystal-clear, your scope is contained, and yet, stuff isn’t getting “done”. In that case, part 1 & part 2 (of this article) … Continue reading

Posted in IT Psychology, Lessons Learned, Methodology, Professionalism, Team | Tagged , , , , | Leave a comment

Why your projects don’t seem to get “done” (part 1)

In my career, I’ve seen a few projects that had a problem getting “done”. Okay, I was being too nice. Let’s just say: it happens more-often than I think it should. I’ve even had a CIO mock me because I … Continue reading

Posted in Lessons Learned, Requirements | Tagged , | 1 Comment