At some point, I lost the motivation to write about anything that would include too much code because of the amount of time it would take to:
- put a functioning solution together,
- architect it in such a way that’d fit with best practices (at least for OOP),
- explain the various features about OOP that the reader may not know,
- then explain the problem.
This is too complex.
I’m not saying that articles shouldn’t be written that explain the concepts of object-oriented programming or shouldn’t talk about certain rationale for why something was done.
Continue reading
