apocalyptic0n3

it's them adding a line item to their AWS bill

That's the future Amazon sees too. We just had a week long session with the AWS team and they pushed that to us multiple times.

I second this. I started as an Audioscrobbler user before the Last.fm merger. I have tracked nearly every track I've listened to for 21 years. It's awesome seeing how my habits have changed over the years.

It should be noted here that the daily high for a good 1/3-1/2 of America is below 0C/32F/freezing for a good 3-5 months each year. Our weather varies much more significantly than most (not all) of Europe. Even with Fahrenheit, it is not uncommon for places like Detroit to be sub-zero for days without getting into positive temperatures.

I've personally lived in Marquette, Michigan and now live in Phoenix, Arizona and have experience both -40F(-40C) and 118F(47.7C). To me, the 0 = really cold, 25 = cold, 50 = mild, 75 = comfortable, 100 = really hot scale makes sense having lived through those extremes. But you're right, that's largely because it's what I grew up with. And with that in mind, it is extremely unlikely America would ever transition away from it for that very reason.

I'd wager that most agency devs have wanted to do this too. CMS's never work the way you want them to as an dev.

Thankfully, the work you have done (along with your competitors) in making headless CMS's viable not just for devs but also for content maintainers has made CMS work far more enjoyable.

It's awesome that you not only built out the dream most agency devs have, but made a successful business out of it at the same time.

In this case, it actually was due to unknown and unpredictable costs. They were about to start production on S2 when the strikes hit. They delays spiked the costs of an already expensive show (S1 cost an estimated $175M) which made it less tenable for Amazon. This happened to quite a few shows during the pandemic and during the strikes – renewed because it made financial sense, then pandemic/strike spiked the cost, and then they canceled the renewal.

Yeah, I agree. I have a Pixel Watch 3 and generally like the circular form factor. I wish they did more with it at times, but I feel like that's kinda what I'm seeing from the previews in the OP blog post

Personally, it's easy for me. If I get above 10 tabs, I just close them all. I don't see any value in having more than that and they just become a distraction for me. Tree style, sidebar tabs, tab groups, etc. are just overkill for me.

It's pretty common for people drive to the bar, get drunk, taxi/Uber/Lyft/DD home, and then return the following day to get their vehicle. I don't think it makes sense personally, but I also don't drink at all so I'm not a great judge here.

Both can be true.

Yes. He also calls the employees Automatticians. So they're all just Matt.

We're all secret moderators except you.

Yeah, I was the same way with my iPod. I was contributing to iPod Wizard and one of the QA testers for iPod Linux, iPod Wiki, and Rockbox. I would install unstable firmwares on my iPod a few times a week and spend a few hours testing. I bricked my iPod more times than I could count. I had two iPod hard drives that I would swap between and I had a way of wiping the drive once it was out of the casing. To this day, I have no idea how my iPod 4G survived as long as it did.

Yeah, this used to be me. I don't do it anymore but I used to spend a great deal of time playing with beta versions of Android, Windows, Firefox, and various iPod and Mac customization applications. I just enjoyed playing with the new features, figuring out how to break them, reporting those issues, and then helping get them fixed (even if I wasn't contributing code at the time). I don't have the time anymore, but it was one of my favorite activities when I was younger.

I've tried numerous keyboards and the conclusion I've come to is that there's low profile and then there's low profile. The bulk of the low profiles I've tried (NuPhy, Keychron K8, the mechanical Logitech, a few others) are definitely low profile compared to the Logitech Pro X TKL I use for my gaming PC. However, they're still tall. Most of the gains are from a shorter switch and keycap, but the body is still quite high.

If you compare it to the Apple Magic Keyboard I'm typing on now – and that seems like a definite inspiration for the Bayleaf – it's a stark contrast. The K3, for example, is more than twice as tall (10.9mm vs 22mm backrow). The Magic Keyboard feels fine to type on without any sort of wrist support and I never feel any strain. But on the K3, even with a support (tried both their wooden support and a similarly sized foam one), I would feel strain after an hour or two.

Most low-profiles are really just a middle ground between the two sides. And, at least in my experience, you get the downsides of both without any of the positives of either.

I think you mean saving a PSD in Photoshop, opening it in ImageReady, slicing it, and then optimizing the slices for web.

I started writing code when I was 12 and started doing it professionally at 22. I'm now in my mid-30s and outside of work, I haven't written anything more than one-off scripts for my homelab in close to a decade. I'm already spending upwards of 50 hours with code each week and I need to do something else at night and on the weekends to release my brain from it. I also didn't go to school for CS, and even if I did... it was over a decade ago. So I have ~25 years of experience writing code but could not show you a single line of it. And even if I could, how would you know I was the one to write it?

This is an extremely flawed interview process in my opinion and the last time I encountered it led to an awkward scenario that led to me walking out. Personally, when I conduct interviews, it's a mix of things. We talk about your past work, I quiz you a bit on some topics you'd encounter in your day-to-day here, and then we'll spend an hour doing some combination of a code review of a working-but-flawed demo project I created, a 30-40 minute coding exercise, and/or a problem-solving scenario where I give you a problem and then we talk through how, as a pair, how we could solve it.

