A software engineer that loves Disroot and the team behind it.
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.
Good luck getting there on a wheelchair… Or under influence of C2H5OH.
One person downvoted? Are they stupid or something? Asking for a friend.
Obviously, that’s what the “arms race” refers to. Birds used to have very strong arms which they used while racing in their super-fast arm bikes.
If you enjoyed it, I’ve collected a couple of others:
Reminds me this great story from a different era:
On a serious note, I really enjoy yerba mate-based (or should I write flavoured) elixirs. Or even yerba mate itself. Just saying! 🤷
That’s like… Your opinion, sis…
Do you eat them too? Asking for a friend!
Could someone explain how they’re going to drive 407 km/h in traffic jam? Or in a city, in general?
What’s the font used in the heading? Is it some flavour of Helvetica?
I keep telling myself that in the ideal world, phones would be programmed in Forth.
That comment… Oh my, I want to joke and talk someone like you! Now!
I tried searching for research on it, but only found results claiming this didn’t work… Not actual scientific research, but better than “we think this should work, so now we’ll try selling it”
What is he holding? An ancient dildo or a shit stick?
And “Y” stands for “Your Mom”. But it was a one night stand…
I suspect it’s related to USA current affairs and have no clue what it’s referring to. Any hints for us outsiders?
First you confirm they have to spend a lot of time to set everything up, then you claim it’s just pressing a button? 🤨
Taking a picture with your phone maybe looks like that, when you don’t care, but knowing one’s gear and using it properly is already many levels above just pressing a button. Then only a few questions and one presses the button. Questions like: what will be blurred? what will stand out? how the picture will be composed? will colours play? or textures? are there relations between objects in the picture?
What in trying to say is: I don’t agree with you, that it’s just pressing a button. Programming is also just pressing buttons, right? 😉
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.