273 karma · joined October 10, 2009
What I think is really cool is that all this stuff is coming. There are a lot of stakeholders deeply invested in seeing these ideas come to fruition.
To the future! Cheers.
I agree, the whole concept of a cloud-based music library is very new. Forget music, the concept of the cloud is new! I'm looking forward to a holiday filled with questions like, "where is it, who owns it, is it secure?"
Once people are comfortable with the paradigm shift, will really be cooking with gas.
I think humans can make better decisions with data. Play Strength attempts to expose insights already locked inside your music library.
For example, one of the big changes in driving some hybrid vehicles is a real-time monitor of how power is flowing in and out of the battery. I think just seeing that data changes your driving habits.
That's what I was going for with Play Strength. Thanks for sharing your thoughts.
@JimEngland, you use stars purely as an organizational tool, which is slick. It's cool that the iTunes interface extends it self to different uses.
@tkahnoski and @zeedog, how would you elegantly expose controls for those different feelings?
Speaking for ourselves, we've historically preferred to have someone else manage our infrastructure. Setting up Redis is fairly trivial, I agree. However, setting up a secure machine out on the internet and making sure it's always there is less trivial. Rather than juggle an ops/engineer role, we just double down on engineering. I'm sure at some point this may need to change. Hopefully, when that day comes we can afford a sysadmin!
Appreciate the time and thoughtful response.
Our API is a Rails project and though we do a lot of work that's "off the rails," so to speak, we do try to follow a convention where possible. A convention that's worked well for us is to use Postgres only for database-backed models in the app. So when it came time to solve this problem, Redis seemed like a good choice.
Map/reduce isn't an option here. First, it's too slow. Second, it's asynchronous by nature, which doesn't work well when trying to load a webpage. We did consider using it in the background, however, to generate the counter-caches.
Thanks for reading!
On a related note, it feels good to know that everything our app needs to run is in the code base. Back in my C# days, I remember relying on stored procedures that were configured manually at the database level. Rails fights that with migrations and the callback chain too, so I guess that thinking has sunk in for me.
Thanks for the comment.
http://blog.sqoot.com/we-can-do-better-an-apology-from-sqoot
http://blog.sqoot.com/we-can-do-better-an-apology-from-sqoot
As @alexmturnbull suggests, the equation is a little different when your scope is large just to be a contender in a space.
It's critical that it not slow down our site, so I'll keep an eye out for performance issues.
Feel free to hit me up directly for more feedback. avand at avandamiri dot com.
Name will definitely be changing so watch out for that.
The design is also going to get a serious overhaul in the next few weeks, so watch out for that, too :)
Check out the feedback tab for some info. About us coming soon.
Twitter login coming soon.