eejai42
@AnAbstractLevel
Creator of http://ssot.me, the low-code toolbox, helping to leverage all of the business decisions and IP currently buried in "source code", and other legacy systems.
THE PROBLEM: "Ideas" are Multi-Dimensional! They exist in an N-Dimensional space; each in it's own, complete, well designed, well normalized, multi-dimensional glory. Ideas should live in an NDLand... a world LineLand struggles to describe! #ssot #ssotme #lineland #ndland
Yesterday I realized: "Language" is a Garbage place for Knowledge because it literally lives in LineLand! 😲 Pictures & diagrams might prompt occasional excusions to FlatLand, but then it's right back to LineLand!! 🤔😮😂 "Source Code" lives in LineLand!🙄 #singlesourceoftruth
With a #knowledgegraph at the heart of a software project, the vast majority of the specs, code, scripts, integrations, docs, tests, etc ... in literally any language, can be _inferred_ from the _structure_ of the knowledge graph. #SingleSourceOfTruth #KnoweldgeGraph #ssotme
The Heart of software should not be "Source Code", because source code is language, and it is a garbage place to store knowledge. A Knowledge Graph (i.e. a Single Source of Truth) should form the *Heart* of any good Software Project. #SingleSourceOfTruth #knoweldgeGraph #ssotme
Holy Crap! The "missing layer" was hiding as a Knowledge Graph all along! A #singlesourceoftruth is just a #knowledgegraph #ssotme
Stop doing Design Time work at Runtime! blogger.com/blog/post/edit…
Allow me to explain... (3 of 3) ssotme.blogspot.com/2022/05/englis…
An obvious reason is that pictures are 2 dimensional and, can make use of all the colors of the rainbow, while if I were to assign a color and a shape to English it would have to be Purple and One Dimensional. (2 of 3)
English is Purple and One Dimensional - Learn why "Source Code" is actually a terrible place to put Software. Everyone agrees that a Picture is Worth a Thousand Words, but have you really stopped to think about exactly why? (1 of 3)
My first two wiki articles. en.wikipedia.org/wiki/Recursive… and en.wikipedia.org/wiki/Derivativ…. #DerivativeCode #Codee #CODEiverse #ChameleonCode
This abstract description can then be shared across all platforms, languages & environments. It's like a cross language Interface.
First describing a project abstract of any specific language, platform or environment helps to identify & then slash key production costs.
The most important software development costs to contain are those associated with expected changes in your platform. i.e. Your wiget cost.
Language independent design? Language agnostic design specification? Environment agnostic? There must be a good name for this missing step!
This is a fantastic article - what a great idea! Thirteen ways of looking at a turtle disq.us/9rd2b7
The hand code for a project of virtually any size, should be written atop a mountain of derived code. #DerivativeCode (#GeneratedCode)
Today, the primary language of most "software specifications" is English. Tomorrow it will be XML. #DerivativeCode #AtAnAbstractLevel
If m + i = c is a viable approach to software development, then github should be full of instructions rather than content ("source code").
Instructions (the i in m+i=c) by contrast are an efficient, concise, reusable, flexible, dynamic description of the problem. #derivativecode
United States الاتجاهات
- 1. Carson Beck 12.9K posts
- 2. Ohtani 67.6K posts
- 3. Miami 91.7K posts
- 4. Miami 91.7K posts
- 5. Louisville 20.2K posts
- 6. #SmackDown 47.3K posts
- 7. #BostonBlue 5,906 posts
- 8. Jeff Brohm 1,762 posts
- 9. Malachi Toney 2,356 posts
- 10. George Santos 63.4K posts
- 11. Mario Cristobal N/A
- 12. Chris Bell 1,996 posts
- 13. #OPLive 2,208 posts
- 14. Nebraska 13K posts
- 15. Geno 9,303 posts
- 16. 4 INTs N/A
- 17. The U 567K posts
- 18. Raiola 2,304 posts
- 19. Ilja 19.2K posts
- 20. Minnesota 46.4K posts
Something went wrong.
Something went wrong.