Laziness I - Metaprogramming
26 August, 2022
1
1
0
Contributors
1.
We get to know them.
2.
We don’t understand them.
3.
We study them thoroughly.
4.
We master them.
5.
We read the bible that tells us that patterns are everywhere.
6.
We abuse them thinking they are our brand new silver bullet.
7.
We learn to avoid them.
Magic is at hand
Open but not so much
1.
Generates a dependency to the Parser class, which is the entry point for this responsibility.
2.
It uses sub-classes with meta-programming, therefore, since there are no direct references, their uses and references will not be evident.
3.
As there are no references and uses, no direct refactoring can be carried out, know all their uses and avoid accidental deletions.
Without references, there is no code evolution
The code should be clean, and transparent, and have as few meta-references as possible that are not reached by someone who can alter that code.
The exception defines the rule
Not my responsibility
The exception to the exception
Conclusions
software
tutorial
programming
beginner