Do State The Obvious


If you are into open source and a bit of a neophiliac when it comes to discovering new software, chances are you have read something akin to the following statements etched proudly at the top of some project’s README on GitHub:

Yo! X helps you write applications that behave consistently, run in different environments, and are easy to test. It is fast, simple, reliable with zero-overhead production readiness and nada ceremony.

You know why?

Because sometimes people wake up in the morning and ask themselves: “What shall I do today? Oh, I know! I shall design a framework that forces applications to behave terribly inconsistent and of course, they must all run in the same exact environment down to the kilobyte level. Not only the application must be crap to test but it must be slow, Lost-The-TV-Show-level convoluted with so much overhead that once you’re done with production, you will yourself wholeheartedly finance a “Thank the Gods for we are forever done with this junk” ceremony.

Yes. Yes. That happens, which is why projects need to explicitly state the obvious opposite.

Seriously[?],

Misagh Moayyed

Related Posts

CAS 5.3.0 RC4 Feature Release

...in which I present an overview of CAS 5.3.0 RC4 release.

Apereo CAS - Test-Driving Feature Modules

An overview of how various CAS features modules today can be changed and tested from the perspective of a CAS contributor working on the codebase itself to handle a feature request, bug fix, etc.

Feedback on draft Apereo strategy

Focus on revenue to achieve sustainability. Defer everything else.

Apereo CAS Best [Mal]Practice - Supercharged Overlays

An overview of how a CAS overlay prepped for deployment can tap into internal components, altering logic and behavior for good and evil...but mostly evil.

CAS 5.3.0 RC3 Feature Release

...in which I present an overview of CAS 5.3.0 RC3 release.

Apereo CAS - REFEDS MFA Profile with shib-cas-authn3

An overview of the shib-cas-authn3 project and its support for the REFEDS MFA profile with both the Shibboleth Identity Provider and Apereo CAS lending a hand.

Forced Authentication with Apereo CAS

Discourse on supporting forced authentication with the Apereo CAS server from the perspective of an application protected with mod-auth-cas, the Apache httpd module for CAS.

Apereo CAS - Dances with Protocols

A short overview of how Apereo CAS may support multiple authentication protocols simultaneously while acting as both the primary identity provider or proxying another. Two Socks could not be reached for comments.

Why does uPortal use Apache 2 license?

Apache2 chose uPortal.

Apereo CAS - Attribute-based Application Authorization

A walkthrough to demonstrate how one might fetch attributes from a number of data sources, turning them into roles that could then be used to enforce application access and authorization.