Beware the Share
来源:互联网 发布:淘宝开店论坛 编辑:程序博客网 时间:2024/06/05 01:39
It was my first project at the company. I'd just finished my degree and was anxious to prove myself, staying late every day going through the existing code. As I worked through my first feature I took extra care to put in place everything I had learned — commenting, logging, pulling out shared code into libraries where possible, the works. The code review that I had feltso ready for came as a rude awakening — reuse was frowned upon!
How could this be? All through college reuse was held up as the epitome of quality software engineering. All the articles I had read, the textbooks, the seasoned software professionals who taught me. Was it all wrong?
It turns out that I was missing something critical.
Context.
The fact that two wildly different parts of the system performed some logic in the same way meant less than I thought. Up until I had pulled out those libraries of shared code, these parts were not dependent on each other. Each could evolve independently. Each could change its logic to suit the needs of the system's changing business environment. Those four lines of similar code were accidental — a temporal anomaly, a coincidence. That is, until I came along.
The libraries of shared code I created tied the shoelaces of each foot to each other. Steps by one business domain could not be made without first synchronizing with the other. Maintenance costs in those independent functions used to be negligible, but the common library required an order of magnitude more testing.
While I'd decreased the absolute number of lines of code in the system, I had increased the number of dependencies. The context of these dependencies is critical — had they been localized, it may have been justified and had some positive value. When these dependencies aren't held in check, their tendrils entangle the larger concerns of the system even though the code itself looks just fine.
These mistakes are insidious in that, at their core, they sound like a good idea. When applied in the right context, these techniques are valuable. In the wrong context, they increase cost rather than value. When coming into an existing code base with no knowledge of the context where the various parts will be used, I'm much more careful these days about what is shared.
Beware the share. Check your context. Only then, proceed.
By Udi Dahan
This work is licensed under a Creative Commons Attribution 3
- Beware the Share
- Beware the Share
- Beware the Share
- Beware of the stopwatch
- Beware the C++ implicit conversion
- Hackers Beware: The Ultimate Guide to Network Security
- share the oracle experiences
- Beware File Open/Save Dialogs: They May Change The Current Directory
- Hackers Beware: The Ultimate Guide to Network Security by Eric Cole
- 狮子那一份the lions share
- Share: The Icon No One Agrees On
- share
- share
- share
- share
- Beware of GPU memory bandwidth!!
- Beware what you wish for
- Beware of unknown root causes
- 泛型 通配符2
- Poj Trie树 水题整理 (Poj 1065+1204+2001+2418)
- Before You Refactor
- 第二章 shell程序设计
- java 技术小结
- Beware the Share
- 802.11协议中帧控制域中To DS and From DS 比特位的含义
- 程序人生--2005年(26)
- 编写程序求n!--C语言中数组的使用
- The Boy Scout Rule
- Catch That Cow
- Check Your Code First before Looking to Blame Others
- PPM / PGM / PBM 图像文件格式
- Choose Your Tools with Care