So I kind of lied. I found this link on Slashdot
today and found it in one of my 14 open iCab
windows while I was brushing my teeth. I haven't read it all yet, so this entry is partly a reminder for me to go back and finish. But it's about how writing poetry and writing code are similar, which I resonate with. I feel bad when my code doesn't look pretty, and I sometimes agonize over which is the better of two ways to do exactly the same thing.
He's arguing that writing code isn't much like engineering. Which I typically disagree with -- I think software engineering has much in common with the usual engineering suspects. So maybe writing is sometimes like engineering. Like, making a James Bond film is an engineering project. It's pretty clear right away what the requirements are, it's just a matter of finding the maximal parameters for several known equations and, hey presto, blockbuster!
So it goes both ways. Writing code is more like writing poetry than many people think. And writing poetry is more like engineering than people think. So writing code approaches engineering from two directions. Integrate that!The Poetry of Programming