The Shape of the FLUID
Introducing FLUID: a new programming methodology based on early AGILE principles and the principle of minimal code per action.
Software Architecture & Design
System design, architectural patterns, and software engineering principles
FLUID 1: Flexibility
The first component of the FLUID methodology is flexibility: characteristic of code being resilient to change with minimal impact.
FLUID 2: Lean Implementation
The second component of the FLUID methodology is lean implementation: to tailor the code on the size of the problem to be solved.
FLUID 3: Universal Interoperability
The third component of the FLUID methodology is universal interoperability: each component provides a single generic functionality to the collective.
FLUID 4: Intuitive Interfaces
The fourth principle of the FLUID methodology is intuitive interface: components should allow all reasonably expected interactions without unexpected behaviours.
FLUID 5: Decentralised Control
The fifth and last principle of the FLUID Methodology is Decentralised Control: moving the locus of the application logic where the context information is readily available.
Cracking open code readability
When you start a career in IT, you are told that writing readable code is the most desirable technical skill you will ever have. But no one can tell you what readable code really looks like.