mixedCase

The coffee still tastes like a Victorian chimney sweeper's piss.

No one in all these years had gone through the effort of replicating the Spotify client with a snappy fast interface for a reason. Everything had been an integration into already existing software, or simpler interfaces, because the effort was not worth it. The equation has changed.

It's also technically cross-platform, as evidenced by FreeBSD's support for Wayland compositors. But it's not its goal either, the goal is an excellent Linux desktop, not something that serves the 17 people in the world that routinely run the same exact desktop config on Linux and non-Linux PCs.

I think the key is to give them a nice assortment of self-verification tools, an AGENTS.md or reference document that they're encouraged to routinely check, and asking the planner to be thorough with the ACs but give the model some space.

The planner routinely finds issues with the worker's output, but that's what it is for.

Rationing does not stimulate investment this way.

I've been running Linux for gaming for well over 15 years and have not missed much in the last 5 or so. There's way too many games out there to play that do run on Linux even if unemployed and have the time to dedicate it as your sole hobby.

Doing all that with containers is a spaghetti soup of custom scripts.

Even if one day you could just squirt the cocktail directly into your receptors or otherwise trick them, there's more to happiness as a part of life than turning yourself into a vegetable, but I digress.

Rules that are not fixed but still are a requirement for code to work/make sense still merit an explicit encoding in the type system. You can have an interpreter somewhere that makes sense of unstructured data and delegates to the right functions once it's able to parse and slap a type on it, which will be better than a function that has a bunch of conditionals laying around which at some point either force you to duplicate them or make assumptions you're calling the right functions in the right order.

https://en.wikipedia.org/wiki/Regime

Relevant quote: "In politics, a regime (also spelled régime) is a system of government that determines access to public office, and the extent of power held by officials. The two broad categories of regimes are democratic and autocratic."

It is true that as a term it has accrued some negative connotations due to the frequent use of the all-encompassing "regime" to speak of governments where their exact denomination tends to fall on the autocratic side of things. From a journalistic point of view, it is better to use a neutral term than a charged one; which unfortunately as you've noticed yourself it can taint the term to readers who are not familiar with its exact scope.

But it is correct to call it Biden's regime, just like the current administration (perhaps a better term given its popularity in the US) is part of Trump's regime.

The BYD Seagull retails here in Uruguay for less than that and we tax cars at about 100%. On China it seems to go for 10-12k.

It's a proper, basic city car. 4 to 6 air bags, ~300km range (more than what this article's car indicates), all basic security features and standard gadgets out of a modern car.

Our EV infrastructure is not viable if you don't have a charger at work/home and yet these have sold like hot cakes.

Legacy carmakers are making increasingly worse ICE cars for the most part (btw does GM sell a C-segment hatchback on any market, anymore?) and their EVs are simply uncompetitive. What's it going to take for them to wake up to the fact they're going to have to stop fleecing their customers with crappy products? Bankruptcy?

I'm just hoping this is what it takes for Google to follow the trend for Android Auto and they go through with their internal integration experiment, don't care if I have to pay a fee, I just want it to understand my accent and be useful consistently.

It's all daemonless, rootless and runs directly with your host kernel so it should be as simple as it an application of this kind gets. Probably you followed some instructions somewhere that involved whatever the podman equivalent for docker-machine is?

> Architectural interviews are likely safe for a few years yet. From talking to people who have run these, it’s evident that someone is using AI. They often stop with long pauses, do not quite explain things succinctly, and do not understand the questions well enough to prompt the correct answer. As AI gets better (and faster), this will likely follow the same fate as the rest but I would give it some years yet.

Completely matches my experience. I don't do leet code BS, just "let's have a talk". I ask you questions about things you tell me you know about, and things I expect of someone at the level you're selling yourself at. The longest it's taken me to detect one of these scumbags was 15 minutes, and an extra 5 minutes to make sure.

Some of them make mistakes that are beyond stupid, like identity theft of someone who was born, raised and graduated in a country whose main language they cannot speak.

The smartest ones either do not know when to stop answering your questions with perfect answers (they just do not know what they're supposed to not know), or fumble their delivery and end up looking like unauthentic puppets. You just keep grinding them until you catch em.

I'm sure it's not infallible, but that's inherent to hiring. The only problem with this is cost, you're going to need a senior+ dev running the interview, and IME most are not happy to do so. But this might just be what the price of admission for running a hiring pipeline for software devs is nowadays. Heck, now feels like a good time to start a recruitment process outsourcing biz focused on the software industry.

  2) Request a $100 Google Store credit that you can put toward the purchase of another Pixel phone or other hardware.
  3) Request a $50 cash payment.

Sadly, I've yet to find a viable alternative.