7 ms·
I would also recommend just going for something boring and fast (for you the developer). It's a poc, the only thing that matters is getting it out the door. In
by onemiketwelve 5y ago
I would also recommend just going for something boring and fast (for you the developer).
It's a poc, the only thing that matters is getting it out the door. In fact code might not even be necessary for a poc.
If this were me, I would dig up my last abandoned monolith with all the boring details like routing, migrations, seeding, auth all figured out, rip out the old code and start from there.
- aloisdg 5y agoAll my poc are in vanillajs. Quick and dirty.
- dnautics 5y ago> that can scale for a few years I don't think "boring and fast" is the only consideration you should take. You should also consider: "are you going to be able to read your code without wanting to tableflip after a year?"
- jaybrendansmith 5y agoThis is the best answer. Don't just build what you know, use something you've already built (if you have it.) Maybe upgrade to the latest, first. And also: If you are trying to create a new business, go as boring as possible. Do you want to experiment with technology, or with business logic? Decide this up-front and if its business logic, go with boring, stable, mature, steady, proven. You can always create experimental services once the boring monolith business takes off.