Welcome to my personal blog - a hodgepodge of my musical, art/design, and fashion tastes, among other things. I reblog like hell because tumblr's got so much good stuff that I want to share with you - it's like a visual buffet. I write/doodle often so I occasionally post my scribbles and creations on here under #words and #doodles. If you're looking for more of my art stuff, check out Kitteh Noir on Tumblr / Facebook. SECTIONS ______________________________________________________ ORIGINAL CONTENT :: WORDS. PHOTOS. ART . COFFEE NOTES . ______________________________________________________ CURATED CONTENT :: FAVORITES. SOUNDS. READS. ARTICLES. INTERVIEWS. DOCUMENTARIES. BOREDOM FEEDER. QUOTES.
I’ve never liked the term “computer science.” The main reason I don’t like it is that there’s no such thing. Computer science is a grab bag of tenuously related areas thrown together by an accident of history, like Yugoslavia. At one end you have people who are really mathematicians, but call what they’re doing computer science so they can get DARPA grants. In the middle you have people working on something like the natural history of computers— studying the behavior of algorithms for routing data through networks, for example. And then at the other extreme you have the hackers, who are trying to write interesting software, and for whom computers are just a medium of expression, as concrete is for architects or paint for painters. It’s as if mathematicians, physicists, and architects all had to be in the same department.
Sometimes what the hackers do is called “software engineering,” but this term is just as misleading. Good software designers are no more engineers than architects are. The border between architecture and engineering is not sharply defined, but it’s there. It falls between what and how: architects decide what to do, and engineers figure out how to do it.
What and how should not be kept too separate. You’re asking for trouble if you try to decide what to do without understanding how to do it. But hacking can certainly be more than just deciding how to implement some spec. At its best, it’s creating the spec— though it turns out the best way to do that is to implement it.