technical debt refactoring software engineering

Limits of the technical debt analogy

The triangle of project management is a well-known model, used through and through since ages. I assume most software developers, even junior ones, are familiar with those: TimeCostScope As for my personal experience in the software industry, all projects have been behind schedule, with only a few exceptions for small projects (some man-months). The reason might probably because initial estimations were too low, either by accident or on purpose, but that is a subject best tackled in anothe

performance software engineering

Performance cost of reflection

In Java, it's widely admitted that reflection - usage of the java.reflect API, comes at a high cost in terms of performance. Older Java versions had huge performance overhead, while it seems that newer versions bring it in the acceptable range. But what does 'acceptable' really mean? This is the question I asked when commenting on a performance review that advised to replace code based on reflection by standard code.

software engineering versioning

What's the version of my deployed application?

In my career, I've noticed many small and un-expensive features that didn't find their way into the Sprint backlog because they didn't provide business value. However, they provided plenty of Return Over Investment during the life of the application, but that was completely overlooked due to short-sighted objectives (set by short-sighted management). Those include, but are not limited to: Monitoring in general, and more specifically metrics, health checks, etc. Environment data e.g. development,