When Walker put the objects, along with their accompanying stories, up for sale on eBay, the results were astonishing. On average, the value of the objects rose 2,700%. That’s not a typo: 2,700%. A miniature jar of mayonnaise he had purchased for less than a dollar sold for $51.00. A cracked ceramic horse head purchased for $1.29 sold for $46.00. The value of these formerly abandoned or forsaken objects suddenly and mysteriously skyrocketed when they were accompanied by a story.
Spreedly is one of my favorite companies because they’ve solved the problem of payment processor lock-in for my business. Their service is a very affordable, independent payment information “vault” — a secure, PCI-DSS compliant place to store customers’ data, and later charge it using whatever payment processor I want.
Spreedly is built for developers — it is a set of APIs that my software can communicate with to store payment information or tell Spreedly to do things with it, like charging some amount or deleting some information when a customer cancels their subscription. There’s no way to look at what’s been stored in an account other than writing code. That’s why I created Vault Viewer, a small PHP application that lets you look into your account and see, search and delete your stored payment gateways, payment methods and transactions.
The code is open source and free to use, and installation is typically just a matter of dropping the whole thing into a web server document root configured to serve PHP. There’s a Live Demo Here if you’d like to try before installing. I recommend only using the demo if your account only contains test data, as it’s not on an SSL-secured domain.
My date range picker component for Twitter Bootstrap has been updated with the much-requested ability to choose times as well. You could use it in an app to schedule meetings, choose flight departure/arrival times, etc. Enjoy.
P.S. Yes, it works with the upcoming Bootstrap 3 as well.
The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality.
His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: 50 pounds of pots rated an “A”, 40 pounds a “B”, and so on.
Those being graded on “quality”, however, needed to produce only one pot — albeit a perfect one — to get an “A”.
Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity.
It seems that while the “quantity” group was busily churning out piles of work-and learning from their mistakes — the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.
For many, many years, Gary Keith maintained a set of files (“the files”) as part of the Browser Capabilities Project. These files contained thousands of entries mapping regular expressions to browser families, versions, platforms and capabilities, and these files were used by parsers written in a dozen languages to turn website visitors’ user-agent strings into structured data about their system. I’m truly thankful for the hard work Gary put in maintaining those files single-handedly for so many years.
At the end of 2012, after many months of warnings about his health and declining ability to run the project, it was closed with no new maintainer. Nobody’s stepped up to provide the same level of support he provided, and it’s no longer a reliable source of information about browsers and their capabilities.
If, like me, you need the ability to parse user agents for browser and platform information, I recommend the ua-parser project. It’s up-to-date, with a team of contributors, takes pull requests on github and provides libraries in 10 languages. It’s also much simpler to maintain, with only 1000 lines of YAML rather than 28,000 lines of INI files.
I’ll be using ua-parser as the basis of W3Counter’s browser and platform reports going forward.
Sunroom, wall-to-wall sliding windows, fold-up table. The Surface Pro comes with me when I go out for server emergencies..