3 ms·

I liked the humble, “lessons learned” tone of the post. > every feature you add is a feature you maintain forever. This. Keeping a framework/app/SDK “pure” i

I liked the humble, “lessons learned” tone of the post. > every feature you add is a feature you maintain forever. This. Keeping a framework/app/SDK “pure” is very important, in my experience.

PartiallyTyped 11mo ago
> Keeping a framework/app/SDK “pure” is very important, in my experience. Could you elaborate?
- ChrisMarshallNY 11mo ago
  I’m a fan of “singleness of purpose.” For example, if the framework provides text storage, adding text processing might be a mistake. Instead, make another framework that can be strung onto the text storage one. It increases the granularity, and the usefulness of the modules. You could have multiple processing frameworks. In addition, it allows you to refine discrete functionality domains (which can also be personnel assignment domains), and reduces the places for bugs to manifest. You can devote more tests to each framework.
  - PartiallyTyped 11mo ago
    I see. I follow the same approach; with my interns I try to force them to define logical boundaries and think / design their software as libraries / components that compose together nicely.
shagie 11mo ago
> I liked the humble, “lessons learned” tone of the post. > > every feature you add is a feature you maintain forever. ... until it becomes a security flaw. Log4shell (IIRC) goes back to a feature to do an indirect lookup of a string over jndi in a beta version of the library. https://issues.apache.org/jira/browse/LOG4J2-313 https://issues.apache.org/jira/browse/LOG4J2-313
1718627440 11mo ago
> Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.