i frequently compare workaday web-dev to general contracting (a favorable description from my perspective). no issues with the article title.
here's my issue with the article text: it describes
I came to the Graide Network and immediately started breaking our legacy app into microservices.
as "overengineering," and perhaps it was ... or perhaps it was just not-great planning. after all, the premise of the article is that the microservices are now incurring costs that can be described more like plumbing than engineering.
here's where some of my experience partially aligns with the article's complaints
Investors are guilty of pushing it on us
this has happened to CEOs at startups i've been at: [some] investors asked for diagrams, etc., and
we made decisions to build invisible fanciness instead of product for users.
here's where the author begins upon the path to enlightenment
we can build more with less
here's my issue with the article text: it describes
as "overengineering," and perhaps it was ... or perhaps it was just not-great planning. after all, the premise of the article is that the microservices are now incurring costs that can be described more like plumbing than engineering.here's where some of my experience partially aligns with the article's complaints
this has happened to CEOs at startups i've been at: [some] investors asked for diagrams, etc., and we made decisions to build invisible fanciness instead of product for users.here's where the author begins upon the path to enlightenment