yolovoe

My experience with Google hardware has been the opposite. Three early Pixel phones died within a year or two, and pretty abysmal experience with Pixel Buds. They'd send me replacements, but I tired of them breaking.

I switched to an iPhone after being a long-time Android fan. Haven't looked back. Converted my wife to an iPhone too. Apple is better at hardware.

iPhones also receive security updates for a long time. I buy iPhone 3+ generation old brand new at the Apple store, and it... works really well.

That's one free round trip international flight per year in a lot of cases. Plus sometimes other benefits like theft insurance, warranty extension, phone insurance, etc.

You're subsidizing everyone else if you're not trying to get the best loyalty program.

Fedora is good and fairly stable, but it has bugged on me a few times.

In the past 3 years: - mouse/cursor issues due to some kernel upgrade I think, as Fedora stays close to upstream - unresponsive computer due to a bug in the AMD graphics driver

Both were easy to fix (kernel cmdline change or just kept updating my computer), and I absolutely recommend Fedora. That's what I'd use if I had servers. But, you'll probably have to debug _some_ issues if you use something less-used like AMD.

I will have forgotten almost everything by the time something inevitably breaks in a few years. Unless I am constantly recalling the knowledge and applying it, I don't find it worth it. And I _don't_ want to be constantly recalling this knowledge. I want it to just work.

OMZ has been working steadily for me for the past 8+ years. Autocomplete, syntax highlighting, and a concise prompt--really all I need.

AWS is very heavy on Rust internally for core services.

EC2 (lots of embedded work on servers), IAM, DynamoDB, and parts of S3 all heavily use Rust for quite a few years now already.

We can move really fast with Rust as compared to C, while still saving loads of compute and memory compared to other languages. The biggest issue we've hit is the binary size which matters in embedded world.

Linux has added support for Rust now. I don't think Rust's future supremacy over C is doubtful at this point.

AWS might honestly be the biggest on Rust out of all the FAANGs based on what I've heard too. We employ loads of Rust core developers (incl Niko, who is a Sr PE here) and have great internal Rust support at this point :). People still use the JVM where performance doesn't matter, but anywhere where performance matters,I don't see anyone being okay-ed to use C over Rust internally at this point.

Just a single data point against this. I got interviews with 4 companies out of 30 or so I applied to. Cleared all the onsites. Think FAANG, famous hedge fund, popular data analytics platform, and defense. 4 different industries. Job market's not the best, but it's also not that bad if you have 5 YOE+. Offers were good, ~$50-100K over my current pay.

So many people are using AI during the interviews to cheat, as long as you don't use AI and are good at leetcode, probably not that hard to snag an offer. I also interview people at a FAANG, and #1 reason to reject people these days is AI use. If you don't use AI and can leetcode and system design, you're pretty solid and will stand out from other half-baked candidates.

I know your comment is mostly in good faith, but I wish people considered whether it's worth it to use terms like "right wing commentators" instead of the simpler "commentators".

The "right wing" label will just shun around half of Americans from taking your comment in good faith. Is the point to snark or to convince people to change their minds?

Yes and Yes.

This is a really good link. Will definitely refer to this when making a car purchase in the future. Thanks!

It seems like Volvo's reputation as one of the safest car is still well deserved after all. I don't own a Volvo--too expensive for me, but good to know.

Leetcode is a standardized test that shows your ability to write code, grind and pattern match in a very complicated space. It is not possible to memorize solutions to all problems. There are way too many problems in this space. All the people complaining about leetcode are a prime example of this. It takes a lot of time and background knowledge to learn all the algorithms, data-structures, and problem-solving patterns... to get good to the level where you can ace FAANG and trading interviews with a high probability. It's a more useful metric than memorizing specific APIs which is not standardized, has basically no/simple pattern matching, and does not really test coding skills. There are also too many frameworks, and this just doesn't stand the test of time. People would need to constantly re-learn frameworks for interviews.

Most companies have been using leetcode and system design for dozens of years for a reason. It's not changing anytime soon.

Also, leetcode can be really fun :) if you remind yourself to be truly curious about the problem.

Leetcode shows candidates willingness to grind.

> They really don’t require you to know the latest frameworks, databases, Kubernetes, etc

The latest "framework, databases" are constantly changing. Being good at leetcode and system design is a better signal (ofcourse, not perfect) than knowing specific tools.

Being good at system design implies you are aware of tradeoffs across various systems, and that coupled with willingness to grind means you can at pick up new tools and probably deliver on projects. I have used 13 languages and an equally absurd amount of tools across 4 orgs in my 5 YOE at FAANG. It's constant learning, or you're out basically. Doesn't make sense to quiz on anything specific. The interview process is quite fair actually.

Is the “card” work EC2 Nitro by any chance? Sounds similar to what I used to do

That's a good point.

