3 ms·
"We should have built the absolute minimum and then manually maintained transactions through the backend if need be. To hell with formality. We were in the busi
by jakejake 12y ago
"We should have built the absolute minimum and then manually maintained transactions through the backend if need be. To hell with formality. We were in the business of proving a hypothesis yet we acted as if it had already been proven"
We do this at my company when we add a new feature that we are not sure will take off. You can get something running quickly that looks good enough to the customer, but behind the scenes is all smoke and mirrors. Then if the amount of traffic starts to grow you start putting in your automation.
It's really hard to resist the urge to build out all of your automation, scaling, etc up front. But, most of the time the new feature goes unused and it winds up being a waste of time.
- untog 12y agoThis is where client-side A/B testing frameworks can be really useful, but people get all huffy about it. Inject some custom HTML onto your page! Yes, it looks a little ugly when you look at it closely, but 95% of your customers won't. It'll prove a hypothesis very, very quickly.