swish_bob

i was so disappointed when I realised they were emulating a USB keyboard to enter the PINs. That first picture made me think they had a actual robot finger for a moment ...

I am and have done both. I tend to prefer a functional style, but even then I'm going to be using classes (or a similar construct) for quite a lot of problems.

I came here to talk about Liskov, but since you beat me to it I'll mention SOLID principles of class design instead, which it really sounds like the OP isn't aware of or just isn't following and it feels like is the source of a lot of their class based woes.

Dunno, watching people cat something then pipe it to grep drives me up the wall. I'll let piping grep to wc -l instead of just using -c pass this time though.

And a late 80s early 90s children's TV programme.

"Are your parents proud of what you do for a living?" is quite effective.

Your test should explain what it's testing. Via it's name or some other mechanism. Otherwise how do you know what's gone wrong when it fails?

Why it exists ought to be explained by the existence of a test.

This isn't always possible, but it's far more possible than many developers seem to think.

It's (mostly) a broadcast service. Them metaphor in this case, it's the radio station boosting your signal ...

I remember trying to create an MHD proof of concept in physics at school after reading the book, well before the movie was released. I thought it was inspired by the book ...

I particularly enjoy IntelliJ's local history, which will go so far as to tell me whether the tests were passing or failing (and how many failed) on a specific file at a specific point in time.

Use a graph database?

I'm stunned by the number of people who think that reviewing a PR is just a matter of checking the code works and looks clean.

Does nobody ask what the code is for and why you're doing it? I mean, I don't expect people to require detailed specs before approving, but a quick "what's this code for, and why are you doing it?" before addressing the details.

Surely that's the bare minimum, isn't it?

How would they complain to you? How would they know what the problem is?

Assuming they don't just fail to register and move on ...

So, when I registered for my primary email account (many, many years ago), Firstname.Lastname@provider was already taken, so I took FirstnameLastname@provider.

Are you suggesting I shouldn't be allowed an account with you if the person who beat me to my preferred email address also beat me to registering with you?