Yes, breaking the law is illegal. Do you understand that doesn’t make the person illegal or even a felon?

The current MAGA “Christians” are like the Pharisees of Jesus’ time. So focused on the law while trying to feel holier than others that they would condemn the savior for healing on the wrong day instead of recognizing the miracle of the healing

Well said. I often say we’re more interested in being proven right then doing actual good. The Pharisees embody that attitude.

Yes, exactly like that. The act is illegal. Not the person. It’s not even a felony for heavens sake.

“fail to participate in the legal system”

Given my own experience with a brother-in-law being deprorted to a country where he cannot legally work, this sounds like a euphemism. We participated in the legal system, lawyers and all.

Two things can be true. Still shouldn’t hold a teenager wholly responsible for being scammed.

Absolutely. It’s amazing how many articles showcasing vibe coding is just people reinventing things like a password generator.

That’s the point. We should not make our children feel bad for not knowing better when we ourselves aren’t doing any better. Show some fucking empathy instead of saying you’re shit out of luck.

I do get therapy, thanks for the concern random stranger. I hope the same is true for you and that you understand that just because bad things happened to you doesn’t mean we should give such things a free pass and make ourselves emotionally unavailable to empathize with our children.

It’s like a parking ticket. Is everyone who had a traffic violation now an illegal person?

Amazing parenting to let them hurt themselves and their friends because you couldn’t educate them well enough to avoid a scam.

Edit: I am not saying the parent should have educated the child better, I am just saying when you go down this path of “well you should have known better” then the responsibility is on the parents to teach the kids better.

Exhibit A for why everyone needs therapy. I guess it’s little consolation that people reap what they sow.

You know what’s also a learning experience? Getting mugged. I hope you learn compassion before you learn that lesson.

Maybe not code but certainly use it to generate more slopspam

If it gets it wrong the first time I rarely reprompt. I know I can get it to fix it, but it’s usually faster for me to do it because I already figured out where and what to do the fix. Low key think it’s just a ploy to get us to burn more tokens. Sure correcting it means it writes a few lines to the memory file, but it’s only a matter of time before it trips over that context as well.

I have similar problems whenever I send it to investigate a bug and the local runtime is inside a container. It cannot reliably translate paths without the help of an IDE. Hell, it even occasionally mangles API paths if I have it prefixed elsewhere in the codebase (despite having Claude.md etc, your context needs to be pure for it to be reliable). Having it fix a Dockerfile is comically bad.

Any luck with integrating platform.io? Have a esp32 project but VSCode can’t provide type hinting with it’s main c++ extension that is used by platform.io.

Everything listed should be done before ever getting into code along with business and product partners.

Ehh, it really depends on where the risk is and the problem is LLMs can’t evaluate for that unless you feed it everything. Some projects need code experiments before you settle on an architecture, but that’s only if you’re a pioneer (which frankly is where the money is at).

In my experience there are three ways to be successful with this tool:

• write something that already exists so it doesn’t need to think
• do all the thinking for it upfront (hello waterfall development)
• work in very small iterations that doesn’t require any leaps of logic. Don’t reprompt when it gets something wrong, instead reshape the code so it can only get it right

The issue with debugging is that it doesn’t actually think. LLMs pattern match to a chain of thought based on signals, not reasoning. For it to debug you need good signals in your code that explicitly tell what it is doing and the LLMs do not write code with that level of observability by default.

Edit: one of my workflows that I had success with is as follows:

• write a gherkin feature file describing desired functionality, maybe have the LLM create multiple scenarios after I defined one to copy from
• tell the LLM to write tests using those feature files, does an okay job but needs help making tests run in parallel.
• if the feature is simple, ask the LLM to make a plan and review it
• if the feature is complex then stub out the implementation in code and add TODOs, then direct the LLM to plan. Giving explicit goals in the code itself reduces token consumption and yield better plans

Yeah, to some extent that’s what is going to happen. For a some of us the question isn’t “if” but how long will we have to endure.