Apply the knowledge

I’ve always been interested in improving myself as a developer. I read and study, I discuss, I attend presentations and seminars, and so on. I really invest alot of time and effort into my knowledge. The obvious question really, is why? Put short, it’s about writing better code, and designing better systems. There is no point in aquiring the knowledge without applying the knowledge.

Realizing this, I started using a simple, yet effective method of making this transition a bit easier in everyday life. Basically, whenever I read something interesting that I want to make use of, I study it, make out the essence of it, write it down, and put it over my desk (virtually or physically). Then I make a point out of considering/applying it whenever applicable.

For instance, when I first read about the Law of Demeter, I wrote down the essence of it, and put it over my desk. whenever I got to a point where I broke that law, I was reminded by my note, and started to dwell abit about what the Law of Demeter was about, how my design would look if I solved my problem without breaking it, and the costs and benefits for doing it this way. Pretty soon I really understood the point, and it became a part of my general skills. I learned by doing. Doing it this way kind of forces you to actively consider the theory, testing it, applying it, and evaluating the results.

I’m really happy with this technique, and nowadays there is always a note over my desk.

If you want to try it out, you really should. Here’s a few simple guidelines:

• Keep your scope simple. Don’t write things like: “apply XP”. It’s too general. Keep the scope narrow and concrete, like: “always write the test first”. It’s easier to apply, and it’s easier to evaluate the costs and benefits.
• Do not have more than one scope at a time. It’s important that you can be focused. Having to many things to consider, will complicate things, and you’ll probably fail applying anything.
• Commit yourself. When you have a scope, be true to it. This is the best way to learn it.
• Switching scope. Don’t switch the topic before you feel you’ve learned it properly.

Tore Vestues