Welcome

Agents and swarms of agents are quite nifty nowdays. My current setup is simple. It runs a coordinator that I communicate with, and that delegates work to a others. The flow is generally: "Hey, I need this feature from roadmap. Ask questions if needed, if I don't answer in due time, make the best call with our north star." -> Coordinator makes a plan for dev/qa -> dev devs -> pushes to branch when tests are green -> qa verifies results on dev server -> loopy-loop until obvious bugs are fixed. Review bot makes review for PR. Later on I test the feat to see if it's anything like I wanted and correct, then merge when good and pool to releases that are gated. Currently working on trying to get the agents to know what is good in my opinion.

I think the current killer combo is the ability to be creative and have some propriatory data, as that's something that can't be accessed by competition. The cost of iteration is low. So low that I see no point in using a wireframe demo for the ui, as simple paper sketches can be read by AI to close enough for live iteration for actually working software. And most rigid general UI's are going away too in favor of agents generating a personalized UX on the fly, so this is just temporary. Omarchy is the beacon for this, a machine that is ever evolving to your needs.

The stuff that stays valuable is hard to automate - having taste, accountability, human relationships and even defining what is good. No one knows what the future will be, but it will be awesome.

MCP was not clicking for me, so the best way to learn was to build a thing with it. I have a plethora of notes everywhere and now I have a machine that drops rough ideas into my publishing backlog.

MCP is basicly an api for AI that tells agents how it's supposed to be used.

Building an app factory, that utilizes Cloudflare's free tier resources to have quick and dirty apps to demo.

When you can do whatever you want to do, what do you want to do? I'm personally not so sure, since most of the problems in my world have been solved. On the other hand, you don't know what you don't know.

If you can automate something away quickly, you should do it. Writing the article is the part that provides value, and scheduling provides a way to write about things so that you don't need to do it on demand.

Internet attention works in such a way, that it's good for you if you get traffic. Increasing the amount of attention grabbing you can do with no extra effort is therefore valuable.

As a builder, this is also a fun hobby project to have while the baby is sleeping.

Most of the effort was for the implementation was looking for the right buttons to obtain tokens on LI's page, which made me feel like a archeologist looking at ancient ways of work. We also implemented an email-notification system that notifies me when tokens to various integrations are about to go stale, and I need to go clicking around to obtain new ones. I may outsource that to traditional browser automation when I get the 1st email in about 40 days.