Vanit

The one real caveat to this is that if your application has particularly heavy cold starts it can be hard to actually run your worktrees. I usually end up swapping to a regular checkout as each worktree is due for hands-on attention.

Replaced by projects with nebulous ownership of copyright.

Vault is an Obsidian thing. This is just an "agent" (read: LLM harness in a loop) with access to it, a system prompt and a few markdown files. Nothing meaningful has changed in the LLM primitives, nor will it :)

The American discourse around these killings are actually insane. In any other developed country it wouldn't be possible to escalate these situations like this regardless of what you were doing.

Ugh a terminal purist. Just as insufferable as the ones in person at work. Yeah have fun with your gigantic unorganized git diffs I guess.

Like you said I think it's culture, particularly ones that are food oriented. It's gonna be hard to get buy-in if people think it's too weird.

The tact aspect seems like a real possibility. In a world where users are likely to cut&paste responses it can't really be sprinkling in references like this.

Is this written by AI?

Also pretty funny to compare to peanut butter & jelly, goes to show American self-centrism, and also the same bubble that's around AI tooling.

My favourite one was debugging a crash in an Electron app deployed to iOS. It turned out throwing an exception from a point event callback (deep in our app's code) was bubbling up into the device's kernel code.

I agree with the article, but that's not how the vibe coders see themselves. From their perspective they can't see the gap between programming and product, and in my experience are pretty hostile to feedback from real software engineers.

I realise your answer wasn't assertive, but if I heard this from someone actively defending AI it would be a copout. If the selling point is that you can ask these AIs anything then one can't retroactively go "oh but not that" when a particular query doesn't pan out.

Ah, somewhere you can find all those terrible interviewees in one place!

You may as well just use a singleton pattern if you're going to do this, and at least that's easier to maintain if your use cases change.

I read through half the docs and couldn't get a definitive answer on if nested custom components (ala React) we're even possible.

I'm throwing some shade here, but this reeks of backend engineers not caring about UX.