3 ms·
This conjures up the image of someone maintaining a bonsai tree, meticulously clipping of every errant leaf with a tiny scissors and refusing to use any other t
by esperent 5y ago
This conjures up the image of someone maintaining a bonsai tree, meticulously clipping of every errant leaf with a tiny scissors and refusing to use any other tools or fertilizer.
Much like a bonsai tree though, the code you write in this way will remain tiny and mostly useful as a talking piece. You might be able to write some tiny useful applications this way but good luck scaling it up to a team of people working on the code, or any kind of larger application.
And that's fine! There's a place for bonsai trees, and there's a place for meticulously hand written code, and both are as ornaments.
Referring to any code not written this way as "pollution" , though, comes off as extremely arrogant and turns this into another "my way is better than your way" bs article. Very disappointing.
- bigDinosaur 5y agoBonsai tree as a metaphor for microservices? It could work! Lots of little utilities that can communicate in an ultra-simple way, say just with text - hang on.
- mdp2021 5y ago> and refusing to use any other tools or fertilizer No, come on, it's a not a matter of being playing some sort of "puristic game": it is a matter of looking at the product and judge it. What can be "for the benefit of scaling" when you look at the engine and it looks like a hand grenade exploded in it (which is visible e.g. in the source of a large number of web pages, to mention something quite common)? Do you remember the code which was output by early WYSIWYG web editors? It is just a matter of quality assessment. Also, a call for low level awareness, which is good grounding; and also, a matter of manageability (again about teams), because "cleaner" facilitates "understandable".