<h2>Must know</h2>
<ul>
<li><strong>TypeScript compiler rewrite promises 10x speedup</strong>: The TypeScript team is rewriting its compiler in Go, aiming for a 10x performance boost in type checking with TypeScript 7. This shift, focusing on error clarity and agent-friendliness over new features, means TypeScript 6 is the last JavaScript-based version. It also deprecates legacy features and module resolutions, aligning with the Go-based future. <a href="https://app.daily.dev/posts/hoJQMf3s6" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Frontend developer role expands to full-stack devops</strong>: The ‘pure’ frontend developer is a dying breed. Modern frontend roles now demand full-stack and DevOps skills, driven by React Server Components, edge functions, and infrastructure-as-config. Job listings increasingly require ORM usage, CDN invalidation, and CI/CD, traditionally backend or DevOps tasks. Developers need to adapt by upskilling in areas like Server Components, edge functions, and observability, or risk being left behind. <a href="https://app.daily.dev/posts/RXxBjrWnR" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>AI agents are transforming software development, but with a catch</strong>: AI agents are rapidly changing how we build software, with tools like Cursor and Claude Code enabling developers to generate significant portions of code and even entire applications. Spotify claims its top developers haven’t manually written code in months, relying on AI. However, this shift introduces new challenges: a ‘comprehension gap’ where developers ship code faster but understand less, and a ‘review bottleneck’ as AI-generated code overwhelms human review capacity. The focus is shifting from writing code to orchestrating AI, defining intent, and rigorously verifying AI outputs. <a href="https://app.daily.dev/feed-by-ids?id=7hHra6Ai0&amp;id=Bl6akHr3q&amp;id=ZrBLHCGzU" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
<h2>Good to know</h2>
<ul>
<li><strong>Vitest 3.x crushes Jest 30 in performance benchmarks</strong>: Vitest 3.x is significantly faster than Jest 30, showing 5.6x faster cold starts and 28x faster watch mode re-runs in a 50,000-test monorepo. It also uses 57% less memory, making it a strong contender for projects already using Vite or struggling with ESM issues. <a href="https://app.daily.dev/posts/T3G4VUzdk" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Laravel introduces official svelte starter kit</strong>: Laravel now offers an official Svelte starter kit, joining React, Vue, and Livewire. This kit combines Svelte 5, TypeScript, Inertia 2, Tailwind CSS, and shadcn-svelte, providing a robust foundation for new projects with built-in authentication and SSR. <a href="https://app.daily.dev/feed-by-ids?id=runkXqODs&amp;id=J0baIl5WX" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Node.js 25.7.0 released with ESM support for single executables</strong>: Node.js 25.7.0 is out, bringing ESM entry point support for Single Executable Applications (SEA), an upgraded npm to 11.10.1, and various fixes for HTTP/2, zstd memory, and zlib brotli compression. <a href="https://app.daily.dev/posts/K4geCuziz" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Tailscale workload identity federation now generally available</strong>: Tailscale’s workload identity federation is now GA, allowing CI/CD pipelines and cloud workloads to use short-lived OIDC tokens instead of static credentials, enhancing security and simplifying management across various platforms. <a href="https://app.daily.dev/posts/ekx9IIs1v" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>New react animation libraries and css features for frontend development</strong>: Frontend development sees new tools like TanStack Hotkeys for keyboard shortcuts and a comparison of seven React animation libraries. Interop 2026 focuses on CSS Grid Lanes, <code>::search-text</code>, and a new HTML <code>&lt;geolocation&gt;</code> element, pushing web platform capabilities. <a href="https://app.daily.dev/feed-by-ids?id=wbsbYcCdU&amp;id=JnqS7Iz41&amp;id=GrvyC75oV&amp;id=RoxLCkIyX" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>AI agent skills for vue ecosystem released</strong>: An open-source repository, <code>vue-ecosystem-skills</code>, provides pre-generated AI agent skills for the latest Vue ecosystem libraries, including Vue 3.6, Pinia v3, and Vue Router v5, helping AI coding agents stay up-to-date with API changes and best practices. <a href="https://app.daily.dev/posts/rV2zAtzZP" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Shopify graphql api enhances subscription billing</strong>: Shopify’s GraphQL Admin API introduces <code>SubscriptionBillingAttemptState</code>, replacing multiple nullable fields with a strongly-typed discriminated union pattern. This improves API ergonomics and self-documentation for managing subscription billing attempts. <a href="https://app.daily.dev/posts/WcjzF6cXJ" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
<h2>Bullshit police</h2>
<ul>
<li><strong>AI-generated production assets in 2 days: the 90% prompt tuning myth</strong>: A case study touts building an AI-powered thumbnail generator in two days, claiming 90% of the work was ‘prompt tuning.’ So, we’re just swapping coding for prompt whispering now? And apparently, internal tools need ‘UX’ to get adopted, which is a groundbreaking insight for anyone who’s ever built software. <a href="https://app.daily.dev/posts/dbKW2IViX" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Web components: the framework-free renaissance (or just more boilerplate?)</strong>: Apparently, modern browsers now do everything, so we don’t need frameworks like React, Vue, or Angular. Web components offer ‘encapsulation, loose coupling, and long-term stability’ that frameworks can’t match. Because manually managing event-driven communication and data flow across components is definitely less ‘upgrade treadmill’ than, you know, using a framework. <a href="https://app.daily.dev/posts/LVuCvixaF" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Don’t use next.js if you’re building for the long term (because churn is a feature, not a bug)</strong>: A developer argues against using Next.js for long-term projects due to ‘upgrade churn, tight coupling to Vercel, and implicit behavior traps.’ It’s almost like frameworks evolve and require maintenance. Who knew that building software for the ‘long term’ might involve, gasp, adapting to change? <a href="https://app.daily.dev/posts/0vMYzSZd0" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
