Why the hell can't I forward Whatsapp messages to Muse (in Whatsapp)?

The whole "Meeting clients where they are at" premise not working is really disappointing.

Before AI, I used to start a side project and never finish it.

Now with AI, I start way more side projects and still never finish them.

We’re in the Instagram era of intelligence — optimized for the feed, the aesthetic, and the appearance of knowing

re: youtube.com/watch?v=Usufn8… @dexhorthy

For the non-vibers around I feel like this is a great talk but I can't resist the idea that it's all meaningless.
Yes the concepts would stay and the tooling would change, but the whole "give it context" but "not too much" is a dice roll

And the whole stance against dark factories (which I get) but then how do you handle the load of code that comes in?
You need to pick either you deliberately slow down or not. And if you do, is that smart?

Ultimately I think the question is: Does code matters?
I don't know if it does anymore.

Maybe the attention should be on the larger pieces - the architecture, the integrations, the right services and let Codex/Claude rip...

I'm so lost :)

Almost forgot - @CodeSignalCom there's a new xterm flag you should probably enable so this doesn't happen to future candidates called `scrollOnDisplayErase` (github.com/xtermjs/xterm.…)

1/ Tech interviews can be annoying.
It's time to share how I bombed my @AnthropicAI screening interview.
/A uses @CodeSignalCom . I had to write a node script and run it to ensure it's working.
I like to have a fresh terminal between runs so I usually use command + K shortcut

/7 I knew something was wrong, and initially thought it was my code. But it made no sense. Took me a while to realize it's a problem with the platform, but I didn't know what it was. I called it out, tried refreshing, nothing worked.

I was blind to my own code...

/8 tbh I was frustrated and pissed for a while. But there are lessons here.
I blamed the interviewer & the platform but this was a great example of the work we do daily and being able to overcome it regardless of it being unrelated to the question is part of it.

IMO A lot of the "agentic work" would scale down to building deterministic apps instead of agentic runtime.

Why? Mostly because of Token Cost & determinism.

I see so much stuff that could have been a script/program.

One cool trick I use is "deep linking" into a thread.
So I'm on CodexApp/Claude and I have a skill that's basically "if work is needed on another repo, deep link to it". This opens a new thread with the prompt ready.

Clean context, clear visual separation of work.

When a request requires work in a different repository than the active workspace, hand it off to a fresh Codex thread.
Create a new worktree
Open the new thread with a deeplink:
codex://new?path=<absolute-worktree-path>&prompt=<url-encoded-prompt>

Waiting for #codex to support multiple folders like Claude with additional-dirs 🤤

me: "I'm going to bed - You're going to loop until this works: Fix bug, push, deploy, test, verify. Repeat until it works.
Claude: "Understood. Setting up an autonomous loop. Sleep well."

Barebone. No plugins/ralph skills.
It used native "ScheduleWakeup" tool. It just works 🙌