My experience has been the opposite: affordable slop makes me way more conscious about architecture because bad patterns become useless exponentially quicker.

But in many cases self hosted or dedicated boxes are cheaper than cloud.

One approach is "Trust No Code" and the other is "Trusted code should run safely".

the first one sounds better on paper, but leads to a very complicated system. That said, I haven't worked with jails much or other forms of sandboxing. It just seems to me that to make software function you need escape hatches, and the more of those you have, well, now you're back to plugging exploits with a more complicated system.

It was interesting to me to hear that even though OpenBSD had designed their software to limit permissions even before pledge and unveil were released - upon release they found that a shocking amount of their software actually wasn't following their own rules.

I have not really used airdrop, and this app is super useful to me.

This seems to be a good window where I can implement a pretty large feature, and then go through and address structural issues. Goofy thinks like the agent adding an extra database, weird fallback logic where it ends up building multiple systems in parallel, etc.

Currently, I find multiple agents in parallel on the same project to be not super functional. Theres just a lot of weird things, agents get confused about work trees, git conflicts abound, and I found the administrative overhead to be too heavy. I think plenty of people are working on streamlining the orchestration issue.

In the mean time, I combat the ADD by working on a few projects in parallel. This seems to work pretty well for now.

It's still cat herding, but the thing is that refactors are now pretty quick. You just have to have awareness of them

I was thinking it'd be cool to have an IDE that did coloring of, say, the last 10 git commits to a project so you could see what has changed. I think robust static analysis and code as data tools built into an IDE would be powerful as well.

The agents basically see your codebase fresh every time you prompt. And with code changes happening much more regularly, I think devs have to build tools with the same perspective.

The more accessible software becomes the more infra is required to support it, and the more complex and convoluted the software will be

I think it'd be cool to do assembler on a Pi Pico or something, that seems like it would be a fun exercise.