Having trouble getting Claude to one-shot the thing you're trying to do? Have it one-shot a tool that lets you do the parts it is struggling with instead.
@theo Weird thing about bad developers: “bad code” is more expensive than correct code.
If a developer gets stuck on a problem, they run around in loops, burning calories and costing money.
@samgoodwin89 I’ve resorted to having the test harness always write its output to a tmp text file and have the test harness emit a “Full test logs available at <path>” as a final message.
@kenwheeler The art of the iteration is where all the fun is, plus you get better results that way too. Can't have happy little accidents without being in the loop.
https://t.co/jozpEocF7k
Having trouble getting Claude to one-shot the thing you're trying to do? Have it one-shot a tool that lets you do the parts it is struggling with instead.
SemiAnalysis x Fluidstack is kicking off GTC with a Power to Prefill, Dirt to Decode, Transformers to Transformers: A Full-Stack AI Infrastructure Hackathon.
Build with the best. Bring your project, win prizes, and listen to insights from top industry leaders like @marksaroufim GPU MODE, @cHHillee Thinking Machines, Thomas Raoux OpenAI, @dylan522p, and more.
Limited spots, apply below. You won't want to miss it.
https://t.co/XTVz1vB93t
Doing this to bootstrap your own product is dumb. But doing this on an individual basis to shape the tool to how you need to work feels like the inevitable end state.
there's a company that forked opencode and are posting as though they built it from scratch
idc about all that but they couldn't even find and replace things right and i had to submit a PR to them to correct their user agent saying "opencode"