Claude, change the “Add to Cart” button to blue
481–486 of 486 posts
Re: Claude, change the “Add to Cart” button to blue
#482Earlier quoted context omitted.
>Maybe I'd waste a day trying to get an API to do something it turned out it couldn't do. I was working on a side project recently. I had spent months designing the data model in my spare time, thinking through how to make it as elegant and durable to change as possible in the long term, since (if I launched it) the repercussions for getting it wrong would be significant. Once I had a working design, it probably woul…
(Appreciating this entire thread) - side question: you used the word ‘shape’ in the abstract sense, something I never came across until Claude vibecoding came along. Was it common / did you use ‘shape’ in the abstract sense before say 2025? Also, my coming from being a non-coder, I have a lot of appreciation for the possibilities for project failure one way or another due to a data model or project schema being wrong…
As far as I can remember, this has been fairly common in tech (or at least where I've worked) for some time, though it's possible that my memory here is a bit fuzzy. I will say that my spouse has often commented that "Claude talks like you", which I suspect is because it is trained on a lot of language specific to the tech world.
>My question is, does your conception of data models in the abstract come from a formal academic course, like an algo’s & data structures course, or from trade-knowledge acquired through the practitioner grapevine?
I have worked for over a decade on the telemetry for a specific major product that most people have probably used, and shepherded it through a major re-architecture, so most of this is from my career. I came in right after it was built and witnessed the pain as things had been layered on over a long period of time as the product evolved, so I've just witnessed all the pointy bits where naive early decisions can come back to bite you later.
Re: Claude, change the “Add to Cart” button to blue
#483Earlier quoted context omitted.
So instead of talking directly, you talk indirectly through ticket ?
I’m of the feeling that talking directly to these things all day is a path to madness. They talk to each other, come to consensus, and give me a structured thing to look at that has already been vetted and tested and screenshot evidence and a verification plan. It’s not conversational for me.
Do you run into this problem? If not, then I need to figure out how to stop running into it myself.
If so, then how do you give it all the incremental corrective feedback without a conversation?
Re: Claude, change the “Add to Cart” button to blue
#484At least with Codex, this has not been my experience at all. It still screws up sure, but in every case I can ask "why did you do this" and it can trace back what made it take that particular decision. Typically it's always that I either didn't specify the problem correctly or made a really dumb mistake (executing the task on the wrong project....did this one yesterday) or it's something within a skill file that inst…
When you've been perfectly precise in your spec and language, isn't that programming? Why use a stochastic goblin to do things in that case?
ofc we don't have that, so code is compressible, and compressible a lot. You can say what you need in English much shorter than in in any programming language
Re: Claude, change the “Add to Cart” button to blue
#485Earlier quoted context omitted.
I learned this from "The Elephant in the Brain", which I strongly recommend: https://amzn.to/4iSyLX8
I learned this from Dirk Gently’s Holistic Detective Agency , which I strongly recommend.
Don't remember that part though. It's been a few decades.