{"id":3163,"date":"2017-12-21T00:00:00","date_gmt":"2017-12-21T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/4-tips-for-keeping-your-resolution-to-learn-azure"},"modified":"2025-06-27T06:55:37","modified_gmt":"2025-06-27T13:55:37","slug":"4-tips-for-keeping-your-resolution-to-learn-azure","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/4-tips-for-keeping-your-resolution-to-learn-azure\/","title":{"rendered":"4 tips for learning Azure in the new year"},"content":{"rendered":"\n

It’s that time of year when many people take pride in the resolutions they met, lament the ones they failed to keep, and make new ones to start afresh. Recently, I spoke with a friend and former colleague who is a software developer at a technology company in Virginia. As we shared our plans for 2018, he told me about an unmet resolution he had for 2017, which was to learn Azure. He recalled that this resolution originated back in 2013. As is the case with most abandoned resolutions, he had plenty of reasons at the ready to defend himself. He even joked that he\u2019d keep the tradition alive by resolving to learn Azure in 2018.<\/p>\n\n\n\n

I suggested that part of his problem was with the resolution itself (the other being procrastination). For me, the notion of learning Azure triggers the snowclone that it \u201cis a journey, not a destination.\u201d Instead of trying to learn Azure like it was something fixed and finite, I said he should make his resolution to just learn something new about Azure each day. If he implemented that one change, he could be successful with this year\u2019s neglected resolution starting today.<\/p>\n\n\n\n

Here are the tips I shared with him to help him keep his resolution to learn Azure:<\/p>\n\n\n\n