Figure out programs while writing them through experimentation and debugging, instead of designing everything on paper first.
Figure out programs while writing them through experimentation and debugging, instead of designing everything on paper first.
More from this article
See all →The original 1985 Macintosh succeeded because users never had to understand or prepare for the…
Premature design is as dangerous as premature optimization. Deciding too early what a program…
Makers learn from masterpieces by reproducing how successful works were constructed, not merely by…
New mediums are explored most intensely during their first generations, when novelty gives…
Institutions rely on publications, standardized tests, and lines of code because they are easy to…
A programming language should be a pencil for discovering designs, not a pen for recording…
Broken code is a sketch: debugging is not cleanup after creation, but part of programming’s…
Write programs for people to read, then let machines execute them incidentally. Readability serves…
Don't lose this one
A free account saves cards like this to your Collection, and Korva resurfaces them so you actually remember.