I hope this reviewer is right. It seems reasonable to me that the potential value of the Watch is in changing the relationship between us and our devices, letting us recapture some of our time for real life.
Mike Godwin explains what lawmakers and regulators need to understand about Net Neutrality, “zero-rated” services, and Wikipedia.
This is one genre of writing where it’s best to start in the middle and work toward the ends.
Twitter has added a useful new capability: you can now embed a tweet in your tweet without having to delete characters to allow for it.
That’s it. One retweet with your comment. It’s a welcome change and solves a problem, but it’s worth pointing out that it’s a problem that Twitter created.
In a rational universe we’d have implemented links differently, as Ted Nelson wanted, and we wouldn’t be celebrating the chipping of tiny windows in walled gardens.
Here’s the latest news from the Pragmatic Bookshelf.
The very engaging and useful Your Code as a Crime Scene: Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs is now in print and shipping. We have an article by its author, Adam Tornhill, in the upcoming April issue of PragPub.
And Ruby Performance Optimization: Why Ruby Is Slow, and How to Fix It is now out in beta. It’s by Alexander Dymo, it’s edited by, uh, me, and it’s great!
Seems to me that one big problem with the “create the social media platform, grow it, and figure out how to monetize it later” model is that you create existential uncertainty for anyone who might try to extend your service. You should want other developers to enrich your users’ experience, but if they don’t know what part of the ecosystem you’re someday going to wall off as your own and what parts you’ll open up for them, they attempt to extend your ecosystem at their peril.
3.14159 26535 8979 323
7510 5820 (974-944) 59230
78164 0628 6208 (998) 6280
34-825-34 211 70679
8214 8086 51
0664 (70938) 4460
… that’s all I’ve got.