4 ms·
Serverless, OOP, functional programming, domain driven design, monoliths, microservices, server side rendering, etc... . All have their different upsides and d
by c048 3y ago
Serverless, OOP, functional programming, domain driven design, monoliths, microservices, server side rendering, etc... .
All have their different upsides and downsides. But the past 10 years as a software developer has taught me one thing above all; I'm sick and tired of every paradigm shift being sold as a silver bullet.
There. Are. NO. Silver. Bullets.
If you look up ideas or methodologies and they never present both upsides and downsides they tend to either posses limited knowledge on the subject matter or they're trying to sell you their idea.
I still remember a meeting with all senior devs at a large client about pitching microservices deployed on kubernetes. I was the only one to state that we'd be shifting complexity and not eliminating it. My remark was voted to be removed from the report, because it sounded too negative.
Years later, and hearing how terrible it turned out, I'm still shaking my head.
- pjmlp 3y agoFashion driven industry. The best technical skill any senior can have, is to get a feeling when to ignore fashion, and when to actually pay attention to fashion that stays around.
- JackMorgan 3y agoIt's true that sometimes fashionable skills stick around. I think of all my past coworkers that dismissed: git, CI, repository branches, unit and integration tests, code review, local development databases, automated deployment, automated migrations, separating display logic from business logic, putting comments in git commits instead of in code comments, and removing secrets from code. Almost two decades later most is these are taken for granted in mature teams. On the other hand, some tools and techniques are on a continuum: microservices/monoliths, thick/thin UI clients, schema/schemaless databases, SQL/ORMs, strong+static/weak+dynamic types. A team needs to carefully consider their project to determine what fits best (and it might change over time). None of these are "always the right choice." We have very little science about how to accurately determine the needs of a project, so we get a lot of hearsay and fashion.
- chrisandchris 3y agoTo quote from the post: > The Correct Way [(tm)] To many people today believe that their way is the only way. But sometimes the boring technology is way better than the latest stuff. Bot to say that boring tech is always better, but asking the question "Wouldn't ... be enough?" is a valid question - and the answer "no" is also valid to it.