January 25, 2022
Let's get logical! On logical and physical architectural views
Having a deep understanding of the differences between physical and logical boundaries can help shed light on the way we architect systems. Usually, it leads to simpler solutions.
We're too stressed about (vendor) lock-in
Developers and managers are worried about (vendor) lock-in. They build castles of cards in a vain attempt to work around what they perceive as a problem. Is this a different form of over-engineering?
I'm lazy, I have a checklist for everything
I don't want to waste brain cycles to remember things that aren't worth remembering. To-do lists and checklists are a much better approach. They help me not to forget things, and simultaneously, they free up my brainpower for more important matters.
Is it complex? Break it down!
Sometimes, we choose technology based on the perceived complexity or heaviness. We focus our decisions on the technical solutions and rather than looking deeper at the problems, we stick with what we know. Are we making the right choices?
Do I still need a smart watch?
I feel misplaced sometimes. People around me, apparently, happily buy a lot of things I find completely useless. Every time I look at my wish list I only find good reasons to not buy something. Am I missing something crucial? What do I really need?
You don't need that abstraction
Abstractions, abstractions everywhere! We're obsessed with clean design and architecture. Do we need that, or does the introduced cognitive load come with more issues than benefits?
Continuous integration: are pull requests bad?
There are continuous integration advocates and pull requests evangelists. They both present valid arguments to sustain their thesis. Is there a different point of view we should be considering before choosing one style or the other?