Fundamentals of Software Engineering

Chapter 12. Learning to Learn

Live as if you were to die tomorrow. Learn as if you were to live forever.

Mahatma Gandhi

If you’ve been in the technology space for any length of time, you’re familiar with the reality that technology changes. Constantly. Which means you will be challenged to learn new things regularly. Many engineers believe they are paid to write code, which is true. However, you are also paid to think. You earn a living by using your brain, so you have to feed your brains with knowledge, which means learning.

Arguably, the ability to learn new things quickly is the most important skill of a successful engineer. Additionally, you need to not only understand new things but also apply what you’ve learned to real-world scenarios. Many people benefit from the “see one, do one, teach one” approach.

The Shiny New Thing Paradox

Software engineers are attracted to “new” like moths to a flame, and when something first appears, it is often accompanied by a flurry of activity that makes it seem like you’ll be left behind if you don’t immediately embrace it. In the early days though, technologies might not be ready for prime time; the rough edges haven’t been sanded down yet. Over time, the hype fades. But that is often when the new thing is most ready for adoption. Never forget, new technologies are like buses: another one will come along in 15 minutes.

Cramming Doesn’t Work

Odds are at some point in your educational career you crammed for an important test. And it might ...