A sports piece of clothing or equipment is functional with or without the flashy branding; a piece of merch however is not (especially if it’s just decorative - like a pin, a sew-on patch or something like that).

Same sentiment here - but with the exception of band t-shirts and other merchandise - where in most cases you do want to show your support for the artist.

It’s not even that much of a pain. I’m mostly dealing with TypeScript, very rarely vanilla JavaScript, and it’s even enjoyable most of the time.

Eh, whatever. It puts food on the table…

Yes, indeed, I see javascripts in the wild every day.

The only argument I see in favour of office time is if your home situation doesn’t allow you to focus - family, kids and so on, or if you deliberately want a physical separation and you don’t have a dedicated office space at home.

“Catching mice is a stupid question.”

The other way around makes more sense IMO: “An existential crisis is just applied philosophy.”

This must be a “hold my beer” kind of joke and someone wanting to see how far they can take it.

Weren’t you getting runtime errors for the function not being found?

Imagine having so much time to complain.

Yes, and there’s that small thing that’s done in a slightly different manner that you can’t change through settings and it messes with your muscle memory.

Where I am people do not trust people and shopping carts are coin operated.

No, we must rewrite it in this fancy new framework that came out last week.

(/s if not obvious)

Imagine playing a shooter over a network using this protocol.

My take is use a GUI for anything read-only/nondestructive (i.e. anything that won’t modify your local or remote state). It’s nice for example to compare the state of two branches.

For anything that does changes make sure you know what’s happening under the hood, otherwise you might shoot yourself in the foot. It’s convenient for example to do a commit and push in one go, but then you lose the ability to edit any changes (you’re forced to either do another commit, or change your local commit and force push).

In VSCode you can go to the Output pane and switch to Git - there you’ll see everything that gets done through Git’s CLI for whatever you do through the GUI (although it can be a bit noisy); same goes other GUI utils.

One key thing that can help you wrap your head around rebasing is that branches get switched while you’re doing it; so, say you’re on branch feature and do git rebase master, for any merge conflict, whatever’s marked “current” will be on master and what’s “incoming” is from feature.

There’s also git rerere that should in theory remember a resolution you do between two branches and reuse it every time after the first; I’ve rarely used it in practice; it would happen for long lived branches that don’t get merged.

This is now the correct database.

“We conform to the open standard, but only to the parts that we like”

Ah, a fan of Wodos.