Programming is mostly research. Researching curses to cast on the guy who wrote the Incomprehensible mess you’re currently debugging.

Most can’t, but that’s why clandestine cyber-intelligence firms like NSO group exist.

I’ve programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.

It’s one of those things that almost should never be used, but the times it’s been needed, it removed a lot of silliness.

async/await was introduced in version 4.5, released 2012. More than a few releases at this point!

Powershell

/s

The company I work for is smort

This is every company I’ve ever worked for. If other people didn’t vouche for their own tests, I’d assume automated testing was a myth.

Machines aren’t people. Machines don’t learn. Machines copy data, manipulate and replicate it. That is copyright infringement. The laws for Machine duplication don’t apply to human learning.

Razor

Razor is the templating engine that’s been there since the original MVC. Blazor Server is the one that needs a server and streams changes to the client using signalR. Blazor WASM is the one that uses Web Assembly. As of .Net 8, Blazor can now also ne used as a generic SSR backend. They all use Razor Components, which is a component model using the Razor engine.

Not to be confused with Razor Pages, which is also a generic SSR backend.

To list some good ones that haven’t already been ssid:

Stop podcasting yourself

A problem squared

Secretly Incredibly Fascinating

Oh wow, I’ve seen this guys shorts start popping up constantly. He seems like he understands the algorithm enough to explode

Seems it got much worse.

Seems like it’s going great for the developer.

Htmx for server requests and AplineJS for client interactions

You can write it in whatever language you want, as long as it’s rust.

/s

Depends:

For websites: Htmx + AlpineJs on the front end, ASP.NET Razor Pages and PostegreSQL on the backend.

For Web Apps; Blazor and PostgreSQL

In a 4-D chess move, by canceling everything with no resolution, they’ve made their shows not worth pirating by making them not worth watching.

I thought it was a balance between new shows getting better engagement than old shows, and contracts lasting 3 seasons, which required re-negotiations in favor of the talent. Basically a business model hyper-focused on subscriber growth metrics instead of subscriber retention.

I didn’t have an answer for a very long time. Or more seriously, the answer was “the one that paid the most”. I’ve run the gamut of popular languages, C, C++, Java, Javascript, perl, ruby, Python, Visual Basic, VB.Net, C# and F#.

But the last couple years it’s really been C#. The pace of development on the language/runtime has really picked up with yearly releases. The features that are added and iterated on are expressive and intuitive. You can tell from the discussion posts on how a feature is being considered for inclusion is thoughtful and deliberate. It really feels like the language is in good hands.

Just wish those hands weren’t Microsoft.

Wild swings between the greatest trip you’ve ever had, and excruciatingly slow death.

I find ORMs exist best in a mid-sized project, most valuable in a CQRS context.

For anything small, they massively over complicate the architecture. For the large enterprise systems, they always seem to choke on an already large and complex domain.

So a mid size project, maybe with less than a hundred or so data objects works best with an ORM. In that way, they’ve also been most productive mainly for the CUD of the CRUD approach. I’d rather write my domain logic with the speed and safety of an ORM during writes, but leverage the flexibility and expressiveness of SQL when I’m crafting efficient read queries.

Some of us have had to support multiple database targets. So I don’t know about changing a database in a running application, but a good abstraction has made it easier to extend support and add clients when we could quickly and easily add new database providerz