Hey there, “doesn’t read”? That’s not true.

Fresco, not fiasco, damn it! 🤭

Yeah, very well beaten… I was talking about Luigi at work today (EU person here) and when I said it is a young guy from a wealthy family, one dick stood up and said “oh, so it was just a spoiled kid?” And there’s probably much more people like this around me.

I don’t know the thing you’re referring to. Could you please share a link?

Removed by mod

It’s not a picture, it’s a sequence of bytes

We’re in this together! Wait, wrong note…

We’re terribly sorry, but we’ve run out of thoughts and prayers because of all the school shootings. We apologize for the inconvenience.

Or even better, install Emacs and run away laughing wildly! Bwahahahaha!

Is that called “relatives with benefits”?

Any hints for the unaware? What’s going on?

30 minutes and not a single downvote! Well done OP!

Why does JavaScript before-guy look like Alan Kay? 🤔

Found the first one, but I need the original. Help!

https://ca.pinterest.com/pin/383368987046945659/

I have no idea, but I’m ok with that. Cheers!

If woodchuck could chuck… Or whatever it went. Now I’ve got a new version:

Can shit can shit?

It’s called Big Geo and they keep lyin’ to us!

A true FP programmer would make it apply instead of run…

Maybe that example was made terrible because the author couldn’t think of a good ways to show how great this can be. I’m obviously a fan of SOLID, and OCP is exactly why I don’t worry if I have only one class at the beginning. Because I know eventually requirements would change and I’d end up with more classes.

Some time ago I was asked by a less experienced coworker during a code review why I wrote a particularly complex piece of code instead just having a bunch of if statements. Eventually this piece got extended to do several other things, but because it was structured well, extending it was easy with minimum impact for the code-base. This is why design matters.

Above claims are based on nearly 2 decades of writing software, 3/4 of it in big companies with very complex requirements.

I wouldn’t say that inheritance is for avoiding code duplication. It should be used to express “is a” relationship. An example seen in one of my projects: a mixin with error-handling code for a REST service client used for more than one service has log messages tightly coupled to a particular service. That’s exactly because someone thought it was ok to reuse.

In my opinion, inheritance makes sense when you can follow Liskov’s principle. Otherwise you should be careful.

Wake up Nee-Oh!