Androider

There might be better air purifiers, but the recommended Coway purifier is really good. I've had one for 5 years, still working as well as the day I bought it. I also have a 3x more expensive high-end Alen unit, but it's not nearly as effective or quiet as the simple Coway. The filters are way more expensive too.

In my first game, I carefully managed the interest rate to keep inflation around 2%: Your economy produced 431540 apples.

Next game, I set the interest rate to -0.50% right away and left it there: Your economy produced 442411 apples. Inflation was 1.5% in the end.

Doesn't seem to matter too much what you do. Maybe in real life too.

The sensors, optics and processing on any recent iPhone leaves even $200 webcams (Brio, Elgato) in the dust. If you want a better camera, you have to go with a mirrorless or DSLR hooked up to your Mac, and these setups are finicky and require third party software. If this Just Works, it will be a massive upgrade in image quality for most people with a camera they already have, perhaps not for everyday (except if you want to reuse your old phone as you upgrade) but for that one job interview or other important meeting where you want to look your best.

Tesla's are well known for having lots of defects right at delivery.

https://www.reddit.com/r/TeslaLounge/comments/v3jkn3/update_...

You couldn't do everything that Terraform does today without a local state, but perhaps that would be a good thing? Call it "Terraform strict mode".

As every application developer knows, duplication of state is a primary source of bugs. To combat this, React/Flux type of architectures became extremely popular where state flows in one direction only. They dictate that, no you can't just cheat a little and use jQuery to modify some element, it _will_ get bulldozed on the next render. And a lot of Terraform headaches do come from this analogous reconciliation of what really is (our cloud env), what we want (our TF code) and this intermediate state of what TF thinks the cloud state is.

So, by saying that you cannot have resources outside those defined by TF there is actually a massive simplification with far reaching consequences possible.

How I imagine the experience would be:

- You could say that your Dev env is a shitshow and always will be, of manually created resources and only partially TFed. But your Production and Staging envs are opted in to "strict mode". This means that if there is a conflict you do only have two options: import the offender or destroy it, and the critical mindset change is that this is a good thing and will save us a lot of tears later on.

- Caching is an orthogonal concern. Terraform mixes these two together to its detriment, but the nature of a cache is such that you can safely blow it away and perhaps the next reconciliation will be slow, but it will be accurate. I also don't believe it would actually be that slow, tools like Cloudcraft map the entire metadata of your account in seconds.

- I find the excuse that some resources don't support tags intellectually lazy. Of the top of my head thinking about it for a minute, could you tag a parent resource with the child metadata you need? E.g. individual DNS records don't have tags, OK tag the Zone with childA=value. Same thing with tag length limits, you can work around it, concatenate values or whatever. However, in a truly strict mode you wouldn't even need metadata in tags because the TF code describes the entire target environment.

I hope Terraform would entertain such a strict stateless mode. Unfortunately it will probably take another tool, because the problem is not so much technical as it is an entire mindset change.

For mortgages, lenders will entirely or heavily discount RSUs for income calculations.

However not discouraged by that fact, some tech folks are known to instead have taken out regular non-mortgage variable rate loans with their RSUs as collateral. So there are folks, who bought a house "all cash" with loans backed by stock collateral that is now worth much less. Those types of loans also have a double-digit APR, which might have been fine if you thought you could flip your house for 30-100% in the near future. In the current housing marking it is like putting everything on black at a casino, it might work out, but it might be also be a complete catastrophe.

Firefox 99 on Linux, the square is visible. Chrome 100 on Linux, square is not visible. None of the colors match the RGB value #0cf4c7 when using a picker :/

Gimp shows a color of that hex the same as Firefox's square. The Chrome color is much paler in comparison. There's no color profile set for the monitor.

Where is the ssh-agent reading your private key from? If from ~/.ssh/, you're just one "npm install" away from the key being exfiltrated by a compromised package. If the private key is on your Yubikey, you're already good. The 1password agent will provide a good hardwareless method of keeping your private keys off the local filesystem, and it'll sync between your devices too.

How about uBlock Origin, but for search? A crowd-sourced + manually vetted ban list at the domain level. Google is too timid and can't just permaban low quality SEO spam domains for fear of getting sued, instead they can only tweak the algorithm. But a community solution has no such limits.

