Posts
-
Recursive Design, Iterative Design By Example
-
Various Playlists
-
Grasem Tool
-
Glue Tool
-
DI - Design Intent
-
Compiling Diagrams
-
Two Syntaxes For Every Programming Language
-
Syntax Primitives
-
S/SL - Syntax Semantic Language
-
SCN
-
Random Anecdotes
-
Notation vs. DSLs and PLs
-
Notation Example
-
ASON Notation Pipeline (building 7 passes)
-
What if making a compiler was easy?
-
Kill math
-
Meta Programming
-
Recursive design knowns and unknowns
-
Projectional editing
-
Peg cheat sheet
-
Crass simplifications
-
State, analysis of
-
Simplicity vs complexity
-
Programming redux
-
Mathematics redux
-
Scls little languages playlist
-
Patterns
-
Message passing
-
Cps considered to be a goto
-
Bootstrapping
-
Svg to code (1)
-
Regex vs peg
-
Glue manual
-
Programming paradigms vs syntax
-
Everything is a fractal
-
Breaking free of the cell paradigm
-
Racket peg
-
The rain god
-
The f**k program
-
Testing
-
Toe for software development
-
Little language
-
Learning about compilers quickly
-
How to design an scl
-
Divide and conquer in pls
-
Peg vs. other pattern matchers
-
Details kill
-
Asking the right questions
-
Apl
-
Component diagrams
-
Triples
-
Toolbox languages
-
Need to know
-
Indirect calls
-
Architectural archaelogy
-
Svg grammar
-
Toolbox languages
-
How many inputs vs how many outputs?
-
Dynamic anything is bad
-
Divide and conquer yagni
-
Components (again)
-
Universal datatype
-
Programming language design
-
Dataless programming language
-
Scheme to javascript
-
Fractal design
-
Dsl in a day
-
State machines to javascript
-
Statecharts (again)
-
The stack is a global variable (again)
-
Processes are state machines
-
Superposition 2
-
Compiling diagrams 2
-
Blocking
-
The case for fanout
-
Curse of the editor
-
Superposition
-
Fbp v actors v erlang
-
One in how many out?
-
Erlang v actors
-
What is programming
-
Factbases
-
Transpiling diagrams to code 101
-
Superposition
-
Pure research vs applied research
-
Html components arrowgrams
-
References
-
Pure research vs applied research
-
Transpiling diagrams to code 101
-
Restricted thinking programming editors
-
Miscellaneous
-
Induction vs recursion
-
Transpiling diagrams overview
-
Architecting, engineering and implementing software
-
Apple® refunded my money because of a bug
-
The problem
-
Sofware kleenex®
-
Software ceiling
-
The primary issue
-
Refactoring
-
The stack 2
-
Peg
-
Compile time and runtime
-
The stack
-
The algol bottleneck
-
Filereader
-
Dlls
-
The stack is a list
-
Concurrency bare bones
-
Concurrency bare bones
-
Software development roles
-
Blockchain overview
-
Anecdote secretary vs. synchrony
-
5 whys of software components
-
5 whys of multiprocessing
-
5 whys of full preemption
-
Sequencing
-
Variable names not needed
-
Type stacks
-
Two syntaxes for every language
-
Two stacks for every type
-
Twenty milliseconds the magic number
-
Statecharts
-
State machine for javascript
-
Shuhari
-
Scanning and parsing overview
-
Scalability
-
Scalability ii
-
Reuse
-
References
-
Ry vs dry
-
Programming languages are skins
-
Programmers vs humans
-
Parsing and compiling diagrams
-
Ohminsmallsteps
-
No Code
-
New Breed hlls
-
Multitasking is easy
-
Mathematics is not reality
-
Javascript concurrency
-
Isolation
-
Introduction
-
Inspiration
-
Html is nocode
-
Html components handling callback logic explicitly
-
Html components arrowgrams
-
Fbp is no Code for banking apps
-
Everything is an interpreter
-
Efficiency
-
Editor for gratoms
-
Divide and conquer
-
Divide and conquer is recursive design
-
Diagram based languages
-
Dsl manifesto
-
Di design intent
-
Concurrency is not parallelism
-
Concurrency is a paradigm
-
Computing then and now
-
Computing then and now ii
-
Complexity
-
Complexity ii
-
Call return spaghetti
-
Box And Arrow dsl for concurrency
-
Anecdote language learning
subscribe via RSS