@isaiah

862 Followers
670 Following
8.2K Posts

i'm a software developer. primarily for macOS. primarily in Obj-C. primarily working on https://yourhead.com/stacks

but it hasn't always been that way. i used to write other software, in other languages. and before that i designed microchips.

Webhttps://yourhead.com

like, just imagine working with another engineer that behaved this way, cheerily bootlicking everything you say and trying to divert your attention towards other fun little projects.

exhausting

RE: https://someone.elses.computer/@mikarv/116679213626907810

“It's a thermonuclear ADHD amplifier“

i’ve often wondered about this… if this is one of the reasons AI coding just never really “sticks” for me.

i’m not an ADHD sort of person. if anything i’m the opposite. i enjoy focusing on a single difficult task. and working with folks who bounce around multitasking is just exhausting.

and that’s exactly what AI does. at each interaction Claude purposefully tries to redirect me with a few side quests.

why do billionaires lose their marbles?

top notch healthcare, personal trainers, and all the resources of the world, literally, and it seems like they’re on a one way ticket to crazy town the moment they bank their first billion.

what gives?

@isaiah This has been my experience, too. I let it point me in what it thinks is the right direction, push back on it with a lot of skepticism, and eventually arrive at a solution I haven't hand-written myself, but hopefully understand as well as if I had.

The idea of blindly accepting whatever it spews out at first pass is lunacy. And I really don't think this is saving any time in the long run. It's just shifting the time spent to understand the solution from before the code is written to after.

"But it happened."

YouTube

the amount of hours i wasted using Claude to build this…
then debugging it's shitty code…
again. and again.
then having to tear it out and do it myself in the end anyway.

it's exhausting!

i'm not surprised people like using AI. not at all.
i'm just surprised people are willing to pay so much for privilege of debugging the junior engineer bullshit mistakes it makes.

so it turns out this is part of a larger change that i asked Claude to build a while back.

the solution always seemed too complicated.

i asked Claude to fix this bug yesterday and it handed me a nearly complete rewrite of the entire NSOutlineView subclass.

😭

and the solution broke other stuff

🤬

so i decided to dust off the AppKit NSOutlineView docs and have a go myself.

it took me all day, but i have the simple, understandable, and functional solution i was after in the first place.

After nearly six months of work, I'm thrilled to introduce Shortcuts Playground:

A plugin for Claude Code and Codex to create native Apple shortcuts with natural language.

Type a sentence in, get a shortcut back. It can one-shot complex shortcuts, make changes, and remix old shortcuts. Full Shortcuts action library supported.

Free and open source. Install it in your favorite agent here: https://github.com/viticci/shortcuts-playground-plugin

My story on how and why I made this: https://www.macstories.net/stories/introducing-shortcuts-playground/

to add chaos to it: i tend to tap on my Magic Trackpad on my desk when using my machine in closed clamshell mode, but tend to click when using the built-in trackpad on same machine open in normal laptop mode.

for the past couple weeks the bug seemed to come and go randomly.

new weird bug achievement unlocked!

i somehow created a bug that happened ALWAYS if a mouse-down event was triggered by a **tap** on a trackpad.

but the bug was NEVER triggered by a mouse-down event that was triggered by a **click** — pushing on the bottom of the trackpad.

🫠