I'll second this.
I'll second this. I have built a lot of ideas and prototypes over the last year or two. I used to spend a lot of time focusing on the architecture design of these things, building in microservices using the latest technology wherever possible. I figured this was the best way to go about it, until the day I realized I was spending 50% of my time trying to set up a distributed microservices environment, 40% of my time fighting with the tools I was trying to use to build my prototype, and 10% of my time actually building my prototype. This is the biggest problem with trying to scale too early - you take the focus away from your product. The reality is that most businesses will not work out. Instead of focusing on scaling something that may never sell, you should use the tools that allow you to iterate on your product as quickly as possible - where reasonable. As stated above, if you end up needing to grow the business, all the code will eventually be rewritten. The data, however, will likely be much more expensive to change. Put some time into thinking about your data model, but otherwise focus on building your product.
Posted by cmorelli on Jun 13, 2015, 9:07 PM
Tags
Related issues
- Not at all, actually.
- A car battery with reduced range is still perfectly useable as a storage battery for a PV system.
- Here in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
- You should do some basic research yourself.
- Well, actually not.
- I have a 2022 mini that I use constantly.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments
pricing (Other)
Not at all, actually.
NewA car battery with reduced range is still perfectly useable as a storage battery for a PV system.
NewHere in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
NewYou should do some basic research yourself.
NewWell, actually not.
NewI have a 2022 mini that I use constantly.
Two observation: 1.
Cautiously optimistic for them.
I'll second this.
I'll second this. I have built a lot of ideas and prototypes over the last year or two. I used to spend a lot of time focusing on the architecture design of these things, building in microservices using the latest technology wherever possible. I figured this was the best way to go about it, until the day I realized I was spending 50% of my time trying to set up a distributed microservices environment, 40% of my time fighting with the tools I was trying to use to build my prototype, and 10% of my time actually building my prototype. This is the biggest problem with trying to scale too early - you take the focus away from your product. The reality is that most businesses will not work out. Instead of focusing on scaling something that may never sell, you should use the tools that allow you to iterate on your product as quickly as possible - where reasonable. As stated above, if you end up needing to grow the business, all the code will eventually be rewritten. The data, however, will likely be much more expensive to change. Put some time into thinking about your data model, but otherwise focus on building your product.
Comments (0)
No comments yet. Start the discussion.