jsmith12673

Didn't geohot leave Comma like ~2 years ago

I can corroborate this. My family was involved in a chemical manufacturing business in India from the 60s onwards. My understanding from what my family tells me is that the 80s and early 90s is when a lot of these base manufacturing inputs became readily available.

I've had to use Google Sheets a lot recently, and it doesn't hold a candle to excel. There are a lot of basics missing esp. when it comes to charting.

But I don't like excel much either. If working with spreadsheets was a bigger part of my day job, I'd switch to excel

Janky LSP support is easily Sublime's biggest weakness. Hope they fix it in ST5 if that ever happens

I also paid for ST3, but I switched to ST4 for the hardware accelerated rendering. I don't like their licensing policy anymore, so I just dismiss the purchase signs. I want to get my company to pay for it because paying 100 USD _again_ is just absurd for me.

I have no plans to switch off though. This is still a heck of a lot faster than the alternatives

Rare to find a fellow ST4 user these days

People are pretty cagey about what they use in production, but yes, speculative sampling can offer massive speedups in inference

This company is older than Elon's

Hmm I haven't, will give it a try!

I was curious about how many inserts Postgres could handle so I made a synthetic benchmark to measure it.

I've been trying to leave my current gig for the last 9+ months. It's tough to find the right roles these days

Tried to save my company 100k per month by cutting down idle compute, clearing out petabytes of unused buckets, and using on-demand compute in testing envs. This resuted in me getting pummelled by directors asking questions, staff engineers saying random what-ifs, until I eventually gave up.

I used to think startups would be one of the few places that actually gave a shit about being lean and efficient - but turns out that's only true if they're bootstrapped.

Try BetterSnapTool.

As others have mentioned, this feature is patended. `BetterSnapTool` is $3 is for a lifetime license and does what you'd expect coming from XFCE/windows etc.

Signal is a not-for-profit organization.

I can only speak for myself, so to me this technique is kind of like how they did colour photographs in the 20th century [1] - taking multiple photographs from the same perspective with different filters.

For that reason, I would argue that these are 'true' photographs. Sure, things have been differently exposed, maybe some ultraviolet light has been brought into the visual spectrum; but for all intents and purposes, the light from the subject(s) hit the lens(es) at the same time and the composition is true to what actually happened.

Now, with all that being said, there are many famous photos that are actually composites [2] and what makes 'a true photograph' is still hotly debated.

Digital processing is such an integral part of modern photography that trying to decide what makes a 'true photograph' is bound to get messy.

[1] https://petapixel.com/2014/03/10/incredible-color-photograph... [2] https://www.youtube.com/watch?v=2NeyTEO_JP0

It's possible that Xbox serves as a loss-leader for introducing/keeping people in the brand.

For kids who may only have chromebooks at school, and macs at home, an Xbox may be the first time they make a Microsoft account. That account then goes on to accumulate digital assets and stays with them until much later when they're ready to make bigger financial commitments.

Anecdotally, for the past few years, gaming has been the only reason for me keep a Windows device around at all.

I would caution you by saying that no quote, paraphrase, or evidence of exactly what Timnit said.

Since this is Google's side of the story its in their interest to use words that would imply she's overbearing, or otherwise unaccommodating

(for all I know she could be all of those things, but this narration isn't sufficient evidence to prove that)

I'd argue that even as engineer 2, or VP of whatever, you're still replaceable.

Outside whatever thin veil of prestige your job offers you, the larger world couldn't care less about what you do or what you make.

> recruiters are bottom-of-the-totem-pole, lowest-common-denominator, bottom-feeders

Recruiters are just people just doing their jobs. It's a shame that you've labelled a diverse group of people so heavy-handedly.

Similar experience here.

The only setups I can use for >1month are the Kinesis Advantage and MX Ergo, or the butterfly keyboard and trackpad.

I've chocked it up to the super low travel keys and not having to put any force on the trackpad.

Besides that I've tried the MS Sculpt keyboards plus all sorts of mechanical and chiclet keyboards. None of them have been comfortable

Don't have much to add, but want to say thanks for sharing those blog posts, they were interesting reads.

The slack CTO's comment about choosing RDBMS because 'familiarity' is interesting. IMO it's a gamble. I've seen it happen with my company when being a latecomer to containerization.

When it came to picking a container management tool, it was a tossup between k8s, Nomad, or just saying to hell with and running those containers ourselves on EC2 instances. Having run our stack on bare metal for year = we were really pretty good at it. There was a surprising amount of automation that could be ported over.

Eventually we picked k8s, and coincidentally, our usage grew more in 6 months than it had in the last 2ish years. So all in all, the gamble paid off.

... but I like to think there's another world where we picked the 'its familiar option' and things still worked out. If our traffic hadn't grown the way it did, we would never have felt the pain of having to manually scale out our systems - or basically write an in-house version of Kubernetes.

So in that sense, I'd guess that maybe some teams have the bad habit of playing the same side of the coin everytime. It may be prudent to stay conservative when picking a Datastore, maybe it's would be smart to pick a risky technology for your app servers? (and vice-versa)

Could someone comment on why exactly this a poor design for their backend? Genuinely curious, I don't have any real world context on systems like this.

For this to be effective you'll need:

- Global agreement and partnership, since you need to decrease temperature globally to make a dent

- Convince everyone that injecting aersols into the atmosphere is the only alternative to catastrophic warming (view in contrast to convincing people of the efficacy of vaccines etc.)

Both of these are incredibly challenging undertakings, even without trying to address the issue of continually acidifying oceans.

And yet, sadly I feel like this is the only most realistic option out of them all.

You seem to imply that people are being persecuted en-mass for seeking material wealth.

While there might be a vocal minority here (and elsewhere) that scoff at material wealth, its pretty clear that society at large still measures status by your possessions.

People still seek out more luxurious cars, more gadgets, new fashions year after year without fail; evidenced by the unstoppable growth in those industries.

Even if people might say that material riches are a 'sin', they certainly are not behaving as such.

That's news to me. Guess I won't be ditching my QC25's soon/or ever

I unfortunately work in a place where on-call is unpaid. I'm an SRE stuck in the 90s.

The policy states that only the Operations team gets paid on-call, because I guess in the old days they would be the expected to deal with production.

Fast forward to today, and the Operations folks are a small team managing 2 datacentres, and all on-call rotations between SREs and developers are considered unofficial and therefore not eligible to be paid.

One of our Sr. Managers tried to take this up the chain, but then got reprimanded for putting developers on-call.

Want to jump in here - I have worked at a company where engineers are not on call for their code, and it was a living nightmare.

_You_ might not be on call for your code, but _somebody_ will be. Often some poor SRE/ops person that has absolutely no idea what the app is doing/or why it's failing in production.

Not being on-call makes engineers complicit. I've seen it all, known memory leaks shipped into production, apps where half the endpoints couldn't even be compiled, code dumping the production redis at 1AM ... and every time the pain just felt on deaf ears.

If your code is what wakes you up in the middle of the night, you have: - Incentive to fix/mitigate as soon as possible. - No blame game to play. Either the error was made by you, or someone on your team. It doesn't have to go up 3 rungs on the ladder then back down again.

I don't think the author was suggesting that everyone should always be on call, just that you _must_ be responsible for your own code in production

In my experience, large sales team = pushing hard into B2B

This survey is incredibly suspect ... as the author themself states, there's an inherent bias for non-american brands.

I find it surprising the FCA and GM cars are topping the list, while being notoriously unreliable in the car community.

Also worth noting that both Toyota and Ford have been ranked as worse than industry average.

I'm not saying that Tesla(s) don't have quality issues, but this survey seems pretty meaningless.