3 ms·
That presumes a project starts with people who intend to charge from the get-go, but defer that step to later. Rather than being started by folks who love what
by TheRealPomax 7y ago
That presumes a project starts with people who intend to charge from the get-go, but defer that step to later. Rather than being started by folks who love what they're doing, getting funneled into a PM'ed project where the enthusiasm is curbed by "product viability", and then goes through a period of a few years where the original project folks rotate out until no one left is invested in how useful the product is, and a lot of folks are invested in how much money can be made by pivoting to a model that heavily monetizes on scoping down to purely the most used features used by its biggest, financially secure customers.
- takeda 7y agoThat reminded me of a project where person leading it estimated that it will be cheaper and faster to use AWS, they only forgot all the hidden fees that AWS adds, most commonly the network fees (which are charged between AZs) or EBS etc. On top of that an instance that claims to have specific parameters won't deliver the same performance as supposedly equivalent physical machine, so you will need to use bigger instances etc. Ultimately the project did not have resources to set up DR version which was originally planned and still went way over the budget.