abuob

If you're genuinely curious, a few suggestions that I personally found incredibly enlightening:

Anand Giridhardas, Winners Take All: The book is fantastic, there's also his now infamous google talk where he talks about dismantling google: https://m.youtube.com/watch?v=d_zt3kGW1NM

Thomas Piketty, Capital in the 21st century: Probably the most comprehensive (but at times also longwinded) outline on how wealth inequality comes to be, why it's not good for society and how it could be adressed

In my perspective, "Analyze code, come up with edge cases and gaps and create unit tests for them" is one of the use-cases where AI was starting to get really good at, so I can see why someone would want to extend their test-suite dramatically using it.

But yes, using AI to then generate code that still causes regressions doesn't quite square with that. Given the huge amount of test-changes I'd still assume good faith by the maintainer; possibly just a bit of overexcitement paired with a dash of too much confidence into the new tools that is now hitting reality.

It feels like the real news is that the metaverse division still had 1500 people in it...

I find it very unfortunate that browsers (or rather, the spec) do not support some kind of versioning. If we could declare which version of HTML, JS and CSS to use, it would allow for breaking changes without breaking the entire web.

There are so many (in hindsight bad) design choices and implementation accidents that currently exist in perpetuity because of backwards compatibility; the web would really benefit if every now and then we could shed old baggage.

Probably not too popular of an opinion on HN but email in my opinion would be a great example of a service that could be run by the government. Just like postal service (at least in some parts of the world)

But you can detect serverside (at least probabilistically) if a user is abusing it to their advantage.

Some Valve guy gave a great talk about their cheating detection a while back; I found it incredibly impressive: https://youtu.be/ObhK8lUfIlc (can't comment on their effectiveness these days, haven't played CS in a long time)

Shameless self-plug and probably not what you're looking for, but anyway: I've created https://github.com/abuob/yanice for that sort of monorepo-size; too many applications/libraries to be able to always run full builds, but still not google-scale or similar.

It ultimately started as a small project because I got fed up with NX' antics a few years back (I think since then they improved quite a lot though), I don't need caching, I don't need their cloud, I don't need their highly opinionated approach on how to structure a monorepository; all I needed was decent change-detection to detect which project changed between the working-tree and a given commit. I've now since added support to enforce module-boundaries as it's definitely a must on a monorepo.

In case anyone wants to try it out - would certainly appreciate feedback!

I'm dabbling in the monorepo-tool-space for quite a while already and somehow managed to never hear about Turborepo, seems very interesting!

Just a few years back, the monorepo-tooling-landscape left much to be desired, there were a lot of opinionated 'zero-config' tools out there that always seemed to fall apart the moment you strayed from their happy path. I even went so far to create my own tool (https://github.com/abuob/yanice), in parts because it was fun and taught me a lot and in parts because I simply didn't find something fitting our usecase.

It's cool that the tooling in this area is getting better and better, monorepos solve a lot of very annoying enterprise problems but require solid tooling to make it work, even when way smaller than google-scale.