3 ms·
Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. Also, they never claimed technical
by jabradoodle 3y ago
Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer.
Also, they never claimed technical superiority of microservices, quote:
> For example, a startup with five engineers may choose a monolithic architecture because it is easier to deploy and doesn’t require their small team to learn multiple programming languages.
- quadrifoliate 3y ago> Also, they never claimed technical superiority of microservices, quote: No, but they are arguing against the strawman of the perceived technical inferiority of monoliths. Look at the title of the article. I am simply calling out that strawman as such. If they wanted to convey the message of "It all depends, use the best architecture for the job", they should reflect that in the title.
- jabradoodle 3y agoMaybe we have radically different experiences, I don't see that as a strawman, the industry as I have seen it largely does view microservices as superior.
- Aeolun 3y ago> Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. That’s weird. Any time I’ve seen anyone let their engineers engineer, those engineers have immediately started following the hype.
- sopooneo 3y agoI have many times seen management hire what they thought were "the best engineers" and let them completely loose for months or years straight to eventually deliver... nothing. Literally nothing. Or at least nothing that actually works in any way.