I changed my mind after years of mentally not supporting TypeScript 😈

Programming is not the most essential part of the development process, but the collaboration is.

Pretending it is not exposes your client’s system to the unpredictability of the world’s reality.

I'll do a small revision of the SOLID pronciples, shifting it more towards high-level components.

DRY (Don't Repeat Yourself) WET (Write Everything Twice)

Software development, in a nutshell, is about coupling management.

very system you develop is distributed. Pretending it is not exposes your client’s system to the unpredictability of the world’s reality.

Yesterday, I wrote about magic components 🥩🥕 consisting of most of the patterns, approaches, strategies, processes and workshop methodologies.

If "Hexagonal Architecture" were changed to "Hexagonal Implementation", it would be much less confusing, IMHO.

I faced moments of feeling lost, confused, futile and frustrated as I navigated through a myriad of methodologies, patterns, processes, and workshop tools. It was overwhelming at times, but I realised that it was all part of the journey.

I temporarily joined a team working with a modular monolith and single database. This is the most common case in our software house, and I believe it's the best way to start many projects.

An Archetype is a defined solution to a business problem. The Time Availability answers the question: Can I schedule resource X between D1 and D2?

If you do THAT, THEN YOU DO IT WRONG!

My thoughts on how we can help ourselves to successfully deliver the MVP on the market.

The common language for healthcare data exchange

Have you ever gotten stuck with your task because of a change introduced by another developer in a completely separate service?