Yes, I know. It's only mid-week and I'm complaining about the length of the work week. This week has been a bit more challenging as I've been taking a self-guided tutorial on Test Driven Development (TDD). It was supposed to be at a leisurely pace with plenty of breaks. However, someone in the organization I work for (no naming names) decided to put a deadline on the course completion. As I've been supporting a project on 3 continents that is on a crash and burn deadline, not to mention my upcoming vacation time, I've been a bit remiss and hadn't even started the course until late last week. Catch up time!
The course has been a bit more challenging than I'd anticipated and between rushing through the material to keep pace with my projects and trying to complete the assignments, my performance has been less than stellar. In fact, the course has helped me feel like I'm college again, with evaluations online and responses from instructors. While I've gleaned a lot from the course, I've also learned that I have zero desire to return to school for continuing education.
So to break up the work week I'm blessed to have a soccer game tonight. Game #3 (yeah, I'm a little superstitious of last year's debacle and resultant knee blow out and I'll be taking it easy tonight) and a chance to keep our lead in our division. And to our advantage, the game is not a late one (last week was 11:30 PM) so I'll not be as exhausted tomorrow.
Just 2 more working days and I'm off for the rest of the year. Can it really be possible? Yeah me!
Showing posts with label continuing education. Show all posts
Showing posts with label continuing education. Show all posts
Wednesday, December 12, 2007
Long Work Week, Time for Some Soccer
Labels:
continuing education,
education,
indoor soccer,
work
Tuesday, April 03, 2007
AspectJ: New Learning
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.
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.
Labels:
AspectJ,
continuing education
Subscribe to:
Posts (Atom)