july

Example: The philosophical idea driving engineers is to convince future marks about the infinite significance of reproducibility and the need to appreciate copies of copies of copiea, even in a world flooded with originals  @july

I remember I had the opposite problem. When I started first learning how to program when I was about ~13 yrs old or so, I remember having a difficult time. 

The difficulty wasn't in knowing what a variable was, that it was memory somewhere on the computer saved at an address somewhere, while I didn't know exactly what that meant, I had enough of an understanding to grok it enough to use it. What I didn't understand was, what was a variable, and was, why was it called a variable, and how do variables work in the world, why did they choose it, who made it and kept going down a rabbit hole.

In other words, engineering inherently requires you to almost suspend this rabbit hole about diving into the philosophy and larger societal implications about what these things, and the consequences, and how it challenges norms, and disrupts notions of traditional representations of concepts, or what the philosophical meaning is -- if you don't suspend you dont get to the next step

creating and destroying; built flying cars & autonomous vehicles, now building /faust, more here: /july, web: july.rocks

its like blindly being initiated into a cult this was my early programming experience too and seems to apply to many fields flooded in jargon