Be Fullstack, because everyone should
summary
Claim: everyone should become at least a bit full stack because a T-shaped engineer avoids blocking dependencies and delivers faster. Examples: a backend feature stalls for two weeks when the lone frontend dev is on vacation; a frontend POC fails to prove value without basic backend and DevOps skills; a new team lead cannot manage unknown domains. Learning uses web resources (search, Wikipedia, YouTube) and the rapid improvement phase to reach proficiency quickly.
AI-written summary · about
chapters (6)
- 0:00Start
- 12:18aka Business Need
- 14:53aka Point to Prove
- 17:35aka Leader
- 22:06What is the Alternative?
- 24:57Learning Curve
related talks
08mFull Stack Developers: Myth or Reality
41mWhy Full-Stack Is the Future of Web Application Development
01h 01mThe world needs full-stack craftsmen
08mFull-Stack Testing Ethos For a Progressive Team
05mFull Stack Isn't Enough - The Rise of the Full Product Developer
35mDiscussion: Frontend or Fullstack
54mFull Stack Development: What Does It Really Mean?
55mThe Fuller Stack