or wondering how you’ll close up a veggie bag.

Get yourself some of these for all of your bag-closing needs: https://www.ikea.com/se/en/p/bevara-sealing-clip-anthracite-dark-yellow-90524179/

Costs just above 1 EUR for a set of 6, so you can probably even afford to get 2 or 3

There are tariffs on Chinese EVs in the EU as well.

The primary use-case for LLMs once again appears to be gooning

It’s mostly a skill issue for services that go down when USE-1 has issues in AWS - if you actually know your shit, then you don’t get these kinds of issues.

Case in point: Netflix runs on AWS and experienced no issues during this thing.

And yes, it’s scary that so many high-profile companies are this bad at the thing they spend all day doing

You prepare for these by doing specific exercises for them, sad as it may seem.

Leetcoding problems? You grind them out for a month or two to prepare for doing them during interview loops.

Mock interviews can help too, to get you better at handling the stress. You can use services/groups for these, or just go interview for random places you’re not necessarily planning to actually say yes to.

You can see it in the article. He got sent down in a dunk tank, filled with champagne of all things.

It’s cringe

No need for the likely-qualifier - it definitely won’t make a difference in perceived sound quality.

You basically need expensive gear under the right conditions and training to be able to tell. Modern audio codecs are extremely good - the main thing you will get out of lossless is more storage/data usage

Still on the Slay the Spire-train. A downright excellent game.

Also playing some Hades 2

Pick-Up Group

Perhaps the most pathetic attempt at intimidation ever, from a shitstain with exactly zero leverage in the situation.

Agreed. If your commits are reasonably structured, rebasing is far more helpful.

Although these days I usually opt for one ball-of-mud commit while developing the code, which is always fairly trivial to rebase - only one commit, can’t have follow-up issues - and then I redo the commit structure from scratch as a part of preparing the code for the benefit of the reviewer.

Use a rebase.

Well, she is the opposition leader in Venezuela, aligned with conservative interests, so I don’t know that going to war with the current Venezuelan regime will actually be a good idea.

Not that any ideas being good or bad has ever stopped him from doing anything, but I guess it bears repeating

You enable it using git config, after that it will apply to whatever frontend you’re using.

Depending on how structured your commits have been, it can either be very difficult to get a rebase through or a complete breeze. There are some features to make it easier - rerere being the main one I’m thinking about.

What’s your mental model for a Git commit, and a Git branch?

Once I properly learned those two concepts, understanding rebases became a lot easier.

I’ll try to explain it to the best of my abilities.

• Think of a commit being a patch - a description of how to take a particular file from one state to another
• A branch is a list of patches to be applied in order, from the point where the branch was created until the last commit on the branch

When you rebase a particular branch, what you’re essentially doing is taking all of the commits that are currently on your branch, checking out the other branch, and then applying each of the patches in order on that new branch.

A rebase can be cleanly applied if the premise for each commit has not changed when applied, but if the premise has changed, you get a conflict to be resolved before being able to continue the rebase.

I mentally model a rebase a bit as a fast version of how it would look like to build the branch I was on, but on top of the branch I’m rebasing on.

ps aux | xargs kill -9

Well, you might be inclined to not roll the feature out at all, depending on the results you see from the rollout/an A/B-test. Also, having it written out with a date in the changelog binds you to that date, unless you want the embarrassment of not shipping on a promised time. Maintaining a changelog for very large app development organizations is also a pretty damn hard task, trying to coordinate whatever all teams are releasing in a particular build.

I agree that getting cute with the changelog messages is a bit stale. Might as well not add anything at that point.

Modern mobile app development almost always releases features gradually behind feature flags, so changelogging things is not necessarily practical to do.