Copying Stack Overflow questions and answers to your site? Entire domain is banned, no appeal process, nobody using "uBlock Origin for Search" will ever see your site again. Boom, done.

Maybe it could be done as an extension? It puts a little ban button next to a search result on google.com, that instantly bans the domain locally for you, and also nominates the site for the global ban list.

I feel like there's a lot of low hanging fruit here, like completely banning just the top 1000 SEO sites would already dramatically improve the results.

Right, Apple is only providing the hardware and it requires to use a (partnered) processor, like Stripe, which was the example they used in their recent announcement. Stripe coincidentally sells chargeback protection as a service https://stripe.com/radar/chargeback-protection if that is a concern.

Apple and Stripe are also set to commoditize the small business Point of Sale that is Square's bread and butter. iPhones were just announced to soon accept contactless payments directly, and probably also the next iPad will include the required NFC hardware.

It's 100% a culture / organization problem.

Check this out. The original poster of the tweet thread being discussed here retweeted:

"The bug where background audio stops playing for PWAs seems to be fixed in iOS 15.4 Beta" https://twitter.com/wes_goulet/status/1491238784020905986

Job well done, ship it! Hang on, let's check out that bug's public tracker at https://bugs.webkit.org/show_bug.cgi?id=198277

- Reported in 2019

- In 2021 got a "Thanks for further reporting this bug... This bug is tracked internally".

- Lots of excitement when someone finds it's fixed in 15.4 (of course no feedback from Apple that a fix was made anywhere or released, bug is still in original "New" state)

