Lane keep assist is always enabled, this "copilot" or whatever it's called is an extra feature i can manually enable over the default lane assist. And it will steer and follow the road quite well in most conditions. But sometimes it starts the ping pong behaviour.
Should also be noted that i never take my hands of the wheel. And the volvo is quite fast at beeping at me if it detects that i dont hang onto the wheel.
My volvo also has a "not perfectly tuned" PID loop. With "autopilot" engaged it keeps weaving constantly left and right inside the lane im in. Have gotten used to keeping a firm-ish pressure on the steering wheel at all times to compensate. But drivers behind me must have thought me drunk before i got the hang of it.
Having installed Arch myself a couple of times, i think i would disagree. Not really much in that process that teaches you how linux actually works. It's more just about managing disk partitions and moving files around than anything else.
LFS is just on a whole different level, and is on my bucket list to complete the entire process one day.
> I also think “3 out of 3” is not a good idea, as it allows any single key holder to prevent election outcomes that they don’t like (something that may have happened here, too. I don’t think cryptography experts often lose such keys by accident)
It's also important to factor in the case of "a key holder was hit by a bus, and now we can no longer access their private key".
I have been an avid proponent of the way errors are managed in Rust and Go for a long time. However, this article raises a very good point. Before i started developing in Rust and Go, i did Java and python for several years. And damn, do i miss those stacktraces every now and then when something bad happens that isn't properly handled by the code.
Still, i do think returning the error as a return value is better than having a completely separate flow when dealing with exceptions. I like that it forces me to properly deal with an error and not just ignore it and think something like "meh, i'll get to this later". Because i will never "get to it later".
I like Rust as much as the next guy, but statements like this makes me roll my eyes:
> hk is written in rust, pre-commit is written in python. hk will be much faster.
I have no idea how fast hk or pre-commit is, i have never used them. What matters to speed is the algorithms used and their complexities. If you implement a shitty algorithm with exponential complexity in Rust it's going to be slower than a linear complexity algorithm in python.
"Platform Engineer" has started to grow as a name for pretty much this. An engineer that builds the platform that all things run on. For example, the k8s clusters, the observability stack, has on-call, and builds the internal tools and automations (called the IDP, or internal developer platform).
That depends entirely on the infrastructure necessary for hosting the multiplayer servers. Such as, does it require a database server for persistent storage of player information? It might be built for a k8s based environment. Split into many smaller services that all interact using a service mesh or message queue.
You cant just take these things, press a button, and voila, a small bundled server platform anyone can run at home. The modern day software development experience is a massive and complex beast.
This is exactly why i as a manger want to assign bigger projects on new hires. They have fresh eyes, and are not used to things we do just because we have always done them in a special way. It's interesting to see how they solve tasks, before they get used to the status quo.
I dont know about the pricing. Over the last couple of months i have been investigating different alternatives for better access control to our internal resources. And Tailscale seems to be on the cheaper end compared to other offerings.