Re:A Plea for Lean Software (1995) [pdf]
by ChrisMarshallNY on Monday June 28, 2021 @10:21AM
(#27662344)
Oh, no. I use it all the time, for code components.
If you look at my portfolio[0], you’ll see it packed with things like widgets and adornments. Most of these, I use in my own projects. I eat my own dog food.
But today’s languages, with their reliance on extensibility and interfaces, makes writing standalone code assets a lot less cumbersome. I write in Swift, and there are some pretty big Swift "extension suites" out there[1]. The Apple Swift Package Manager is nice, too[2].
It's just that when I write a code module, I do it as a standalone product, with a full test suite (usually a harness[3], which often takes the form of a "full-fat" application), and a unique release management cycle.
My modules are pretty independent, so they aren't usually custom-tailored for all of their implementations; acting in a fairly general capacity.
If you look at my portfolio[0], you’ll see it packed with things like widgets and adornments. Most of these, I use in my own projects. I eat my own dog food.
But today’s languages, with their reliance on extensibility and interfaces, makes writing standalone code assets a lot less cumbersome. I write in Swift, and there are some pretty big Swift "extension suites" out there[1]. The Apple Swift Package Manager is nice, too[2].
It's just that when I write a code module, I do it as a standalone product, with a full test suite (usually a harness[3], which often takes the form of a "full-fat" application), and a unique release management cycle.
My modules are pretty independent, so they aren't usually custom-tailored for all of their implementations; acting in a fairly general capacity.
[0] https://stackoverflow.com/story/chrismarshall
[1] https://swifterswift.com
[2] https://swiftpackageindex.com
[3] https://littlegreenviper.com/miscellany/testing-harness-vs-u...