3 ms·
Your comment seems unduly negative. But, after reading the article it really does seem like a forced analogy. I suppose in some ways it's quite surprising that
by new299 14y ago
Your comment seems unduly negative. But, after reading the article it really does seem like a forced analogy.
I suppose in some ways it's quite surprising that writing code is so much different than writing a novel. They are after all linear sequences of statements. But a novel is always trying to draw you toward the end, to a conclusion. The lasting ideas it places in your mind, it does using indirect means. A computer program on the other hand creates something dynamic and non-linear.
What surprised after reading the article is how little I felt writing code, even narrative driven games, is like writing a novel.
- L0j1k 14y agoI think that's what struck me most about this, that it felt forced, and also written by someone that doesn't quite understand exactly what programming actually is and is not. Writing a novel? No. I'd say it's much more like building a bridge than writing a novel. We use small machines to build a bigger structure that serves a purpose. That's why I accused the author of not knowing much about programming (indeed, he is a self-described "product guy"). Otherwise he'd be much more likely to draw parallels with building bridges or some other kind of engineering than writing a novel or authoring some other literary product.