- Disappointment strikes: "(on 15.4) it sometimes keeps playing, but sometimes stops when you pull down Notification Center or switch apps. Sometimes the Play button doesn’t work. It also stops when you get a push notification with a sound" :(

Now, how much do you want to bet that the "internally tracked" bug is marked fixed, the developer is not aware of these corner cases, but could probably fix them if they only knew. No worries, another developer (the original having long moved on) will probably take a crack at it again in 2024 when this information makes it back to them.

I've worked in organizations just like that, where every bug report is a game of telephone. Everything takes exponentially longer and is perpetually broken because the developer and the user having the problem can't just talk to each other. Throwing bugs (and fixes!) over a wall and hoping for the best just doesn't work.

That thread has hundreds of legit replies with bugs (that are impossible to read on desktop Twitter from what I can tell). I saw a few cases of "I published an article about our challenges supporting Safari, the team reached out and then ghosted us", like http://blog.apps.npr.org/2021/08/31/joy-generator.html. Search for Safari on that page... oof.

Dear Safari team, the first step in fixing any problem is to admit that you have one. Please internally acknowledge that Safari has _lots_ of issues like these and has a reputation problem among web developers. It's not just people hating on Safari and being ignorant, I would love to support Safari better, but it's just so frustrating in practice and when filing bugs they seem to go into a black hole. I think a big problem is that bugs seemingly get duplicated into some internal system where there might be some discussion going on, but none of that is visible to the rest of the world and it creates that black hole perception and lack of back and forth discussion with the people who are reporting these issues.

Using a shared iPad with a family is a bad experience with all kinds of Apple account issues. Other apps Netflix/Amazon/etc. thankfully provide quick user switching which makes it tolerable.

For comparison, my US bill is currently 9.5c/kWh, which is 7p/kWh. Your UK price is 4x that of mine! The SpaceX office where the dish was designed is just down the road from here, so I can totally see the engineers thinking "What's the big deal, it's only 100W? That's a few dollars a month."

esbuild is > 125x faster than Webpack, doing the exact same job. It's not some theoretical microbenchmark, you'll see it when converting a project from one to the other. If a software hasn't been designed with speed in mind, and I don't think tsc has, there can be massive performance improvements possible if you create a new implementation with performance as a top goal.

The UK has https://www.gov.uk/service-toolkit and https://design-system.service.gov.uk/

I placed an order just this month from Costco, with UPS sending three separate "Shipment has left LA" notifications repeating every few days, and the "UPS 3-day delivery" ended up taking over two weeks in the end. The 4th delivery attempt then originated from Canada and did arrive. I didn't have to do anything about it, and it didn't show any errors like "oops we lost the package". This makes me think that they did lose the package(s), and either UPS or Costco just ate the cost.

Justworks was critical in bridging the 1 to 10 employee gap for our company that many other providers has.

The problem is, that when you hire your first employee many providers will consider you too small to provide health benefits, even if they can do your payroll. E.g. Gusto was happy to process payroll for us, even for a single employee (or just yourself), but wouldn't provide us health plans for our first W-2 hire (I think the minimum was 3 at the time). Their loss, as we switched to Justworks and provided full health benefits comparable to any big company for our first full time employee, and now we're at 10+ employees and growing and certainly not going to bother switching back.

Overall we've been very happy with Justworks. They make it super easy to hire employees in all US states while keeping compliant.

What possible good, from the point of view of the company, would come out of stating that as the actual reason to the candidate? Companies, like Stripe, are completely ghosting candidates who did long onsite interviews largely due to perceived legal risks in sharing any feedback whatsoever about the actual interview performance.

I'm not trying to place blame, I would however like to warn readers of this board, younger ones who have grown up with social media and consider it normal to share everything they do, that a lot of companies don't think that "amplify [a] company’s social marketing" is an unequivocally good thing that they want their employees to engage in. When you're in a vulnerable position like just before starting a new job, why invite that extra scrutiny.

> And then she tweeted that she would be joining the company.

> “A few days after that, I got a call from an executive recruiter who I had never heard from before, and she said, 'There is no easy way to say this. We have to rescind our offer due to changing company priorities.

When you tweet about a company you're about to join, maybe tagging them for good measure, it's like focusing the eye of Sauron on yourself. Unless your timeline is completely inoffensive and bland, maybe wait until you've started... or maybe just don't.

Nitro SSDs appear to only be available on specific new instances types, like the just announced Im4gn and Is4gen.

Literally any tech company paying US engineering salaries? Try to calculate what a bay area engineer makes hourly sometimes, then go ahead and flip that AWS cross-region data replication checkbox (and maybe make your S3 bucket immutable too, storage is cheap), then tell your boss that you just saved the company a whole bunch of money compared to your team cobbling together some janky bespoke backup solution that nobody will remember how or if it works 12 months from now.

AWS has both 12 months free tiers for some services, as well as pretty generous always-free offerings, like the data transfer announcement today. The 1TB/mo CloudFront traffic is now always free, as is the 100GB/mo of data per month from AWS regions to the Internet.

https://aws.amazon.com/free/

You run `ssh-keygen -t ed25519-sk -O resident`, and that's it, no additional software required as of OpenSSH 8.2. If you have an older model Yubikey you can try ecdsa-sk instead.

For more details, see:

https://github.blog/2021-05-10-security-keys-supported-ssh-g...

https://www.yubico.com/blog/github-now-supports-ssh-security...

All of this signing is only useful if someone is actually checking or enforcing those signatures, otherwise it's just LARPing.

Being able to sign commits with your SSH keys makes signing actually useful, because it enables a new workflow that developers will use:

- You give every dev on your team a Yubikey

- They generate an ed25519-sk key that only resides on the Yubikey, no software required as it works out of the box with both openssh and GitHub

- They upload the public ID of the key to GitHub, same as before

- You enforce commit signature verification for your GitHub org. You're done, no need to install any software, everything Just Works.

You now have:

- No private keys on developers machines, rendering all types of supply chain attacks like NPM stealing your .ssh files ineffective

- Enforced 2FA for everyone without any hassle

- Every commit signed by developers, enforced and with no developer overhead. Checks a lot of boxes for those SOCs and ISOs.

You have to realize that it is not at all in the interest of most commercial web applications to be transparently delivered as ES modules, all neatly split up and perhaps lightly minified. No, the fact that your 1000+ constantly version churning NPM dependencies and your proprietary business code are all bundled up in a big undecipherable blob is seen as a feature. The only thing that I can see that is going to replace it, is probably going to be WASM or a binary format blob, or the application code executing entirely on the backend and the frontend streamed like Netflix.

CPU prices are usually much closer to MSRP except perhaps right at launch. You can put a 12700K or 12600K in your bag at Newegg right now at ~MSRP+$20, and you were able to do that for the 12900K Newegg pre-order last week. The 12700K at $449 on Newegg right now is some excellent value you have to admit (same P cores as 12900K, 4 less efficiency cores) any way you look at it, and the 12600K even more so.

Claiming that the Intel CPUs are "many times more expensive" than the AMD comparables is just wrong.