3 ms·
> but they only benefit after you've actually written a program, which is the barrier the potential users are struggling at No, you miss the point. There is li
by phoe-krk 6y ago
> but they only benefit after you've actually written a program, which is the barrier the potential users are struggling at
No, you miss the point. There is little benefit in interactive and incremental development once a program is written. The very benefit that this such incrementality provides is noticeable during the process of writing the program, not after it; when a program is written, it's written, and from some point it doesn't really matter if you've done it by mutating an image-based programming language or by linking together compiled C objects.
- pjc50 6y agoPrograms are never finished. Most work is incremental modification and debugging of existing systems. The "getting started" bit of going from a blank editor to something that starts to be useful is a small part of the process. But it's the very beginning that is a surprisingly hard barrier to cross. The starting to write a program in the first place. Which is where the OP has got stuck. And is dismissed as irrelevant?