Younes Jaaidi

Younes Jaaidi

@younesjd.dev

👨🏻‍🍳 Software Cook, Teacher & Coach @ https://marmicode.io ✨ Google Developer Expert for #Angular 🌊 Nx Champion ✅ https://marmico.de/test.ng: Pragmatic Angular Testing Course 👨🏻‍🏫 https://marmico.de/workshops 📚 https://marmico.de/cookbook

984 followers 135 following350 posts

Pinned

🚨 Tired of tests that: – block your refactoring – slow you down – chase 100% coverage but miss real bugs – kill your confidence? 👉 That's why I made Pragmatic #Angular #Testing course: marmico.de/test.ng 🎓 Lifetime access — 80€ ✅ Free updates & new modules included

#Vitest Browser Mode module is live in Pragmatic #Angular Testing. - Catch bugs, not false positives: user can't click it, test can't either. - No more `detectChanges`, `whenStable` or `waitFor`. - 🌗 Partial vs. 🌕 full browser mode, and how to migrate progressively. 👉 marmico.de/test.ng

C’est ce soir ! EnterpriseJS à SupInfo Lyon 🎉 On essaie de résoudre ces problèmes ensemble : 😵 Review fatigue : des PRs générées en quelques minutes… suivies d'heures de review ⚓ Biais d’ancrage : l’agent nous influence subtilement 🚣 Dérive fonctionnelle et architecturale

No more detectChanges / whenStable / waitFor. Real-browser #Angular tests with #Vitest 5 + Angular 22, written so your agent can't fake a green run. The Browser Mode module of Pragmatic Angular #Testing goes live tomorrow. Last day at €80, then €120.

If your tests lie, how do you expect your agent to get it right? This test passes in a real browser. But the "Add" button is hidden behind a salad 🥗 🎁 The fix: the new #Vitest Browser Mode module of Pragmatic #Angular #Testing. Live Fri Oct 16. €80 until Thu, then €120.

The course is here marmicode.io/test.ng

marmicode.ioPragmatic Angular Testing Course | MarmicodeFire in the kitchen? Are you tired of bugs or unmaintainable tests slowing you down? Join this course to learn how to adopt a pragmatic testing strategy and cook better apps.

User expectations drive engineering priorities. Half a century of innovation to reach single-digit latency... in milliseconds. The new SLA: single-digit latency... in seconds... to display: Great question! • thinking...

I got tired of burning tokens, and worse, review time on Jest to @vitest.dev migrations, so I built Vitestify, a CLI that does it for you. npx @testmex/vitestify 🎯 Deterministic & beyond test files: configs, setup files, mocking APIs... 🪜 Incremental: tests that fail keep running under Jest 🧵

🔄 Re-runnable: run it again as your suite, and Vitest, evolve ↩️ Safety net: runs Vitest, rolls back only the failing tests 🧩 Tooling aware: #Angular CLI, #Nx, #React, Testing Library... 🚧 Coming next: Agent instructions for the non-deterministic edge cases #javascript #testing

and docs are here testmex.dev

Younes Jaaidi reposted

@vladimir.berlin

`vmThreads` is 30% faster in Vitest 5 for your jsdom tests. It is now a much better alternative to the default forks+jsdom. Vitest 5 also comes with a `vitest doctor` command that will find the best settings for you! As a note, browser mode also becomes ~30% faster, but for different reasons :)

🍿 Reviewing a PR is like watching the last five minutes of a movie and being asked whether the plot made sense. The thing about Charted Coding (github.com/marmicode/sk...) is that it breaks a feature into small intent-driven commits: 🧵 #AI #AIAssistedDev #ChartedCoding #TDD

View full thread

👀 Reviewer routing. Maybe one person takes the design doc and another takes the implementation. See who reviewed what, at the commit level. Still early, but I'm curious how you deal with this? and if such an OSS tool would be useful to you and what you would except from it?

Obviously, diffing, comments etc... are still handled by your current tools (e.g. Github)

🍿 Reviewing a PR is like watching the last five minutes of a movie and being asked whether the plot made sense. The thing about Charted Coding (github.com/marmicode/sk...) is that it breaks a feature into small intent-driven commits: 🧵 #AI #AIAssistedDev #ChartedCoding #TDD

