2 posts tagged with "software engineering"

The debates from 2015 are back.

Microservices v/s Monolith.
Server v/s serverless.
Stateless v/s Stateful
No-SQL v/s SQL
Screwdriver v/s Hammer
Bread v/s Cake

These arguments have become the equivalent of a wrestling match in the software engineering world, where the last man standing gets the privilege to write code his way. And, of course, we all know that the only way to code is their way, right?

While we're engrossed in these seemingly infinite debates, guess what we're not doing? You've nailed it. We're not paying attention to the real craftsmanship of software engineering. Who cares about creating effective, sustainable, and scalable software solutions when we can spend our time arguing about whether or not to use microservices?

Have you ever encountered a situation where a leader uses Socratic questioning on the wrong audience? For example, asking a PHP developer why users are complaining about high cloud bills or questioning a backend engineer about a low website score on search engines. In the realm of software engineering, it's important to understand the distinctions between software engineers and software developers.

While there may not be a concrete difference, tech leaders should be aware of the nuances between these roles, especially when engaging in Socratic questioning. In this article, we will delve into their primary differences, explore situations where one role may not efficiently perform the other's responsibilities, and discuss the importance of organizations differentiating these roles and aligning them with platform and feature development.