I used to work at a SF startup before the FAANG about 4-5 years back. All the engineers there have unfortunately been replaced with those in LATAM too. LATAM engineers were making like $80-$90K in USD, which is apparently really good money there, whereas US engineer asked for base pay twice that. So it seems like a win-win deal for the cofounders and LATAM engineers.

Just not so great for those of us in the US.

I don't mean to spread FUD, but as an interviewer at a FAANG in the US, I have mostly been interviewing candidates in LATAM (Brazil and Mexico). Same for some of my other coworkers.

It's happening, and happening fast.

You can replace software engineers with anything else here. Most VPs and higher leadership I see at FAANGs (who're arguably the ones recognizing opportunity) come from a PM or other non-software background. As much as I'd like to believe we're special, it doesn't seem like we are any special. We have no protection.

It's best to start hedging and learning other skills. Or focus on making as much money as possible ASAP so you have some financial safety net to fall back to as AI and Trump/Musk and offshoring has increased in recent years. All of us need an escape plan ready.

I don't mean to spread FUD. Just hedge please. I assume I have at most a decade of tech career left in the best case. A couple years in the worst case.

Which is most information...

Huh, thanks. Really good to know where Linus stands here. Seems to me like Linus is completely okay with introduction of Rust to the kernel and will not allow maintainers blocking its adoption.

Really good sign. Makes me hopeful about the future of this increasingly large kernel

Medicare, social security. We already have this in the US. We pay for the old, to receive the same benefits when we’re old.

Google buys transaction data from credit card companies (Visa, Mastercard, etc). They almost certainly know what you spend money on

An increasing amount of AWS EC2 dataplane (Nitro firmware/software) is using Rust.

We hit this issue too, and our solution was to go busybox-style with binaries. One binary that then gets linked to with different names. Solved the problem for us.

AWS Graviton servers are ARM. These tend to be cheaper and more reliable than Intel/AMD counterparts.

Not my experience with Tesla servicing. First off, you don’t have to service the car besides tire rotation and air filter replacement once a year or so.

When I do walk in to get something checked out, I get an estimate via the app and can chat with someone before even dropping off the car, which is nice. Tesla servicing has been a good experience for me so far, and does make me want to order another Tesla when our ICE car dies a couple years from now.

An out-of-spec DNS server implementation that helps me understand and control my internet usage.

The DNS server resolves queries based on rules I've set up. Essentially, I can configure certain categories of websites to only resolve at certain time periods.

For example, I could make it so reddit, HN, etc, only resolve for a 5 minute time period (either anytime or only in the mornings) every day.

The point of the server is to track my web usage across all personal devices, and then make conscious decisions to control my internet usage based on this data. (All personal devices are on the same tailscale VPN... that's how I ensure I am always using my DNS no matter the network I am on.)

It's still a WIP, but I've probably easily sunk over 40 hours on it by now. I also wrote a custom Rust async runtime (single-threaded) for fun.

You could have gotten rid of the middle paragraph. It’s not fluff. These are valid technical points. Issues most companies would rather (reasonably) pay to not have to deal with.

And do you really think you can offer better security and uptime than AWS? Not impossible but very expensive if you’re managing everything from your own hardware. You clearly vastly underestimate all that AWS is taking care of.

Nitro does measure firmware. If any firmware is unexpected, server will essentially stop being connected to the EC2 substrate network and/or server wiped clean automatically. People will be paged automatically, security will likely be pulled in, etc.

There is no reason to measure hypervisor firmware as it’s not firmware in the case of EC2. The BIOS/UEFI firmware on the mobo is overwritten if it’s tampered with. Hypervisor code (always signed, like all code) is streamed via a verifiably secure system on the server (Nitro cards, which make use of measured boot and/or secure boot).

No idea what the customer facing term “Nitro enclaves” means, but EC2 engineers are literally mobilized like an army with pages when any security risk (even minor ones) is determined. Basic stuff like this is covered. We even go as far as guaranteeing core dumps don’t contain any real customer data, even encrypted

Ah, this makes sense. Thanks for clarifying!

> I suspect they're not getting a dedicated server from Amazon.

If it's literally called a dedicated server, why would you suspect otherwise?

Source: I worked in the core EC2 dataplane for a couple years. PEs and leadership there would not be happy with misleading customers. We constantly thought of the customer experience there.

Of course not.

I am just saying we should understand why the attacks happened, and why many more like them will continue to happen for the next couple generations.

I highly recommend you read the book The Lemon Tree.

I used to think the same as you. Obviously, Palestinians are wrong, right? They rape and murder Israelis? Well, look < 100 years back, and "Israelis" did the same to Palestinians when they forced out Palestinians from their homes to make present-day Israel. Obviously, there was a lot going on in Europe at the time, so it's a bit hard to blame the "Israelis" from 1940s completely too.

Understanding how we got here tho is very important. It helps humanize Palestinians, understand why they're mad, and what we can do to peacefully move forward. I believe there is a peaceful solution to the almost 100 year long Israel/Palestine conflict, however unlikely it is to come to fruition.