6 ms·
> What proof would you expect him to bring? Data. Data about software projects. What bugs me most about Fowler is his reception, not his writing. If we take h
by routerl 5y ago
> What proof would you expect him to bring?
Data. Data about software projects.
What bugs me most about Fowler is his reception, not his writing. If we take his writing in the spirit you've outlined (an experienced developer sharing his anecdotes), there's no problem. But that just isn't how he's seen in the industry. There is a whole class of developers who take his writings as gospel, without the critical sense to wonder whether Fowler's experience/insight actually matches the project at hand.
- JamesBarney 5y agoWhat data? Each project is building a different product with a different team. Even if he had data like "Teams that use monoliths complete there projects 20% faster", it'd still be useless because of the confounds. But let imagine through some miracle he did have data that conclusively proved 75% of the time it was better to build a monolith. This might suggest you should more seriously consider building a monolith first, but still this doesn't make the decision for your project. You have to decide based on your project, teams, goals, and budget if a microservice is right for you. I think you're 100% right that it's the reception. Our industry is filled with people who take the practice of software as a matter of dogma. But we do that with everything, we'll turn any technique into a cult TDD, microservices, unit testing, immutability, functional programming, BDD, etc..
- scintill76 5y agoIf he provided the data you think he lacks, you could still complain about architects who didn’t apply “critical sense” to see whether their project’s data matched his projects’.