I’m tired of these AI written articles man. There could be information worth sharing here but having it all generated makes me assume you don’t care. So neither do I.

Same! We need a "Stop the Slop" movement or something like that.

One man's starter workspace is another man's context pollution.

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.

Claude.ai Web (non-Code) has this feature where you can write into /areas/ or /topics/ and these files are automatically updated in other chat's sandboxes (but not re-loaded in those chats).

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.

what is chat?

From "What chat mode can’t give you", non-code Claude on the web.

This blog post immediately reads as AI slop. Why bother reading it if they can’t be bothered to write it?

Sometimes I wonder what 'product-level' code really means. What actually is a product?

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?

I belief is product simply has come to mean the most visible layer of the thing. For hardware "visible" layer is a literal device but more important product is what the device can do, a port is useless if there are no driver codes for it. For websites product can just mean the site/app does the thing, regardless of if it does it well, consistently, or could be done better. This is why words like "taste is what matters" and "code was never the goal" are said so often, I argue code is in the point but more people just care it works without going much deeper.

A product is what people (or now agents) can use to carry out any activity.

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?

Any product manager worth their salt should be in a coding interface--the line between Product and Engineering is blurring a lot more now, and to stay competitive PMs will need to reach a little further into the technicalities. Otherwise you risk just being another “idea guy” pushing tickets around, basically customer support on steroids which is getting eaten by Agents. Connecting the ideas to something tangible and translatable that an Agent could not do themselves is the new game.

(I am a PM of 15 years trying to navigate all of this…)