14 ms·
> To program any more was pointless. My programs would never live as long as [Kafka’s] The Trial. As a programmer, I want to believe I'm a writer, a poet, a sc
by saalweachter 12y ago
> To program any more was pointless. My programs would never live as long as [Kafka’s] The Trial.
As a programmer, I want to believe I'm a writer, a poet, a sculptor.
But the truth is programmers are dancers, mimes, ventriloquists. We're performance artists, and the systems we program really only have meaning as long as we keep programming them (or, if we're really lucky, someone else takes up the dance when we grow tired of it). Once we take our final bows, the programs will fade away and die and all that will be left is a memory of the performance.
- colechristensen 12y agoI don't like the theory that a piece of software can't be complete. Not all software can be complete, but some simple tools (which most software should be made of) can and should be able to be finished forever, or at least asymptotically approach completeness to a degree that the distance becomes irrelevant.
- organsnyder 12y agoA perfect, fully complete piece of software will still need adaptations: even if feature requirements never change, the underlying platform surely will. Even a complete, self-contained system—one which never sees any changes at any level from software to hardware—will still require periodic hardware maintenance.
- egiboy 12y agoEven the simplest, most -seemingly- feature-complete software can and will need fixes. The best example comes from the Big Iron world, where a program which does nothing was needed: http://en.wikipedia.org/wiki/IEFBR14 http://en.wikipedia.org/wiki/IEFBR14
- Terr_ 12y agoConstruction/architecture-metaphors work a bit too: They can outlive the involvement of the initial designer, many bits can be tacked on or changed, and they have some overriding functional requirements.
- saalweachter 12y agoThey especially work if you've owned and maintained an actual, physical building. You can build for the ages, but if no one patches the holes in the roof every now and again, it will rot from the inside out in a few years.
- tormeh 12y agoUnless you build in stone.
- brc 12y agoEven if you build in stone. Most long-lasting stone structures are in constant decay. Without being weather sealed and maintained, they will decay and fail. Even if they are in moisture and vegetation free environment like the pyramids, they are still subject to that most basic human trait - theft.
- pjc50 12y agoI've seen plenty of roofless stone buildings. They're decorative but not useful.
- galfarragem 12y agoArchitecture metaphor is relevant because architecture is a mix of art and science. The same happens with software. Very few houses become or have the pretension to be monuments. Most of them only have a mundane function: they are shelters. The same happens with software. Very few architects are visionary enough to project an house in a different way and point a new direction. Most of them just follow the existent trends. The same happens with software. Most houses become monuments because of historical reasons, not because they are the best ones. The same happens with software.
- michaelochurch 12y agoAs a programmer, I want to believe I'm a writer, a poet, a sculptor. But the truth is programmers are dancers, mimes, ventriloquists. We're performance artists, and the systems we program really only have meaning as long as we keep programming them (or, if we're really lucky, someone else takes up the dance when we grow tired of it). Once we take our final bows, the programs will fade away and die and all that will be left is a memory of the performance. Nah, it doesn't have to be that way, although it often is. We're like artists or architects, but most of what we build isn't lasting because there's little demand for that, just as many architects will never get paid to work on anything that might last. The Sistene Chapel lasted; the slums of Rome from almost any era haven't. For every artist whose work makes it into a museum, there are thousands hawking cheap prints on the streets of Paris. Programmers can build software that will last for a long time. I know people whose programs are still running, untouched, after 30 years. We can solve problems and keep them solved. It doesn't have to be just code; papers and new algorithms can advance the state of the field. Since we're a progressive sort who really believe in the ability of our "magic power" to blow away drudgery, we love when we're able to do that: to solve a problem and keep it solved. If this is applied to code, you can get exponential growth in codebase or library or ecosystem value for a long time. Here's the problem, though: no one is willing to pay for code that lasts. Just as most architects are building clapboard houses in the suburbs, most of us get stuck writing throwaway code because The Business won't pay for good code by giving us the autonomy and timeframes that'd enable it to exist. Of course, bad code and failed software projeects are far more costly in the long term, but executives are not a tribe known for thinking long term; most corporate climbers have the political skill to get promoted away from their externalized costs before anything can be linked to them.
- tel 12y agoIn your opinion what does an organization which does pay for Sistine Chapels of code look like? It's an interesting thought experiment since presumably we're looking for the Holy Roman Empire of a company (Google? Google in 20 years? Google if they last another 20 years? Or 200?)
- michaelochurch 12y ago
- wcummings 12y agoI prefer the term `software gardener' to `software engineer' for this reason: software is slowly created over time and requires constant care, or it will wilt and die.
- TeMPOraL 12y agoI never liked this analogy. There is no such thing as software entropy - bits are bits, and the code doesn't decay with time. The only reason we have maintenance problems is because we keep changing components. If you program a box, unplug it from the Internet and leave it running, the code will continue to work until the hardware physically fails. Programming for the on-line world is more like managing a clothing brand - everything is constantly changing around you, things go out of fashion every other month and you need to keep up or else your brand will die and get quickly forgotten.
- wcummings 12y ago>everything is constantly changing around you Like an ecosystem? ;)
- TeMPOraL 12y agoWell, ok. I guess my point is that programming is like gardening only if you deliberately decide to work in an environment that forces you to keep up with changes, like the Internet. Software for infrastructure can easily last unchanged for 20+ years.
- saalweachter 12y agoI really like the ecosystem analogy. Ecosystems have a variety of niches which change at varying paces. A shark isn't better than a finch because it is more stable on the evolutionary timescale, it is well-adapted to a stable niche. More stable niches are not better or worse than transient, quickly-changing niches, they're just more stable. I think it is important to recognize that the stability of a niche is independent of its value or the care that should be taken filling it. A feed processor must be written carefully even though most often they only live a couple of years before the underlying need for it goes away. A compiler is of great value but without constant maintenance it will be worthless within a few years, as compiler techniques evolve, languages are restandardized, and machine architectures shift. Software written as part of scientific inquiry is frequently worthless and uninteresting after the questions being examined have been answered.
- e40 12y agoI generally agree, but I have been surprised. We had a bug in a program my company released in the late 90's and that bug only became apparent last year. 5-6 people contacted us for a fix (which we provided). The program was more than 15 years old and it was still in production. That surprised me and made me adjust my views of each of my software releases. They might be deployed in the field for far longer than I had assumed.
- huxley 12y ago> To program any more was pointless. My programs would never live as long as [Kafka’s] The Trial. I found it a touch ironic considering that Kafka, on his deathbed, asked his friend Max Brod to destroy all of Kafka's unpublished work, including The Trial.
- gwern 12y agoThe request was the final grand gesture. > BORGES: "In the case of Kafka, we know very little. We only know that he was very dissatisfied with his own work. Of course, when he told his friend Max Brod that he wanted his manuscripts to be burned, as Virgil did, I suppose he knew that his friend wouldn't do that. If a man wants to destroy his own work, he throws it into a fire, and there it goes. When he tells a close friend of his, “I want all the manuscripts to be destroyed,” he knows that the friend will never do that, and the friend knows that he knows and that he knows that the other knows that he knows and so on and so forth."
- huxley 12y agoAs much as it pains me to disagree with Borges, Kafka had already burnt almost 90% of his unpublished work [1] before his health declined due to starvation from a then untreatable laryngeal tuberculosis. I think Kafka did truly want to burn his work, but also feel Max Brod was right to save what he could. [1] http://www.nytimes.com/2010/09/26/magazine/26kafka-t.html?_r=0 http://www.nytimes.com/2010/09/26/magazine/26kafka-t.html?_r...
- gwern 12y agoHe had burnt a lot, it's true, but that raises another question: given that he did burn a lot of it regularly throughout his life before his fatal illness, why did he not burn the remainder while healthy and instead later asked Brod (who claims to have immediately told Kafka he would not do that) to do it? Borges's reading here makes more sense; it was simply the final Kafkaesque gesture.
- timharding 12y agoProgrammers are really boring analogy whalers, out at sea forever hunting their perfect, elusive, bloody boring, analogs.
- surrealize 12y agoCall me HTML
- octatoan 12y agoBurritos!
- deleted 12y ago[deleted]
- tbirdz 12y agoI don't think this is true. Consider the popularity of emulators for older systems. People still care about and use old programs and games. You can even still buy games released 35+ years ago from online retailers like gog. Think about how old programs like ls, dd, etc are (even older when you consider the design and not just the implementation). People still care about "Super Mario Bros" (a computer program) today, over 30 years after it's original release. Is it really going to be forgotten in the next 10 years? 20? 30? I think not. Will all emulators be abandoned? Maybe appreciation for old computer programs is a niche interest, but let's face it, Kafka is not exactly popular among the masses either. Most software may be forgotten, but most books will be too.
- SoftwareMaven 12y agoI think this would fall into the category of "picking up the dance". For some software, people don't want the performance to end, so they bring the performances to new stages, but, as soon as they stop actively "performing", the dance will end.
- bentcorner 12y agoI find it a little sad that most modern computing will be lost to time. Early console games were easily self contained systems, and lent themselves well to emulation. Today's consoles are towers of complexity that will likely never be emulated. At best compatibility layers will be built into future systems to interoperate, the likely result is that the classics of today will continue to hobble along on a dwindling number of devices. At worst, a corporation loses interest and all their consoles immediately turn into expensive paperweights.
- korethr 12y agoI disagree. It's easy today to think of the consoles of yesteryear as simple self contained systems (A 6502-based CPU? How quaint!). However, Consider the unholy trinity that was the Sega Genesis/Master System/CD/32X. Though no longer modern, that absolutely is a tower of complexity, especially when it was brand new. The emulators of the game consoles of the past exist today because some hacker got curious and interested. Complexity certainly isn't stopping emulator devs. The Wii was more complex than the Gamecube, which was more complex than the N64, which was more complex than the SNES, which was more complex than the NES. And yet there are emulators available for all of those systems. What is different today that would prevent an enterprising hacker tomorrow from making emulators of today's consoles?
- trustfundbaby 12y agoProgrammers are indeed like writers, but some of us get to write Beowulf, some others get to write college term papers and the rest of us lie somewhere in between.
- dasil003 12y agoThe irony is that a digital information is theoretically lossless, but in practice software and hardware changes so fast that it is one of the most ephemeral things humanity has ever created. So if you got into programming because you wanted to create something lasting, I think you are destined to be disappointed. But then again, all human endeavor, and indeed everything in our human experience, even the seas and the mountains and the stars are all ephemeral on some time scale. As the Buddhists say, the temporary nature of things is unavoidable and neutral, it's ones desire for permanence that causes a problem.
- mikekchar 12y agoI see myself as a bonsai artist. Bonsai trees need to be cared for, trimmed, styled, wired, etc. They grow over time. You can change things, but you can't realistically change everything without starting again. A bonsai tree is not "done" until it is dead. I think this is the same as software.