New tools, old rules

What is the relationship between all three of them?

Concepts, Entities, Data

Compile-time, run-time - what is next in the evolution?

How do errors evolve?

I, interface

Overdebugging

Are we losing something important while getting better tools?

Easy will make you dizzy?

Are we doomed to become "slaves" of tools?

Tools make fools?

WTF are you talking about? Acronyms, jargon and abbreviations

Is there a universal way of composing things?

Composing a PIE

Is there a single way of yielding results?

Functions, objects, actors: deliverying results

Where is the difference between evolving and hacking?

Evolve, don't hack

is there a single unified way of looking at reality?

Context Segregation Principle

The ambiguity of problems

Can everything be modeled with this pair?

Functions (and facts) describe the world

Abstracting over people

The ambiguity of objects

What are the different levels of representing knowledge?

Representing knowledge: what, how and why

The ambiguity of team work

The ambiguity of application

Why is it important to broaden our perspective?

Dogmatic engineers and a product

Map, don't ask

The law of eventual composition

The ambiguity of code

How does need-driven thinking shape the way we design?

The ambiguity of interfaces

Inverse Bruce Lee maneuver

Does a design mean anything without people?

Systems: by, with, for people

Psst, wanna solid options?

Does software architecture depend on the ideas?

From concepts to architecture

What does make state machines functional?

FSM - Functional State Machines

Are there common words that you can share to scare your teammates?

Common words of the shared apocalypse

Easy becomes complex

Why simplicity does not require less but more?

Simple isn't easy

The ambiguity of composition

What do we mean by "software architecture"?

The ambiguity of software architecture

The ambiguity of documentation

Why are we hiding the transformational nature of the problems?

Concept maps

Rethinking "missingness"

Can broken modularity be easily observed and easily fixed at the same time?

Modularity Uncertainty Heuristic

What one could learn from a broken coffee grinder?

"Solution-Probleming"

I don't know

Modeling Maturity Levels

The ambiguity of encapsulation

A solid grasp of responsibility

Slow down

Can bool be considered as non-modeling friendly?

Bool considered harmful?

How could we represent Aggregates, in the tactical DDD sense, using F#?

Many faces of DDD Aggregates in F#

The ambiguity of abstraction

The cost of modeling

(Fr)Agile

Language of the problem

What we can learn from the evolution of a small business?

"Microoffices" vs "Officeolith"

How to keep up with tech when babies are crying?

Software Engineering for busy parents

Is it only about the primitive obsession?

The value of Value Objects

Feature toggling as a design tool?

Why it really matters how you think of your tests?

"The ambiguity" of TDD

Exploring a metaphor about how we can think of software components

"Organization-Driven Design"

Having fun with encapsulation in TypesScript

Modeling Value Objects in TypeScript

The metaphor of how to perceive the system (or its parts) you are building

Conversation-Driven Design

An observation on the missing piece of problem solving

Essentially bounded, Accidentally unlimited

How I discovered Functional Programming and re-discovered Object-Oriented Programming

Where did my methods go?

How to spin up Kubernetes cluster and deploy Graph Neural Network

All Posts

New tools, old rules

Concepts, Entities, Data

How do errors evolve?

I, interface

Overdebugging