Talk
Whose Stack Is It Anyway?
Examining the evolution of the full stack developer concept and the complexities of truly mastering all layers of the technology stack.
Stick To The Script Leeds, UK 1 min read
This talk examines the evolution of the “full stack developer” concept from 2013 to 2023, exploring how software relies on layered abstractions and the complexities of truly mastering all components.
Core Concepts
- Definition of “stack” as both data structure and technology collection
- OSI and TCP/IP networking models as abstraction frameworks
- Popular solution stacks: LAMP, MEAN, MERN, JAM, WAMP, T3
Technical Deep Dives
- JavaScript language specification vs. environment-specific implementations
- V8 engine execution: parsing, interpretation, and JIT compilation
- Bytecode generation and machine code optimization
- Browser vs. Node.js contexts and their distinct APIs
Implementation Examples
Looking under the hood at how common JavaScript features are actually implemented:
- Object.defineProperty (C++ implementation in V8)
- Array.prototype.sort (Torque implementation using Timsort algorithm)
- fetch() API (Fetch Living Standard, Node.js implementation via Undici)
Key Advice
Being truly full-stack is likely impossible, but we should build comfort through foundational knowledge rather than framework-specific expertise. Junior engineers should avoid narrow specialization, and senior engineers should mentor these principles.