Full Stack Development: What Does It Really Mean?
summary
Search of LinkedIn shows ~7000 “full stack” results and the talk reframes the phrase into concrete CS tools and gotchas: ADTs and stacks, Hoare triples and given-when-then tests, partial vs total functions with Java/C++/Optional, a live-ish Python self-modifying stack demo that enforces dynamic interfaces, and a Go channel-based stack goroutine implementation with select/timeouts to illustrate the halting problem. Also shows how to test Liskov substitution and classifies problems as S/P/E for deciding testability.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:15Full Stack Development
- 7:32Stacks
- 10:25Programming by Contract Model
- 14:25Stack the Alphabet
- 16:00State Machines
- 17:15Nesting
- 20:28Throws
- 22:10Empty Stack
- 23:20Stack
- 25:25Class Stack
- 27:12Pop
- 28:10Queues
- 31:49Stack and Go
- 37:48The halting problem
- 40:47Lambda calculus
- 42:12Block and procedure
- 42:57Object orientation
- 46:37Non duplicate top
- 47:08Liskov Substitution Principle
- 48:08NonDuplicate Behavior
- 49:18Code as SP
- 52:32Conclusion
related talks
08mFull Stack Developers: Myth or Reality
55mThe Fuller Stack
45mBe Fullstack, because everyone should
41mWhy Full-Stack Is the Future of Web Application Development
08mFull-Stack Testing Ethos For a Progressive Team
25mBreak into full stack from Java
05mFull Stack Isn't Enough - The Rise of the Full Product Developer
35mDiscussion: Frontend or Fullstack