I can't really completely agree with the article. Having full-stack developer(s) on a project does not lead to a substandard product - but having bad management does.
In an early stage of a product, especially when building an MVP it makes most sense to start with a single full-stack dev.
As you said, it's cheaper and easier to manage project that way. Later down the road, when the product grows it makes sense to hire more specialized people and while the initial full-stack dev moves into a team lead position - for which he/she is perfectly capable because he/she has understanding of the system as a whole.
It's not that hard to do full-stack development, as long as you make right technical decisions and you don't shoot yourself in the foot by trying to use all the hyped up technologies at the moment. Rails app with some jQuery/Stimulus.js sprinkled on top hosted on Heroku will do just fine for an early stage product.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can't really completely agree with the article. Having full-stack developer(s) on a project does not lead to a substandard product - but having bad management does.
In an early stage of a product, especially when building an MVP it makes most sense to start with a single full-stack dev.
As you said, it's cheaper and easier to manage project that way. Later down the road, when the product grows it makes sense to hire more specialized people and while the initial full-stack dev moves into a team lead position - for which he/she is perfectly capable because he/she has understanding of the system as a whole.
It's not that hard to do full-stack development, as long as you make right technical decisions and you don't shoot yourself in the foot by trying to use all the hyped up technologies at the moment. Rails app with some jQuery/Stimulus.js sprinkled on top hosted on Heroku will do just fine for an early stage product.