It's weird their main reason is performance, but then proceed to benchmark SQLite. Who's inserting 10s of millions of records per minute on sqlite?
Even in production, client-server DBMSs, I'd wager that there are plenty of other things that dominate performance before you even get near your choice of a primary key, so it probably doesn't matter until you get a large enough throughput in your database.
In most cases it's more useful they're not predictable, and I'm definitely not remembering private keys myself, so what's the point. You can have preservation of creation order with UUID v6 and v7.
The vast majority of those we laid off last week were measurers. We cut middle managers across the organization because AI allows us to have more direct reports per manager while still measuring and mentoring our teams effectively. We consolidated our operations functions into a single group that can support teams across the business, using AI to gain specific expertise when needed. We significantly reduced our marketing team, which, like in most companies, was teeming with measurers. Across our finance team, we found opportunities to consolidate and automate.
But the layoff wasn’t about reducing headcount. In fact, we have a record number of open positions. In coming years I expect our number of employees will continue to grow. With fewer people needed for measuring, we can now invest more in people in the areas that drive growth.
You'd think so, but Windows runs better on snapdragon today than Linux. I was very interested in buying one, but in the current state it's a toy for enthusiasts.
IME some people (at least the ones who care) start more critical repos with good intentions, enabling most of these things.
But then comes a time where a hotfix must be merged asap to production and there's no one to review it for 3 days; branch protection gets disabled.
or an update in the code quality tooling detects an additional dozen warnings without the codebase changing; check enforcement gets disabled.
I think in most cases this is completely fine. Whoever is already a contributor should know what's the team policy merging things, and having ways to occasionally bypass these checks can be more beneficial than not.
Qwen 3.6 and gemma4 models are the only ones usable for agentic prog sessions that I and my employer run locally. It's less stable and slower than third-party services, even on much better hardware (as it's with my employer). The best way is to go with a provider hosting deepseek flash/pro if your privacy policy allows though. It's going to be hard to beat their price.
I got the second half