Its been a frantic couple of days in the office since Dev Week. In the past, I'd attend an event such as Dev Week or a course then go back to work wanting to completely change the how I approach the current project I'm working on. This week however, I had a new project to start, a bespoke content management system that feeds content for both pages on a site and an online help system. I took the learning curve gamble and drew out the application architecture with ASP.Net MVC in mind. I've spent two days now and have hacked out the db structure and the basic UI allowing me to "CRUD" Html content to the db. I've been using the Nerds Dinner chapter as a guide and merrily crunched away to get the job done. The app is not even half baked yet but I'll have something presentable by next week. Whenever I ran into a problem, I tended to Google the symptoms to get some guidance on how best to resolve the issue.
This whole "learning by doing" scenario made me start thinking about how I as a developer, should learn a new technology as efficiently as possible. I normally just one-click a book from Amazon when the need arises but now I'm starting to wonder if that's the best way for me to learn something.
I took a learning styles test and found my learning type to be Visual/auditory/kinaesthetic which basically means I'm quite a flexible learner and learn best in a range of styles. With that in mind when grokking up on a new technology, I think I'm going to watch more tutorial videos and write some concept applications as opposed to just reading books in future.