kamen

Okay, I get the idea of smart AC for example - be elsewhere, turn it on remotely so that it’s comfortable when you get home. Fine. But a toilet? You are physically present there, you can push a button to flush. Or are you telling me that you’re shitting remotely now too?

Somewhat agree, but since Scrum is supposed to be bent to the team’s needs, it might differ from team to team, but it’s fine as long as those numbers are consistently used in one team.

If story points are now hours, I hope you’re fine with me putting a 40 on that ticket.

I’d argue that deploying from one codebase to 3+ different platforms is new functionality, although not for the end user per se.

I wish though that more of the web apps would come as no batteries included (by default or at least as a selectable option), i.e. use whatever webview is available on the system instead of shipping another one regardless of if you want it or not.

Well, over time, you accumulate some judgment about things like that. But you have some point too.

For anything that doesn’t seem entirely obvious I try to leave a comment. It could end up being helpful to me some time later, because let’s face it: your code is indistinguishable from someone else’s code 2 weeks after you commit it.

pænis

Laugh tracks have a purpose though. I understand they’re not to everyone’s liking - and that’s fine, but they work for some comedy shows - and usually they’re from the live audience that sees things performed in front of them.

As if someone’s telling a joke and saying “This is where you should laugh”

As if default keywords are the biggest deal-breaker.

There are no bugs, it’s just not doing what you expect it to be doing…

… which, now that I think of it, can be said about all software in general.

You have a point unfortunately.

Implying the orange fella has any say in programming language design and general tech conventions

A bit slow to be honest, but I’m shooting Eluveitie and Infected Rain this weekend, so looking forward to that.

Yeah, fair point. Thanks for explaining. Not a native speaker, so I kind of forgot about that.

General advice - don’t be picky about dedicated media controls; sure they’re nice to have, but they severely limit your choices (I was in that boat too). At the same time it’s very easy to make key combinations; e.g. the Caps Lock key very often gets neglected, and if this is the case for you, you can repurpose it to Fn, and from there you can do Fn+W to play/pause, Fn+Q/Fn+E for prev/next track respectively and so on (of course the specific keys are up to you). Look for QMK/VIA support over manufacturer-specific software.

Sorry I can’t give a more specific recommendation. I second the idea that Keychron generally have good value for the money, so do Vortex and Ducky (although Ducky have gone up in price while not staying very competitive).

“Пиян като мотика”. Translates from Bulgarian to “Drunk as a mattock”. I remember asking my dad about this phrase when I was a kid - “Why? Do mattocks drink?” - and he answered “No, they fall down”. Classic dad.

In this line of thought I like how “tool” is something useful in its primary meaning, but derogatory when used about a person.

We have a similar one in Bulgarian too: “Парен каша духа” - roughly the same thing, but without explicitly mentioning youghurt.

I agree with the “learn the CLI”, but to newcomers I’ll also suggest to look at the IDE/editor’s output channel - if there’s GUI for Git, there are also most likely logs for what’s happening under the hood - even if a little noisy, it can be a good learning resource. And of course if you’re learning and unsure of what’s happening (with the CLI or through a GUI), do so in a non-destructive manner (by having proper backups).