In the old days you could tune IIS + Garbage collector manually to get similar behaviour but was usually not worth it. Time was better spent elsewhere to optimize other things in the pipe and live with the GC freezes. I suspect GC hickups should now be much smaller/shorter too, as the overall load will be lower with new GC.

Scoped & transient lifetimes along with the new GC will make the runtime much leaner.

Some application are singleton heavy or misuse the MemoryCache (or wrap it as a singleton... facepalm) - these will still mess the GC situation up.

If you build web/api project it pays dividends to educate yourself on the 3 life times, how the GC works, how async/await/cancellation tokens/disposables work, how MemoryCache work (and when to go out-of-process / other machine aka Redis), how the built-in mechanisms in aspnet works to cache html outputs etc. A lot of developers just wing it and then wonder why they have memory issues.

And for for the dinosaurs: yes we can use the dependency injector in Windows Form, WPF, Console Apps and so on - those packages aren't limited to web projects alone.

Try this:

Have a look at xyz.cs. Do a full audit of the file and look for any database operations in loops that can be pre-filtered.

Or:

Have a look at folder /folderX/ and add .AsNoTracking() to all read-only database queries. When you are done, run the compiler and fix the errors. Only modify files in /folderX/ and do not go deeper in the call hierarchy. Once you are done, do a full audit of each file and make sure you did not accidentally added .AsNoTracking() to tracked entities. Do no create any new files or make backups, I already created a git branch for you. Do not make any git commits.

Or:

Have a look at the /Controllers/ folder. Do a full audit of each controller file and make sure there are no hard-coded credentials, username, password or tokens.

Or: Have a look at folder /folderX/. Find any repeated hard-coded values, magic values and literals that will make good candidates to extract to Constants.cs. Make sure to add XML comments to the Constants.cs file to document what the value is for. You may create classes within Constants.cs to better group certain values, like AccountingConstants or SystemConstants etc.

These kinds of tasks works amazing in claude code an can often be one shotted. Make sure you check your git diffs - you cannot and should not blame AI for shitty code - its your name next to the commit, make sure it is correct. You can even ask claude to review the file with you afterwards. I've used this kind of approach to greatly increase our overall code quality & performance tuning - I really don't understand all the negative comments as this approach has chopped down days worth of refactorings to a couple of minutes and hours.

In places where you see your coding assistant is slow or making mistakes or it is going line by line where you know a simple regex find/replace would work instantly, ask it to help you create a shell script as a tool for itself to call, that does task xyz that it can call. I've made a couple of scripts that uses this approach that Claude can call locally to fix certain code pattern in 5 seconds that would've taken it (and me checking it) 30 mins at least and it wont eat up context or tokens.

What would really be useful is a very similar prompt should always give a very very similar result.

Your brain doesn't have this problem because the noise is already present. You, as an actual thinking being, are able to override the noise and say "no, this is false." An LLM doesn't have that capability.

It’s the same reason why great ideas almost appear to come randomly - something is happening in the background. Underneath the skin.

maybe it can work if you are running your own inference.

It had the best slide-out keyboard of all the phones, nice and rubbery keys. Super smooth sliding motion.

It also had a FM Transmitter (not just Receiver), so I could blast audio in my first car back then without struggling with bluetooth kits & audio cable (neither was standard).

It also had an infra-red transmitter that was programmable, so you could use it as a remote in certain circumstances.

It the time, the 32GB storage was absolutely massive for a phone.

It also had stereo speakers & a kick-stand, so you could watch a movie on it without issues.

I really miss this phone & era. Maemo OS could've owned the market today, as at the time it was much better than early Androids. Nokia messed up so hard after this, the N9 was shitty in comparison.

Here is one output:

The Frog Monk and the Squirrel Student

Deep within the bamboo grove, where the wind whispered like flowing code, sat Master Frog, robed in emerald cloth, staff resting across his lap. Before him, a young squirrel, bright-eyed and eager, bowed low.

“Master,” the squirrel said, “I wish to learn the way of software engineering. But the paths are many, and I do not know which road leads to wisdom.”

The frog monk closed his eyes, and spoke in a voice like rippling water: The Virtue of Type Safety

