3 ms·
Harsh, but not wrong. To the OP: What you are doing is somewhat akin to sketching or doodling. It can be an important step towards creating something tangible,
by raganwald 16y ago
Harsh, but not wrong. To the OP:
What you are doing is somewhat akin to sketching or doodling. It can be an important step towards creating something tangible, but as it has no deadlines and imposes no constraints, it has limited utility. Design is all about making tough choices about what to include, what to leave out, and why.
My suggestion--and I am no expert on writing programming languages or creating anything--is to borrow something from Paul Graham and recast your project as an attempt to answer a question. For example:
Probe is an attempt to answer the question "Does an operator syntax for mapping and folding functions make code easier to read?"
Good luck!
- messel 16y agoThanks, appreciate the redirect to reframe as a question. This is the type of question many developers should periodocially ask themselves, "what do I want in a language?" Our tools deeply affect how we think through a problem.