Beware the Share
From WikiContent
(New page: 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 f...) |
|||
| Line 2: | Line 2: | ||
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? | 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? | ||
| + | |||
| + | By [[Udi Dahan]] | ||
| + | |||
| + | |||
| + | This work is licensed under a Creative Commons Attribution 3 | ||
| + | |||
| + | Back to [[97 Things Every Programmer Should Know]] home page | ||
Revision as of 21:00, 4 October 2008
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 libraries where possible, the works. The code review that I had felt so 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?
By Udi Dahan
This work is licensed under a Creative Commons Attribution 3
Back to 97 Things Every Programmer Should Know home page
