Lego Naming Prevents Higher Level Thinking :
GunPowderedPoweredLargeIronBallLauncher <<-- Clean Code
Cannon <<-- Terse Invented Concept In Your Code
If you agree. Check out my coding stream.
I do Data Oriented Game Engine Design. (DOGED)
www.twitch.com/kanjicoder
www.twitch.com/kanjicoder
//:2021_02_23:===============================================://
WindowExternalVisibilityController ==> BLIND
ExtraFlufflyCushionedChair ==> LazyBoy
MultiBarrelRotatingMiniCanno ==> GatlingGun
LargeIronBallLauncher ==> Trebuchet
GunPowderedPoweredLargeIronBallLauncher ==> Cannon
You cannot think of
"GunPowderedPoweredLargeIronBallLauncher"
at the next level of abstraction until you
condense the word into a TERSE/SHORT word.
Example:
You won't invent a "Gauss Cannon"
until you STOP CALLING YOU CANNON A:
"GunPowderedPoweredLargeIronBallLaunched"
Same applies to your code.
You can't to the next level of abstract thinking
until you stop your lego-naming.
( agglutanative naming )
@VID_IID[ 0151 ]TIME[ 05:52:13 ]
DATE[ 2021_02_23 ]
//:===============================================:2021_02_23://
Comments
Post a Comment