Best of AgileMay 2025

  1. 1
    Article
    Avatar of workchroniclesWork Chronicles·50w

    (comic) I need you to be agile

    A humorous comic highlights the challenges and expectations in adopting agile methodologies within workplace dynamics, emphasizing the gap between management's demands and practical implementation.

  2. 2
    Article
    Avatar of thedevcraftThe Dev Craft·1y

    Entropy in Teams: The Silent Productivity Killer

    Software teams naturally deteriorate over time due to entropy, where processes that once worked efficiently become bloated and ineffective. The solution involves constant maintenance through entropy-focused retrospectives, regular documentation updates, and dedicated improvement budgets rather than waiting for major interventions. Success comes from consistent small actions that prevent disorder from accumulating.

  3. 3
    Article
    Avatar of infoworldInfoWorld·1y

    Technical debt is just an excuse

    Technical debt is often misused as an excuse for poor coding practices. Originally, it represented deliberate decisions to write sub-par code temporarily, with a plan to address it later. However, it has become a label for all bad code, which can stem from accidental complexity or rushed development. To reclaim its true meaning, only code with a planned fix should be labeled as technical debt. Anything else should be recognized as code rot.

  4. 4
    Article
    Avatar of microservicesioMicroservices.io·51w

    Microservices rules #8: Design independently deployable services

    Designing independently deployable services is a key principle in microservice architecture. This concept involves creating services that can be deployed and updated without affecting other components, leading to greater agility and efficiency. The post discusses the importance of this characteristic, common pitfalls such as reliance on end-to-end testing, and strategies for transitioning to more flexible deployments.

  5. 5
    Article
    Avatar of devsquadDev Squad·50w

    The Development Process

    The post humorously describes a chaotic development process where coding is done sober, code is pushed while drunk, and debugging while hungover, with releases driven by spite. It contrasts this approach with agile and clean methodologies, highlighting the challenges faced by developers.