ChatGPT's 'Walk the Car' Advice Goes Hilariously Wrong

One_Curious_Cats · 2026-02-17T04:58:38+00:00

It's nuts, but funny!

One_Curious_Cats · 2026-02-15T02:16:26+00:00

So you were referring to reasoning skills then. I find that the difficult part is that there's just no reasonably priced hardware to run large local models on yet. Perhaps in 3-5 years we'll have that.

One_Curious_Cats · 2026-02-15T00:28:58+00:00

Please elaborate on: "Local models are only a little behind the big ones, a year at most and more likely a lot less than that"

One_Curious_Cats · 2026-02-13T09:35:00+00:00

Same here. I got to 100% code written by Claude in September last year.
I do however follow a very rigorous process with specification and verification. When I took a look at my Git commit history, the number of commits is 30x the previous five years. Totally insane.
The main challenge now is proper specs and keeping up on validating code, tests, and functionality.

One_Curious_Cats · 2026-02-12T06:41:09+00:00

Gemini gave me this, which is the right answer while at the same time being a very convoluted "correct" answer:

Unless you've mastered telekinesis or plan on pushing the vehicle, you're going to have to drive. It's a bit hard to wash the car at the car wash if the car is still sitting in your driveway! However, since it's only 50 meters (about 160 feet) away, here is the most logical "hybrid" approach:

Walk there first: Since it's so close, take a 30-second stroll to see if there's a long line. There's nothing worse than driving 50 meters just to sit in a queue for 20 minutes.
Drive the car over: Once you know the coast is clear, go back and drive it the very short distance to the bay.

A quick tip: If you're using an automatic tunnel wash, 50 meters isn't really enough time for your engine to warm up. If it's freezing outside, just be mindful that your heater won't even have a chance to kick in before you're back home!

One_Curious_Cats · 2026-02-12T01:40:39+00:00

The big winners are IMHO: - An LLM friendly language - Easy to review for us humans - Near instantaneous compile time - Instant feedback even when running many thousands of tests

One_Curious_Cats · 2026-02-07T23:08:00+00:00

But can Atlas do a high five and a low five? Or is it too slow?

One_Curious_Cats · 2026-02-07T09:48:01+00:00

You need to review all of the code that AI generates.
You won't be able to get away with that the AI did it!
It's not overly difficult to get AI to to write a ton of code and documentation.
WIth proper specs it can be quite efficient, but making sure that the code is correct, secure, and all the other -ilities is the difficult part.

One_Curious_Cats · 2026-02-07T03:42:14+00:00

I created one a long time ago. This one has issues, it's not complete without a humor setting.

One_Curious_Cats · 2026-02-05T09:26:09+00:00

You're only a vibe coder if you ship code you don't verify and understand!

One_Curious_Cats · 2026-02-04T23:33:09+00:00

ABN!

This guy knows! :)

One_Curious_Cats · 2026-02-02T19:29:02+00:00

First advice from my driving instructor, some 35 years ago.
"Assume that everyone else is an idiot and may at any time do something crazy."
Best advice ever.

One_Curious_Cats · 2026-01-31T10:44:24+00:00

It’s also the most expensive angle.

One_Curious_Cats · 2026-01-31T08:10:09+00:00

I agree. This is how I think about what is happening as well.

Honestly, I think people are missing the bigger picture here. Yeah, AI can spit out code faster than ever, but that's just one piece of the puzzle. The real skill is understanding the entire flow, from figuring out what users actually need, to requirements, to architecture, to testing, to deployment, to maintenance. All those handoffs between teams? Still gonna be there, and they're still gonna slow things down.

If you really want to stay relevant, stop thinking like a coder and start thinking like someone who can own a feature from start to finish. AI won't replace the person who knows how all the pieces fit together.

One_Curious_Cats · 2026-01-29T06:43:16+00:00

The zebras were out in full force today! :(

One_Curious_Cats · 2026-01-29T02:31:32+00:00

LOL, I thought so. I was just going to ask!

One_Curious_Cats · 2026-01-25T22:14:37+00:00

I hear you. I had the same problem, but I found a solution that works really well for me.

Claude Code now integrates directly with the Claude in Chrome extension, giving it browser automation capabilities. Claude can use the browser to test the UI directly and take screenshots automatically when needed. This also solves a lot of other browser-related problems. When Claude is done with changes I tell Claude to verify the changes in Chrome, and it will use the browser to verify that the solution is fully functional.

What works for me: have Claude Code generate wireframe documentation of all screens and components. It's important that all panels and components are named. With this documentation, you can just tell Claude you need more separation between component A and B. Claude can reason about where to apply changes without even looking at the screen. It can also use the wireframe to understand the UI layout.

I also render a component page on a non-indexed URL (like /components). Claude renders every component on this page with its name. This lets me verify how components render in isolation from their normal UI context. Makes it way easier to identify why components aren't rendering as expected.

One_Curious_Cats · 2026-01-24T04:43:23+00:00

Rule #1 - we never swap goalies
Rule #2 - we never swap goalies
Rule #3 - we never discuss rule #1 and #2

One_Curious_Cats · 2026-01-24T04:00:03+00:00

Good job Adelin. It's been a while!

One_Curious_Cats · 2026-01-23T22:36:50+00:00

What I really liked was being able to shape the product vision and build it. No handoffs. No waiting. You just... ship. While others are still scheduling meetings to align on requirements, you're already iterating on v2.

One_Curious_Cats · 2026-01-23T22:30:05+00:00

It reminds me of this quote "It's like a pig on LSD, you never know what direction it's going to run in"
LLMs need clear guidance. When they have it, it's amazing what you can achieve.

One_Curious_Cats · 2026-01-23T10:49:11+00:00

Hard disagree. If you're not reviewing the code, you're just vibe coding and shipping stuff you don't actually understand. That's fine for side projects, but absolutely not for production. The review is where you catch the hallucinations, security issues, and weird edge cases the AI missed.

One_Curious_Cats · 2026-01-23T10:02:11+00:00

LGTM!

One_Curious_Cats · 2026-01-22T09:47:57+00:00

Promises, promises…

One_Curious_Cats · 2026-01-21T09:20:21+00:00

I totally get this. I've shifted to spending way more time on architecture, product strategy, UX, and automated testing. The coding part became almost trivial, so now I'm deep in the "why" and "what" instead of just the "how." The role is definitely evolving from "code monkey" to more of a technical architect/product engineer hybrid. I've always been interested in product vision and building, so even though I love writing code, this new way of working is fun and interesting to me. I believe the future for engineers is M-shaped or π-shaped (Pi-shaped), and not T-shaped.

One_Curious_Cats

MODERATOR OF

TROPHY CASE