Not sure if you have a kid or not, but another thing new parents struggle with are the once-a-month photos that show the babies age in months in a cute scene. That might have some potential if your newborn photo is too narrow of a market.

It's more of an orchestration and weaving them together than a deployment and hosting issue.

So far, I have tested by hand, but I have a few scripts where I turned the temperature down, and I seem to get the same results 100% of the time. This is for things like parsing salary details from a job posting, etc.

I don't struggle with writing them or testing them, but I have yet to find a good way to share and run them. I have several I can run from my terminal for scheduling meetings, but I don't really want a dozen agents running their own chat servers.

I am looking into PydanticAI because I use Pydantic for almost every one of my apps these days. I have also been using Anthropic's MCP framework which is amazing, but it only runs locally so far. I suspect one or both of those are going to make it easier for me to run Agents across dozens of apps, but I'm not there yet.

I also haven't seen a great way to chain Agents together as some of the DAG frameworks (like Airflow) do with tasks. I could be overthinking it, but this feels like it should be tackled.

Good luck and lawyer up then. Make sure you add damages to what is owed if you have to go to court. Might be worth reaching out to other vendors too.

The lawyer normally works, but sadly, once you get this far, they might be running on vapors. Good luck with it. We haven't had many of these over the years with my agency, but it's sadly non-zero. Long term, we have more than made up for it, even with former employees giving us referrals or work with their new companies over the years. I know a few who have got put in bad situations when the company ran out of money and couldn't pay them either. Bad deal.

You probably have three options. Work something out with the CEO that looks like a payment plan, hire a collection agency (expect to only recover 25% to 50% of it), or hire a lawyer to send them a letter and possibly take them to court. The letter is worth every penny, but taking them to court might not be.

In the future, make sure you get enough upfront that saves you from the last bit, and I would work out some level of, if we don't get paid, this code never going into production.

I would avoid all drama and if you have access still to anything. Delete that access and don't do anything that gets you in trouble. Short and long term, it's not worth it.

No, not in a while.

I liked Windsurf's side panel for prompting though. That's a step in the right direction. I used it to add a new view and it checked the right boxes for a Django project.

Overall, I am a fan of the LLMs powering these tools, but I don't think anyone has nailed the UI. I suspect in five years what that solution should be will be more obvious.

TIL Windsurf. I will give this a look and see.

Overall, I have never found Copilot or these apps to helpful. I think they can be excellent for some people, but I find myself fighting suggestions and getting distracted instead of focusing on the problem at hand.

Claude Projects I find to be mindblowingly productive, and I have several apps that are >90% written and updated by Claude. I also fine code generation via the raw APIs with both Claude and o1 to be worth the effort, but it's a big lift if you aren't sure what you want.

RE: exposing your time zone to the public - Ideally, anyone who is logged in with would only see times through the context of whichever timezone they selected. The rest should be UTC or whichever you pick. The point of the website is to work-in-public so I'm not sure why it would get more complicated then that.

People have to do something while they wait for results. So launch and write up how it goes.