While it's true that the packages are first party, .NET still relies on packages to distribute code that's not directly inside the framework. You still probably transiently depend on `Microsoft.Extensions.Hosting.Abstractions ` for example - if the process for publishing this package was compromised, you'd still get owned.

It's true that it takes 2 seconds to fasten a seatbelt but it still had to be mandated by law before most people started actually doing it

16MB is less than a display buffer for a 4k display. It is never ever going to happen again just due to hardware realities.

Do you add these into the code or into the review itself? I sometimes write these into the review, but I wonder if it's a useful information that should actually be inside the code that will get lost when the PR is merged

Into the review is what I’m talking about. The diff is often a scattered collection of files missing context, and may have refactors that obscure behavioral changes.

So there is reason to add comments that address a different readers understanding than the code rest.

I've gotten notices from Hetzner for hosting IPFS node, apparently it does some local network discovery by default which looks like a malware when you squint hard enough.

Don't forget that some of the new features are mutually incompatible. For example couple years ago you couldn't use the "new ui system" with the "new input system" even when both were advertised as ready/almost ready

As someone who's learned Vulkan to a fairly deep level over the last two years I've found learning with LLMs invaluable, especially for explaining concepts and the whys behind things.

That said debugging graphics bugs has to be some of the hardest things you can do as they generally manifest as driver crash followed by VK_DEVICE_LOST error. Vibe debugging these inside a 60k vibecoded rust renderer is... just not possible.

Agents can get you the initial boilerplate for setting up most of the resources, but are completely clueless about subtle issues with synchronization, transitions, formats and so on.

Doesn't that make people with best opportunities (most skilled workers) leave and people with least opportunities (least skilled workers) stay?

Personally if I was offered 6+ months of severance I just couldn't justify staying even in the best companies I've been at.

Yes but usually that’s fine because you structure it to happen over a timeframe that you (the company) chooses based on the person.

You joke, but I remember seeing a talk by Wunderlist CTO who has pretty much that. Also polyglot company and microservices in random languages. Can't find the talk now, but https://www.infoq.com/news/2014/11/gotober-wunderlist-micros... mentions 60 services at least.

I need to get more ideas for my side project. A todo list app with micro services, but everything in bash scripts. So far it's just 6 services.

https://github.com/andi0b/vibe-todo

I'd guess that today cameras with microphones are no more expensive than cameras without