It'd probably be cold day in Hell before AI replaces veterinary services, for example. Perhaps for mild conditions, but I cannot imagine an AI robot trying to restrain an animal.

All these so-called safe jobs still depend on someone being able to afford those services. If I don't have a job, I can't go see the vet, the fact that no one else can do the vets job is irrelevant at such a point.

I would like to know if there's some kind of inflection point, like the so-called Laffer curve for taxes, where once an economy has X% unemployment, it effectively collapses. I'd imagine it goes: recession -> depression -> systemic crisis and appears to be somewhere between 30-40% unemployment based on history.

Every job deemed "safe" will be flooded by desparate applicants from unsafe jobs.

I appreciate that Finland considers Internet access of a minimum of 1 Mb to be a basic human right. I am not sure if other countries follow, but I wish the USA did.

It's laughably slow given how bloated the modern Web is. In fact even 10Mbps is barely enough to stream 1080p content.

You’re not entirely wrong about bloat on modern websites, but if you griped about being unable to stream 1080p video to someone even just 15 years ago you would sound absurdly privileged

In my time, I have potentially written code that some legal jurisdictions might classify as a "crime against humanity" due to the quality.

I firmly agree with your first sentence. I can just think about the various modders that have created patches and performance enhancing mods for games with budgets of tens to hundreds of millions of dollars.

But to give other devs and myself some grace, I do believe plenty of bad code can likely be explained by bad deadlines. After all, what's the Russian idiom? "There is nothing more permanent than the temporary."

> choosing to use AI isn't all or nothing.

That's how I have been using AI the entire time. I do not use Claude Code or Codex. I just use AI to ask questions instead of parsing the increasingly poor Google search results.

I just use the chat options in the web applications with manual copy/pasting back and forth if/when necessary. It's been wonderful because I feel quite productive, and I do not really have much of an AI dependency. I am still doing all of my work, but I can get a quicker answer to simple questions than parsing through a handful of outdated blogs and StackOverflow answers.

If I have learned one thing about programming computers in my career, it is that not all documentation (even official documentation) was created equally.

It's funny you say this because this is considered the "old" way to use LLMs since agents can write code so well, but I don't think enough people realize how much more efficient your preferred approach is compared to the era before LLMs were widely available at all.

Gone are the days of hopeless Googling where 20 minutes of research becomes 3 hours with the possibility of having zero solutions. The sheer efficiency of having reliable, immediate answers is a tremendous improvement, even if you're choosing to write everything by hand using it as a reference.

"Reliable" is still a huge misnomer here. You definitely need to grok through hallucinations and sometimes come up empty.

Same! I don't mind copy/pasting a code snippet or asking a question, and I also always ask it to show its sources for anything non-obvious. That alone cuts down on a lot of bullshit.

> nullable reference types.

What would you suggest instead? I quite like the nullable reference types, but I do know many get annoyed. My brain is often a scurry of squirrels, so I grew to become thankful for the nullable refs overtime.

I don't mind NRT but I hate dealing with C# projects that haven't set < Nullable>Enable</Nullable> in their csproj. It's not perfect because I know at runtime it can still be nullable but it's nice when the compiler does most of the checks for you.

The compiler now mostly solves this now but the abstraction is a little leaky.

I heavily use nullable types but I always want them to be declared nullable.

It's true. You will incur the wrath of C#'ers if your simple ToDo list app doesn't have a ToDoListItemRepositoryServiceFactory.cs and a minimum of 4 separate layers in which one must update 20 files because you added a property to one class.

Don't get me wrong, I still love C#/.NET. I use it everyday, but my god, has Swift been a breath of fresh air. The Swift community, when not whining about Swift UI, has been much less dogmatic in my experience.

Blazor is pretty cool if you are into that kind of stuff. Mind you, you still might need the slightest tiny dash of JS, but depending on your needs, you might be able to get away from JS entirely.

Somewhere its in my list of things to try one day. Maybe an ai agent can help make this happen.

> the "default" ORM is far more flexible and powerful

I have never used any ORM that is as capable. Entity Framework Core with Linq is what keeps me on .NET.

Because EF's default behavior implements Unit of Work, a LOT of the complex transactional spaghetti ended up disappearing when we switched.

This aspect of EF is highly underrated for complex entity graph mutations.

EF makes the 90% use case easy and the 10% case possible with very little pain. The interceptors, global conventions, and other extension points are an enabler of complex behaviors that are still transparent to most of the team.

> Because EF's default behavior implements Unit of Work, a LOT of the complex transactional spaghetti ended up disappearing when we switched.

I have never felt more understood by a fellow HN user. I think I know the exact spaghetti you are talking about, and I agree with you 100%. I wish EF could create (SQL) views, but it's not really any issue considering I can just use raw SQL to accomplish the same thing.

> complex entity graph mutations.

I'm too dumb to know what those words mean together. But I going to assume it's something to do with complex entities. If so, I completely agree as well. I sometimes harness the powers of the Dark Magics where my domain entities and database entities are the same objects (I'm not one of those DDD people either). Thanks to EF, I've been able to create some complex objects that really have cut down on a lot of useless objects I used to litter applications with.

Discriminated Unions is one thing I would like.