Pinned post
Mateusz Stefańczyk
Verified account This account is verified. Learn more@m_stefanczyk
Google Developer Expert in Angular. Software Engineer & Angular Team Leader at @houseofangular | @AngularLovePL community member
394 Following 433 Followers 1.5K Posts
Latest posts 5
I can't believe that someone is one-shotting anything with Astra - I just made 1 task, on lowest effort mode - 9 lines of changes in simple code + browser verification, and already have 82% of the limit left for the upcoming 5 hours.
A new way of loading route data is coming. Resolvers aren't going anywhere, but Router resources fix their biggest pain: resolvers run sequentially parent → child, route resources run in parallel across the whole matched hierarchy.
200ms parent + 300ms child = 300ms instead of 500ms.
Opt-in via withRouterResources(). Shipping in 22.2.
200ms parent + 300ms child = 300ms instead of 500ms.
Opt-in via withRouterResources(). Shipping in 22.2.
Sneak peek into the #angular Router resources !View quoted post on X
They will be shiped in next week's pre-release and in 22.2 later this month !
next.angular.dev/guide/routing/…
One of the things I really don't like in terms of conversation with agents is that even my theoretical assumptions, or things I simply want to discuss, are added to memory and treated as true.
One of my agents asks another one to review its code before it hands anything back to me. I went and read the prompt it sends over.
Its code-quality checklist: OnPush, no class instances in state, naming, missing tests, design.md, comments, dead code, unused imports, style budgets.
What would you add?
Its code-quality checklist: OnPush, no class instances in state, naming, missing tests, design.md, comments, dead code, unused imports, style budgets.
What would you add?