Skip to main content
The notion that physical books are ending their lifecycle is upsetting to people who hold them to be synonymous with literature and terrifying to those who make their living within the existing structures of publishing. As an editor and a lover of books, I sympathize. But why should a civilization that reads electronically be any less literate than one that harvests trees to do so? And why should a transition away from the printed page lessen our appreciation and love for printed books? Hardbacks these days are disposable vessels, printed on ever crappier paper with bindings that skew and crack. In a world where we do most of our serious reading on screens, books may again thrive as expressions of craft and design. Their decline as useful objects may allow them to flourish as design objects.

How the Kindle will change the world. - By Jacob Weisberg - Slate Magazine


Outstanding article by Jacob Weisberg. A lot of people are freaking out about the Kindle due to a misguided idea that physical books are literature.


They aren’t. They are artifacts. Just because we have the Kindle doesn’t mean we are going to start burning our books. All it really means is that instead of having to keep a god damn wall covered with bookshelf after bookshelf of books that I bought and read once, I can keep a single bookshelf with the 50 or 100 books I own that I re-read every year or so, or books that have a sentimental value for me.

Comments

Popular posts from this blog

On sleep deprivation and Incan Monkey Gods

From: Dilbert comic strip for 08/03/1992 from the official Dilbert comic strips archive. I was trying to show this strip to a coworker who is dangerously toying with the harsh mistress that is Insomnia. What shocked me is how quickly I was able to look up the strip, which was published when he was just 11 years old, and two weeks before my just-out-of-college ass shipped out to US Army Basic Training.

Add custom speed settings to your ifit map workout

Ifit.com allows you to build a workout walk/race/bike route simply by clicking on a Google Maps interface. You can then use a compatible ifit-enabled workout machine to recreate the route automatically. The problem is that the user interface still isn't final, so there are features in place that aren't exactly obvious. For example, if you create a workout your machine starts at 1 MPH, because that's the default. But how to set it to start at say, 3 MPH? Easy, just switch from map view to graph view: That button switches from the Google Maps interface to a chart that allows you to visualize and control effort: You can't change the elevation, this is fixed due to the geography that you selected. But you can drag the yellow (speed line) to change the speed of your device.  What if you want to have segments at different speeds? Easy, just click and drag and it will break the line, and you can drag each segment of the line independently: ...

Software Entropy and the Strangler Fig: Surviving a 20-Year-Old Codebase

Right now, I find myself fighting a three-front war. Front one is keeping a 20-year-old behemoth of a B2B application alive. We are talking about decades of legacy ASP.NET and VB.NET where two decades of tweaks, patches, and "temporary fixes" have become permanent, load-bearing pillars of the architecture. Every time I touch it, it feels like playing Operation with oven mitts on—spending 90% of my week untangling logic just so a simple bug fix doesn’t cause a ripple effect that crashes a critical service. Front two is modernizing the architecture. I am actively trying to implement a rudimentary Strangler Fig pattern—slowly carving out legacy functionality and pushing it into a clean, testable shared library project so we can actually run proper unit tests and stop the bleeding. Front three is modernizing the team. While keeping the lights on and quietly rebuilding the engine, I am also pushing a retraining effort to get my peers up to current framework versions and embracing ...