2,133 karma · joined June 13, 2008
67K flT7c.jpg
558K flT7c.png
Once those JPGs make it across the network and arrive on the device, we're stuck with plain old CGImages, right?http://www.kihongames.com/blog/labs/2011/04/labs-pvrtc-power...
Some highlights from the article:
- "Avoid using PVRTC when you have static images that are the focus of your content" - "images are 2-4x larger, but memory use is less" - "amazing memory improvement, but no real change in performance" - "textures must be power of two"
It probably doesn't fit my use case, but it's fascinating.
Someday I'll write up the story about the time we met in person. Yes, I too got yelled at by Steve Jobs.
http://www.geekwire.com/2011/hawaiian-beach-vacation-hell-sp...
This behavior on the part of HomeAway (VRBO) is really a natural consequence of their business model. When the property manager is your only customer, it doesn't make sense to post negative reviews.
We're doing things differently at Dwellable, of course.
Hot tips for crawling data:
- Cache pages locally while you work on the indexing
- Nokogiri is awesome
- Don't be afraid to use regular expressions
- Initially, put data into a spreadsheet (not the db).
That way it can be checked in and diffed.
I also have a lot of subtle tricks for cleaning up messy data. For example, to see if two similar authors refer to the same person, I have a method that converts an author name to an author key. The key is just like the name, only it's been uppercased, apostrophes removed, etc. Plus weird stuff like this: # replace all vowels with the letter E
s = s.gsub(/[AEIOUY]+/, "E")
It's little things like this hack that make a big difference in data quality.(edit: formatting)
http://www.geekwire.com/2011/hunger-science-fiction-books-sp...
Also, thanks to webwright for the title suggestion.
It was just too complicated, though. Most people don't even understand what "coinsurance" is. I might add some pretty calculators later if the site gets some traffic.
Of course, they can still mess with you and they won't hesitate to do so if they think they can't make money at this price. There's no way to find out the final rate without completing the entire application process. In that respect it's similar to auto insurance.
PickHealthInsurance still has a lot of utility compared to existing sites, though.
You can get often get the advertised rates, but not always. In Washington State for example, you can get these rates if you're running out of COBRA and you've been covered continuously. They aren't allowed to ask questions.
I don't think there's a magic bullet, unfortunately. Suggestions welcome.
I put this together over a few weekends. My COBRA is about to run out and I found it exceptionally difficult to compare plans and prices with the existing sites. This is the third time I've had to buy individual insurance and I finally decided to do something about it.
Things crystallized for me when I almost bought a plan that claimed to cover maternity, only to discover late in the game that it had a separate $20,000 maternity deductible! What a mess!
I have a few goals with PickHealthInsurance:
- start showing approximate rates almost immediately, don't pester me with a bunch of questions
- explain confusing terms like "coinsurance" and point out the difference between a PPO and a POS.
- show plan stats up front, not buried deep within the bowels of the application process
- make it easy to use and blazingly fast
Built with:
- Rails 3.1 (HAML, Sass, Coffeescript)
- Twitter Bootstrap CSS
- Deployed on Heroku/MongoHQ
What do you think?
user "admin"
ruby "1.9.2"
apt "deb http://downloads-distro.mongodb.org/repo/ubuntu-upstart dist 10gen", :key => "7F0CAB10"
role :app, :packages => [:memcached]
role :db, :packages => [:mongodb-10gen]
server "server_app1", :role => :app
server "server_db1", :role => :db
packages [:atop, :emacs, :gcc]
More details on github. Feedback welcome!"Waiting for indexes to build takes approximately as long as it takes AWS engineers to fix EBS issues."
The first system to fall over was our message-queue that talks to LinkedIn for logins and refreshes. I had to spin up a separate machine at Rackspace just to help logins along. Hopefully that'll hold things steady for a bit.
Resto duel is an interesting idea. Ethan (from Urbanspoon) actually mocked this up at one point but we thought it was kinda lame. The results just weren't that compelling, sadly.