Lots of great stuff, some of which I am still don't follow completely, but should.
But two things I don't agree belong here:
SSR vs SPA: there are excellent established clientside frameworks today.
It's not that you will need a big overhaul if you start with code you can't port to the clientside and couple frontend and backend code. (You will tho :v)
It's that for some people/teams SPA is just as fast if not faster to develop than a server-rendered application/site.
Monolith vs monorepo: you say not to do microservices, but really what you mean is that you don't need to have independently versioned deployables with api boundaries at the beginning. You can still benefit from having separate deployable units, such as keeping authentication or emailing out of application server.
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.
Lots of great stuff, some of which I am still don't follow completely, but should.
But two things I don't agree belong here:
SSR vs SPA: there are excellent established clientside frameworks today.
It's not that you will need a big overhaul if you start with code you can't port to the clientside and couple frontend and backend code. (You will tho :v)
It's that for some people/teams SPA is just as fast if not faster to develop than a server-rendered application/site.
Monolith vs monorepo: you say not to do microservices, but really what you mean is that you don't need to have independently versioned deployables with api boundaries at the beginning. You can still benefit from having separate deployable units, such as keeping authentication or emailing out of application server.