Interesting process for hiring developers at Treehouse, especially the paid project. If I were looking for a job, I’d definitely appreciate the opportunity to see what sort of work I’d really be doing, but also the opportunity to showcase what I’m capable of beyond what’s possible in a short interview.
Great and funny history of programming languages. A few gems:
1972 - Dennis Ritchie invents a powerful gun that shoots both forward and backward simultaneously. Not satisfied with the number of deaths and permanent maimings from that invention he invents C and Unix.
Great post by Marco Arment on handling customer comments. The bit about pricing complaints especially stood out.
Someone saying they won’t buy at your price is just one data point. Each sale of your appis another data point. If you sell 100 copies of your app and get 3 comments on Twitter from people saying it’s too expensive and they won’t buy it, I’d say you’re doing great.
Your product will never be affordable to everyone (and some of those who can afford it won’t be happy about the price). If you can find enough people who attribute more value to your product than what you charge them for it, you have paying customers and a potentially growing business.
I feel I’ve seen useful cases for certain types of duck wrapping, e.g Google Closure functions that take either a string or an element and getElementById if you gave them a string. If it’s well documented it doesn’t seem that bad?
The best part of this article was the beginning:
Duck-wrapping (verb): If it doesn’t quack like a duck, wrap it in a duck.
It never ceases to amaze me how quickly technology improves. I remember hearing about IBM Roadrunner beating the speed record for supercomputers (it feels not that long ago), and now it’s already obsolete as one?
Interesting categorization of currencies. I was initially pretty skeptical about bitcoin, but I’m getting really curious about how a non-government-based currency (not necessarily Bitcoin) could work long term. I need to find more articles about this.
Cool experiment, using voice commands in the browser. Definitely keen to see where this goes, but it’s Chrome only at the moment (and just a quick experiment to get people thinking). I’m especially interested in the natural language aspect of it. This would take out the technical requirements around understanding _what_ you want. Sometimes, people using a device don’t know what they want exactly, but know what they don’t like about their current experience:
"The text is too small" -> browser increases text size
"I can’t see the text" -> browser adjusts the brightness settings. This would be nice to pair with some context, so the browser can ask, "is it better now?" and the user can respond "yes/no" until they get to something they’re happy with.
Interesting perspective on the elections in Kenya. It’s hard to comment on from the outside or fully appreciate the issues with Kenyatta being elected while on trial with ICC (without much research), but either way, I’m glad it was generally a peaceful election.
On Opera switching to WebKit, and what would happen if Webkit became the dominant/victorious engine: “It wouldn’t be the worst possible outcome —- victory of a closed-source engine would be worse —- but it would be a far cry from the open Web goals we’ve been striving for.”
As a web developer, my short term thought is “yay, fewer platforms to debug against”. But I do agree to a large extent with the worries expressed in this article.
Worked reasonably well with some test images I sent it. I don’t have any direct use for this right now, so I can’t test it further, but it looks like it could be useful for anyone that wants to do image processing to build a product but doesn’t have the engineering time/people to build out the processing itself.
What’s really cool to me is this (especially with its per image, pay-as-you-go pricing) is to image processing what Amazon’s AWS is to server management. Hiding the complexity of that one piece of the problem so you can easily build a product on top of it without having to solve that problem yourself.
Fantastic interview with Gabe Newell on the future of gaming in our homes (input devices, consoles, connectivity - he touches on many topics). Had a great little anecdote about a “Theory of Fun” that they came up with when first developing Half-Life.