I like the intellectual discussion that this thread has sprouted. I am in a category somewhere between "young engineer" and "slide rule era engineer", and I absolutely agree with the comments that have been made so far by Terry, israelkk, and gg. If I may expand a little on Terry's comments, I think the one of the key aspects that comes from working with software is that of visualization. I agree that a deep understanding of fundamentals is one of the necessary traits for expert-level engineering, and one of the best ways to acquire this is by reading and comprehending the information in high quality reference works, especially those from the era that israelkk identied. However, another necessary aspect is that of visualization, and this is a trait I have found difficult to obtain from a traditional engineering/university education. Experience, such as trial-by-error or make-it/test-it/break-it, certainly helps address this, but this is where Terry's argument of using software and iterating designs makes a lot of sense-- the user can visualize, in almost real-time, how a design works, how changes affect the performance of the design, etc. I know that I have benefitted significantly by using software tools that aid my visualization of how a design responds to forces by deflecting, how stresses can vary by location due to multiple body interactions, etc.