3 ms·
I wouldn't say that boring solutions are always the best, unless they satisfied the conditions below. Here's what is REALLY important: A) How fast can you get
by weixiyen 13y ago
I wouldn't say that boring solutions are always the best, unless they satisfied the conditions below.
Here's what is REALLY important:
A) How fast can you get your first product in front of customers?
B) How often can you measure and iterate on that and get the new version in front of customers.
You should pick the best solution that optimizes for A & B. Both are really important because they will help you discover the actual thing you need to be building.
- collyw 13y agoI am involved in an ongoing discussion at work. The guys implementing the project want to go with a NoSQL / Angular / Node solution. I see a relational database as being a better fit. "Its so fast, even running on my laptop" "you only have 3Gb of data just now" "Its so quick to develop, just plug Angular straight into elsaticsearch, no schema,..." The thing is, I just see lots of problems stored up for the future. Sure you have to define a schema up front if you go for a relational database, but changing it isn't such a big deal, not until you are in production with live data. Sure you might save time up front, but you are essentially cutting corners to achieve this, and storing work for the future.