I’ve just had a sudden realization. All those years in school looking at the other students thinking why can’t they be smarter and just get the math, science, or whatever – I was wrong. They weren’t the slow ones because they were learning exactly the lesson the curriculum was designed to teach them. I was slow. I missed the point. I did not learn my lessons properly.
I’m declaring my storage problems to be resolved. Though I’m sure this will come up again. I have to believe at this point I will not encounter the issue for several more years. I now have about 5 TB of free storage across several systems, with another 1.5 TB drive ready to act as either a backup or additional space. About three years ago I had about 1 TB of free space and no idea how I’d ever fill it. Now I know.
The introduction of catalogs of patterns has been a great advancement to software engineering. These collections of common solutions to common design problems are an excellent way to pass knowledge of the software engineering craft from one practitioner to another. I am happy to have several great texts from this category taking up valuable shelf space. Design Patterns, Patterns of Enterprise Application Architecture, the Pattern-Oriented Software Architecture series, Release It!, and Enterprise Integration Patterns are some of my favorite references that continue to be a source of inspiration whenever I encounter difficult design decisions. However, they are not the last word in software engineering that some engineers present them as. Acting as though pointing out that a pattern exists is a valid appeal to authority for using that pattern is like saying that serving seafood to those that are allergic is acceptable because the seafood was prepared using the recipe of a master chef.
Here are a few of my favorite software engineering related books I’ve read in the last year. To make this list the book had to be something I read in 2009, and it had to be interesting, useful, or just plain insanely great at totally changing my perspective on something.
Since 2009 is almost officially over here is a list of my favorite software engineering related tools I’ve been using this year. Most of these tools have been around for a while, and I didn’t necessarily just start using them this year. These are all things I just found to be very useful throughout the year doing my job.
Seth Godin wrote this ingenious analysis of market changes titled “It’s not the rats you need to worry about“. It got me to thinking about how I prefer CDs over downloaded music. Primarily I have this preference based on the quality of the content. I’d prefer not to have more physical media taking up space in my house, but until someone offers CD quality lossless downloads I feel like I’m stuck. However, I’m not the ideal customer. The last time I bought a CD was 6 months ago, the time before that was a year and a half. One CD a year is not going to sustain your industry.
I had an interesting exchange with my manager yesterday. We had our very first team meeting under the guise of the new “Great Place to Work” initiative. We were informed that there is no budget for conferences this year so SOL on the professional development plans. There was also an open question about if we understood our performance goals. The exchange went something like this:
Management: Does everyone understand their performance goals?
Me: I’m a little confused. I’m told I need to make 4 contributions that fix an issue in production. What if there are not four issues in production in my product? (I’m thinking do I really need to break something in order to have done a good job this review cycle.)
© 2009-2010 Maurice Carey All Rights Reserved