Here is a list of topics I’m going to write about in the next few months. If you want to add something here, please submit a pull request.

When should you implement more than one interface instead of using a decorator?

Support principles. Free, Paid, Fast, Slow, Open Source, Commercial. What’s the right approach that everyone should adopt?

Does Enterprise Messaging have a future and can anything be done to simplify EAI?

To what extent should people think for themselves?

Good vs bad people:

Design bubble

How much OOP is in Kotlin?

Fluent interface and OOP:

Serialize/deserialize and OOP:

How to do risk management right

Why do we need interfaces if we have PowerMock?

How to implement data layer in OOP

Data structures, sorting, and OOP:

Prototype-based inheritance



Object composition vs function composition

Biggest mistakes architects make

Technical democracy - how to make decisions with multiple opinions

Equality is a perfect way to ruin a software team

Bigger ORM example:

Example of properly architectured projects/proper architecture with pictures.

Word about a distributed systems, how should they communicate with each other (should it be RPC-over-something or message passing or whatever).

How to be an Architect in a Scrum team. Since there is no architect role in Scrum, who will handle the long term goals/system-level consistency of the modules, examining the risks while introducing a system level change in the product, etc.?

sixnines availability badge   GitHub stars