Stop writing software like it's 1999! - Hannes Lowette - NDC Copenhagen 2026

Value of the Information & Strength of the Argument

The talk provides valuable insights into common software architecture pitfalls and offers practical alternatives. The speaker’s argumentation is clear and structured, using relatable analogies and personal anecdotes. He effectively contrasts the historical context of these practices with modern development realities, making a compelling case for change. However, the arguments are largely based on anecdotal evidence and personal experience rather than empirical data, which limits their generalizability. The suggestion to use modular monoliths is well-reasoned and aligns with current industry trends, but the talk could benefit from more concrete examples or case studies.

Scientific Rigor, Source Quality, Title Accuracy

The talk is an expert opinion without formal citations, but it references well-known concepts and practices in software engineering. The speaker mentions Sam Newman’s book on microservices and the concept of service-oriented architecture, but does not provide specific sources. The title accurately reflects the content, and the talk is coherent and well-structured. The lack of external references is a minor weakness, but the speaker’s credibility and practical experience lend weight to his arguments.

The title accurately reflects the content: the speaker argues that many current software practices are outdated and should be modernized.

7/10

The talk is an expert opinion based on two decades of industry experience, with practical examples and references to established concepts (layered architecture, microservices, modular monoliths, CI/CD). It lacks formal citations or empirical data, but the arguments are coherent and align with common software engineering practices.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 02:00Introduction: speaker confesses nervousness and explains the talk's premise.
• 05:00Audience exercise: raising hands if they shipped code using 1990s practices.
• 10:00Discussion of layered architectures and their historical context.
• 15:00Problems with layered architectures in modern agile development.
• 20:00Alternative: organizing code by feature, with benefits for developer productivity and AI context.
• 25:00Introduction to microservices and their origins in SOA.
• 30:00Pitfalls of microservices: operational overhead, context switching, and cross-cutting concerns.
• 35:00Advocacy for modular monoliths as a default architecture.
• 40:00Case study: a customer project suffering from lack of CI/CD and formalized specifications.
• 45:00Importance of CI/CD from day one, with automation and continuous delivery.

• NDC Conferences — Conference website where the talk was recorded.
• NDC Copenhagen — Specific conference event page.

• Sam Newman - Building Microservices — Referenced in the talk as a key book on microservices.