In the software business for over 40 years. I never thought serious programmers would use words like "describing the vibe" and "watching it manifest." Or to see pseudo-meaningful phrases like "dopamine hit" and "hyper-flow" in an article about programming.
The humblebrags alone turn me off: You think too fast and have too many ideas pouring out of your "speed of thought" brain. Mere software design and coding impose "drag" and "friction," like a shark forced to swim in mud with the rest of us with less-hyperactive minds. Lay off the Adderall.
I raised three kids. Children go through a period of intense curiosity where they try to make sense of the world, ask what feels like a hundred questions an hour, and present random thoughts and ideas and theories at the "speed of thought," or a speed faster than an adult can pay attention. I think of that as fun and charming with children, not aware of what they don't know, and interpreting their random theories as novel ideas. Then they grow up and learn to focus their mental faculties, and with some luck and skill discern signal from noise.
Shouldn't even be typing code while planning. There's no software idea that needs to be coded as it's planned. It's just a waste of time, and potentially harmful. The devs I've worked with that "think" in classes, or tables, or whatever code structure they're most comfortable with, inevitably end up creating garbage in the first 10 minutes that ends up lasting the lifetime of the project, confusing the hell out of everyone that looks at it, including themselves a week later.
In the software business for over 40 years. I never thought serious programmers would use words like "describing the vibe" and "watching it manifest." Or to see pseudo-meaningful phrases like "dopamine hit" and "hyper-flow" in an article about programming.
The humblebrags alone turn me off: You think too fast and have too many ideas pouring out of your "speed of thought" brain. Mere software design and coding impose "drag" and "friction," like a shark forced to swim in mud with the rest of us with less-hyperactive minds. Lay off the Adderall.
I raised three kids. Children go through a period of intense curiosity where they try to make sense of the world, ask what feels like a hundred questions an hour, and present random thoughts and ideas and theories at the "speed of thought," or a speed faster than an adult can pay attention. I think of that as fun and charming with children, not aware of what they don't know, and interpreting their random theories as novel ideas. Then they grow up and learn to focus their mental faculties, and with some luck and skill discern signal from noise.
Shouldn't even be typing code while planning. There's no software idea that needs to be coded as it's planned. It's just a waste of time, and potentially harmful. The devs I've worked with that "think" in classes, or tables, or whatever code structure they're most comfortable with, inevitably end up creating garbage in the first 10 minutes that ends up lasting the lifetime of the project, confusing the hell out of everyone that looks at it, including themselves a week later.