ElBarto

Do you tell Claude to make a plan first?

That helps me tremendously. Whenever something needs to be modified, I tell it to update the plan first, and to stick to the plan.

That way, Claude doesn’t rewrite code that has already been implemented as part of the plan.

And understanding the plan helps understanding the code.

Sometimes if I know there will be a lot of code produced, I’ll tell it to add a quick comment on every piece it adds or modifies with a reference to the step in the plan it refers to. Makes code reviewing much more pleasant and easier to follow. And the bugs and hallucinations stick out more too.

Thanks! Yeah, lack of ethernet ports is annoying. I bought a USB adapter to have one.

Nice! Thanks for your answer.

Whoa, what laptop did you end up getting? 64GB? Nice!

Thanks for the links.

Well, that’s disappointing.

Is programing.dev a lemmy instance, or a piefed one?

♾️

How are they assholes? What did I miss?

Thanks! It’s interesting to hear folks say that other machines are as powerful and less expensive. The irony is, they’re less expensive because they have everything soldered on and designed to be eventual e-waste more quickly.

Ransomware that can’t be decrypted is just destructive malware like any other.

How do you really like it?

I’m considering getting one.

I’m far from being an AI defender. And for the longest time I resisted the idea of vibe coding.

I will give you that, without the right experience, vibe coding feels like gambling.

But I learned rather quickly that you must first work on a dev plan with an LLM, and until that plan hasn’t covered every scenario, then you don’t move on.

That yields much better results, and it has the advantage of having the blueprints for when you need the LLM to make changes.