The Majestic Pseudo-Monolith

Nice! In terms of switching between different editors - I use Command+` for that. I usually have UI and API open, and switching between those 2 is as easy as pressing that hotkey. Don't have to muck around with Command+Tab.

In terms of running 2 things at once, I prefer apple scripts - I have a script which opens up a bunch of iTerm tabs with all the watchers I need.

All in all, nice setup, good job! Always interesting to see how other peeps organise that stuff.

A boilerplate doesn't get updated and so practically ensures that your components will drift out of sync. Far better to use a library (if your build system doesn't support that, get a better one - plenty of "backend" build systems integrate npm or yarn).

And if you only have one repo and you often edit multiple components at the same time, maybe consider making it an actual monolith?

Really enjoyed your article! I usually write my API's in Go and always reach for NextJS for my front-ends. How you handle things like authorization and authentication?

I don't see how this has anything to do with a monolith (in the sense of the monolith vs. microservices approaches).

It's not really front page material either (IMO), it's just a basic article about placing frontend and backend code in the same repo and making a script to run both locally.

It doesn't even tackle any interesting problems like handling the separate needs of both codebases in the CI scripts, nor it gets much out of bundling the two together except for opening them in the same editor - which is somewhat conflated with it being a monorepo? (you could simply open a parent folder with two different codebases inside and achieve pretty much the same).