I wrote about my experiences using LLMs + Claude Code. Both the good and bad. These tools can cut both ways on efficiency. But my biggest concern is I'm worried developers won't know when to put them down. One takeaway I have: devs who use LLMs should have a surface understanding of how they work.

https://www.colincornaby.me/2025/07/llm-coding-and-the-sunk-cost-fallacy/?utm_source=mastodon&utm_medium=jetpack_social

@_Davidsmith the ideal would be some way of the tool identifying and automatically capturing and arranging the screenshots so all I have to do is traverse the full app, on device or in a simulator, till it’s mapped the entire ‘fingerprint”.

@_Davidsmith I would love to find a tool that is designed to capture and organise a flow of screens like this. I have a current and immediate need.

Well that's definitely an interesting choice from Microsoft

https://support.microsoft.com/en-us/account-billing/changes-to-microsoft-authenticator-autofill-09fd75df-dc04-4477-9619-811510805ab6

The great part about iPad's new windowing model is that you can't hide from it if you're a developer. Users are going to window your apps, layouts are going to be resized, and your menu bar is going to be investigated.

The menu bar API, which is shared with Catalyst, should be your first port of call, as it's something that apps shipping today, built with the older SDKs, now show in the OS. There are plenty of iPad apps that never filled out their menu bar, and you can/should fix that right now

@gernot @alpennec @b3ll I asked this question in two group labs and it remained pending, never approved to show to attendees. They did say in some labs they did not think it was the right forum to address “code level” questions so maybe that’s why.

@elight the main comparison I was thinking was base M4 vs M1 Pro, and it does seem the base M4 with same core count is about 10% faster in CPU benchmark. Obviously cooling may still make a difference if in a MacBook Air vs Pro but I think the latest MacBook Airs are thus getting pretty compelling for dev.

@elight I think so for having multiple simulators, but the M1 Pro does have a lot of CPU grunt over the M1. (M1 Max on the other hand was just more GPU and tests I saw said for most dev tasks, didn’t make much difference.)

I am guessing a base M4 would be at least as good as the M1 Pro? But I think RAM often undervalued for dev efficiency.

I wonder if those #iOSDev indies who adopted version numbering of 2025.1 etc are having buyers remorse they didn’t go with 25.1 so they could now match the operating systems.

Non devs won’t know that you can iterate app version numbers on the App Store however you like, with the one limit that the number can only ever *increase*. So adopting a 202x.x numbering scheme is forever. No backsies.

@elight an M1 Pro MacBook Pro with 32Gb RAM still works pretty well for development. My tests run on seven simultaneous simulators.

This might be a case where Sherlocking is a blessing. I’ve thought for years that macOS should probably have a clipboard manager, but I’ve never taken action despite knowing that third party options exist. Once I get my first use free, I might want the harder supply.

From: @simonbs
https://mastodon.social/@simonbs/114706031280599276

@clairikine I was right with you and then instead I was heading off to look up what an interpunct was. Love it. Though I don’t really understand how it fits in this list.

@jsq with applications in a similar stare, you can bypass this dialog by right clicking (ctrl-clicking) and selecting Open from contextual menu. I believe the theory is you’re flagging greater intentionality that you know about the warning and what you are doing. Might work here?

@colourfool that is a surprisingly grounded argument for someone who claims to be a type of “fool”.

@colourfool maybe they don’t want to commit to an annual update cycle?

@ryanbooker I’m now curious whether the order of these modifiers affects the result you see. But also too lazy to set up a test myself. 🤓

I’ve seen in app purchase pricing that looks pretty bad but this takes the cake. Hey #iOSDev don’t put a price in one currency in your in app purchase name as it may cause you problems on the App Store in other locales.

@manton @jim requires some thought as generally speaking making links behave like this is considered bad for accessibility. See one discussion at https://theadminbar.com/accessibility-weekly/opening-links-in-new-tabs-or-not/

I can’t believe that none of the tech journalists have used the headline “Apple Will 86 Intel Next Year”

Got a `dyld_shared_cache_extract_dylibs failed` error in trying to prepare for building to a physical iPhone running the iOS 26 developer beta? Turns out, might not be a complex Xcode 26 beta bug. Could just be Sparkling Lack of Disk Space on your Mac. 🤦🏽 #WWDC25