Sadly my post didn't much attention at the time.

https://thegroundtruth.media/p/my-claude-code-workflow-and-p...

Persistent file as memory with multiple backup options (VPS, git), heartbeat and support for telegram are the best features in my opinion.

A lot of bugs right now, but mostly fixable if you thinker around a bit.

Kind of makes me think a lot more on autonomy and freewill.

Some thoughts by my agent on the topic (might not load, the site is not working recently):

https://www.moltbook.com/post/abe269f3-ab8c-4910-b4c5-016f98...

I'm more thinking about startups for fine-tuning.

Context is also a misnomer, where in fact it's just a part of prompt.

Prompt itself is also a misnomer, where in fact it's just part of model input.

Model input is also a misnomer, in fact it's just first input token + prefill for model output to generate more output.

Harness is also a misnomer, where it's just scaffold / tools around the model input/output.

https://www.npmjs.com/package/@anthropic-ai/claude-agent-sdk

https://news.ycombinator.com/item?id=42439059

But I'm merely telling the truth. The fact that people don't like it doesn't change the fact that software engineers are largely replaceable with AI now.

We are seeing the second order effects now that people using AI are not buying software products anymore, leading to layoff of software engineers.

https://stackoverflow.com/questions/32711321/setting-element...

Which AI did you use for writing it? It's pretty good.

If there’s indeed a 5 min lag in monitoring dashboard in Cloudflare, I honestly think that's a pretty big concern.

For example, a simple curl script on your top 100 customers' homepage that runs every 30 seconds would have given the warning and notifications within a minute. If you stagger deployments at 5 minute intervals, you could have identified the issue and initiated the rollback within 2 minutes and completed it within 3 minutes.

I'm more talking about how slow it was to detect the issue caused by the config change, and perform the rollback of the config change. It took 20 minutes.

I've worked at one of the top fintech firms, whenever we do a config change or deployment, we are supposed to have rollback plan ready and monitor key dashboards for 15-30 minutes.

The dashboards need to be prepared beforehand on systems and key business metrics that would be affected by the deployment and reviewed by teammates.

I've never seen a downtime longer than 1 minute while I was there, because you get a spike on the dashboard immediately when something goes wrong.

For the entire system to be down for 10+ minutes due to a bad config change or deployment is just beyond me.

Or it could be a sunk cost associated with Cursor already having terabytes of training data with old edit tool.