stankmut

They make dedicated Nvidia images and I’ve heard good things. It’s supposed to be one of the distros to pick if you want a good out of the box experience with Nvidia. Only used the Amd/Intel image myself though.

Crypto was an annoying bubble. If you were in the tech industry, you had a couple of years where people asked you if you could add blockchain to whatever your project was and then a few more years of hearing about NFTs. And GPUs shot up in price. Crypto people promised to revolutionize banking and then get rich quick schemes. It took time for the hype to die down, for people to realize that the tech wasn’t useful, and that the costs of running it weren’t worth it.

The AI bubble is different. The proponents are gleeful while they explain how AI will let you fire all your copywriters, your graphics designers, your programmers, your customer support, etc. Every company is trying to figure out how to shoehorn AI into their products. While AI is a useful tool, the bubble around it has hurt a lot of people.

That’s the bubble side. It also gets a lot of baggage because of the slop generated by it, the way it’s trained, the power usage, the way people just turn off their brains and regurgitate whatever it says, etc. It’s harder to avoid than crypto.

I made a typo for one of my employment dates while filing the background check. Caught it right after submitting it and then asked around and everybody told me that they’ll call and ask about it if they can’t figure it out from just looking back at my resume.

Next morning they called me and said they had to close the role because of budget cuts. Two months later I got an email saying my hiring was being paused because my background check was flagged and I had 10 days from the check to dispute it. I decided to call the company and they told me that they had already hired someone else for the role.

So yeah, getting the dates right can be important.

They aren’t artificially sweet, they are a sweetener that is artificial (man-made). As opposed to natural sweeteners that you can just grab from nature.

It’s a common thing in programming. There’s some legacy code that isn’t being used and yet removing it causes things to break. Nobody has the time to figure out what is still referencing that code, so it just gets a comment next to it saying “Not used, but removing it breaks the build” and then forgotten about.

This press release is from 2023. Not sure why it was posted like it was news.

I think mistakes like this are usually caused by someone changing their mind on one thing they wrote and forgetting to proofread the whole thing to see if it still makes sense. I imagine this sentence started out as “Rock the size of a small boulder”.

Allowing Google to run an ad campaign targeting their members wasn’t the benefit Blue Cross was talking about, that’s a side effect from them not turning off the data sharing option in the Google analytics settings.

The analytics data is used for prioritizing development work. If a tool they have on the website relies on a library that isn’t compatible with a new version of React, for instance, do they know how many people use it? Having analytics allows you to decide what’s worth spending the development time to maintain.

The analytics would be for the web development team to see which pages/features are used. Usually a product manager uses that data for setting priorities on what gets worked on.

I have a bottle of the Dr. Doctor syrup in my pantry. I forgot I had it tbh, since I haven’t been drinking soda for a while. It’s a decent brand if you have a machine that carbonates water.

It’s the final paragraph of the 12th amendment

But no person constitutionally ineligible to the office of President shall be eligible to that of Vice-President of the United States.

It wouldn’t be as easy as just having him run as VP, since you can’t be Vice President if you aren’t eligible to be President.

If you turn the disc over, you can actually count the rings without needing to cut into it! This lets you skip having to glue the disc back together after checking the age.

If the APIs are meant for public consumption, requiring feature parity makes a lot of sense. But when it’s for internal use by your own developers, waiting means you are making a bunch of new API endpoints no one will ever use. People will write more and more code using the older endpoints and those endpoints will start getting changes that your new ones will need ported over.

I think if you are going to force people to use new endpoints, you’ll need them to either write the endpoints themselves or have a team member who can write it for them and account for this while planning. If getting a new endpoint requires putting in a JIRA ticket with a separate backend team, 4 planning meetings, and a month wait, people are just going to stick with what currently exists.

It was basically the same thing. In the code base, there was only v3 and v4. I never bothered to check what happened to v1 and v2, but I suspect they were used in an older, archived code base.

In my experience, having to write new v2 (or in my case v4) endpoints for most new features was expected.

The 21 year old is a separate person.

I was just using the term that the previous commenter used to keep terms consistent.

To add on to this, the 5000 series now generates 3 fake frames per real frame instead of just 1.

Seems a few people have gotten that confused. Article spent too much time rehashing the change in 15.0 before getting to 15.1 and felt like a typical ragebait article.

Still seems a little ragebaity, they don’t really have a lot of proof that Apple has intentionally disabled running unsigned apps. Their argument is that Apple changed the process for running in 15.0 and an app won’t start in 15.1, therefore the end of the era of sideloading. Personally, I would’ve liked more details on that part and less on history of 15.0.