2 ms·

Rather than "bull", I suspect we're already in agreement, given your statement, "At the level of thinking where you’d pull out pen and paper". We appear to agr

Rather than "bull", I suspect we're already in agreement, given your statement, "At the level of thinking where you’d pull out pen and paper". We appear to agree there's a place for pen & paper, and we appear to agree that's a different level to coding implementation. Writing down code, complete with correct syntax, parentheses, indentation, etc, as the article wants, is not in my opinion that level. At that level, the tooling does not suck. So yes, I agree, "At the level" where pen & paper shines it should be used. That level is not writing correct code, unless you can convince me otherwise?

doublerabbit 3y ago
For myself by writing prototypic code correctly with pen; not only does it keep my vision straight, it also gives myself clarity and a sense of sanity of say, what that function does. With the hard evidence you can then refer back to. So, when you are ready to expand your design you already have the foundation on page. It acts as a pillar to the psuedo code that comes with design later on. If that is the going to be foundation to that function, it might as well be written correctly on paper.