Part of my responsibilities at work is to implement scalable and well-performing solutions to exist product offerings and to monitor outgoing projects to meet critical standards. The project that I've worked for 6 years slipped under the radar of the aforementioned criteria and in and of itself performs and scales quite well, but without proper standards.
I've spent the last few development cycles refactoring the application's logging underpinnnings (about 6000+ lines of code were hand modified) and now I'm implementing a way of "crosscutting" the application without changing it to provide monitoring at an enterprise level. The technology I'm learning to implement is called Aspects and more specifically, AspectJ from the Eclipse Foundation.
I began by reading how out enterprise logging utilities need AspectJ and then began doing research on AspectJ. I've been reading "Mastering AspectJ: Aspect-Oriented Programming in Java" by Joseph D. Gradecki and Nicholas Lesiecki from 24x7 Books (a service our company subscribes to) and it's proven quite helpful. I'm beginning to understand the concepts and I've begun implementing some rudimentary solutions. My biggest hold up was integrating the current Ant build scripts with the new necessary classes and src directories.
But what I've learned from all of this is I must never let up on what I may learn, what I must learn, to keep pace with the industry. Others around me already understand these fundamentals, though very few here in my organization. It's so easy to slip into a secure mode and the moment something new, especially a paradigm in software development, is introduced its easy to just lay back and wait until you must implement or learn before engaging and embracing the technology.
Hopefully I'll continue to be conscious of this poor habit and make corrections through continuing education. It will only make me more marketable.