Keep your source code SIMPLE

My feeling is these paradigms, SOLID and SIMPLE, boil down to basically: small objects, connected minimally, though interfaces.<p>SIMPLE appears to be leaning even more towards the functional programming side of things; I think we should probably just get it over with and accept that composition of functions operating on immutable data structures is just the right way to go.

&gt; Error: ENOENT, no such file or directory &#x27;~&#x2F;foorc&#x27;<p>I can’t count how many times I’ve seen error messages that look like this, often with no context at all, in JavaScript apps, even widely used ones like npm and webpack. Proper error handling is never easy, but the JS community seems particularly given to avoiding it.

Complexity is combinatorial. If you compose your code of overly complex components the end result will have much more emergent behavior.<p>If everything at the bottom is straightforward, then people will spot more overarching concerns, instead of bogging down in minor details.<p>I’d really love to see some cognitive science applied directly to UX and code quality concepts. Surely some of the things we espouse but don’t enforce are spot on, and others are cargo culting. Refining that list might make it harder to ignore.

can author of that medium post show real world example of an app, build with those principles and rules from start to end?<p>it would be also very educational to see decision and design process of an app build with those rules.

I couldn’t agree more.<p>Also; keep it <i>clean</i>. Don’t over-comment, but comment.

But wait, I want all my code to work in linear space and time, look like assembly code and scale to 4 billion servers.

&quot;Keep the story going. Sign up for an extra free read. You&#x27;ve completed your member preview for this month, but when you sign up for a free Medium account, you get one more story.&quot;<p>Sorry, can&#x27;t read behind paywall.