How to organize Claude Code for product work(theaithinker.com) |
How to organize Claude Code for product work(theaithinker.com) |
Personally both apply to me, I also don't care about projects where the author hardly did any coding themselves.
The only semi impressive vibe coded projects I've seen so far have been rewrites, though.
The least interesting content is "here is how I burn tokens to build mediocre software".
However I would never use someone else's starter repo. The whole point is to augment my own perspectives and strengths. On top of that, the AI written pitch is extremely off-putting. If you can't even bother to take the time to write your own pitch, why would I believe for a second that your workflow has anything unique that goes beyond the lowest-common denominator AI capabilities.
There is danger in over-fitting the agent. Fast release cycles require frequent model switching, sometimes to another provider altogether.
In the end, it's hard to measure improvement. Most of the advice out there is vibes based, treat it as such.
You cannot write the files directly nor can you download them directly, but you can ask a chat to show you the content or only the mermaid diagram that exists in workspace.md (or however you want to name it), and mermaid can represent quite complex networks out of the box, their relations, what is blocking something else, and so on. Chats can then edit this file with search-and-replace instead of re-writing it all over again.
(I am a PM of 15 years trying to navigate all of this…)
I'm seriously worried that my and other companies in my network have product leadership that are wasting their mental bandwidth on AI fun stuff, needlessly writing their own random tools, etc - while the product scope is going in random directions with zero product vision. This is not about job protection or "stay in your lane".
For those that didn't read the article, one of the first things it says, in bold nonetheless, is "I didn’t design this system. I arrived at it"
The code that goes into PLC equipmentss and hardware is incredibly simple—but it's still a product. If you look under the hood of a lot of software, the code is a mess. Still, it's a product. And when Claude's code leaked, everyone laughed at the code hygiene—but a lot of people still used it.
What is a product, really?
What is a product? 106 points by rogix 4 days ago | 68 comments https://news.ycombinator.com/item?id=49202690
There is a lot of hand wringing in the software space about ai code being a mess - but from a product perspective code quality doesn’t matter. It’s the reliability of what people (or agents) use that matters.
Code quality used to further that goal but only because it was really hard to rewrite or fix code. If that barrier is removed does anyone really care what the code quality under the hood is?