(no subject)

[andrewducker]

More and more I'm convinced that programming isn't about breaking down processes into their component parts/instructions and then implementing those instructions in a language understood by computers.

That, after all, is dead easy.

Programming is all about knowing the pitfalls inherent in any system, how to work around them, how to spot the errors quickly and what solutions fix them. It's about being an encyclopedeia of workarounds.

Comments

[kpollock.livejournal.com]

I think it's mainly about communication - finding out what's needed, finding out what works, what people like/dislike about systems and why. How they help people do their work. Getting a good explanation of the existing code.

And also the inter process commuincaiton - what to pass and when is pretty important.

It's hard to have a workaround for something you ahven't even designed yet. :-)

[aberbotimue.livejournal.com]

i think you are see ing the fact that you have workarounds as the answear, but altermatly, the real programming was when you devised said workarounds surley?

which would have been breaking down the process, etc... and lets face it, as you said, the bulk of the code, is dead easy, but the time consuming bit, is as you rightly point out where pitfalls exist, so Ithink add the two staements together, and we have coding..

but we cirtainly becomne "better" no, maybe not... we become more able the more work arounds we have been involved in, as we can apply them accross to other problems, thus faster at dealing with them..

[allorin.livejournal.com]

Spoken like a true newly jaded, Mainframe/IMS/Cobol cynic. Programming is like the world's best jigsaw puzzle, but one where though you have a picture, you have license to change it a little. It's fun!