The 7 Battles of Software Architecture: How to Protect Your Project!

on YouTube ↗36m

" summary

Seven concrete early decisions prevent huge rework: use reference labels for localization (one startup’s hack forces 5 days vs 2 weeks of fixes for Portuguese), plan deletion and HTTPS from day one, prefer off‑the‑shelf auth and documented APIs for extensibility, write developer onboarding to avoid hidden 10‑hour/week taxes, keep release notes public, test with ~5 real users for acceptance, and design for 8% red-green color blind and keyboard use for accessibility.

AI-written summary · about

" chapters (3)

1. 0:00Introduction
2. 0:29Session "Seven Righteous Fights" by Heidi Waterhouse
3. 36:00Outro

" related talks

• 30mThe seven righteous fightsHeidi Waterhouse · The Lead Developer 2016
• 47mHow To Build Future Proofed ApplicationsPeter van Vliet · Build Stuff 2024
• 47mMaking architecture decisions, the Agile WayNic Wortel · Dutch PHP Conference 2024
• 50mTactics and strategies on software development: how to reach ...Otavio Santana · GeeCON 2023
• 40mBuild Better SoftwareMahesh Chand · Code Quality Conference 2022
• 45mFive things every developer should know about software architectureSimon Brown · Voxxed Days Bucharest 2024
• 45mGeneric or Specific? Making Sensible Software Design DecisionsBert Jan Schrijver · GOTO Amsterdam 2023
• 41mThe lost art of software designSimon Brown · Agile meets Architecture Berlin 2022