Author Archives: Ted Kaminski

The future of growth

Or, “among the many reasons I love Paul Krugman.” Krugman reviews a Robert J Gordon book, “The rise and fall of American growth.” I’ve just put this book on my library queue, so bear in mind I haven’t yet read … Continue reading

Posted in Futuring | Leave a comment

Wind powered cars

There’s a neat, long article over at Wait But Why that I found quite interesting. It purports to be about Elon Musk and Tesla (which might dissuade some readers) but it’s actually about climate change and electric cars. I wanted … Continue reading

Posted in Energy | Tagged , | Leave a comment

Algebraic data types: without them, we all suffer

Perhaps you’ve heard of “stringly typed” code. The use of strings instead of actual, you know, proper data structures, in places where it seems completely inappropriate. Why do programmers write such things? I’m sure some of it is simple bad … Continue reading

Posted in Programming | Tagged , , | Leave a comment

Human-computer interaction and programming

The other week, I was dismissive of an attempt at creating a “non-programming” sort of programming. I’d like to explain myself a bit more. The trouble, I think, is that many people confuse the problem. Programming is pretty terrible, but … Continue reading

Posted in Programming | Tagged , | Leave a comment

The Fermi paradox… isn’t.

There is a common topic among people who like to think about the future and space travel: the Fermi paradox. Simply put, if you take even tiny-seeming growth rates for any civilization in the galaxy, it should be everywhere in … Continue reading

Posted in Futuring | Leave a comment

Programming is the new literacy

Chris Granger has a post ironically titled “Coding is not the new literacy.” It’s pretty good. Despite the early part where he attempts to redefine literacy in order to have a catchy title: This is certainly accurate, but defining literacy … Continue reading

Posted in Programming | 1 Comment

More on Abstraction

Almost a year ago (evidently), I wrote briefly about Abstraction, Modularity, and Composition as important principles in designing software. I’ve had a few more thoughts to add about abstraction. There are two sides to the abstraction “coin”: there’s (for lack … Continue reading

Posted in Uncategorized | Leave a comment