As a tech guy, I love to discuss technologies. And as discussions go, it’s generally the comparison kind: JVM vs. Net, Java vs. Kotlin, Go vs. Rust, Maven vs. the unspeakable one, etc. However, it’s too easy to fall into the quagmire of the merits and flaws of our beloved toys, talk about them for hours, and not reach a satisfactory agreement.

A couple of years ago, I worked as a “Solution Architect”. The job has different titles, e.g., Solution Designer, and Solution Engineer, but the goal is always the same: find the “best” solution for a problem, most of the time, a business problem.