Explaining Angular to My Grandma
Trying to explain Angular to my grandma was a mistake... but here we are 😂. In this stand-up comedy bit, Dommy Bytes breaks down the difference between viewChild() and contentChild(), Angular's "view" vs. "content", and why debugging Angular sometimes feels like talking to a passive-aggressive roommate.
If you’ve ever wrestled with ExpressionChangedAfterItHasBeenChecked, fought with change detection, or questioned your life choices while using Angular, this one’s for you!
Topics Covered:
- What is viewChild() vs contentChild()?
- Why does Angular pretend not to see your projected content?
- Debugging Angular… or why your app silently judges you
- The real reason we all stick with Angular (Hint: Laziness)
If you’re an Angular developer, a frontend engineer, or just someone who enjoys developer comedy, SUBSCRIBE for more!
🚀 More Angular Comedy & Tutorials Coming Soon!
Get Ahead of Angular’s Next Shift
Most Angular apps today still rely on reactive forms, but that’s starting to shift.
Signal Forms are new, and not widely adopted yet, which makes this a good time to get ahead of the curve.
I created a course that walks through everything in a real-world context if you want to get up to speed early: 👉 Angular Signal Forms Course
