gtaylor

Different car, but I've been super pleased with my Ioniq 5. The build quality and comfort are much better than the Teslas we were considering.

I switched my personal laptop (Dell XPS 17) from Ubuntu to Fedora about a year ago and have been pleased. The GPU situation is more polished, suspend and resume works with less quirks, and I like the more recent versions of upstream software. I’ve also been feeling pessimistic about Ubuntu’s general direction and Snaps in particular.

Had some issues on recent Ubuntu with my XPS 17, but it runs wonderfully on Fedora.

As one point of data, I've been trending towards remote-or-bust as I've aged. My tolerance for time wasters (like commuting) is low and my desire for flexibility is much higher.

I’m sure some prefer in-office more with age, but it’s definitely not the case for all!

X4 and any other titles in the X series. It’s single player spreadsheets in space.

I've seen background checks at most of the mid-to-large sized tech companies I've worked at.

I feel like there are two minutes of ads for every ten minutes of content on Hulu. It's ridiculous that you have to pay even more for an experience that is similar to the flat rate on Netflix and Disney+.

The debugging and profiling features are excellent, too. Love the thread visualizer on PyCharm.

I've found Unifi to be a pain to set up just right. But once you've got things just right, it's generally pretty fast and reliable.

Our southern border is over 2,000 miles long. I doubt that the relatively few miles of wall that were built made much of a difference.

Opinions on this vary wildly, but you can be very productive with any of them. Pick what makes the most sense to you and get to it!

re: Django, it continues to chug along but is at this point a very mature ecosystem. There are larger things in the works (like the async support effort), but they tend to be gradually rolled out.

It's not going to score points for being flashy, but is a healthy tech and community. Hard to beat as a safe default if you don't already have strong preferences and are working in Python!

Plenty of jobs to be had, too.

Right there with you. Used to want the same, now I've got the drive to do other things with the time and headspace.

One of the software engineers that I respect the most was bussing tables a few years ago.

Not everyone has the same goals or mobility as you. What you described is especially tough for families with kids.

Turned my MUD addiction into a MUD development addiction. Learned all kinds of stuff (Linux, SQL, a little PHP) while building those games. Eventually went to school, didn't do well in Comp Sci, changed majors to an unrelated degree. Graduated and found a software eng position in the same field as my degree (print) and got on the tech path after that (tech startups, Reddit, Twitter).

This. And there are plenty of high paying companies that will respect your time better than FAANG.

I'd not bat an eye at someone saying this. Some of the most productive engineers I've worked with weren't pulling 50+ hour weeks.

Oh my. I'm not sure that I'd use Python to make a point about easy interop with distro package managers. It quickly descends into a nightmarish hellscape if you have more than a few dependencies or, different versions of python, or god forbid: C extensions.

What happened to them?

No, not that particular outage.

We pushed a CDN config that triggered a CDN provider bug. Took down the CDN's entire presence on one continent. Broke a whole bunch of recognizable sites for a bit.

And it's crushingly expensive even in better times.

Most seat-mounted units have retractable nozzles that keep them out of the splash zone.

The companies that I've been a part of that employed this non-negotiation strategy ended up only shifting the negotiations from compensation to title. The same negotiators still come out on top, since they'll request higher titles in order to meet their comp expectations (since they can't negotiate for comp directly). As a result, the eng org can end up topheavy in leveling.

This is a tough problem, but these non-negotiation policies aren't the solution. They make the inequity even worse since it becomes harder to negotiate (for title) than for incremental comp increases.

No, it's about DHH using politics as a stand-in for the actual issue: they mishandled this issue with the name list, they got called out and held to task for it, and they don't like that behavior.

The politics thing really amounts to "don't challenge me" and is a nice diversion from the actual issue.

Someone want to tell this commenter how expensive daycare is?

They've had plenty of time to change their behavior. The issues are well known at this point.

I do whatever I can to best support the team. It is practically never coding at this point. My team would likely end up frustrated with me (and rightly so) if coding comes at the expense of other things like sourcing, hiring, coaching, distilling and communicating our plans, refining and scaling our processes, etc.

Those were fairly short and did not take out the entirety of the Bay at once.