The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,640 other followers

Archive for the ‘Technical Debt’ Category

Technical debt: “taking shortcuts leads to long-term bleeding…”

Posted by jpluimers on 2019/07/19

From a while ago:

Just tried to explain technical debt: “taking shortcuts leads to long-term bleeding.”

[WayBack] – Jeroen Wiert Pluimers – Google+


Posted in Development, Software Development, Technical Debt | Leave a Comment »

The Spilled Juice Analogy for Technical Debt | Disciplined Agile 2.X

Posted by jpluimers on 2018/06/21

Interesting take on Technical Debt: [WayBackThe Spilled Juice Analogy for Technical Debt | Disciplined Agile 2.X

Not just because of the analogy, but also because of this comment by Ramu Iyer:

Conway’s Law states that software (or the structure of an IT system) mimics and is isomorphic to the organizational-social structure around it. In layman’s terms, a poorly designed software system is a vivid indicator of the underlying pattern of team communication, coordination and cooperation in the software team. Oftentimes, strained social and organizational interactions get in the way of smooth software development and operation. This results in social liabilities during intergroup coordination and accumulates “social debt” within or across one or more communities in a (software) organization. Any suboptimal socio-technical decisions also impact the technical debt of a software system in tandem. Digging one’s “way out of the technical debt pit” also requires the proactive mitigation of social debt around a system.

D. A. Tamburi, et al. Social debt in software engineering: Insights from the industry. Journal of Internet Services & Applications, 2015.


via: [WayBack] Vivid and better analogy than interest payments.The Spilled Juice Analogy for Technical Debt #technicaldebt – Marjan Venema – Google+


Posted in Development, Software Development, Technical Debt | Leave a Comment »

Technical Debt – Dilbert Comic Strip on 2017-01-03 | Dilbert by Scott Adams

Posted by jpluimers on 2017/01/03

Is it funny because it so true? Would it be funnier if it weren’t true?

  • Boss: Did you finish the software yet?
  • Dilbert: No, I’m still paying off the technical debt from the last programmer you rushed.
  • Boss: I don’t know what that means.
  • Dilbert: Well, that explains a lot.

[WayBackTechnical Debt – Dilbert Comic Strip on 2017-01-03 | Dilbert by Scott Adams


Read the rest of this entry »

Posted in Development, Fun, Technical Debt | Leave a Comment »

Extreme Programming, a Reflection (via: 8th Light)

Posted by jpluimers on 2013/12/29

Thanks Uncle Bob Martin for posting this.

I’ve been trying (with increasing success: it takes time to get this all right) to practice XP (through various name changes) as much and wide as possible since almost 14 years, and only the last few years it is starting to be common practice for many more people.

take a moment to reflect back on 1999. A time when Kent Beck wrote a ground-breaking book. A book that changed everything. Look back and remember: Extreme Programming; and recognize it as the core of what we, today, simply think of as:

Good Software Practice.


via: Extreme Programming, a Reflection | 8th Light.

Posted in .NET, Agile, Continuous Integration, Delphi, Design Patterns, Development, Software Development, Source Code Management, Technical Debt, Testing, Unit Testing | Leave a Comment »

Reminiscence of the past: Delphi I/O error 131

Posted by jpluimers on 2013/08/06

I was called by a client that didn’t want to do maintenance on an old Delphi application, but wanted to get dir of an I/O Error 131:


MessageText: An attempt was made to move the file pointer before the beginning of the file.

Tough luck: psychic powers told me someone is using an unsigned 32-bit integer to access a file using traditional style Assign/Reset/Seek/Read/Close patterns that Delphi kept as intrinsic routines for Turbo Pascal backward compatibility, and that file has grown over 2 gigabyte in size.

I quickly found an import file had grown over the 2 gigabyte, so this was indeed the case.

The original developers didn’t do the file access using the 64-bit Seek/Position of the TStream descendant TFileStream.

Too bad, as now someone has to dig through the mothballs to find the sources (if they survived 3 different version control system switches), create a working development environment, and fix the bug.

Another instance where technical debt in IT raises its ugly head and the compound interest is really expensive.


via: – IO Errors in Delphi.

Posted in Delphi, Delphi 5, Development, Software Development, Technical Debt | 14 Comments »

%d bloggers like this: