It seems the original poster hasn't extensively tried various AI coding assistants like Cursor or Windsurf. Just a quick heads-up based on my recent experience with agent-based AI: while it's comfortable and efficient 90% of the time, the remaining 10% can lead to extremely painful debugging experiences. In my view, the optimal scenarios for using LLM coding assistants are: - Architectural discussions, effectively re…
I've been using Claude Code for a couple of days
261–270 of 507 posts
Re: I've been using Claude Code for a couple of days
#262It seems the original poster hasn't extensively tried various AI coding assistants like Cursor or Windsurf. Just a quick heads-up based on my recent experience with agent-based AI: while it's comfortable and efficient 90% of the time, the remaining 10% can lead to extremely painful debugging experiences. In my view, the optimal scenarios for using LLM coding assistants are: - Architectural discussions, effectively re…
Re: I've been using Claude Code for a couple of days
#263And notice how few benchmarks will include Sonnet 3.5/7 in their new model announcements, because they’re awful compared to Sonnet.
What’s going on here?
Re: I've been using Claude Code for a couple of days
#264How does it compare to Aider with the same model?
Re: I've been using Claude Code for a couple of days
#265Earlier quoted context omitted.
Have you tried using Cursor rules? [1] Creating a standard library stdlib with many (potentially thousands) of rules, and then iteratively adding to and amending the rules as you go, is one of the best practices for successful AI coding. [1] https://docs.cursor.com/context/rules-for-ai
> …many (potentially thousands) of rules, and then iteratively adding to and amending the rules as you go… Is this an especially better (easier, more efficient) route to a working, quality app/system than conventional programming? I’m skeptical if the answer to the way to achieve 10x results is 10x more effort.
Re: I've been using Claude Code for a couple of days
#266Earlier quoted context omitted.
So you’re not _interviewing_ them, you’re having them complete expensive work-sample tests. And your evaluation metric is “completes lots of steps in a small time box.”
Seems more like trying to find out the most proficient LMM users than anything else. I’ve never done interviews but I imagine I’d be hard pressed to skip candidates solely because they aren’t using LLMs. Each to their own and maybe their method works out, but it does seem whack.
This is why I wouldn't hire a person who doesn't know how to do this.
Re: I've been using Claude Code for a couple of days
#267Re: I've been using Claude Code for a couple of days
#268Earlier quoted context omitted.
I have to say that I am worried that, by taking myself out of the loop for the 99%, I'm going to get worse at the 1% of things that occasionally fall into my lap because the LLM can't seem to do them. I think software engineering is a skill that is "use it or lose it", like many others. There's also the question of whether I will enjoy my craft if it is reduced to, say, mostly being a business analyst and requirement…
It's very specialized already, though. How many devs could debug both a K8s network configuration issue and a bug in an Android app caused by a weird vendor's OS tweak? Not most of us. Some people will be better at pushing the LLM things to generate the write crap for the MVP. Some people will be better at using these tools for testing and debugging. Some people will be better at incidence response. They'll probably…
Re: I've been using Claude Code for a couple of days
#269I decided to check this out after seeing the discussion here. I had previously misunderstood that it required a Claude.ai plan, but it actually just uses your API keys. I did a comparison between Claude Code and Aider (my normal go-to): I asked it to do clone a minor feature in my existing app with some minor modifications (specifically, a new global keyboard shortcut in a Swift app). Claude Code spent about 60 secon…
Re: I've been using Claude Code for a couple of days
#270Earlier quoted context omitted.
No, I'm not doing leetcode or algorithm questions - it's basically "build a [tiny] product to specs", in a series of steps. I'm evaluating candidates on their process, their effectiveness, their communication (I ask for narration), and their attention to detail. I do review code afterwards. And, bear in mind that this is only round 1 - once I talk with the ones who do well, I'll go deep on a number of topics to under…
> it's basically "build a [tiny] product to specs", in a series of steps That seems like exactly what the person you're replying to is saying - that sounds like basic standard product-engineering stuff, but simpler, like any of a million examples out there that an LLM has seen a million times. "Here's a problem LLMs are good at, wow, the people using the LLMs do best at it." Tautolgy. So it's great for finding people…
Yes, product engineering, the thing that 90% of developers do most of their time.