Fredrik wants to think about long-lived code. Lars is offended, Andreas only a little bit so.

Are there other good software development practices out there? Other than the ones focusing on building something quickly? Practices for building software which lives on and is maintained for much longer than we seem to care to admit? Should we remove dependencies over time? The swamp of dependency management and vendoring is probed, gradually shifting into firmware, the horrors of floating point (proper excuses are made), small language models.

Finally, of course, indecent cups of tea.

Links

• Lagom
• React
• Flux architecture
• Redux
• Changelog episode with Justin Searls about dependencies as liabilities
• Kent Beck talking about managing risks in software development
• Kent Beck drawing on a whiteboard and staring at the audience
• Mithril.js
• Interact.js
• Vendoring
• Working effectively with legacy code - the book about legacy systems
• Delphi 5
• Flask
• Dynamic linking
• SAML
• POSIX
• Libc
• Glibc
• Musl
• H.264
• Microcode
• Oxide and friends
• Coral TPU:s
• Tensorflow lite
• 286
• Pentium
• CUDA
• ROCm
• Quantization
• LLaMA