3 ms·
I didn't think this would necessarily be HN material so I didn't bother submitting it, but apparently someone disagrees with me. I figured I had to "profession
by patio11 17y ago
I didn't think this would necessarily be HN material so I didn't bother submitting it, but apparently someone disagrees with me.
I figured I had to "professionalize" A/Bingo a bit because recently from reading my email I get the impression that it is looking less like the 10% time project from my 10% time project and more like "Oh, effity, if this breaks businesses with employees start losing money." So I did a bit of code cleanup, wrote some tests, and created a versioning plan so that folks depending on it are not totally on their own for evaluating whether a particular commit will break stuff if they pull it in.
Since I had the opportunity I also made some changes to the user experience, such as decreasing the amount of code you have to write even further, and incorporating the Minimum Viable Dashboard.
If you aren't A/B testing yet, I want to change that. Tell me what I need to do to make it happen.
- stakent 17y agoI'm this "someone". Why? Because I believe your "If you aren't A/B testing yet, I want to change that." is beneficial for significant part of HN'ers.
- dlib 17y agoI'm going to have a look at this in a few weeks. I only knew about Vanity so I'm glad I came across this post. Does A/Bingo also auto-select an alternative if there is a 95% reliability that it's better?
- patio11 17y agoNo, it does not. Vanity and A/Bingo have some fundamentally different takes on the problem. This is totally fine -- there are a lot of good ways to do A/B testing just like there are a lot of good ways to parse an HTML document. Use whichever fits your needs. I'm happy to answer specific implementation questions, but the bumper sticker version is "In general, Vanity wants to be your one-stop measurement shop. A/Bingo wants to make A/B testing so easy you do it automatically, every single time."
- michael_dorfman 17y agoHow about "A/Bingo vs Google Website Optimizer"? What's the bumper sticker on that comparison?
- patio11 17y agoA/Bingo: Written by programmers, for programmers. GWO: written by an advertising company, to be used by non-technical stakeholders in marketing. GWO makes significant compromises on usability -- both for the site's programmers and the site's users. Previously I recommended it only very hesitatingly, to non-technical marketer types. These days Visual Website Optimizer exists and it is embarrassingly better in every possible way for that audience, including the WYSIWYG interface. You can read my thoughts on GWO at length in the A/Bingo documentation. http://www.bingocardcreator.com/abingo/compare http://www.bingocardcreator.com/abingo/compare
- paraschopra 17y agoThanks for recommending http://visualwebsiteoptimizer.com/ http://visualwebsiteoptimizer.com/ It exists to make A/B and Multivariate testing dead-simple for non-technical types :)
- dminor 17y agoMost of your technical arguments against GWO are obviated by using their multivariate version.
- ehsanul 17y agoWould this work in a non-Rails project? Say Sinatra?
- patio11 17y agoAs written there is an ActiveRecord dependency, and it depends on code implementing the general contract of ActiveSupport::Cache::Store for proper operation. However, if you've got a day or two to kill, you could probably fix that. After that you'll have to rebuild the dashboard. I'm not sure how Sinatra handles the view layer typically but you may need to redo the syntax sugar for it, as I think my implementation probably depends on ActiveView magic.