The decades-old chasm between code and architecture is a status quo worth challenging. Bridging it could mean a world of possibilities. Effortless application remodeling, unconstrained code reuse and harmonious design patterns as the standard. I want to share with you my findings and a framework that ties everything together. Join me in an insightful session packed with radical but simple-as-day concepts. Learn today the tools and workflows that can unify the future of development.

1. THE
UNIFIED
FIELD
THEORY
OF
APPLICATION
DEVELOPMENT

2. THE JSON ARCHITECTURE
An architecture pattern for data driven
functional programming
BucharestFP - 11 May 2016
THE JSON ARCHITECTURE
Re-engineering programming
BucharestJS - 29 June 2016
MVC 2.0
A Breakthrough
Barbcode - 1 Octomber 2016
JSONMVC
The Framework that lost it’s API
BucharestJS - 11 May 2017
THE UNIFIED FIELD THEORY OF
APPLICATION DEVELOPMENT
Softbinator - Today
@dumconstantin

3. Let’s begin

4. GRAVITY
OTHER FORCES
&
PARTICLES

5. GRAVITATION
WEAK
STRONG
ELECTROMAGNETIC
forces
ANTI/QUARKS
ANTI/LEPTONS
BONSONS
particles
+
AN UNIFIED FIELD THEORY IS
IN ESSENCE:
f(time, space) = { props }

6. PHYSICS
IS STILL
AN
OPEN-ENDED
EXPLORATION

7. What about the digital universe?

8. SYSTEM
SOFTWARE
PROGRAMING
SOFTWARE
TASK
SOFTWARE

9. PROGRAMMING
SOFTWARE
SYSTEM
SOFTWARE
TASKS
SOFTWARE
Device Drivers
OS
Servers
Engines
Compilers
Tools
Scripts
Processing
Coordination
Activities
User Benefit
Manipulation
Graphics
MeaningFacilitatorMedium

10. Data
is meaningless.
Data
is meaningful.
Transformation
is stateless.
Transformation
is statefull.

11. ABSTRACT DATA
TYPE
ALGEBRAIC DATA
STRUCTURES
OBJECT
ORIENTED
PROCEDURAL
FUNCTIONAL

12. If an application can
be written in all
variants it means
that the thing that
makes the
application an
application is not
present in the code.

13. Instead,
the way data makes
its path to
transformations and
then back again is
the essence of all
applications.

14. Without a
MODEL
there is no complexity
Without a
VIEWER
there is no output
Without a
CONTROLLER
there is no input

15. DECLARATIVE POINTERS
/birds/duck/mammals/squirrel /birds/penguins/1

16. SIMPLE FUNCTIONS
let season = {
/elements/tree
/elements/rocks
/weather/snow
}
makeScenery(season)
-> /scenery
/scenery/scenery

17. PROPERTIES
Data through patches
Centralized state
Universal pointers
Deterministic system
Language agnostic
No data corruption
Maximal validation
Minimal computation
Least amount of code
100% Reusability
Predictable to the CPU
Automatic scaling

18. IMPLEMENTATION
. . .

19. OPPORTUNITIES
. . .
Lingua Franca of Application Development
Reach a consensus amongst communities
Create positive niches for language uses
Allow cross-language reuse through declarative pointers
An enabler for a true business ⇔ developer relation

20. CURRENT IMPLEMENTATION
https://github.com/jsonmvc/jsonmvc

21. Q & A
Every question I can’t answer is
an invitation
to join the challenge

22. Thank you!
@dumconstantin
I do not own nor
take any
ownership for any
of the images used
throughout this
presentation
-
all credit is given
where credit is
due.