Reusing and Recycling Code

An anonymous reader sends us to a writeup about when and how to recycle code, excerpting: "As developers, once we start separating our code into abstract ontological typologies, we make use of the human mind's phenomenal ability to work with types. Our code becomes less about jump tables and registers and more about users, email messages and images. What once was a problem of allocating resources and operations within the computer becomes an abstract, logical problem within a collection of objects....Over time, by constantly working to reuse our own code, we choose practices that work well for ourselves and discard practices that don't work as well or slow down our workflow. For developers flying solo or those working on small projects, this evolutionary process is a sufficient way of going about things. But there's trouble when we add other players into the mix--other developers, a user interface person, a database person, a sysadmin, a project mana-jerk: as a developer, they don't have access to our 'experience' of the code and we don't have access to theirs. "

Comments

Re:Hell is other people

[Anonymous Coward]

Truly good programmers enjoy working with other people. They like the learning experience the others provide. They work as a team, capable of working together to handle the largest of challenges. It's too bad there are fuckers like you to get in the way of such progress.

And cats and mice sing each other songs and cuddle up by night to keep each other warm? What usually happens is that the "team players", against the advice of the better coders, pick a technically unsound solution and run with it. When this circle jerk of the incompetents is finished, coders further down the line will have to work around the braindamage. Some progress!

Too bad fuckers like you can't be screened out at application time, or better still, at birth!