Just a reminder to have redundancy in your cloud environment. One of my hosting providers had a hardware failure and needed to offline migrate some services. My instance was mostly unaffected, but for maybe 20 minutes. However my service as a whole were completely uninterrupted, users shouldn't have noticed whatsoever, and all I had to do was keep an eye on my logs, everything else was automatic. The server came back online and traffic was restored.

That's rough. Could have been a thousdanare

I don't like to share active hardware, but it's replacing a Dell r330 as a witness.

I just traded a 64gb kit of consumer DDR4 for a new server XD. Then I'm about to sell an 8 year old machine for just shy of the price it was new. Hardware prices are wild.

That's where I really wish the OSS devs were moving toward. AI is focused on fast, consuming MW of power just to give you a smart response on demand. I don't need that all the time. I need predictable automation that can run 24/7. I don't care if my server runs all night (that's it's job) automating tasks predictably. Just add things to my calendar, schedule phone calls, import and filter my emails, organize my notes, organize my filesystems, fetch and store relevant extra information. Just automation tasks that require some consistant reasoning that can be written down, and so long as it's reasonably deterministic, and the tools have error checking and correction, shouldn't be a problem.

For coding, I've found qwen 3 coder to be the "best" but even the 27b model is not very useful when things like Claude 4.5 are just becoming useful. It's good for checking for typos, or very basic single file changes, and even with a beefy server it's going to take a few minutes to submit a single patch, assuming it gets the tools correct. I've found the smaller instruct models know how to use the tools a little better, but they're dumb and direct.

I use continue.dev extension in vscode with my OpenWebui server (connected to ollama). I assume you're running locally?

That's the fun part about mono-repos. Lots of things packed together, very few are part of the same application. Could be though I suppose. My CMNext application ships at about 12mb compressed, about 23mb on disk. If you added all the extra bells and whistle features like database support and caching stuff it could probably grow to double that. It's worse during dev. I think the total disk size is somewhere around 5gb, mostly thanks to nodejs

It is over 100k files on the disk in the workspace directory is has to filter. Only about 13k are editable source code files. The rest are binaries and other package related files I suppose.

Worth getting back to pen and paper imo! I'm off an on with it. But I can't use anything electronic, the only thing is the pad I have is a little to large to take with me.

It's only about 13,000 source code files XD

vscode really be struggling with workpaces with over 100k files :( I added another repo and it's just tanked to be almost unusable. I've removed all but 2 extensions. Copilot and my theme.