View full thread

🫠 The problem is that most tooling is PR-first. I want to read the story, not just the last scene. So I'm exploring a commit-first review tool: 🔥 A heat map of review cost, so attention goes where it matters.

🏷️ Tags for each Charted Coding step (design, scaffold, red, green, ...), so a reviewer knows what kind of change they're looking at. 🤖 More importantly, it should tell if the AI commits were supervised or not.

🍿 Reviewing a PR is like watching the last five minutes of a movie and being asked whether the plot made sense. The thing about Charted Coding (github.com/marmicode/sk...) is that it breaks a feature into small intent-driven commits: 🧵 #AI #AIAssistedDev #ChartedCoding #TDD

- design doc, - scaffolding (the noisy boilerplate), - failing test, - making the test pass. That sequence is the review. You can watch the feature get built, decision by decision.

A few days ago, while coaching a team. They showed me this Angular code... ... it turns out that the ubiquitous language of chromatography data systems (en.wikipedia.org/wiki/Chromat...) overlaps almost perfectly with #Angular 's. 😄 #javascript

Younes Jaaidi reposted

Rainer Hahnekamp

@rainerhahnekamp.bsky.social

At Google I/O Connect, we got the chance to record in a professional studio. So I asked my three “Angular Buddies”, @younesjd.dev, Marko Stanimirović, and @manfredsteyer.bsky.social to join me for a conversation about #Angular. Signals, what is still missing, and AI. 🎥 youtu.be/0_NsqGF8gM8

youtu.beWhat’s Next for Angular? Google I/O Connect Berlin RoundtableYouTube video by Rainer Hahnekamp

Nothing changed since the 20th century. Waterfall is still broken and AI just makes us hit the wall faster… but still not soon enough to make it a good feedback loop. The instinct is to want faster, smarter agents, or more agents judging each other. 🧵

View full thread

In the meantime, here's an example where I measured “Common” usage of Spec Kit vs. Charted Coding. Note that on token usage, Spec Kit almost ties, but only if you accept everything and it all goes well. That's the Waterfall bet, and it rarely pays.

What matters most here is the review cost and steering opportunities.

Nothing changed since the 20th century. Waterfall is still broken and AI just makes us hit the wall faster… but still not soon enough to make it a good feedback loop. The instinct is to want faster, smarter agents, or more agents judging each other. 🧵

View full thread

Small steps. Tight loops. Cheap reverts. That's the whole game, and none of this is new. It’s just some of the core values of Kent Beck’s eXtreme Programming: feedback, and courage — the courage of reverting.

Wanna dive more into this or share your feedback, because I need more of it? See you Thursday live on #NgAsiaAngular YouTube channel youtube.com/@NgAsiaAngular

Nothing changed since the 20th century. Waterfall is still broken and AI just makes us hit the wall faster… but still not soon enough to make it a good feedback loop. The instinct is to want faster, smarter agents, or more agents judging each other. 🧵

View full thread

The trick is making every step small enough that validating or reverting costs nothing. Around 1 minute to produce. A few minutes to review. And then, every time: continue, or revert and try again.

Cheap reverts close doors to slop. When steps are small, drift has nowhere to hide — the wrong turn shows up in a few dozen lines, not 600. And because you review right after each step instead of babysitting a long run, you stay focused.

Nothing changed since the 20th century. Waterfall is still broken and AI just makes us hit the wall faster… but still not soon enough to make it a good feedback loop. The instinct is to want faster, smarter agents, or more agents judging each other. 🧵

View full thread

