 iOS Code Review Newsletter

Newsletter for iOS devs spreading good code vibes 🚀 subscribe at 🚀 #SwiftLang #SwiftUI #iOSDev

[ iOS Code Review Newsletter @ios_code_review]

Swift just escaped Xcode.

Now runs in Cursor, VSCodium, and other AI IDEs.

Meanwhile:
• Xcode 26.4 paste bug is painful (there’s a fix)
• April 28 SDK deadline is creeping up
• A Swift game engine just dropped

Swift isn’t “just iOS” anymore.
It’s going general-purpose.

[ iOS Code Review Newsletter @ios_code_review]

Issue #79 is out 🚀

defer is underrated. Instruments is essential again. @Observable testing finally has a clean answer. Oh, and WWDC is one week away.

https://t.co/PvR9Iblg2T

[State of AI @stateof_ai]

Okay this one's genuinely exciting!

Every self-improving agent until now turns ONE knob, edit the scaffold or train the weights. SIA turns both, in a single loop. And it rips:

LawBench: 50% → 70.1% once weights kick in
CUDA kernels: 14x speedup
RNA denoising: +502% over baseline

And the tell is on denoising—this is the part that's genuinely awesome. The scaffold-only loop, across every single iteration, never found a fix. Then the first weight update just... figured it out: a two-line clip that rounds imputed counts to non-negative integers. A basic biological constraint that no prompt, no scaffold, no amount of clever engineering ever surfaced. The model learned it on its own.

That's the whole thesis in one moment! The harness changes how an agent searches. The weights change what it knows. And you really, really want both.

[ iOS Code Review Newsletter @ios_code_review]

Issue #78: The Paste Bug Is Dead, Bottom Sheets Done Right, and WWDC Is 30 Days Away

https://t.co/piEEJXj3T7

[ByteSizedDesign @bytesizeddesign]

HubSpot had a 37-minute outage last month where every customer lost UI access to half their workflows.

The endpoint returned HTTP 200 the entire time.

Monitoring saw nothing wrong.

New Byte-Sized Design on why availability ≠ correctness 👇

[ iOS Code Review Newsletter @ios_code_review]

https://t.co/BHV4jHM2GL

[ iOS Code Review Newsletter @ios_code_review]

Swift just escaped Xcode.

Now runs in Cursor, VSCodium, and other AI IDEs.

Meanwhile:
• Xcode 26.4 paste bug is painful (there’s a fix)
• April 28 SDK deadline is creeping up
• A Swift game engine just dropped

Swift isn’t “just iOS” anymore.
It’s going general-purpose.

[State of AI @stateof_ai]

Hot take: 90% of "bad AI outputs" are a data freshness problem, not a model problem.
You're blaming GPT-4 for confidently answering with info that was accurate 3 months ago.
That's not a model failure. That's infrastructure debt.
Read more on how to solve this here!
https://t.co/IyFQgFKPHm

[ iOS Code Review Newsletter @ios_code_review]

Issue #76 is out! 🚀
Swift 6.3 dropped with Android support, smarter Swift Testing, and the new attribute for C interop. Plus: Xcode 26.3's agentic coding is here, and don't miss the April 28 SDK deadline.
https://t.co/qSTe9qskVX

[ iOS Code Review Newsletter @ios_code_review]

Swift 6.3 is out!
🎉 Highlights: official Android SDK, @c attribute for C interop, Swift Build preview in SPM, and Swift Testing improvements including image attachments & test cancellation. Cross-platform Swift is becoming very real!

https://t.co/8aaMkky9tj

[ iOS Code Review Newsletter @ios_code_review]

📢 iOS Code Review is now open for sponsorships!

If you have a dev tool, iOS/Mac app, or product you want in front of working iOS engineers, this is your spot.

Spots are limited, get in touch soon 👇
📧 [email protected]
🔗 https://t.co/6XBbqMoc2g

[State of AI @stateof_ai]

This is awesome!

You can get Replit Core FREE for 1 month AND gift someone Replit FREE for 1 month.

Great win for builders!

[ iOS Code Review Newsletter @ios_code_review]

@Tech_Over_Lord More on this in our next edition as well!

[ iOS Code Review Newsletter @ios_code_review]

Swift on the backend is underrated.

Compile-time safety + real multithreading (no GIL) = fewer bugs, lower infra costs.

Some teams are already running production systems at scale with it.

iOS devs have an unfair advantage here

[ iOS Code Review Newsletter @ios_code_review]

@Tech_Over_Lord Start at https://t.co/bKmIU2e15d, that's the official hub. Then pick up Vapor at https://t.co/W6qSSsEB66. For articles and tutorials, https://t.co/6GlOOCR6mc is the best resource. Apple also dropped a WWDC24 session called "Explore the Swift on Server ecosystem"!

[Marina Vatmakhter (Gornostaeva) ✨ @hybridcattt]

iOS Code Review newsletter is back 😍

I’ve been building awesome tech to fight climate change since 2024, and coincidentally (not) I got no time to write anymore.

Finding someone worthy of taking over the reins took time, and I’m happy to introduce Sam and his first issue 🎉

[ iOS Code Review Newsletter @ios_code_review]

Issue #75: We're Back!
Tool Calling, Default Actors & the Clock Is Ticking!
https://t.co/uaXfrwWCRg

[ByteSizedDesign @bytesizeddesign]

Most engineers are asking the wrong question about AI.

It’s not “Will AI replace developers?”

It’s which parts of the job disappear first.

The junior work is going first. The mid-level work is under pressure.

Architecture isn’t shrinking. It’s moving up a level.

The job is no longer designing services. It’s designing systems where humans and AI make decisions together, and knowing exactly where the human must stay in the loop.

The engineers who learn that boundary early will be fine.

The rest will feel like they’re slowly disappearing.

https://t.co/MczVQsYzxR

[ByteSizedDesign @bytesizeddesign]

Stop trying to learn every new framework.

Start learning why systems fail. Read postmortems, study outages, understand how things break at scale.

The engineer who's seen 100 systems fail is worth more than one who's mastered 100 tools. Experience is just pattern recognition for disasters you haven't caused yet.

[ iOS Code Review Newsletter @ios_code_review]

Did you miss us? 👀
iOS Code Review is coming back VERY soon with:

Deep dives into SwiftUI patterns
Latest iOS development news & best practices
Performance optimization tips

Coming Soon!📱✨

[ByteSizedDesign @bytesizeddesign]

The best engineers aren't the ones who never get stuck.

They're the ones who get unstuck in 20 minutes instead of 2 days.

They ping someone instead of spiraling.

They read the actual source code and documentation instead of panicking.

They write the failing test to understand the bug.

Being stuck is part of the job. Staying stuck is a choice.