Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, career growth, and navigating the AI revolution.
What This Article Covers
This article delves into the often unquestioned paradigm of separation in software development, specifically in web development. It critically examines how practices like double backend layers, microservices, and Redux have become staples, yet may introduce more complexity and inefficiency than they solve.
Questions This Article Answers
- Why might maintaining two backend services be more harmful than beneficial?
- What are the hidden costs associated with microservices, and when are they truly necessary?
- How does Redux exemplify the pitfalls of excessive separation in frontend development?
- What are the common misconceptions about separation as a marker of quality in software engineering?
- How can we identify when the paradigm of separation has been taken too far?
Length and Time
A thought-provoking exploration with practical insights for software developers. Approximately 10 minutes to read.