oh yay @github.com added a "Copy Markdown" option on the menu for issue comments so I don't have to play the edit and Ctrl + C game anymore 😁

Just the back

Mullet guy at my gym cut his hair

The winds of change are blowing and I don’t like where they go

Asked an agent to fix a tricky race condition in tests and now I feel like I've definitely made it on the shitlist for the robot apocalypse

The former. I use the review skill to audit PRs before submitting them and getting something that approximates what I might’ve gotten from a bunch of human reviewers is helpful.

Google needs to explain this icon change. I’m disturbed.

Pro-tip: dig up some PRs where you've gotten some great code review and ask your coding agent of choice to generate a code review skill based on the style of feedback left by the reviewers in those PRs.

Sometimes instead of using AI, I Google something and read the docs page just to feel alive again.

I wish I had that problem…my current mechanical keyboard is plain but does the job

Fair on some things but it was too bit-picky, IMO.

Which makes perfect sense given the prompt 😆

Don't ask Gemini to review your code like a senior engineer who hates your PR and wants to block it unless you're in an emotionally healthy space.

Will people come for me if I confess that I bang my mechanical keyboard against my desk to shake the crumbs out? 🫣

I needed a landing page for a new project and was completely stuck on the UI.

I tried v0 a try and the first feature that caught my eye was a little magic-wand button that refines your prompt before generating anything.

Such a simple idea, but it instantly brought me joy.

Feel a bit of loss at the decline of GitHub as a *social coding* platform.

It seems like people are quick to dismiss that premise in the era of AI-enabled coding but I think there is still value in providing a space for communal ownership over software.

I joked about the "QA engineer for my agents" thing earlier but it's honestly so peaceful to just sit and polish software with the help of agents.

You can really fight a lot of slop with intentionality and attention to detail.

Another weekend shift completed being QA engineer for my coding agents 😆

inside me are two wolves

GitHub - nteract/desktop: Desktop app for interactive notebooks powered by runtimed Desktop app for interactive notebooks powered by runtimed - nteract/desktop

It's early but feel free to give github.com/nteract/desk... a star ;)

Such an unreal experience watching a agent build and run a Rust app and then test a feature in a VM.

I'm excited for people to start using this app soon...IYKYK 😉

Yep, one limitation of PRs is that they don't value context that is built in non-GitHub side channels.

Things agents say all the time that I’ve never heard a person say: "Alternatively, I could use sed for surgical replacement.” 😆

Yep, I put this under the bucket of trusting people to do the right thing although that does assume the team is aligned about the what counts as technical debt and how to manage it.

I find it too aggressive lol

This is how I bucket PR reviews:

- Request changes: Never use this lol
- Comment only: Not ready to merge; blocking feedback
- Comment + approve: Ready to merge; feedback is non-blocking; trust dev to do the right thing
- Approve: Ready to merge

What’s your bucketing?

I actually chuckled out loud at this 😆

You can name Git stashes with the `-m` flag.

```
git stash -m "client-db-iteration"`
```

I've been using this to "discard" agent code I don't like so I can retrieve it later.

You can also tell the agent to look at previous stashes by name as context in agent sessions.

Designing cute little logs is my favorite part of these side projects 😃

I’ve heard of it, skimmed the docs, but I haven’t actually incorporated it into my workflow.

Just shipped Grove v2!

- Swapped TS + Bun for Rust so binaries are nearly 40x smaller
- Support initializing new worktrees with custom commands
- Harden Windows support and shell integration

Try it out: github.com/captainsafia...

I think @mitchdenny.dev is probably already on this but there should be a nice experience for using the @aspire.dev MCP in Warp and also setting up skills in the standard .agents directory.