91–100 of 248 posts
It's funny since Anthropic asked their job candidates not to use AI [0]. I know it's not the same as actually working at Anthropic already, but I just thought it was funny. [0] https://fortune.com/2025/02/04/anthropic-tells-job-candidate...
My optimization hack is that I'm using speech recognition now with Claude Code. I can just talk to it like a person and explain the full context / history of things. Way faster than typing it all out.
The SuperWhisper app is great, if you use a Mac.
https://apps.apple.com/us/app/voice-type-local-dictation/id6...
The developer is pretty cool too. I found a few bugs here and there and reported them. He responds pretty much immediately.
A repeated trend is that Claude Code only gets 70-80% of the way, which is fine and something I wish was emphasized more by people pushing agents. This bullet point is funny: > Treat it like a slot machine > Save your state before letting Claude work, let it run for 30 minutes, then either accept the result or start fresh rather than trying to wrestle with corrections. Starting over often has a higher success rate th…
The slot machine thing has a pretty compelling corollary: crank the formal systems rigor up as high as you can. Vibe coding in Python is seductive but ultimately you end up in a bad place with a big bill to show for it. Vibe coding in Haskell is a "how much money am I willing to pour in per unit clean, correct, maintainable code" exercise. With GHC cranked up to `-Wall -Werror` and some nasty property tests? Watching…
So this style of articles is the future? Pages of unconnected bullet points that mention the word "Claude" at least 100 times. No real information and nothing to remember.
Yeah, I don't think all the information in the article is useful but it seems like disorganized dump - or a melding together of several article - boiler plate "we use Claude for all good things" and specific useful tips all run together. It definitely has a "we use AI enough that we've lost the ability to communicate coherently" vibe to it.
My optimization hack is that I'm using speech recognition now with Claude Code. I can just talk to it like a person and explain the full context / history of things. Way faster than typing it all out.
The SuperWhisper app is great, if you use a Mac.
I highly recommend getting a good microphone, I use a Rode smartlav. It makes a huge difference.
A repeated trend is that Claude Code only gets 70-80% of the way, which is fine and something I wish was emphasized more by people pushing agents. This bullet point is funny: > Treat it like a slot machine > Save your state before letting Claude work, let it run for 30 minutes, then either accept the result or start fresh rather than trying to wrestle with corrections. Starting over often has a higher success rate th…
> A repeated trend is that Claude Code only gets 70-80% of the way, which is fine and something I wish was emphasized more by people pushing agents. Recently, I realized that this applies not only to the first 70–80% of a project but sometimes also to the final 70-80%. I couldn’t make progress with Claude on a major refactoring from scratch, so I started implementing it myself. Once I had shaped the idea clearly enou…
Earlier quoted context omitted.
The hilarious part I’ve found is that when it runs into the least bit of trouble with a step on one of its plans, it will say it has been “Deferred” and then make up an excuse for why that’s acceptable. It is sometimes acceptable for humans to use judgment and defer work; the machine doesn’t have judgment so it is not acceptable for it to do so.
My favorite is when you ask Claude to implement two requirements and it implements the first, gets confused by the the second, removes the implementation for the first to “focus” on the second, and then finishes by having implemented nothing.
Earlier quoted context omitted.
once upon a time - engineers often had to concern themselves with datacenter bills, cloud bills, and eventually SaaS bills. We'll probably have 5-10 years of being concerned about AI bills before the AI expense is trivial compared to the human time.
This guy has not been hit with a 100k/mo cloudwatch bill
Earlier quoted context omitted.
Thanks for the tip - we employees should run and re-run the code generation hundreds of times even if the changes are pretty good. That way, the brass will see a huge bill without many actual commits. Sorry boss, it looks like we need to hire more software engineers since the AI route still isn't mathing.
Unironically this can actually be a good idea. Instead of "rerunning," run in parallel. Then pick the best solution. Pros: - Saved Time! - Scalable! - Big Bill? Cons: - Big Bill - AI written code