3 ms·
There's a Ben Franklin quote that I'd love to see applied to software. He was self-taught in writing and the way he got better was to develop a one person versi
by hinkley 6y ago
There's a Ben Franklin quote that I'd love to see applied to software. He was self-taught in writing and the way he got better was to develop a one person version of the 'clean room protocol', by relying on the fallibility of long term memory to separate himself from the source material. He would take an article he loved, try to write a summary of it, then put the summary and the article away. Later he would pull out the summary, and try to write an article to match, then compare his results. Put it away again, pull it out and write a new summary, then compare the summaries.
There are a number of problems with writing a new library to replace an old one that cause us to commit most of the same mistakes, or recreate the mistakes of the old old library. Chesterton's fence and Anchoring being two big examples. This makes most new code evolutionary instead of revolutionary. The first time I saw this phenomenon for what it was had to do with attempts to target the JVM with other languages. This facility has essentially been in Java since 1.2, but the initial tools for doing so looked like assemblers, and not even macroassemblers. You were writing assembly by hand, without variables or registers (since the JVM is stack based). The next two attempts to do something better were less awful, instead of good, and my interpretation is that they were trying to fix something that was broken instead of building something new. A whole generation of devs missed out on leveraging that technology, and most of the work to make the JVM a better host happened after Sun Microsystems was no more.
We get a jQuery or a usable macroassembler once a decade instead of twice a year.
We aren't going to get hardware advances like the old days (Apple's "M3" will probably not be 3x better than the M1), it would be good if we could accelerate excellence in library design. TDD hints at a way, but I think we could go farther, and I have an intuition that such efforts could spin off of code reading groups, if they existed.
- akkartik 6y agoI loved this comment and also your https://news.ycombinator.com/item?id=26646153#26669166 https://news.ycombinator.com/item?id=26646153#26669166. I'm curious what you think of my https://github.com/akkartik/mu https://github.com/akkartik/mu