Best of Technical Debt — 2023

  1. 1
    Article
    Avatar of pointerPointer·3y

    Random Thoughts 15 years into Software Engineering

    The author shares insights and lessons learned from their 15 years in software engineering, including the importance of avoiding absolutes, considering debuggability, managing scope, and taking ownership of systems.

  2. 2
    Article
    Avatar of discdotDiscover .NET·3y

    Underrated skill as a developer

    CodeOpinion Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

  3. 3
    Article
    Avatar of stackovStack Overflow Blog·2y

    Stop saying “technical debt”

    The post explores the concept of tech debt and its implications on feature development. It emphasizes the need to redefine tech debt and offers code stewardship practices to minimize maintenance load growth.

  4. 4
    Article
    Avatar of stackovStack Overflow Blog·2y

    Self-healing code is the future of software development

    Large language models have the ability to improve their output through self-reflection, which is beneficial in software development and CI/CD. Self-healing code is being explored as a way to automate solutions and improve code quality. However, there are concerns about the quality and volume of code generated by AI. Companies will need to develop best practices to effectively use generative AI in software engineering.

  5. 5
    Article
    Avatar of communityCommunity Picks·3y

    My 20 Year Career is Technical Debt or Deprecated

    The post discusses the concept of technical debt and the author's personal experience with how technologies and languages have become deprecated or considered technical debt over their 20-year career.

  6. 6
    Article
    Avatar of pointerPointer·3y

    Generating Code without Generating Technical Debt?

    Unsplash GPT and other large language models can produce huge volumes of code quickly. This allows for faster prototyping and iterative development, but it can also leave us with a bigger amount of mess code to maintain. The GPT best practices described by OpenAI can help with code generation as well.

  7. 7
    Article
    Avatar of abinodaSoftware Engineering Research·3y

    How Google Measures and Manages Tech Debt

    A behind-the-scenes look at how Google approaches technical debt. This week I read a paper by Google researchers Ciera Jaspan and Collin Green. The paper describes Google's approach to defining and measuring technical debt, along with their efforts to manage it.

  8. 8
    Article
    Avatar of stackovStack Overflow Blog·2y

    Is software getting worse?

    Apps are getting slower and larger without a corresponding increase in value. There are optimization opportunities in modern apps, but the market focus on features and the expectation of free software hinder developers from prioritizing speed, reliability, and smaller app sizes. Software engineers have the power to improve the situation but face challenges in changing the industry's incentives. However, there are reasons to be hopeful for the future, including new technologies and a growing awareness of the cost of software.

  9. 9
    Article
    Avatar of hnHacker News·3y

    Oh my poor business logic

    Adopting existing tools and focusing on core business logic is underrated. Technical people face problems in companies that care only about measurable outcomes or become engrossed in techno-maximalism. Useless metrics can hinder developer productivity. Finding a middle ground is crucial.

See all Technical Debt archives