Hello!

Anthropic's bold claim that Claude now authors 80% of its new production code has the industry buzzing, while OpenAI's upcoming ChatGPT overhaul signals a shift (is chat really dead?). Meanwhile, Sanity Studio v6 drops with a breaking release that promises to shake up your content management strategies.

At Pagepro, we're all about making your Next.js and Sanity migrations as frictionless as possible (because who has time for headaches?).

Grab your coffee, settle in, and enjoy Frictionless

In the Queue

Deepen Your Expertise

Sanity Studio v6 drops as Node 20 bows out. This update isn't just about keeping up; it's about shaking up.

Why should CTOs care?

First, it's your chance to leverage the latest tools without the fluff. Second, this release focuses on performance tweaks that might just shave precious milliseconds off your load times. The actionable takeaway? Dive into the patch notes and prioritize your upgrade path. Missed the node end-of-life memo? You're late to the party.

Ready to future-proof your stack?

React Server Components are transforming the way we think about page architecture. By allowing each component to handle its own data fetching, we ditch the bloated pages that prop-drill data down the tree. This shift means cleaner, more efficient code and a user experience that's noticeably snappier.

Two key insights: First, you'll redefine loading boundaries at the component level. This reduces overhead and accelerates rendering. Second, by decentralizing data fetching, you minimize unnecessary re-renders, which directly boosts performance.

Forget the giant loaders—opt for modular efficiency. Ready to rethink your architecture?

Chopping build times isn't just a pipedream. Sentry proved it by scrapping their CMS, diving headfirst into Astro, Markdown, and Claude Code skills. The payoff? Build times slashed from 14 minutes to just under four. No more sitting around. Plus, they shook off pesky API failures like a bad cold.

For CTOs, the benefits here are twofold. First, reducing build times directly impacts developer productivity, making everything tick faster. Second, dropping a CMS for a streamlined setup isn't just a speed boost — it's a reliability upgrade too. Fewer moving parts mean less can go wrong.

Consider this: what's the real cost of your current build process?

Reduce Friction

AI is messing with hiring, but there’s a way out. Traditional interviews can't catch when candidates fake it using AI tools. It's time to rethink how we gauge skill and sincerity. Prioritize in-person evaluations and test real-world problem-solving. This isn’t just a hiring issue; it’s a culture shift.

70% of candidates admit to using AI in applications. You're not just vetting skills now, but integrity. Hire right, and you foster a team that sticks.

Authenticity is a culture, not a checkbox. Ready to revamp your hiring process?

Feeling stuck? It's not just you. New data shows that employees who can't see their impact are quitting. 25% of workers feeling blocked have already dialed back their efforts.

Two big takeaways for you: First, transparency matters. Let teams see their contributions in action. Second, communication isn't just about talking — it's about showing results.

Why let frustration fester? Dive into the full story and prevent a talent drain.

Ready to climb the ladder from senior to staff engineer? You're looking at a shift from just coding to crafting platforms that boost team efficiency. Think less about the lines of code and more about the frameworks that make everyone's job easier. Leadership means amplifying team output, not just your own.

Staff engineers aren't just tech whizzes; they're leaders who clear the path for innovation. By building tools that reduce friction, they drive long-term gains. Got your sights on a staff position? Start by thinking about how you can enhance team dynamics.

How will you multiply the impact of those around you?

AI Corner

The Claude Fable 5 brings a fresh take on AI with its Mythos-class intelligence. Anthropic promises big things, but how does it really stack up? Spoiler: it's a mixed bag. Crushing benchmarks sounds impressive—until you realize its real-world execution feels conservative.

In practice, the model's token-intensiveness and fallback safety features are a double-edged sword. They ensure robustness but could slow you down. If you're considering integrating Fable 5 into your stack, focus on resource allocation and risk assessment. Surprised by its cautious execution? Consider whether it fits your fast-paced projects or if its safety mechanisms make you sleep easier.

Blazing new trails or a cautious step forward? Decide before your competition does.

Anthropic reports 80% of its new production code is authored by Claude, its AI tool. This isn't about flashy tech or buying the latest API tokens. It's about a cultural overhaul. Your team needs to embrace change, facing developer anxiety head-on and integrating automated verification guardrails to ensure code quality.

80% is a massive number. It’s not just efficiency, it’s a paradigm shift. Companies must tackle developer fears of obsolescence and foster an environment of continuous learning and adaptation.

Think your team is ready to let AI take the reins? Time to find out.

OpenAI isn't just tweaking ChatGPT—it's gearing up for a seismic shift. The plan? Turn ChatGPT into a 'superapp' by integrating coding tools and AI agents. This isn't just about expanding features; it's a hardcore pivot towards business clients, aiming to outpace competitors like Anthropic. $850 billion is riding on this transformation.

  • Expect an influx of products designed to rake in revenue and solidify market standing.

  • Don't brush this off as hype. If your company uses AI, these changes could redefine your toolkit.

Are you ready to adapt to this evolving AI landscape?

Just Cool

Microsoft's open-source packages are in the hot seat—again. Dozens got a nasty surprise, as credential-stealing code was slipped in, ready to pounce when opened in AI coding assistants. GitHub flagged 73 of these packages but framed it as a "terms of service" issue. Not exactly the warning devs needed. Assume you're compromised if you used these packages. Protect your systems and scrutinize any open-source packages, especially the ones leaning on AI tools. A friendly reminder: sometimes, it's not just the code that needs debugging.

Let’s Stay in Touch! 📨

Do you have any comments about this newsletter issue or questions you want to ask? Drop me a message or book a meeting.

What do you think of today's email?

Your feedback helps me improve Frictionless.

Login or Subscribe to participate

Keep Reading