3 ms·

I haven't really had art classes, no The problem I run into when I'm brainstorming or thinking about high-level architectural/modeling questions, is that if I

I haven't really had art classes, no The problem I run into when I'm brainstorming or thinking about high-level architectural/modeling questions, is that if I start drawing something I get focused on how to represent my current idea and I stop actually developing the idea itself. And then if I change my mind, I have to go back and erase or strike things out instead of just redirecting my thought. Etc. Usually if something is new for me or ill-defined, I take a walk or a shower and work through a rough idea of the big picture (usually realizing and iterating on some of the high-level problems) without any medium. And then when I sit down to start seeing what that established will look like more tangibly, I usually go straight to the computer. Though I will say, I sometimes turn off type-checking when I'm just writing the idea out the first time. It can get really distracting when the code is going to be "broken" for the first 90% of the process. Once I've given it a look over and feel good about it, then I turn editor hints back on to nail it down and get it running.

strken 5y ago
For diagramming, I really only do it to document connections between things. Everything is either a chunk of text, optionally in a box or circle; a line or arrow; or a note beside the first two. It emerges directly from what I'm thinking without much extra thought, and usually gets discarded or rewritten before anyone else reads it, or if there's too much crossed out. Sort of like a swap file, where if the number of items gets bigger than my working memory, I dump some of them onto a sheet of paper rather than thinking about all of them at once. I'm interested in hearing how other people approach diagrams, because I bet there are a lot of different approaches, and no one size fits all.
- brundolf 5y ago
  Right but as soon as I've written down a blurb or drawn a line I feel like it's set in stone a little bit. It feels like a decision. It isn't necessarily - I can always erase it or draw it again on a new page - but that carries friction which interrupts the process. It works better at the phase after ideation, where I'm pretty sure I have the major ideas in place and I want to see them to make sure they make sense. But even then I prefer a digital medium because of how easy it is to delete or modify (even an eraser leaves behind a smudge, adding something to a list on paper means moving each item by hand, etc).
  - dylan604 5y ago
    >Right but as soon as I've written down a blurb or drawn a line I feel like it's set in stone a little bit Use a pencil, and not a pen ;-) Much less permanent. Just knowing you can erase should make it feel less decisionish. For me it's the opposite. If it's a sketch on paper, it is so much more transitional. Once it's in code and executable, it makes me want to keep forcing things until it works. But that's what makes it fun. Each dev sees the same problem totally differently and approaches it in their own way.
Infernal 5y ago
I identify with this so much. Pacing, talking to myself even yes, but always manipulating concepts in my mind - and writing the code once it becomes clear. The idea of introducing diagrams or sketches into that process sounds disruptive and distracting at best.

strken 5y ago

For diagramming, I really only do it to document connections between things. Everything is either a chunk of text, optionally in a box or circle; a line or arrow; or a note beside the first two. It emerges directly from what I'm thinking without much extra thought, and usually gets discarded or rewritten before anyone else reads it, or if there's too much crossed out. Sort of like a swap file, where if the number of items gets bigger than my working memory, I dump some of them onto a sheet of paper rather than thinking about all of them at once. I'm interested in hearing how other people approach diagrams, because I bet there are a lot of different approaches, and no one size fits all.

brundolf 5y ago
Right but as soon as I've written down a blurb or drawn a line I feel like it's set in stone a little bit. It feels like a decision. It isn't necessarily - I can always erase it or draw it again on a new page - but that carries friction which interrupts the process. It works better at the phase after ideation, where I'm pretty sure I have the major ideas in place and I want to see them to make sure they make sense. But even then I prefer a digital medium because of how easy it is to delete or modify (even an eraser leaves behind a smudge, adding something to a list on paper means moving each item by hand, etc).
- dylan604 5y ago
  >Right but as soon as I've written down a blurb or drawn a line I feel like it's set in stone a little bit Use a pencil, and not a pen ;-) Much less permanent. Just knowing you can erase should make it feel less decisionish. For me it's the opposite. If it's a sketch on paper, it is so much more transitional. Once it's in code and executable, it makes me want to keep forcing things until it works. But that's what makes it fun. Each dev sees the same problem totally differently and approaches it in their own way.

Infernal 5y ago

I identify with this so much. Pacing, talking to myself even yes, but always manipulating concepts in my mind - and writing the code once it becomes clear. The idea of introducing diagrams or sketches into that process sounds disruptive and distracting at best.