I don't often use Sublime for coding nowadays (I'm generally using PhpStorm) but I have it open at almost all times as a scratchpad. It's so dang quick that opening it to jot something down or examine JSON is instant. And so performant that if I forget to close it, my system is never bothered by it. And it retains unsaved files forever – a must for a scratchpad in my opinion, and something many others fail to do. Long term notes get converted to Obsidian, but Sublime is just so easy to get something quick going that I love it and happily pay for a license.

Same goes for Sublime Merge, which is the best Git GUI I've ever used.

Firefox on macOS is also completely borked. At least with my freescrolling Logitech Master MX 2. I'll scroll and it will jump the expected amount, I'll scroll some more and it will jump about 4-5x what I expect, and then I'll scroll some more and it will go backward in the page. The site is pretty much unusable for me.

This is the real key. They have an awful reputation amongst technical people (for good reason) but that reputation largely fades away the less technical you are. The average person knows them for their effective marketing, seemingly low prices, and seemingly decent products. They don't get into the weeds enough to expose how untrue those things really are.

For a long time, I worked in an office across from their (now former) headquarters in the Scottsdale Air Park. The number of clients we had come in amazed that we must work so closely with them and expecting great things made the location of the office so invaluable that when they moved to Tempe and Chandler, we had to seriously discuss internally if we needed to follow them.

Wood is incredibly cheap here in the United States. Estimates I have seen in the past is a stone home will cost 15-25% more per square foot than a wood-framed home in the same location. Making it more resistant to earthquakes (a requirement in California) raises the price even further. At the end of the day, cost will almost always win.

From the article:

Some of the homes in Pacific Palisades were 90 years old

90 years exceeds your lifespan, the lifespan of your children, and maybe the lifespan of your grandchildren depending on when in your lifetime it is built. Even if the house is never sold and is simply inherited, it is very likely that a home that age is lived in by someone the builders never met.

So if a house burns down once every 3 generations, what incentive is there to build it to be more fire-resistant? These fires are bad, yes. But LA isn't burning down once a year. LA is massive and only small chunks are affected by each fire. For reference, these fires are the most destructive in history and have destroyed an estimated 12,000+ structures throughout metro LA and Riverside. Per ChatGPT, there's an estimated 3 million buildings in LA County alone with the rest of the greater metro area (San Bernadino, Orange, Riverside, and Ventura counties) have an estimated 5 million.

So while, yes, the odds of your home burning down are elevated in metro LA, they are still quite slim. Slim enough that making the initial building even more expensive is not worth it, especially not in an area that also sees a lot of earthquakes.

they actually make fun of the player for daring to want blueprints that don't suck

In their defense, Coffee Stain/Satisfactory makes fun of the player for absolutely everything. They always have. It's just the culture of their studio.

They also had Space (discontinued in May) and Space Code (discontinued last week). I don't think GitLab makes much sense for them

If you're building a system that sends out emails, you generally can't send emails locally. So you instead use a service like MailCatcher/MailHog/MailPit/Mailtrap as an SMTP server that will "catch" the emails as they are sent. Then you just open that app up and you can see what emails were sent, what their content is, who they were sent to, etc. Some of these services also include email evaluation tools for things like identifying unsupported HTML/CSS, checking image/message sizes, headers, etc.

The other use case is when you're in a staging environment. You should generally seed such environments with fake email addresses but you can never be sure those emails are truly fake, and you can never be sure what email addresses your testers are using. So you set up MailPit and A) you never send a real person a fake email accidentally and B) all testers can see all emails.

I use Firefox + uBlock Origin for the most part.

I also have whole-network blocking via AdGuard running on a Pi. AdGuard also has a hosted option and you can just run it in a Docker container on a machine on the network.

I also have WireGuard setup on my Ubiquiti network so I often will be running my machines through that when remote which blocks ads for them too.

Dropbox just laid off 20% of the company yesterday. In many cases, people don't rush to update their LinkedIn so he may or may not still be there.

Which is also something done by his own hosting companies (unsure if it's in all cases, but at least some).

I'm fairly excited too. It seems the target is "Vercel but for PHP" and the lack of a Vercel/Netlify-style deployment option has pretty consistently been used as an argument against using PHP/Laravel at my agency. I've already started seeing longtime Node/Typescript devs showing interest in Laravel and Laravel Cloud will likely only increase that.

In the past, Apple explicitly forbade this except in certain negotiated cases like Spotify and Netflix if I recall correctly. Has that changed?

Not necessarily. There are a lot of really good, self-taught engineers out there who have never had to do that before and likely don't even know what "invert a binary tree" means.

In my experience, it's much better to give them a problem to solve and have them walk you through the thought process as they try to figure it out. Even if they fail to solve it, the actual process gives you insight into how they think and how they'll perform on the actual job.

Unless your job regularly involves inverting binary trees, that's not a great question because it's basically asking if you've encountered something before. If you have encountered it, you likely know one a half dozen ways to solve it and everyone will give you roughly the same answer. If you've never encountered it, then you just fail even if are a good fit for the job. It doesn't reveal anything except you know one specific thing. In most cases, engineering jobs are problem solving for unique instances that arise day-to-day; a good interview should reflect that day-to-day reality more.