bjpless | 13 years ago | on: Denial, anger, bargaining, depression, & acceptance: The A/B testing lifecycle.
thanks thenomad. There's a funny disconnect between the rational, detached self and the insane subconscious self present in most people.
bjpless's comments
bjpless | 13 years ago | on: Denial, anger, bargaining, depression, & acceptance: The A/B testing lifecycle.
For our logged in user A/B testing (often relating to email), we've built an in-house solution that uses a MOD based system to track group performance (as opposed to storing each group member in our databases).
Pretty clever implementation by the data scientist on our team.
bjpless | 13 years ago | on: Denial, anger, bargaining, depression, & acceptance: The A/B testing lifecycle.
We're currently using Google Content Experiments. The Pros are that it's incredibly easy to get a test started thanks to the presence of Google Analytics scripts in the rest of the website. The major Con is the lack of true multivariate testing.
We experimented with Optimizely but had a bad experience. It seemed as though their javascript was synchronous and blocking. We may have been able to customize that but did not dig deeper.
bjpless | 13 years ago | on: Denial, anger, bargaining, depression, & acceptance: The A/B testing lifecycle.
What is the most frustrating A/B test that you've run?
bjpless | 13 years ago | on: How I Taught Myself Python/Django in 8 Weekends
Very well said.
bjpless | 14 years ago | on: Zaarly swaps anonymity for identity in refreshed mobile marketplace
Still not addressing the chicken or egg problem. I won't use your service until you properly vet workers. Reputation screening requires a lot of transactions.
Task Rabbit has sacrificed short term growth (most likely) to install an incredibly rigorous screening process for their workers.
bjpless | 14 years ago | on: How to Add Django Database Caching in 5 Minutes
Your point is well taken; however, as the writer of the article, I'd say this. Our business requirements dictate that slightly inconsistent data is acceptable in certain circumstances. We would not retrieve objects through the caching flow in situations where absolute data integrity is required.
That points makes all the difference, in my mind. To your point about excessive invalidation, that depends on your Read/Write workload.
bjpless | 14 years ago | on: How to Add Django Database Caching in 5 Minutes
This is an interesting approach. I'm definitely going to check it out. Thanks!
bjpless | 14 years ago | on: How to Add Django Database Caching in 5 Minutes
MySQL does already automatically cache queries internally. However, the scale of that caching is limited, in part because it's difficult to scale MySQL horizontally in the same way as Memcached or other distributed caching systems.
Adding read slaves is a great on many levels. Adding slaves, however, is not without overhead and stale data/programming complexity exists there too.
page 4