Full stack architecture

on YouTube ↗32m

" summary

Pragmatic advice for Laravel teams: choose architecture by concrete tradeoffs not buzzwords — adopt vertical slices, build a monkey proof of concept early (example: touchscreen showroom needing fast user switching solved with simple auth POC), expect migration pain when data was modelled as generic attributes, and beware search limits when mixing marketplace and catalog items with Laravel Scout. Also set explicit laws, responsibilities, glossary and milestones so decisions are codified and revisited, and measure whether each slice actually works before committing.

AI-written summary · about

" chapters (17)

1. 0:00Start
2. 1:01Reflecting on career progression pressure and why levelling up is harder than it looks in software
3. 2:00Jo’s agency background, the many hats she wears and misconceptions people have about full stack roles
4. 3:10Contradictory architectural advice, confusion and decision paralysis in real world teams
5. 4:30How different disciplines define architecture differently
6. 5:33A spectrum of architectural fields
7. 6:45Planning models and migrations before ever touching the UI
8. 8:10How users access information, distinct from how developers store it
9. 9:20Why bottom up, layer by layer thinking causes disconnects between backend planning and frontend execution
10. 10:45Why separating system design and UX leads to brittle products
11. 12:00Architecture as holistic thinking across the entire product, not isolated technical decisions
12. 13:15Small teams, limited time, and the need to prioritise what moves projects forward
13. 14:20How user research, content strategy and UI decisions intertwine with backend decisions earlier than teams expect
14. 15:40Why small teams should adopt vertical slice development instead of horizontal layers
15. 17:05Milestones as flexible, project based checkpoints rather than rigid sprints
16. 18:40Making architectural discussions easy, async friendly and tied to outcomes
17. 19:58Embrace full stack collaboration

" related talks

• 40mEngineering Complex Applications with Laravel 4Kapil Verma · Laracon EU 2013
• 38mCrafting maintainable Laravel applicationsJason McCreary · Laracon AU 2019
• 49mLaravel - If, how and why you should use it!Martin Westphal, Neo Ighodaro · code.talks 2019
• 29mLuke Downing :: Lessons from the Laravel FrameworkLuke Downing · Laracon EU 2024
• 58mDesigning for change with Vertical Slice ArchitectureChris Sainty · NDC London 2024
• 21mSoftware Design Patterns in Laravel 4Phill Sparks · Laracon EU 2013
• 40mSOLID Architecture in Slices not LayersJimmy Bogard · Øredev 2016
• 25mLess Pain with Gain, how Laravel helps you scale your ApplicationsMartin Westphal · Laracon EU 2019