53 karma · joined October 24, 2010
Great concept!
Why not adapt rails for this next generation?
Why do it this way? It’s like walking into a temple to yell about Jesus. It was absurdly obnoxious.
Even then, outcomes at companies require external factors, like markets and competitors, and often don’t majorly depend on the company’s efforts.
Should coordination live in the VCS layer? That sounds like it creates more issues than prevents.
I’ve found it useful to write out a list of feedback / issues and have a bunch of sub agents work on them in worktrees with a loop bringing them all back together. That way it can work for a few hours while I just can review a bulk at a time.
Might be time to increase the value of trust signals over content.
Unfortunately that’s not where we’re headed.
Remember, code does 2 things: 1. Tell the machine what to do 2. Tell the next developer what you were trying to do
My take away is “don’t write your own input tests, use a library”. The rest is AI-slip
ngrok.ai
Personally, I use Raycast for all my personal work
I’m assuming major release vs stable, but this is pretty lackluster so far. Switched back to Sonnet reasoning. Here’s to improving!