@p @jae @fluttersh @jeremiah this is a tangent but I wonder if my way of developing code is uncommon

I imagine how the code "works" by imagining it like a map with paths and tunnels , after spending long enough imagining it like a 2d/3d map I can just type out the code without having to think and it works on the first try

maybe guys who go to code school are used to drawing flowcharts and working off that, idk, i never went to code school, but having a drink or two in me helps me get flexible about first imagining "how the code should work" and then makes bridging the gap between "how it should work" and "what it is" painless and effortless

This is also why weed is not useful for me as a programming aid, get too distracted to build up mental models and then too distracted to reproduce them in the text editor