Andy Park

@thebearmaster
8 Followers
149 Following
55 Posts
Maker of Mac & iOS apps. Chaser of shiny objects. Polyglot.

Any recommendations for a kitchen table top-friendly Bluetooth keyboard I can use exclusively to jot down small notes or tasks?

I’d like to ween myself off the habit of using the iPad on the sofa or lounge chair around the coffee table, or at the dining table.

Elden Beast slain. Only took 1.5 years.

What next?

Intrigued how this rough edge will get refined when macOS 26 graduates beta.

Will they full-bleed the horizontal bars behind the sidebar, deeming it part of the content?

Or maybe they’ll match the colour(s) of the horizontal bar to the content, a la Safari’s favourites bar, and further trade off legibility / visual stability?

The thing I notice most about Safari on macOS 26 (Beta 2): I can't tell which tab I'm using right now.

My current workflow: give out some tasks to Codex, perform a real-life chore, review Codex's code changes in a GitHub PR, maybe check out the branch locally and fix issues that failed Xcode Cloud CI build, finish off the PR.

Open questions:
- Best way to get Codex to produce a PR that nearly works, given it can't run xcodebuild?
- Any way to get Codex to work with comments etc on a PR once it's open?
- Best way to handle merge conflicts? Esp with the Xcode project file.

Last few days I've been trying vibe coding. Just 6 months ago I was a skeptic, now I fear that line-by-line coding will feel like writing assembly in the near future.

There's going to be a lot of changes in both software development and the world at large.

It felt terrifying at first but now I'm beginning to get excited.

This is why I urge everyone who tried AI for coding 6+ months ago and gave up to try them again. Autonomous agents are no longer the future, they’re the present — things have changed, drastically so. https://blog.singleton.io/posts/2025-06-14-coding-agents-cross-a-chasm/
Coding agents have crossed a chasm // flurries of latent creativity

One of the reasons the “iOS-ification" of macOS UI suffers so greatly is that iOS is fundamentally a single-window UI. It literally doesn't have to contend with *any* of the issues that most Desktop chrome was designed to address. So of course it falls flat on its face when applied to macOS. Imagine if every year Apple tried to make iOS as "simple" as watchOS, with no regard for functionality, just stubbornly insisting "if we don't need it on the watch, we shouldn’t need it on the iPhone!”
Uhh.. looks like I accidentally upgraded my main Sequoia installation to Tahoe beta… I was expecting an installer to ask me which drive to install on, but it didn’t. (I used Software Update)
Marketability, then design, then development. A new hypothesis for myself.