Category Archives: Lessons Learned

Training your manager

Disclaimer: This is not about my current workplace. This is about all workplaces. Whether you are a team lead, software architect, PM or a junior developer, you count on your team for stuff. Maybe if you are a one-man-team, you … Continue reading

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

Magnitudes of technical debt

The term “technical debt” really covers a lot of areas of concern. It is not simply relegated to “messy programming”. That is part of it, but there is more to it. Like with many unpleasant things, the impact of technical … Continue reading

Posted in Architecture, Lessons Learned, Review | Tagged , , | Leave a comment

LLT – M53: unknown product code (add it in ‘LLT.prm’ file)

Once again with the LLT. I just got a new PC and had to reinstall all of my software and re-learn the tricks for connecting LLT, etc.  Btw, the help file for LLT has better directions than the rest of … Continue reading

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

LLT_LOAD – RAS Error 633

Today, I needed to upgrade the RBA for my device.  I started by using LLT to set up my connection and make sure everything worked.  I worked-out the configs and was able to get a file list in LLT.  So … Continue reading

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

Why management wants more technical debt

*** Disclaimer: this is not about my current project. It is about every project. *** I think it is safe to say that every program contains some technical debt.  This is because perfection is (somewhat) impractical.  If you actually try to achieve it, … Continue reading

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

Technical Bankruptcy

*** Disclaimer: This is not about my current project, it is about every project everywhere *** Technical-debt is a natural byproduct of software development.  If you don’t recall seeing technical debt in every sw-dev project, it is because most developers prefer to … Continue reading

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

Architectural review phrase book

When a project is in its early stages, (or sometimes, much later), it is time to have your system designs and software/system architecture reviewed. When this happens, it is not unusual to have a difference of opinion with your reviewer(s).  In … Continue reading

Posted in Lessons Learned, Professionalism, Review | Tagged | Leave a comment