Hypothesis: If you keep your source code as short as possible, you will in the process reduce it to the "Legos" your idea is comprised of, and when you need to add something, you will usually be able to using those Legos plus at most a few new ones.
-
-
(The reason I said Legos instead of something more concrete like modules is that in the best case the Legos are of many different types: sometimes modules, sometimes libraries, sometimes language features, sometimes how you represent data.)
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The challenge though is in defining and agreeing on what “as short as possible” means in practice.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That is absolutely true! In fact that is what makes the code scalable and bug free, robust finite units.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Where can I go to read some of your source code?
-
You should have known this
. He wrote The book on Lisp. http://www.paulgraham.com/onlisptext.html - Show replies
New conversation -
-
-
Have you heard of http://stackoverflow.com basically what you are describing. I'm just waiting for someone to make a coding language out of that site.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thoughts are modular: they are stored as transitions and associations. Therefore writing “Legos” is natural. Writing a long source code is unnatural. (Anyway the source code is remembered as modules - whether we wrote them or not.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I resonate with this. It was my motivating principle behind Munchlax: https://github.com/atlassubbed/atlas-munchlax … It's a MobX/Meteor.Tracker clone in 20 lines of code using the exact same legos that a VDOM engine uses. Similar algorithms are used in view engines as are used in state management.
-
This Tweet is unavailable.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.