{"id":2516,"date":"2017-10-25T15:47:00","date_gmt":"2017-10-25T15:47:00","guid":{"rendered":"https:\/\/www.clockwork.com\/?p=2516"},"modified":"2024-05-31T19:56:16","modified_gmt":"2024-05-31T19:56:16","slug":"seven-steps-to-learning-a-new-technology","status":"publish","type":"post","link":"https:\/\/www.clockwork.com\/insights\/seven-steps-to-learning-a-new-technology\/","title":{"rendered":"Seven steps to learning a new technology"},"content":{"rendered":"\n

Have you ever had a client say something like, \u201cI love that idea, but can you write it in Ruby?\u201d<\/p>\n\n\n\n

Your gut drops, and your blood pressure rises. Outside of hearing the Ruby referenced all the time, you know little about it. And you\u2019re supposed to be the tech expert in the room! At the same time, you\u2019ve always wanted to learn Ruby and you\u2019ve got a vague sense that, yes, you could indeed write it in Ruby. So you say \u201cYes!\u201d<\/p>\n\n\n\n

Now what? You\u2019ve done a Google search or two and are on to looking for tips on how to learn new technologies quick. Look no further!<\/p>\n\n\n\n

First, don\u2019t worry about not being an expert. Technology moves too fast for us to keep up with each shiny new thing. Instead, get comfortable knowing a little bit about everything so you can use your gut to guide you during those initial (and often unexpected) discussions, and then follow up afterwards with well-informed, organized plans and communication.<\/p>\n\n\n\n

After learning several new technologies, I decided to put a little structure to this process of becoming well-informed. Here are the seven steps that I\u2019ve found to be useful guides.<\/p>\n\n\n\n

1. Identify & articulate a real problem to solve<\/h3>\n\n\n\n

Using a real-world problem helps frame and focus your learning.<\/p>\n\n\n\n

It\u2019s easier to learn a new technology by digging in, so if you don\u2019t have an immediate problem you need to solve for a project, invent one. If your problem is big, split it up into smaller parts to make the lessons more specific (and less intimidating).<\/p>\n\n\n\n

Each technology builds upon concepts of other technologies so try to subdivide it along clear functional lines. For example, let\u2019s say the problem is to add group notifications to a mobile app that doesn\u2019t have push notifications. You could split that big problem into three small problems that build on each other:<\/p>\n\n\n\n

    \n
  1. adding push notifications for individuals<\/li>\n\n\n\n
  2. adding grouping functionality<\/li>\n\n\n\n
  3. lastly adding push notifications for groups<\/li>\n<\/ol>\n\n\n\n

    Start by learning what you need to know to achieve the smaller pieces, then learn what you need to put it all together.<\/p>\n\n\n\n

    2. Create a roadmap<\/h3>\n\n\n\n

    Creating a knowledge roadmap will help narrow your focus so, once you\u2019ve started, you can keep your eyes on what you need to learn (not all the stuff you could learn).<\/p>\n\n\n\n

    Write down a list, a flow diagram, or even a full project plan that outlines the information you think you need to know to use the technology like a pro. This is your roadmap which you\u2019ll use to guide yourself through the learning process.<\/p>\n\n\n\n

    As you learn more, you\u2019ll refine this document, but having a rough structure in place right from the start allows you to be very clear about your priorities with yourself and others. Be honest with yourself about what you know and what you don\u2019t. Skipping a topic you think you need isn\u2019t taking a shortcut (it\u2019s taking a detour).<\/p>\n\n\n\n

    Sometimes you don\u2019t even know where to start with your roadmap. The Internet\u2019s got you covered; there are a ton of roadmaps out there. Find one that fits your career. Here are just a few examples:<\/p>\n\n\n\n