Legacy Code

There’s a term in software engineering speak called “legacy code,” which essentially refers to leftover stuff from older versions of a particular software. Sometimes its necessary to make sure the old stuff works right alongside with the new, and sometimes the decision is made to cut off support altogether (anybody try to run some of their old DOS games on their nifty Windows 7 machine?) In either case – whether the code is just there for archival purposes, or to maintain compatibility, I’d venture to say that there’s always something to learn from it for the programmer, either in the form of mistakes and inefficiencies or brilliance in a prior version. In other words, there is much to be learned from those who have gone before.

Another, perhaps more powerful, set of examples is this – Marcia and I were recently talking about examples of people who left behind their respected positions in their home countries to come to the United States in the hope of creating a better opportunity for the next generation. A doctor in her home country becoming a part-time language teacher here. A policeman in his home country becoming a custodian here. An engineer in his home country becoming a store operator here. In any of these cases, a certain amount of sacrifice happened with their arrival in the States. Years of training set aside. More years of experience (from a career perspective) placed down for the sake of the next generation. That takes courage and love.

Reminds me of the ancient Israelites. Abraham lifted up his family to travel hundreds of miles to place he never knew on God’s Word that he would multiply his descendants like the stars. Moses, Aaron, and his generation did some heavy lifting getting the people out of slavery in Egypt, following that promise, only to get to the edge of the land God gave to them, never to enter it. It was Joshua’s generation that made it into the promised land, and even they didn’t see the full realization of what God had in store. Interestingly, the initial set of commands given to Joshua speak of legacy code, in a sense. Joshua 1:8 says, “This Book of the Law shall not depart from your mouth, but you shall meditate on it day and night, so that you may be careful to do according to all that is written in it. For then you will make your way prosperous, and then you will have good success.” Throughout the Old Testament, one of the repeated themes is that of remembering. These Israelites were never supposed to forget where they came from, what God did for them, and what God said to them. I can’t help but also think of them telling stories of past mistakes too. Legacy Code, B.C. style.

Just last month I finished an intensive study on 2 Timothy 2:1-13, looking in depth at the sense of legacy that Paul sought to pass on to the next generation of Christians in the first century. I’ll write more on it later, but one of the particularly interesting things about 2 Timothy is that it’s Paul’s last letter, and you catch a glimpse of what’s near and dear to his heart by examining it. He had many ambitions, some realized, many not. Yet his legacy lives on in his writings and teachings, carried along by the Spirit. I think I’m starting to get why history is so important. It’s not only the study of it and gleaning principles and lessons from the past, but the very fact that those that have gone before us have paved the way and opened up new opportunities for us that God is waiting for us to walk into. What will we leave for the next generation? We may never know, but I’d sure like to do whatever my part is to help create something better.

No related posts.

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>