Younes Jaaidi lays out a deliberate, stage-by-stage methodology for working with AI in coding, assigning each phase clear responsibilities for both developer and machine. In parallel, Michael Hladky explores how Angular's SSR and Incremental Hydration shape browser rendering behavior and the resulting performance picture.
"Charted" Coding
Working with AI in software development frequently involves a fair amount of guesswork. The tool might confidently produce incorrect output, and even straightforward assignments can burn through many attempts before yielding anything useful, making the whole exercise feel unproductive.
At the same time, the common refrain is that the operator is to blame, usually for not crafting a "good enough prompt."
A recent video by Younes Jaaidi aims to correct those expectations.
The format resembles a live coding session where you watch the same obstacles appear in practice—how he navigates them and what kind of structure he applies to his workflow.
His answer is what he calls the "Charted" Coding method, a term that plays on nautical terminology.
Development is broken into distinct phases, each with its own split between human effort and AI-generated output. The early groundwork, specifically authoring design documents and laying out test specifications, demands the most hands-on attention from the developer.
The video packs considerable practical material, along with a few neat tips scattered throughout, such as selective use of small MCPs.
Angular’s AI Guidelines
Official guidance for AI-powered IDEs generating Angular code is now published by the Angular team. The intent of these rules is to steer generated output toward accepted Angular conventions, ultimately raising its quality.
A large part of the list covers expected coding hygiene, but one item draws attention: favor reactive forms rather than template-driven ones.
LLM prompts and AI IDE setup • Angular
The web development framework for building modern apps.
angular.dev
Deep Dive: SSR & Hydration
Michael Hladky of push-based.io has established a solid reputation within the Angular ecosystem through his performance-focused talks and writing.
His newly released three-part series covers SSR and Incremental Hydration, detailing their inner workings, their relationship to the browser's rendering pipeline, and the resulting effects on Core Web Vitals.
As of this recording, the entire series has been released:
Incremental Hydration in Angular: Introduction (Part 1/3)
Incremental hydration is a new feature in Angular that impacts performance metrics like INP & LCP, while also reducing the effort to maintain CLS at low levels.
push-based.io
The Game-Changing Impact of Incremental Hydration in Angular (Part 2)
Learn how to use SSR, @defer, and hydration triggers in Angular to improve load time, reduce JS overhead, and boost Core Web Vitals.
push-based.io
Implementing Incremental Hydration in Angular (Part 3/3)
Implement incremental hydration in a real-world Angular app - Basic setup, hydration triggers and important considerations for a seamless integration.
push-based.io
Signals and Reactivity: Explained
An in-depth blog post from Evgeniy Tuboltsev examines how the notion of reactivity connects with Angular's rendering architecture.
He makes the case for why Signals are often preferable to Observables, and stresses that treating state updates as immutable is key to maintaining predictable behavior and solid performance.
Medium