Old Man Learns to Code

It feels as if it was longer, but apparently I needed some time out from actual coding for diversion,  reflection  and introspection.  ( More here ) and ( here ) [Jump to latest thoughts-- click here ] I found every excuse for not doing OOP project #2 which is the abbreviation expansion class and its "objects". Was it nothing more than falling into a bunch of easy-dopamine traps ? Did I get stuck in the identity-politics debates? Did I let 'notifications' on my smart phone distract me? Perhaps. Or maybe I needed to rewire my mental models in the background (the subconscious) of how OOP objects should be viewed ? So now I have a new view of what the definitions should be for what is a "class"? For  what is an  "object",  "attributes", "methods", the init method and so on; all to be found ( HERE = an earlier OML2code post) Given that, I've re-designed the plan for my expander cookie-cutter (aka 'class') p...

" Look before you leap " is a common alliterative warning ( WaZit? ) about diving blindfolded into a strange pool or any other unmapped situation (e.g., a coding project). Yet so many beginner programmers try hammer some code onto a blank page, thinking that doing it from " scratch " is the best way. They're wrong. It's the worst way. See gQAB ::: Plan before you run (Note: QAB stands for Query ABout. The "g" prefix means via google) See also:  Reasons You Should Plan Your Python Code Before You Write It by dts) No general goes into battle without first having mapped out the terrain, without first having studied the enemy and having analyzed the various obstacles that may foil the campaign (e.g., will the Russian winter defeat Napoleon's / Hitler's troops?). So how does that apply to a new coding project? One Python Vlogger ( Wu --here: How to build understandable programs ) gives an example based of designing a Tic-Tac-Toe game to be pl...