The first responsibility that I had was to spruce up the automated test suite in a very narrow and specific aspect of the product. I was assigned a few basic tasks that would help me get familiar with the codebase, workflow, and product. I’ll rewind a little bit to give some context. I learned the most important lesson from him when he lied on stage at a huge Microsoft conference. ![]() He taught me so many things about how to help other people learn quickly.īut here’s the crazy part. I wrote about the most important one on Inc.com a little while back. Throughout my internship, I learned more than one powerful lesson while working with him. ![]() But he always took the time to make sure he put me on the right track and in a position to complete my assigned work. To be honest, I was intimidated by Ransom. I’d always see other senior developers knocking on his door to ask for advice. Ransom seemed to know everything about the codebase. He took me under his wing and accelerated my learning. I had a lot of people to thank, but the most important one was my mentor, Ransom. It was scary.īut by the end of my 6-month internship, I had turned myself into a contributing member of a high-performing team. I couldn’t have doubted myself any more than I did. Despite that, I was expected to help the dev team build a better product. I had to work in a codebase that spanned millions of lines of code and use a programming language that I was completely unfamiliar with. We were responsible for the internals of a distributed peer-to-peer network, and it was one of the most complex applications I’ve ever worked on. ![]() I was working on the Microsoft Office team. Early in my software engineering career, I had an internship at Microsoft.
0 Comments
Leave a Reply. |