Ng-News 25/25: "Charted" Coding, SSR & Incremental Hydration

Younes Jaaidi shares a structured way to approach AI-assisted coding, breaking it into stages with clear roles for humans and machines. Meanwhile, Michael Hladky dives into SSR and Incremental Hydration in Angular, showing their impact on browser rendering and performance.

"Charted" Coding

When using — or trying to use — AI in programming, we’re often confronted with uncertainty. Not just because AI sometimes "lies" to us (aka. hallucinations), but also because even simple tasks often take multiple frustrating iterations and still don’t deliver satisfying results. It can feel like a waste of time.

On the other hand, we’re often told it is our fault because "the prompt isn’t good enough".

Younes Jaaidi published a video that tries to set expectations straight.

It’s almost like a live coding session, where you see the same challenges in real time—how he deals with them and how he structures his process.

Younes calls his approach "Charted" Coding (a wordplay inspired by sailing).

He splits the development process into stages, and for each stage defines a different ratio of manual vs. AI-generated work. The planning phases — writing design docs and specifying tests — require the most manual effort.

It’s a feature-rich video with lots of practical insight and some clever gotchas along the way (like small MCPs sprinkled in).

Angular’s AI Guidelines

The Angular team has also published official rules for IDEs that use AI to generate Angular code. These guidelines are meant to improve the quality of generated code by aligning it with Angular best practices.

While most of the rules reflect common-sense coding standards, one recommendation stands out: prefer reactive forms over template-driven ones.

Deep Dive: SSR & Hydration

Michael Hladky (from PushBased ) is well known in the Angular community for his work and talks on performance.

He recently published a three-part series on SSR and Incremental Hydration, explaining how they work, how they integrate with browser rendering, and what impact they have on Core Web Vitals.

At the time of this recording, the full series is already available:

Signals and Reactivity: Explained

Evgeniy Tuboltsev published a deep-dive article on the relationship between reactivity and Angular’s rendering model.

He explains why Signals outperform Observables in many scenarios and emphasizes the importance of immutable state changes for performance and predictability.