Tales from Dev
The ambiguity of architecture decision records
The knowledge gravity problem
The ambiguity, the curse and the fallacy of domain model
Time, angle and depth: dimensions in software design
Easy will make you dizzy?
Tools make fools?
WTF are you talking about? Acronyms, jargon and abbreviations
Composing a PIE
Functions, objects, actors: deliverying results
Evolve, don't hack
Context Segregation Principle
The ambiguity of problems
Functions (and facts) describe the world
Abstracting over people
The ambiguity of objects
Representing knowledge: what, how and why
The ambiguity of team work
The ambiguity of application
Dogmatic engineers and a product
Map, don't ask
The law of eventual composition
The ambiguity of code
The ambiguity of interfaces
Inverse Bruce Lee maneuver
Systems: by, with, for people
Psst, wanna solid options?
From concepts to architecture
FSM - Functional State Machines
Common words of the shared apocalypse
Easy becomes complex
Simple isn't easy
The ambiguity of composition
The ambiguity of software architecture
The ambiguity of documentation
New tools, old rules
Concepts, Entities, Data
How do errors evolve?
I, interface
Overdebugging
Concept maps
Rethinking "missingness"
Modularity Uncertainty Heuristic
"Solution-Probleming"
I don't know
Modeling Maturity Levels
The ambiguity of encapsulation
A solid grasp of responsibility
Slow down
Bool considered harmful?
Many faces of DDD Aggregates in F#
The ambiguity of abstraction
The cost of modeling
(Fr)Agile
Language of the problem
"Microoffices" vs "Officeolith"
Software Engineering for busy parents
The value of Value Objects
Feature toggling as a design tool?
"The ambiguity" of TDD
"Organization-Driven Design"
Modeling Value Objects in TypeScript
Conversation-Driven Design
Essentially bounded, Accidentally unlimited
Where did my methods go?
Hello world!