Elliot Nash

VP of Product Development & Head of design @aiera. Built the NoZeroDays app @nzdlife, & a few more. opinions are my own etc. Websites amirite.

[Kun Chen @kunchenguid]

ok tinkerers, i've got a fun toy for you

introducing baby-menu - a mac menu bar icon, and it's just a baby

it can't do anything, but you can feed it prompts and help it grow. it's what i think hyper-personalized, self-evolving software can look like

details in thread 👇

[Elliot Nash @nasherasher]

@andrewchen both with https://t.co/U5k6iIX0Dq

[Elliot Nash @nasherasher]

built this based on an old game I used to love https://t.co/NKqg4OaBVc

[Elliot Nash @nasherasher]

@benhylak @bchesky LolaTravel *

[Elliot Nash @nasherasher]

We tried to solve this at LolTravel about 8 years ago (chatting with real travel agents and rich chat UI), and the challenge is travel is not a one click buy decision, so context becomes increasingly difficult the more options that are discussed. which hotel or flight you are referring to from previously sent - even when they are sent as rich UI, it becomes a human memory problem when they are out of view.

Obviously @bchesky would have explored this years ago as well

[Tuomas Artman @artman]

Today is a hard day. I shared this note with the @linear team today: We’ve made the difficult decision to increase our workforce. This is not a cost-cutting exercise or a reflection of anyone’s performance. We’re simply reimagining every role for the agentic AI era. We’re hiring. We’re sorry about that.

[pugson @pugson]

buddy your website has scrolljacking i ain't listening to your design opinions

[Elliot Nash @nasherasher]

My friend and I planning a feature with our two Claude Code sessions in the same chat room. All four of us, talking.

[Trevin Chow @trevin]

https://t.co/JMEg4BhHGu

[Elliot Nash @nasherasher]

@CiprianiRanieri https://t.co/U5k6iIX0Dq

[Elliot Nash @nasherasher]

cranking parallel agents with 4.7

[Elliot Nash @nasherasher]

8) AI makes code is cheap, your time is still valuable, so figuring out how to scale yourself is always going to be better than a tool that tries to scale for you.

[Elliot Nash @nasherasher]

How to use Git Worktrees with Claude Code, a big' ol thread.

[Elliot Nash @nasherasher]

7) You only review code when the worktree agent has reviewed their own code enough times that they (Claude) are happy with the result and submit a PR. Then you review the code, just like any other person on your team. Ask for changes and back to testing.

[Elliot Nash @nasherasher]

6) Imagine each worktree is an engineer on your team, assign work the same way (i.e. no two worktrees should be working on exactly the same feature), then simply answer their questions/help them test their changes/provide feedback.

[Elliot Nash @nasherasher]

5) So to leverage worktrees you need to shift your perspective of shipping a single feature, to managing the outcomes of many engineers.

[Elliot Nash @nasherasher]

4) I.e. trying to watch the changes and pair code with two people writing different features at the same time would be a nightmare.. and the same can be true with pair coding with a few agents in parallel.

[Elliot Nash @nasherasher]

3) Once you have a process you like, it should be the equivalent of you pair coding with a better version of yourself.

Pair coding with one person at a time is not scalable..

[Elliot Nash @nasherasher]

2) Create your own, or use plugins like compound engineering/gsd/superpowers.

Compound engineering for example can take many minutes between each prompt as it explores and thinks. It creates great output (given strong input) at the cost of time, like any person would.

[Elliot Nash @nasherasher]

1) Working on many things in parallel on the surface is very overwhelming.

So we need to start by creating a slow and intentional process for shipping high quality features (i.e. brainstorming documents, planning documents, todos, triage, multi-agent reviews, etc).