Tag: architecture

  • Technical debt and vibe-coding

    When looking at any system as-it-is, my perspective remains: tech debt is the state of a system that captured the understanding of the problem when it was created and doesn’t fully reflect today’s understanding. The (obsolete) understanding applies to both functional and non-functional requirements, so it might be about the business, technical, scaling, or another…

  • First online article on technical debt

    Ward Cunningham introduced the metaphor underlying the term technical debt in a 1992 experience report, where he described how his company incrementally extended a piece of financial software: Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite. Objects make…

  • IcePanel: Design complex software systems

    Seems as an inovative way to document systems and make the knowledge transparent. –✁ Align on technical decisions across your software engineering and product teams