“Child,” said the frog, “imagine a bridge built of stone. Each stone is measured, each arch tested. This is the way of type safety. When you walk across, you know the bridge will not crumble beneath your paws.

But in the land of dynamic languages, bridges are built of twigs and promises. They may hold, or they may break when the storm comes. The traveler must always fear the hidden crack.

Thus, type safety is the discipline that guards against chaos. It is the monk’s staff, steady and unyielding.” The Benefits of Object-Oriented Programming

The squirrel tilted her head. “And what of the world itself, Master?”

The frog smiled. “The world is vast, yet it is made of objects. The tree, the river, the stone—all are beings with their own nature. In object-oriented programming, we honor this truth. We give each thing its form, its methods, its inheritance.

Without this order, the world becomes a tangled forest of functions, each branch crossing another. But with objects, the forest is tended, paths are clear, and the traveler may walk without losing her way.” The Generosity of the Garbage Collector

The squirrel’s tail flicked. “But Master, what of the burdens we leave behind?”

The frog tapped his staff. “Ah, that is the gift of the garbage collector. Like a kind monk sweeping the temple floor, it gathers the forgotten scraps, the abandoned memory, the dust of old variables.

It asks for no thanks, yet it keeps the temple pure. Without it, the temple would overflow with clutter, and the student would drown in her own neglect. This is generosity: unseen, yet ever present.” The Tyranny of Dynamic Languages

The frog’s eyes grew stern. “Beware, child, of the tyranny of dynamic languages. They promise freedom: ‘Write quickly, without rules!’ But freedom without discipline is chaos.

The tyrant whispers: ‘Trust me, the errors will reveal themselves later.’ But later may be too late—when the bridge collapses, when the temple burns, when the forest is lost.

Thus, the wise engineer does not bow to the tyrant. She chooses the path of safety, of order, of generosity.” The Lesson

The squirrel bowed again, her heart alight with understanding. “Master, I see now. To walk the path of software engineering is not merely to write code, but to live with discipline, order, and gratitude.”

The frog monk nodded. “Then go, child. Build bridges of stone, tend forests of objects, and honor the unseen sweepers of memory. In this way, your code shall endure, and your spirit shall remain free.”

And so the squirrel departed, carrying the wisdom of the frog monk into the world of software.

Also have you read some of the setup instructions for some of these things? I'd be churning out 1000 lines of ansible crap.

Either way since Proxmox 9.1 has added at least initial support for docker based containers the whole argument's out the window anyway.

These things are a proxmox home lab user's lifeline. My only complaint is that you have to change your default host shell to bash to run them. You only have to do that for the initial container creation though.

I think it's the best of every world. Self contained, with an install script. Can bring up every dependent service needed all in one command. Even your example of "a simple script" has 5 different expectations.

With Windows 11, although I mostly like the UI (rounded corners on a high dpi tablet also with rounded screen is amazing), it feels absolutely gross, in the corporate soulless sense. It feels mentally heavy top operate. I constantly had to battle it to get it to work the way I want it.

These days all my devices are running Fedora with KDE, which is just the best. You basically set it up once the way you like it, and it won't change by itself for months. It is a buttery smooth experience and have had zero need to go back to Windows yet.

If anyone want the same level one-ness with your computer like back in Windows XP & Windows 7 days, give KDE a try. Fedora is pretty simple distro to get used to if you want a good starting point.

I mentioned to a friend recently that W11 is so difficult to use compared to Linux like Mint nowadays. He didn't understand it, though he tried Mint a decade ago but kept using Windows 10, upgraded to 11, continues to have driver problems with his laptop, some weeks network card stops working some weeks his sound card drops out completely. He uses usb dongles intermittently, it reminds me how I used on laptop Linux 20 something years ago and even then it wasn't that bad. I feel preaching Linux is almost counter-effective, but I'm tired of being asked to solve his hw problems caused by bad W11 drivers.

I get the same feelings whenever I am near an interface that looks anything like NT4.0.

That’s… not a good sell at all

Promise me a decade and I’ll bite. (Joke’s on me, I’ll need to get out of this windows shithole asap)

For servers, we just use containers.