- 🛶 The Drift: the slop and unwanted behavior that slips through the review, and whatever your harness is made of, - 🔁 The Context Switching: yes, multi-agent views look cool... but most humans are bad at multi-tasking (I'm among the worst 😅),

- 💰 The Sunk Cost Fallacy: we wait 10 min for the agent, spend half an hour reviewing, and end up... not really convinced. But reverting means throwing all that time away, so we ask the agent to patch on top instead. Now we’re building on something we already don't trust.

Nothing changed since the 20th century. Waterfall is still broken and AI just makes us hit the wall faster… but still not soon enough to make it a good feedback loop. The instinct is to want faster, smarter agents, or more agents judging each other. 🧵

But I still believe the real move is smaller steps — at least for complex or original features. The real cost is not token usage, and it's not even the review cost. It's what the loop does to you:

Bye #GoogleIOConnect @shairez.bsky.social @eliraneliassy.bsky.social

If you’re at #GoogleIOConnect and wanna chat about where AI-Assisted Dev, Testing, and sailing meet with Monorepos and Polyrepos, come hang out I’m under the A/C by the Modern Web Guidance booth #angular #testing #nx

#GoogleIOConnect is kicking off

Younes Jaaidi reposted

🚀 Vite 8.1 is out ⚡ Experimental Full Bundle Mode: ~15x faster dev server startup & ~10x faster full reloads on large apps 🧩 Chunk Import Map to keep chunks stable & improve caching 🦀 WASM ESM integration 💡 Lightning CSS on the road to default 👀 and more! vite.dev/blog/announc...

vite.devVite 8.1 is out!Vite 8.1 Release Announcement

🤯 I had the chance to play with #Polygraph early — and it just fixes the messy reality of AI-assisted dev: collaborating with other devs, and across multiple repos. Can't wait for you to try it. Watch it launch live today 👇 🎁 Bonus: many amazing talks about #ai ❤️ #monorepo monorepo.tools/conf

monorepo.toolsAI ❤️ Monorepos · Conf 2026A free half-day virtual conference for engineers working at the intersection of monorepos, CI, and agentic AI. June 23, 2026.

Younes Jaaidi reposted

Aboogail Screamini

@abbeyperini.dev

@younesjd.dev 's talk Ashes to Ashes, Spec to Spec: The Rebirth of Modern Testing at #ReactSummit

Just landed in Amsterdam. This church says roses bloom even in bleak winter. 🥀 Good — we’ll need flowers for tomorrow’s service at @reactsummit.gitnation.org: one last goodbye to our old testing frameworks, and what’s next with @vitest.dev… and more 🎁 Ashes to ashes, spec to spec. ⚰️

With AI-Assisted Development, your #Angular tests become the agent's main feedback loop. Brittle tests = noise. A focused suite = clear signal: what works, what broke, what's next. The #testing strategy matters more than ever. Early bird closes Friday 👇 marmicode.io/workshops/pr...

Younes Jaaidi reposted

@ariperkkio.dev

Building this integration has been amazing opportunity to dogfood all APIs we've added into @vitest.dev in past years. It's using features like new Reporter APIs, Vitest plugin hooks, browser commands, CDP, test tags and much more! Vitest is definitely one of the most extensible JS tools out there.

Chromatic@chromatic.com

We’re launching early access for Vitest visual testing with Chromatic! ⚡️ Built with @vitest.dev core maintainer ariperkkio.dev, Chromatic adds visual testing to the browser tests you already write. 🧵 (1/4)

Thanks Logan. It made me realized that I wasn't following most of my friends 😅

This post is unavailable.

#NgBaguetteConf keeps getting bigger every year — great job! Genuinely useful talks back to back, and a crowd that was as enthusiastic as they come. The questions afterward were the gems I'm looking for at confs. ...

Now, about live AI-assisted demos: we all dread the agent going rogue mid-talk... but this time, it's the smoke machine that did not behave 💨. ...

Also, Jean-Sébastien Butcherton stole 5 minutes of my slot and got fired on stage. So long Jean-Sébastien 👋. By the way, you forgot an onion on stage 🧅. Thank you all for the warm welcome 🤗 and see you soon!

#NgBaguetteConf is kicking off, and we’re both ready! Let’s see where AI-assisted development and testing meet… 🧭

#NgBaguetteConf is in 2 days and we still haven't agreed on much with @butcherjs.dev for our keynote talk... 🤷🏻‍♂️

🦸 The legends who stayed till the very end of yesterday's #ReactSummit Pragmatic Testing workshop. I love how @vitest.dev + a resilient testing strategy makes tests look the same across frameworks.

👨🏻‍🏫 Next full Pragmatic Testing workshop sessions: → 3-day #Angular — 🗓️ June 16: marmicode.io/workshops/pr... → 3-day #React — 🗓️ September (waitlist open): marmicode.io/workshops/pr...