Skip to main content

Software Engineering: Reuse Has Finally Arrived

Have you noticed that code reuse works these days? For a long time, software engineers struggled with the difficulty of reusing existing software, but it's now common place

Let me give you some examples. I use Linux, Nginx, MySQL, and Python, not to mention a Web browser. These days, very few people need to write a custom kernel, Web server, database, or programming language to solve their particular problem. Sure it happens, but it's far more common to reuse something existing.

I even make use of an existing Web framework, Pylons, and an existing templating engine, Mako. Those things are often written from scratch, but I didn't need to. They were fine.

Even within my own code, I find plenty of places for reuse. Each of my clients has a pretty different setup. Their input formats and output formats are often pretty different, but by using a UNIXy "small tools that can be pieced together" approach, I usually write only a small amount of code when I get a new customer.

What has changed? Why is it suddenly so easy to reuse code? Has object-oriented programming finally paid off? Maybe. However, I think the more likely culprit is open source. Small companies are now viable because they have access to a huge corpus of freely available source code. They don't have to pay for it. They can look at the source if the documentation is inadequate. They can contribute bug fixes if they encounter bugs. They can even hack it in deep ways to accomplish special tasks. This is particularly common in the BSD world.

Last of all, testing and a strong dedication to docstrings help me with reusing my own code. Per agile thinking, I don't try to get it right the first time. If I need to add a feature to make use of code in an unexpected way, I can. The docstrings help me understand what's already there, and the tests help make sure I don't break it.

Comments

Bob Van Zant said…
At a macro level you're obviously correct. However, the closer we get to any given piece of software we find that code reuse is far from a reality. Within the commercial product that I work on there is plenty of copy and paste action. Within open source applications we find the same thing in the common case.

In a less explicit way we see engineers reinventing the wheel with code that looks and smells like code in a different module. So now you can talk about a different set of problems like communication amongst engineers and how do you structure a codebase so that it can be properly divided amongst teams so that they're less likely to duplicate effort.

So I absolutely agree with what you're seeing and writing, however, I think the problem of today is at a more micro level and very widespread.
jjinux said…
Bob, since I've worked on that same piece of commercial software, I absolutely agree with you. We definitely haven't come to some nirvana of component reuse, as was hoped. You're right, it's hardest at the micro level. However, we have come to a point where large open source projects are reused and languages themselves come with large, useful libraries.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…