> The WSJ report added that the rule is expected to make quarterly reporting optional and not eliminate it altogether.

So companies can still do their quarterly reporting if they and their investors want that.

Good argument for it but I think 80/20 split applies here. It is likely that 80% of the time it is used to farm for upvotes and add noise.

> And despite what people say, the way you write is very much judged as an indication of your education and intelligence.

I have come across plenty of content and online interactions in English where English was the Author's 2nd or even 3rd language and I find that putting a small disclaimer about this fact is more than enough to bypass such judgement.

It is very nice having an Operating system that respects the Hardware I own and makes efficient use of it. My experience has been very good so far. Every device in my custom built desktop PC worked immediately. The only driver I had to build and install was for my XBOX Wireless dongle.

Gaming has been really damn good. I installed Steam and my games just worked. No fiddling around with configs or anything. Even installing a custom Proton version to try it out is very simple.

I've been on Fedora now for nearly a month and only boot into Windows for work. Eventually, I might get rid of Windows entirely. It'll take a massive U-turn from Microsoft on the philosophy for Windows for me to change my opinion now.

Mostly dev-related topics but I'm trying to write about more than just that.

And btw, this is a brilliant idea. I've already found 2 sites in adding to my bookmarks.

A typical backend developer using C#/Java is likely solving more complicated problems and having all the concerns of an enterprise system to worry about and maintain.

Dismissing a dev or a system because it is enterprisy is a weak argument to make against a language. A language being used a lot in an enterprise to carry the weight of the business is a sign the language is actually great and reliable enough.

And that was my point. The choice of using JS/TS for LLM stuff was made for us based on initial wave of SDK availabilities. Nothing to do with language merits.

The language syntax has nothing to do with it pairing well with agentic coding loops.

Considering how close Typescript and C# are syntactically, and C#'s speed advantage over JS among many other things would make C# the main language for building Agents. It is not and that's because the early SDKs were JS and Python.

This is a good point. My answer would be that it depends on how many depend on the software and what is the tolerance for unintended interactions that users discover?

Based on which domain the software is written/deployed in, this answer will be different.

A table is a table. It has one core function. An argument can be made that it could be built in a way that a chair can't be pushed against it for example. But the number of such cases for a table are infinitely smaller than the number of edge cases and unexpected interactions a software system can have.

QA is a way to catch those edge cases that a single developer cannot find because of various reasons. One such reason is that devs are very close to their work and they might subconsciously not trigger the unhappy path in their code.

Testing if a table works is vastly different from testing a software system.

No, your "dear leader" didn't buy intel.

You're on HN not some crappy FB group. The bar is higher around here.