<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blogs</title>
    <description>Blogger, Consultant, Technologist and Very Opinionated.</description>
    <link>https://blog.michaeldeongreen.com/</link>
    <atom:link href="https://blog.michaeldeongreen.com/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Tue, 16 Jun 2026 13:04:05 +0000</pubDate>
    <lastBuildDate>Tue, 16 Jun 2026 13:04:05 +0000</lastBuildDate>
    <generator>Jekyll v3.10.0</generator>
    
      <item>
        <title>Modernizing My Legacy OSS Project With GitHub Copilot And Claude Sonnet 4</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/modernizing-my-legacy-oss-project-with-github-copilot-and-claude-sonnet-4-001.jpg&quot; alt=&quot;Modernizing My Legacy OSS Project With GitHub Copilot And Claude Sonnet 4!&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Happy almost 2026!&lt;/strong&gt; It’s been a while since my last blog, and I’m excited to share something new. Recently, I’ve been exploring the world of &lt;em&gt;Vibe Coding&lt;/em&gt; and decided to write about my experience. Although I’ve been a Software Developer for many years, I only recently started actively using GitHub Copilot to assist with my projects. There’s been plenty of buzz about Vibe Coding and predictions that developers might soon be replaced en masse. This past weekend, I put GitHub Copilot to the test by modernizing and refactoring one of my old OSS projects. In this post, I’ll share what the project needed, how I approached it, and my thoughts on Vibe Coding and GitHub Copilot.&lt;/p&gt;

&lt;h1 id=&quot;oss-project-background&quot;&gt;OSS Project Background&lt;/h1&gt;

&lt;p&gt;The application I targeted for my Vibe Coding deep dive is a roughly 5-year-old .NET 5 ASP.NET Web Application. I originally built this app while working in engineering for two large Microsoft Media &amp;amp; Comms customers. It leverages a mix of technologies, including:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;ARM&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;ASP.NET Core&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Azure&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Bash&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Blazor&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;BlazorStrap&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Docker&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Terraform&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can find the project here: &lt;a href=&quot;https://github.com/azure-samples/eventgrid-viewer-blazor&quot;&gt;https://github.com/azure-samples/eventgrid-viewer-blazor&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The application allows users to view Azure EventGrid messages in real time, which is especially useful for observability and debugging scenarios.&lt;/p&gt;

&lt;p&gt;Previously, the app supported Entra ID authentication controlled by a feature flag and integrated with Azure Key Vault for secure secret management. I’ve temporarily removed this feature during the recent changes but plan to reintroduce it in the near future.&lt;/p&gt;

&lt;p&gt;I still receive questions about whether I’m maintaining this project, which made it an ideal candidate for a deep dive into Vibe Coding and modernization.&lt;/p&gt;

&lt;h1 id=&quot;what-needed-to-be-done&quot;&gt;What Needed to Be Done?&lt;/h1&gt;

&lt;p&gt;Initially, my goal was simple: update the BlazorStrap front end, upgrade the .NET version, and refresh the Azure EventGrid SDK. However, as I became more familiar with GitHub Copilot, it quickly became clear that I could go beyond these basic updates.&lt;/p&gt;

&lt;p&gt;I expanded the scope to include:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Adding &lt;strong&gt;robust logging&lt;/strong&gt; for better observability&lt;/li&gt;
  &lt;li&gt;Converting the app to use &lt;strong&gt;Azure Developer CLI&lt;/strong&gt; for streamlined workflows&lt;/li&gt;
  &lt;li&gt;Modernizing the &lt;strong&gt;documentation&lt;/strong&gt; for clarity and maintainability&lt;/li&gt;
  &lt;li&gt;Removing &lt;strong&gt;authentication features&lt;/strong&gt; (including Entra ID and Key Vault) to focus on building a clean &lt;strong&gt;Vibe Code MVP&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h1 id=&quot;how-did-i-go-about-it&quot;&gt;How Did I Go About It?&lt;/h1&gt;

&lt;p&gt;I started out using GPT-5, but in my experience, Claude Sonnet 4 felt more accurate and faster. The first step was having GitHub Copilot restructure the code so the application could run seamlessly in Visual Studio Code as well as Visual Studio, where it was originally built.&lt;/p&gt;

&lt;p&gt;Next, I asked Copilot to upgrade the .NET version and ensure all existing Unit Tests passed after the changes. I was pleasantly surprised by how efficiently AI handled this task. While it introduced breaking changes, Copilot iteratively resolved them, leaving me with code that compiled successfully.&lt;/p&gt;

&lt;p&gt;After that, I focused on updating the BlazorStrap front end—a task I had avoided in the past since front-end work isn’t my favorite. This was one reason I hadn’t maintained the project after leaving my previous engineering org. Copilot impressed me again: when stylesheet issues appeared, I described the problems conversationally, and it opened the app in a Simple Browser tab inside VS Code, let me select the problematic element, identified the CSS issues, and fixed them.&lt;/p&gt;

&lt;p&gt;Once the app compiled and ran, I turned to deployment. Initially, I followed the old manual steps, but then realized: &lt;em&gt;Why not modernize the deployment process with AI assistance?&lt;/em&gt; I merged the basic changes into the main branch and decided to convert the project to use Azure Developer CLI.&lt;/p&gt;

&lt;p&gt;Before starting that conversion, Copilot amazed me again by diagnosing and fixing a race-condition bug that had existed since the project’s inception. For the CLI migration, Copilot used the existing ARM template behind the “Deploy to Azure” button to generate Bicep files. It introduced a bug by setting the .NET version to “.NetFramework,” causing silent deployment failures. After providing detailed troubleshooting context, Copilot identified and fixed the issue.&lt;/p&gt;

&lt;p&gt;With the CLI conversion complete, I added basic logging, cleaned up and modernized documentation, and removed unused artifacts. I also asked Copilot to strip out all Entra ID authentication code so I could focus on the conversion in a dedicated feature branch.&lt;/p&gt;

&lt;p&gt;Throughout the process:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Copilot ran Unit Tests after each change.&lt;/li&gt;
  &lt;li&gt;I reviewed most generated code and asked for explanations when implementations weren’t clear.&lt;/li&gt;
  &lt;li&gt;When I requested logging, Copilot initially defaulted to Serilog and produced unnecessary code. I rolled back and had it implement built-in .NET Core Logging instead.&lt;/li&gt;
  &lt;li&gt;Similarly, Copilot assumed MSTest for unit tests but adapted to xUnit after clarification.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Eventually, I merged the changes into the main branch once I was confident I could explain every modification.&lt;/p&gt;

&lt;h3 id=&quot;summary-of-changes&quot;&gt;Summary of Changes&lt;/h3&gt;
&lt;ul&gt;
  &lt;li&gt;Updated &lt;strong&gt;.NET 5 → .NET 9&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Updated &lt;strong&gt;BlazorStrap 1 → 5&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Updated &lt;strong&gt;Azure EventGrid SDK 1 → 3&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Fixed a pre-existing &lt;strong&gt;race condition&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Migrated to &lt;strong&gt;Azure Developer CLI&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Updated &lt;strong&gt;ARM templates&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Updated (and later removed) &lt;strong&gt;Bash scripts&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Updated &lt;strong&gt;Unit Tests&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Removed unused artifacts&lt;/li&gt;
  &lt;li&gt;Implemented &lt;strong&gt;logging&lt;/strong&gt;&lt;/li&gt;
  &lt;li&gt;Modernized &lt;strong&gt;documentation&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h1 id=&quot;what-are-my-overall-thoughts&quot;&gt;What Are My Overall Thoughts?&lt;/h1&gt;

&lt;p&gt;After spending the weekend exploring &lt;strong&gt;Vibe Coding&lt;/strong&gt;, I was completely blown away by what an AI assistant can do. I started as a skeptic, but this experience changed my perspective—I can’t imagine developing without a solution like &lt;strong&gt;GitHub Copilot&lt;/strong&gt; going forward.&lt;/p&gt;

&lt;h3 id=&quot;key-observations&quot;&gt;Key Observations&lt;/h3&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Technical skill still matters.&lt;/strong&gt; I had to guide and correct Copilot, have an understanding of the .NET ecosystem, apply SOLID principles, and recognize what clean code looks like.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;AI encouraged risk-taking.&lt;/strong&gt; Normally, I would have stuck to the original goal—updating libraries and ensuring the solution compiled. With Copilot, I confidently expanded the scope, even converting the project to use Azure Developer CLI.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Shift in IDE preference.&lt;/strong&gt; I’ve always considered Visual Studio superior for C# development due to debugging and IntelliSense. With Copilot integrated into VS Code, that advantage disappeared. I’ll likely use VS Code exclusively unless a client requires Visual Studio.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Control and transparency.&lt;/strong&gt; I felt in control throughout the process. Copilot answered questions about its decisions, and most explanations were clear and sufficient.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;AI as a “large dog on a leash.”&lt;/strong&gt; Copilot is powerful but needs careful instruction from someone who understands the task. Without guidance, it can produce overly complex “slop” code that’s hard to justify in a code review.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;final-thoughts&quot;&gt;Final Thoughts&lt;/h3&gt;
&lt;p&gt;This experience reinforced that &lt;strong&gt;AI coding assistants are the future&lt;/strong&gt;. Copilot accelerated the ideation-to-implementation loop, letting me focus on architecture and business logic rather than boilerplate. It has undoubtedly made me a better developer.&lt;/p&gt;

&lt;p&gt;For those still skeptical, consider what Jensen Huang of NVIDIA said:&lt;/p&gt;
&lt;blockquote&gt;
  &lt;p&gt;&lt;em&gt;“AI will not take your job, but a person who uses AI will.”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I encourage my fellow technical colleagues to heed those words and act accordingly.&lt;/p&gt;
</description>
        <pubDate>Tue, 04 Nov 2025 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/technology/2025/11/04/modernizing-my-legacy-oss-project-with-github-copilot-and-claude-sonnet-4.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/technology/2025/11/04/modernizing-my-legacy-oss-project-with-github-copilot-and-claude-sonnet-4.html</guid>
        
        <category>AI</category>
        
        <category>Claude Sonnet 4</category>
        
        <category>GitHub Copilot</category>
        
        <category>Microsoft</category>
        
        <category>Modernization</category>
        
        
        <category>technology</category>
        
      </item>
    
      <item>
        <title>Transitioning From Software Engineer to Partner Technology Strategist Part 2</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/2023-04-01-transitioning-from-software-engineer-to-partner-technology-strategist-part-1-001.jpg&quot; alt=&quot;Transitioning From Software Engineer to Partner Technology Strategist Part 2!&quot; /&gt;&lt;/p&gt;

&lt;p&gt;In &lt;a href=&quot;https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html&quot;&gt;part 1&lt;/a&gt; of my series about transitioning from Software Engineer to Partner Technology Strategist (PTS), I spoke about some of the challenges I have faced in the 1.5 years I have been in the new role.&lt;/p&gt;

&lt;p&gt;In part 2 of this series, I want to get a little vulnerable and discuss how in 2023, I really struggled mentally in the Technology Strategist role and the strategies I implemented to find enjoyment and overcome the challenges of the role.&lt;/p&gt;

&lt;h1 id=&quot;caveat&quot;&gt;Caveat&lt;/h1&gt;

&lt;p&gt;The views that I discuss in this blog post are my own and they are based upon my own experiences.  My hope in writing this blog is to share my experiences with others, in hopes that it will provide insight and guidance to those who plan too or are currently transitioning from Software Engineer to a Technology Strategist.&lt;/p&gt;

&lt;h1 id=&quot;getting-vulnerable&quot;&gt;Getting Vulnerable!&lt;/h1&gt;

&lt;p&gt;In &lt;a href=&quot;https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html&quot;&gt;part 1&lt;/a&gt;, I discussed why the Partner Technology Strategist (PTS) role can be extremely challenging and how many aspects of the role are the opposite of what I had been doing as a Software Engineer.  In 2023, the role really started to wear me down mentally and by the Summer of 2023, I had gotten to the point where I was completely burnt out.  My sleep issues started to worsen, I had a few dizzy spells, and I was constantly fatigued, anxious, fearful and stressed out.&lt;/p&gt;

&lt;p&gt;Surprisingly enough, a blessing in disguise came my way via an adult Tonsillectomy.  I was diagnosed with &lt;a href=&quot;https://www.hopkinsmedicine.org/health/conditions-and-diseases/obstructive-sleep-apnea&quot;&gt;Obstructive Sleep Apnea&lt;/a&gt; a few years ago and &lt;a href=&quot;https://www.mayoclinic.org/diseases-conditions/tmj/symptoms-causes/syc-20350941&quot;&gt;TMJD&lt;/a&gt; last year.  Towards the end of the Summer, my Sleep Apnea and TMJ physician told me that I needed to have my tonsils removed before he would begin treatment.  After getting numerous second opinions and ruminating over the surgery, I decided to get the Tonsillectomy, which forced me to take 3 weeks off work.&lt;/p&gt;

&lt;p&gt;While recovering from the surgery, I discovered that many of the symptoms that I had suffered leading up to the surgery were virtually gone, despite only getting 1-2 hours of sleep a night the first few days after the surgery due to the pain.&lt;/p&gt;

&lt;p&gt;It was at this point that I had an epiphany and realized that the PTS role was really diminishing my quality of life.  The engineer in me immediately started to first contemplate “why” was the role having these effects on me and then implement a strategy to overcome these challenges.&lt;/p&gt;

&lt;p&gt;After much contemplation, along with the issues I spoke about in &lt;a href=&quot;https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html&quot;&gt;part 1&lt;/a&gt;, I identified a few other reasons why the role was having such a negative effect on me:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;I was constantly concerned with getting promoted to Principal.  So, there was a constant focus on what others thought of me.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;I was constantly concerned about being fired or laid off.  I had a hard time figuring out what metrics I was being judged by and Microsoft was having layoffs.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;I was constantly concerned with everyone else’s opinion on what I should be doing with my Partners.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;During my 3 weeks off, after recognizing the above bullet points &lt;em&gt;(whether real or imagined)&lt;/em&gt;, I made a vow to immediately stop being concerned about all 3 of these issues.  Furthermore, I decided to implement strategies to manage the stress and ambiguity that is inherent to the role.  I no longer concern myself with promotions, I no longer worry constantly about losing my position and the way I handle unsolicited advice is completely different than I did in the past.  Once I did this, a lot of the stress and anxiety diminished significantly and it was extremely “freeing” to not consistently worry about these things, some of which I freely admit in hindsight, were not grounded in reality.&lt;/p&gt;

&lt;h1 id=&quot;managing-the-stress--ambiguity&quot;&gt;Managing the Stress &amp;amp; Ambiguity&lt;/h1&gt;

&lt;p&gt;Next, I want to talk about the strategies I implemented to manage the stress and ambiguity that just comes along with the PTS role.&lt;/p&gt;

&lt;h2 id=&quot;understand-the-microsoft-landscape&quot;&gt;Understand the Microsoft Landscape!&lt;/h2&gt;

&lt;p&gt;Microsoft is a very big organization that is filled with seemingly endless organizations and roles.  I started to spend a lot more time understanding the organizations that I worked with and what were the core priorities of the roles within those organizations.  In &lt;a href=&quot;https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html&quot;&gt;part 1&lt;/a&gt; of this series, I talked about how I interface with a lot of people inside of Microsoft and I have no direct reports.  To continue, I spoke about having to constantly &lt;em&gt;“influence without authority”&lt;/em&gt;.  I started to understand that to influence the people around me, I had to understand their role and what motivated them.  Once I was able to do this, I was able to view things from &lt;em&gt;“their”&lt;/em&gt; perspective and this allows me to be in a better position to influence.&lt;/p&gt;

&lt;h2 id=&quot;recognize-and-manage-patterns&quot;&gt;Recognize and Manage Patterns!&lt;/h2&gt;

&lt;p&gt;In Software Engineering, there are tons of documented design patterns that help solve difficult engineering problems.  In the PTS role, I found out that there were &lt;em&gt;anti-patterns&lt;/em&gt; of behavior that continually surfaced and recognizing them helps manage the behavior, which if it goes unchecked, can increase stress.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Dial-a-PM Pattern:&lt;/strong&gt; The Dial-a-PM pattern is typically employed by the Microsoft Partner.  Some Partners may take the view that they do not want to share roadmaps and they don’t want to engage in co-innovation with Microsoft.  The partner that behaves in this manner will typically only care about support and access to the various Microsoft Product Groups.  Typically, they will ask the Technology Strategist to be put in contact with various Program Managers inside of Microsoft, hence the term “Dial-a-PM”.  This behavior is problematic because there isn’t a strategy, the Technology Strategist is “randomized”, it isn’t a real “partnership” and thus, greatly increases the stress level when interacting with the Partner.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Inbox Pattern&lt;/strong&gt;: The Inbox pattern is typically employed by my colleagues within Microsoft and specifically, the ones that work with the customers of my Partner.  What typically happens is that people will find out that the PTS works with a Partner, in my case, a Global Independent Software Vendors (GISV) and they will immediately start including the PTS in tons email (hence, the name Inbox Pattern) and Teams threads, of which, many of the topics are outside of the responsibilities of the PTS role.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Push-Push Pattern&lt;/strong&gt;: The PTS is responsible for helping to craft the technical strategy for a Microsoft Partner.  I believe that the PTS should spend time listening to what the Partner states is important and align these goals with those of Microsoft.  The PTS should do this by consistently &lt;strong&gt;“pushing”&lt;/strong&gt; to get the Partner to follow through on their stated goals.  Also, I believe that Microsoft leadership should support the PTS by &lt;strong&gt;“pulling”&lt;/strong&gt; in the Partner when there are serious technical or business challenges that are preventing business objectives from being realized.  However, on many occasions, a PTS will observe not a &lt;em&gt;“Push-Pull”&lt;/em&gt; pattern with regards to the PTS and Microsoft leadership but a &lt;em&gt;“Push-Push”&lt;/em&gt; Pattern.  What I mean by this is that many of the people who work for our Partners are ex-Microsoft employees who have established relationships with some in leadership positions at Microsoft.  The Partner will sometimes go above the PTS and straight to leadership &lt;em&gt;(to push)&lt;/em&gt; to get answers and/or advice, which can undermine the PTS and, in some cases, the advice received can be counter to what the PTS would have advised as the PTS is working with the Partner on a week-to-week basis and has better context.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;getting-ahead-of-patterns-stress--ambiguity&quot;&gt;Getting Ahead of Patterns, Stress &amp;amp; Ambiguity&lt;/h2&gt;

&lt;p&gt;Outside of the strategies already mentioned and recognizing typical patterns when working with Microsoft Partners, below are some of the other strategies that I am employ:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Set expectations upfront:&lt;/strong&gt; When I start to work with a Partner and the internal Microsoft team, I set expectations upfront.  I educate everyone about what a PTS does and what my core objectives are.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Focus on Strategy:&lt;/strong&gt; I’ve been a PTS for about 2 years.  When I changed roles, I spent a lot of time being &lt;strong&gt;“tactical”&lt;/strong&gt; and &lt;strong&gt;“reactive”&lt;/strong&gt; &lt;em&gt;(I didn’t know any better)&lt;/em&gt;, which gave me very little time to focus on technical strategy.  I had a very hard time saying &lt;em&gt;“no”&lt;/em&gt; to people and the result was burnout.  Now, since I have a very keen understanding of everyone else’s role, I can point people to the right role to get answers that are outside of the scope of the PTS position.  Furthermore, a consistent focus on strategy prevents &lt;strong&gt;“randomization”&lt;/strong&gt; and allows more time to be spent focusing on Microsoft and the Partner’s core goals &lt;em&gt;(stated verbally, in financial earnings reports etc. etc.)&lt;/em&gt; and this puts me in a better position to provide guidance on technical strategy.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Be ruthless with my time:&lt;/strong&gt; When I first started in the PTS role, I would always accept meeting invites, regardless of the meeting topic.  Many of the meetings were reactive and didn’t focus on core objectives.  Now, when I get meeting invites, I either decline or select &lt;em&gt;“maybe”&lt;/em&gt;, if it is unclear what is going to be discussed.  Spending time in meetings that didn’t move the needle on core objectives resulted in randomization, stress and a feeling of &lt;strong&gt;“busy”&lt;/strong&gt; work with no strategic outcomes.  Furthermore, if it is a meeting that is crucial to core objectives, but I am not able to attend, I will politely ask the team to record the meeting and I will watch the recording later.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Accept that everyone has an opinion:&lt;/strong&gt; One of the areas that I struggle with &lt;em&gt;(in my personal life as well)&lt;/em&gt; is unsolicited and often uninformed opinions.  The Partners that I work with are large and have global reach, so it isn’t a surprise that people are going to have very strong opinions about what &lt;em&gt;“should”&lt;/em&gt; be happening with regards to working with the Partners.  I observed in meetings that people would propose solutions that were already being solved or suggest things that weren’t appropriate due to not having the full context.  Now, I accept that everyone is going to have an opinion, this is not going to change, and I must focus on how &lt;strong&gt;“I react”&lt;/strong&gt; to these opinions.  I found that if I am employing the &lt;em&gt;“Push-Pull”&lt;/em&gt; pattern effectively with regards to me and leadership, and I am consistently focusing on technical strategy, I am in a strong position to educate and provide better context when opinions surface in meetings.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Embrace ambiguity:&lt;/strong&gt; Historically, I have been the type of person who shuns ambiguity and is more comfortable with tangible and well-crafted goals.  As stated already, the PTS role is the complete opposite.  Impact, objectives and goals can be very ambiguous and change on a quarterly basis.  I have had to step out of my comfort zone and accept that this just comes with any strategy role, and I had to learn to be flexible and develop the ability to context switch.  Since I consistently focus on strategic goals, instead of being annoyed by the changing landscape, I can ask the Partner (or Microsoft) about priorities, to ensure alignment, which in turn, ensures that we are both working on stated goals, and this gives me the appropriate level of comfort to manage the ambiguity that comes with the role.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;Opportunity Cost:&lt;/strong&gt; When I left Software Engineering for a Strategy role, I was completely obsessed with losing my technical edge i.e. the cost of focusing on strategy at a cost of losing my Software Engineering acumen.  I spent a lot of time trying to figure out how to maintain deep technical skills and grow as a strategist.  Honestly, I had to just accept the fact that yes, I would lose my deep Software Engineering skills because I am not doing it every day and these skills were not as valuable to my Partners in a Technology Strategy role.  I still create POCs, write code and upskill when I have time, but I now take the view of &lt;strong&gt;“I am not losing my technical edge, I am gaining new skills that is allowing me to grow and get out of my comfort zone.”&lt;/strong&gt;&lt;/p&gt;

    &lt;p&gt;Furthermore, the Technology Strategist role is technical, however, it is a focus on other aspects of technology.  For example, one of my first Microsoft Partners was &lt;a href=&quot;https://www.redis.com/&quot;&gt;Redis&lt;/a&gt;.  I was explaining to a fellow Software Engineer that if I was back in Software Engineering, I would focus on Redis SDKs and best practices on implementing Redis Cache from a Software Engineering standpoint.  However, as a strategist, I am more focused on what technical problems Redis solves, what differentiates Redis from competitors (pricing, region availability, performance, availability etc. Etc.) and what should Redis do next to provide better value to their customers and increase their market share.  I must be technical, and my technical background helps me to better understand these problems and how to come up with a competent strategy to solve some of these issues.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h1 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h1&gt;

&lt;p&gt;In part 2 of this blog series, I wanted to shed some light on some of my struggles transitioning from Software Engineering to Technical Strategy.  I also wanted to outline in detail some of the many strategies I am employing to help ease the transition.  I have been in the Technical Strategy role for about 2 years, and I learn something new every single week.  But because I have started to recognize &lt;em&gt;“anti-patterns”&lt;/em&gt; and started to implement strategies to reduce the stress and ambiguity of the role, it has been very rewarding.  I now have more time to be hands-on, focus on Microsoft and Partner products and the above has allowed me to be less anxious, fearful, worried and more confident.  This has led to the ability to more easily develop technical strategies and to be able to articulate my ideas across Microsoft and the Partners that I work with.&lt;/p&gt;

&lt;p&gt;I am no longer worried about promotions, being laid off and the constant stream of unsolicited opinions about what my Partner should be doing.  Since I am technically &lt;em&gt;(no pun intended)&lt;/em&gt; captaining my own ship, working with Partners weekly, and thus have a good contextual grasp at any given moment, I let these facts guide my work and I let my outcomes speak for themselves and cease to borrow problems from the future.  The strategies that I have discussed in this blog post may not work for everyone because everyone is different.  However, I hope that this blog post will be able provide some value for those who are moving from a 100% hands-on Software Engineering to a role focused on technical strategy.&lt;/p&gt;
</description>
        <pubDate>Sat, 17 Feb 2024 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2024/02/17/transitioning-from-software-engineer-to-partner-technology-strategist-part-2.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2024/02/17/transitioning-from-software-engineer-to-partner-technology-strategist-part-2.html</guid>
        
        <category>Microsoft</category>
        
        <category>Strategy</category>
        
        <category>Technology</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>Transitioning From Software Engineer to Partner Technology Strategist Part 1</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/2023-04-01-transitioning-from-software-engineer-to-partner-technology-strategist-part-1-001.jpg&quot; alt=&quot;Transitioning From Software Engineer to Partner Technology Strategist Part 1!&quot; /&gt;&lt;/p&gt;

&lt;p&gt;In this blog post, I wanted to take the time to discuss my recent transition from a Software Engineering role to a Partner Technology Strategist (PTS) role here at Microsoft.  I have been in this new role for roughly 1.5 years, so this is a perfect time to share my experiences as it might help others who may be considering a similar career move.  This blog entry will primarily focus on some of the challenges I have faced while transitioning to the new role.  I plan to create follow-up blogs that discuss how rewarding the role has been for me, how the role has allowed me to grow and some strategies that can be implemented to ease the transition.&lt;/p&gt;

&lt;h1 id=&quot;why-the-role-change&quot;&gt;Why the Role Change?&lt;/h1&gt;

&lt;p&gt;Since graduating in May 2001, I have primarily worked as a Software Engineer &lt;em&gt;(LinkedIn profile &lt;a href=&quot;https://www.linkedin.com/in/michael-d-green/&quot;&gt;here&lt;/a&gt;)&lt;/em&gt;.  As I progressed through my career, I would wear many hats, such as Software Engineer, SCRUM Master, Consultant, Lead Engineer, Software Architect etc. etc., however, my primary role was always a hands-on Software Engineer.&lt;/p&gt;

&lt;p&gt;A big part of the culture here at Microsoft is having a &lt;em&gt;Learn It All&lt;/em&gt; mindset and allowing individuals to move to different roles, to grow their career.  At Microsoft, I started out as a Software Engineer in the Commercial Software Engineering (CSE) organization.  As I increasingly worked with large Microsoft Partners/Customers, I started to feel that after over two decades of being a Software Engineer, I could provide more value by combining my &lt;a href=&quot;https://en.wikipedia.org/wiki/Emotional_intelligence&quot;&gt;EQ&lt;/a&gt; and technical skills to help shape an organization’s overall technical strategy.&lt;/p&gt;

&lt;p&gt;When a friend, mentor and someone who has been extremely influential in my career at Microsoft left CSE, to become &lt;a href=&quot;https://www.linkedin.com/in/jeremiahtalkar&quot;&gt;CTO&lt;/a&gt; of Microsoft’s Global Partner Solutions organization, he encouraged me to interview for a role in the organization he was building (The Global ISV Tech Team), as he felt I would be a good fit and the rest is history.&lt;/p&gt;

&lt;h1 id=&quot;what-is-a-partner-technology-strategist&quot;&gt;What is a Partner Technology Strategist?&lt;/h1&gt;

&lt;p&gt;A Partner Technology Strategist (PTS) focuses on three major areas, and these areas just happen to be the three words in the role name.  The PTS works with &lt;strong&gt;&lt;em&gt;Partners&lt;/em&gt;&lt;/strong&gt; to understand how both Microsoft and the Partner’s &lt;strong&gt;&lt;em&gt;Technology&lt;/em&gt;&lt;/strong&gt; can be integrated to be mutually beneficial to both organizations.  As The PTS develops this deeper understanding, the expertise will be used to develop a &lt;strong&gt;&lt;em&gt;Strategy&lt;/em&gt;&lt;/strong&gt; to realize the goals of both Microsoft and the Partner.  The PTS owns the entire technical relationship with the Microsoft Partner and a major goal is to be viewed as a Trusted Advisor (TA), and eventually, a CTO.&lt;/p&gt;

&lt;h1 id=&quot;challenges&quot;&gt;Challenges?&lt;/h1&gt;

&lt;p&gt;Making the transition from Software Engineer to Technology Strategist has been rewarding &lt;em&gt;(which I will discuss in a later blog entry)&lt;/em&gt; but it has certainly come with its many challenges.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Perceived Effectiveness!:&lt;/em&gt;&lt;/strong&gt; In the role of Software Engineer, how effective I was at doing my job was objective and easy to identify.  My manager and peers can perform code reviews on my work, they can see the features that I was working on and through consistent interaction, such as architecture design reviews and backlog grooming, the engineering team could observe my competency level.&lt;/p&gt;

&lt;p&gt;In the PTS role, the goals can often take months &lt;em&gt;(maybe even years)&lt;/em&gt; to be realized due to the complexity of the working environment.  The PTS must build trust with the Partner, have a solid understanding of both Microsoft and the Partner’s goals and technology. Also, because the PTS is focusing on the overall technical roadmap for a Partner, the PTS must work with several decision makers, both within Microsoft and the Partner to &lt;em&gt;move the needle&lt;/em&gt;.  Due to this type of complexity, it is a lot more difficult to measure the effectiveness of a PTS.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Time Management!:&lt;/em&gt;&lt;/strong&gt; As a Software Engineer, I spent most of my time writing code or pondering how I would design and implement a solution.  I did attend meetings but most of the meetings were planned i.e., SCRUM, Sprint Planning, Design Reviews etc etc and with a regular cadence.  Also, in most cases, if a decision needed to be made, it was typically a Lead Engineer &lt;em&gt;(in some cases, that was me)&lt;/em&gt; or the Product Owner &lt;em&gt;(in some cases, a Business Analyst serving as a proxy)&lt;/em&gt;, which were very accessible.&lt;/p&gt;

&lt;p&gt;In the PTS role, I often view things at an organizational level, and I must meet the needs of at least two organizations, Microsoft, and the Partner.  As a PTS, I spend a lot of time having to meet with several decision makers, who themselves have limited time, influencing without authority and bringing different resources together to help drive technical strategy and solve problems.  All the above takes time and because of this, I have had to develop strong time management skills, avoid being randomized and learn which items to prioritize and dedicate most of my time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Learning to Say No!:&lt;/em&gt;&lt;/strong&gt;  As a Software Engineer, I had to tell people no a few times but for the most part, that was the job of the Product Owner.  The Product Owner worked with the engineering team to groom and prioritize the Product Backlog and indirectly, the Product Backlog would be used to determine when a feature was going to be implemented.&lt;/p&gt;

&lt;p&gt;As a PTS, I am constantly pulled in several directions and there are constant attempts to randomize my day &lt;em&gt;(not on purprose of course)&lt;/em&gt;.  Co-workers that are working with the customers of my Partner will ask me for my time, my Partner will ask me for my time and my manager, and my teammates will ask me for my time.  I found out very quickly that if I did not learn to say no, I would burn out in the PTS role very quickly.  I had to learn that &lt;em&gt;No&lt;/em&gt; was not necessarily a bad word because there just is not enough time in a day to accomplish everything and in the words of a mentor, &lt;em&gt;“In the PTS role, you will absolutely drop something, you just have to figure out the items that cannot be dropped.”&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Influence Without Authority!:&lt;/em&gt;&lt;/strong&gt;  As a Software Engineer, I typically worked with the same 10-15 people every day, even when I was a consultant.  In Software Engineering, I did not spend a lot of time trying to influence people and when I did, it was typically the same small group of people i.e. what framework to use, design patterns etc. etc.  In Software Engineering, you typically know &lt;em&gt;what&lt;/em&gt; feature to implement, however, discussions tend to focus on &lt;em&gt;how&lt;/em&gt; the feature is implemented.&lt;/p&gt;

&lt;p&gt;As a PTS, I easily meet 2-3 new people every single week.  I must scale both Microsoft and my Partner’s organization, to find decision makers and resources that can answer specific questions &lt;em&gt;(you will never have all the answers)&lt;/em&gt;.  Also, as stated already, co-workers that are working with the customers of my Partner will seek me out because I may have the answers they are looking for.  I am an individual contributor, which means I have no direct reports, so I must &lt;em&gt;influence without authority&lt;/em&gt; and manage the different personalities and objectives of the people I work with.&lt;/p&gt;

&lt;p&gt;I had to understand very quickly that it was imperative to understand the roles of the people I meet and most importantly, how they are measured by their leadership.  Understanding the answers to these questions helps to &lt;em&gt;influence without authority&lt;/em&gt; because I gain insight into what motivates them, which in turn, helps to align common objectives.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Learning How to Depend on Others!:&lt;/em&gt;&lt;/strong&gt;  As a Software Engineer, I certainly had to depend on other people from time to time, to be effective at my job.  However, the number of people that I needed to depend on was small and the areas where I depended upon others were very narrow.  I depended upon teammates to review code, provide expertise around a certain technology stack or concept in which another engineer might be more knowledgeable (i.e. design patterns, frameworks, DevOps etc. etc.).&lt;/p&gt;

&lt;p&gt;As a PTS, my scope is at the Microsoft and Partner level.  My Partner could ask me anything from Azure Blob Storage, Azure Purview, OpenAI or why they are not able to deploy their SaaS solution into a certain Azure Region.  And on the Microsoft-side, my co-workers could ask me random questions such as what industry my Partner is targeting, would the Partner be interested in integrating with a new Microsoft product or how redundancy is implemented in my Partner’s product.&lt;/p&gt;

&lt;p&gt;Due to this complexity and the fact that I cannot possibly know everything, I tend to have to depend more on others than I did in Software Engineering.  I have had to learn that sometimes; it is okay if my only contribution to solving a problem is that I found the right person who did have the answers to a particular problem.&lt;/p&gt;

&lt;h1 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h1&gt;

&lt;p&gt;The decision to switch from a Software Engineering role to the role of a Partner Technology Strategist has presented new challenges.  With any new role change, I have had to adapt, grow, and learn new skills.  I have learned to play the &lt;em&gt;long game&lt;/em&gt;, better time management, understand that I will not be able to say &lt;em&gt;yes&lt;/em&gt; to everyone, become better equipped to influence others without authority and understand that it is okay to lean on others to solve complex problems.&lt;/p&gt;

&lt;p&gt;In this blog entry, I focused on the challenges that I have faced as I transitioned to the new role.  In my next blog, I want to spend time discussing how rewarding the role of a Technology Strategist has been for my personal growth and my overall career.&lt;/p&gt;
</description>
        <pubDate>Sat, 01 Apr 2023 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2023/04/01/transitioning-from-software-engineer-to-partner-technology-strategist-part-1.html</guid>
        
        <category>Microsoft</category>
        
        <category>Strategy</category>
        
        <category>Technology</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>Don&apos;t Let Impostor Syndrome Ruin Your Career Like I Almost Did!</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/2021-10-23-dont-let-impostor-syndrome-ruin-your-career-like-i-almost-did-001.jpg&quot; alt=&quot;Don&apos;t Let Impostor Syndrome Ruin Your Career Like I Almost Did!&quot; /&gt;&lt;/p&gt;

&lt;p&gt;In this blog post, I wanted to talk about &lt;a href=&quot;https://en.wikipedia.org/wiki/Impostor_syndrome&quot;&gt;impostor syndrome&lt;/a&gt;, which is a subject that is deeply personal and something that has had a very detrimental effect on my professional career growth.&lt;/p&gt;

&lt;p&gt;I have waited roughly 7 years to write this particular blog due to shame, guilt and worry about how colleagues and potential employers would perceive me after reading about my experiences with impostor syndrome.&lt;/p&gt;

&lt;p&gt;But alas, time tends to heal most things, with some slight nudging from some colleagues and the fact that it has been about 7 years since an incident occurred that almost ruined my professional career due to impostor syndrome, it is time to write this blog entry.&lt;/p&gt;

&lt;h2 id=&quot;imposter-syndrome&quot;&gt;Imposter Syndrome?&lt;/h2&gt;

&lt;p&gt;So what is impostor syndrome?  According to Wikipedia, &lt;a href=&quot;https://en.wikipedia.org/wiki/Impostor_syndrome&quot;&gt;impostor syndrome&lt;/a&gt; is:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;Impostor syndrome is a psychological pattern in which an individual doubts their skills, talents, or accomplishments and has a persistent internalized fear of being exposed as a “fraud”.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Wikipedia goes on to say:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;Despite external evidence of their competence, those experiencing this phenomenon remain convinced that they are frauds and do not deserve all they have achieved.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The above quotes can basically sum up my experiences since my college days, most likely dating even further back than that.  As the quotes suggests, no matter how much tangible evidence is right before my eyes that I am in fact a competent technologist, there is always that doubt in the back of my mind that somehow I have fooled the IT world for several years.&lt;/p&gt;

&lt;p&gt;Furthermore, not only have I managed to fool everyone, but I am only a new job or role away before the &lt;strong&gt;impostor&lt;/strong&gt; police arrive at my door, arrest me and carry me off to the mythical land of frauds.&lt;/p&gt;

&lt;h2 id=&quot;early-history-of-impostor-syndrome&quot;&gt;Early History of Impostor Syndrome&lt;/h2&gt;

&lt;p&gt;My history of believing that I am an impostor goes back pretty far and it is something I have carried with me to varying degrees throughout my career in IT.  I remember talking to some friends in college about what majors we were going to choose.  One of my friends said he was going to either do Computer Science or Information Systems and I remember thinking, “Yeah, I probably won’t go that route, those are for the smart people”.
After switching my major from Accounting to Management Information Systems, I remember I was leaving the Business Administration building one Friday evening and there was a group of students that were members of one of my college’s organizations &lt;a href=&quot;https://mavorgs.campuslabs.com/engage/organization/aitp&quot;&gt;AITP&lt;/a&gt; asking people to come to their weekly meetings.&lt;/p&gt;

&lt;p&gt;As usual, two thoughts popped in my mind.  The first thought was, “This would be a great way to network, meet like minded people and since they have professional speakers each week, I might just find a job”.  But unfortunately, the all too familiar thought of “You are not as smart as those people, don’t even think about attending” crept in my mind.  Fortunately, one of my friends was with me and he told me he was going to go so I ended up going with him.  Not only did I join, I ended up being elected to Publicity Chair, Vice President and then President of AITP (and of course, that took some convincing for me to run for those offices as well).&lt;/p&gt;

&lt;p&gt;I use the word “fortunate” for a few reasons when I talk about this decision.  First, one of the people I met in AITP, my good friend &lt;a href=&quot;https://www.linkedin.com/in/josh-littrell/&quot;&gt;Josh Littrell&lt;/a&gt;, literally helped me get my first and third job out of college.  The first job, he was trying to replace himself and the third job, he was the actual hiring manager, hence the AITP motto “Join us now or work for us later”.&lt;/p&gt;

&lt;p&gt;Second, the decision to go to the AITP meeting would lead to me being able to demonstrate that I was just as smart as all the other people in my major and allowed me to cultivate leadership skills that I still use to this very day.&lt;/p&gt;

&lt;h2 id=&quot;the-height-of-impostor-syndrome-insanity&quot;&gt;The Height of Impostor Syndrome Insanity&lt;/h2&gt;

&lt;p&gt;2014 was the year where impostor syndrome almost sunk my professional career.  I was talking to a friend of mine over email one day about what could possibly be next for me, from a career standpoint.  He mentioned a company called &lt;a href=&quot;https://www.thoughtworks.com/&quot;&gt;ThoughtWorks&lt;/a&gt; and he thought it might be a good move for me.  I had never heard of ThoughtWorks, so after doing research, it didn’t take long to understand that this was one of the top consulting companies in the world and many times, voted as one of the hardest companies to get into.&lt;/p&gt;

&lt;p&gt;I felt ThoughtWorks would be a great place to work as they seemed to hold a lot of the ideals I personally believe in but of course, impostor syndrome kicked in and I begin to have very serious doubts about being good enough to join a company such as this.&lt;/p&gt;

&lt;p&gt;Depending upon how you look at it, my first mistake (could be argued that having doubt was my first) is that I made a deal with my impostor syndrome.  The deal was, “Well, you are not good enough to get into ThoughtWorks, so let’s just go through the interview process, where surely I will get destroyed and use it to get information about the interview process and re-apply in a year”.&lt;/p&gt;

&lt;p&gt;The ThoughtWorks interview process is pretty intense (I discuss my experience in the blog &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2014/05/18/my-interview-with-thoughtworks.html&quot;&gt;My Interview with ThoughtWorks&lt;/a&gt;) but surprisingly enough, I was able to get through the various stages of the interview process (with some hiccups).  One would think as I got past each stage, the feeling of being a fraud would slowly disappear but unfortunately, the opposite occurred.  The further along in the interview process I got, the more unqualified I felt.  I remember after my last interview, the recruiter told me as I was walking out the door that they were going to make me an offer but I remember thinking to myself “Man, yeah right, I’ll see you all next year when I get a little more skill and interview again”.&lt;/p&gt;

&lt;p&gt;And of course the recruiter was correct, ThoughtWorks ended up making me an offer.  ThoughtWorks sends new employees to Chicago for a week for orientation.  In my class, there were folks with Stanford degrees, PhDs and &lt;a href=&quot;https://en.wikipedia.org/wiki/Deborah_Berebichez&quot;&gt;Dr. Debbie Berebichez&lt;/a&gt; was in my class, who already had a TED Talk under her belt.  After seeing the caliber of people in my class, my impostor syndrome kicked into full gear and it was really only a matter of time before I would self-select, buckle under the self-doubt and quit.&lt;/p&gt;

&lt;p&gt;Fast Forward I believe 1.5 months and I am working for ThoughtWorks at their Addison, TX location.  I had not yet joined a project because they are very careful about what project they put new people on.  ThoughtWorks just had a ton of smart people and everyday I interacted with my colleagues, I just felt like a fraud.  The recruiter would tell me that this was normal and even gave me stories of folks who were rock stars now that had huge self doubt early in their ThoughtWorks career.&lt;/p&gt;

&lt;p&gt;Unfortunately, despite ThoughtWorks being where I first started blogging (which my first ever blog and profile can still be found &lt;a href=&quot;https://www.thoughtworks.com/en-us/insights/blog/so-you-want-be-it-consultant&quot;&gt;here&lt;/a&gt; on their website) and all the positive feedback I got from my colleagues and management, it was just not enough to overcome my impostor syndrome.  On a Friday, only having been an employee for maybe 1.5 months, I decided that I was going to call it quits at ThoughtWorks the following Monday.  That weekend, I spent a lot of time crafting an email basically thanking ThoughtWorks for the opportunity but informing them that they had indeed made a mistake in hiring me because I was not qualified.&lt;/p&gt;

&lt;p&gt;So on Monday morning, I arrived at the ThoughtWorks Dallas office early like I normally do before everyone else to leave my laptop in the office and then hit send on the “goodbye” email I had crafted.  As I stated, I always arrived at the office an hour or so before everyone else and so I was the one that disabled the alarm in the morning.  Well, that morning, probably due to being nervous, the PIN for the alarm just would not work and I ended up setting the alarm off :).  I had to rush to my desk, drop my laptop off and rush out of the building as I set the alarm off.  I had to append the “goodbye” email to not only say I was quitting but sorry for tripping the alarm off.  Yeah, I am pretty sure that annoyed them and added insult to injury.&lt;/p&gt;

&lt;p&gt;The shameful part of this is that ThoughtWorks really believed in me and actually tried to convince me to stick around but nah, the “impostor” force was strong in this one.&lt;/p&gt;

&lt;p&gt;I remained unemployed for maybe 3 months, as I had a full fledged identity crisis and questioned whether or not I belonged in IT.&lt;/p&gt;

&lt;h2 id=&quot;how-i-combat-impostor-syndrome&quot;&gt;How I Combat Impostor Syndrome&lt;/h2&gt;

&lt;p&gt;After ThoughtWorks, I made a deal with myself.  I basically told myself that I would never ever not take a job because I was afraid I was not good enough and that once hired, I would let the employer decide if I was doing a good job, not me.  I had to remind myself of this very rule several times when I was interviewing with Microsoft, which the blog can be found &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2018/10/20/my-interview-with-microsoft.html&quot;&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Also, what has helped me battle impostor syndrome is understanding that extremely talented people also suffer from it.  Last year, I got an opportunity to talk to a Microsoft Distinguished Engineer and he told me that he has suffered from impostor syndrome throughout his entire career and I remember just being shocked that a person of this calibre struggled with it as well.&lt;/p&gt;

&lt;p&gt;After ThoughtWorks, I had an epiphany of sorts about impostor syndrome.  I began to understand that constantly believing that I was a fraud and unqualified for a position for which I had to interview for was actually a form of arrogance.  It is arrogance because I literally had come to believe that I was more of an authority on who was qualified for a position then the interviewers.&lt;/p&gt;

&lt;p&gt;Finally, the biggest weapon I have developed in my fight against impostor syndrome is consistently looking at the tangible evidence.  Whenever doubt creeps in about whether I am qualified to do something, I just think of my experiences, my accomplishments and most importantly, the many times I had self-doubt about my abilities and things turned out just fine.&lt;/p&gt;

&lt;p&gt;The war against impostor syndrome continues and as you have now seen, at times, I have let it get the better of me.  However, as I gain more experience, become more accomplished and I have met and learned from very talented people who also suffer from it, I have been able to overcome impostor syndrome.&lt;/p&gt;
</description>
        <pubDate>Sat, 23 Oct 2021 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2021/10/23/dont-let-impostor-syndrome-ruin-your-career-like-i-almost-did.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2021/10/23/dont-let-impostor-syndrome-ruin-your-career-like-i-almost-did.html</guid>
        
        <category>impostor syndrome</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>Coaching My First OpenHack</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/Production_Fundamentals_Coach.png&quot; alt=&quot;Production Fundamentals Coach&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Over the past 4 months, I have had the opportunity to help create the latest &lt;a href=&quot;https://microsoft.github.io/code-with-engineering-playbook/CSE.html&quot;&gt;CSE OpenHack&lt;/a&gt; content and also serve as a coach for the first time, as our team held dry runs to preview our content to selected audiences inside of Microsoft.&lt;/p&gt;

&lt;h2 id=&quot;background&quot;&gt;Background&lt;/h2&gt;

&lt;p&gt;For those who are unfamiliar with Microsoft OpenHacks, you can go &lt;a href=&quot;https://openhack.microsoft.com/&quot;&gt;here&lt;/a&gt; a to get a fairly good overview of what a Microsoft OpenHack is, who they target and what are some of the goals of an OpenHack.&lt;/p&gt;

&lt;p&gt;The OpenHack that our team created focused on teaching attendees about CSE’s &lt;a href=&quot;https://github.com/Microsoft/code-with-engineering-playbook&quot;&gt;Core Engineering Principles&lt;/a&gt;, which involves concepts such as code quality, testing, process automation, how to prepare to go to production, observability and troubleshooting live-site issues.&lt;/p&gt;

&lt;h2 id=&quot;reaching-consensus&quot;&gt;Reaching Consensus&lt;/h2&gt;

&lt;p&gt;Whenever you are part of a team that is creating content that will teach people core fundamentals of any industry, you would actually be very surprised at how many people have different ideas about what are “core” fundamentals. A subject such as Software Engineering Fundamentals can be very divisive because people have their own ideas about what this entails. Fortunately, even though people on our team had different and often times, “passionate” ideas about what are engineering fundamentals, everyone was able to voice their opinion openly, have respectful debates and ultimately, come to a working consensus as a team.&lt;/p&gt;

&lt;p&gt;One of the great takeaways from this project is that when you are creating content that will help guide people on a particular subject, you have to really examine assumptions, reduce your own personal biases and understand the content you are producing from several angles.&lt;/p&gt;

&lt;h2 id=&quot;not-everyone-works--learns-the-same-way&quot;&gt;Not Everyone Works &amp;amp; Learns the Same Way&lt;/h2&gt;

&lt;p&gt;Another major takeaway from coaching my first OpenHack is that everyone has their own dev setup and learn in different ways. I know that this may sound like common sense but it was something that caught me a little off guard when I coached in the first dry run. For my development environment, I use Hyper-V to create Ubuntu (Preferred) or Windows Virtual Machines, depending upon the project. I do this so I don’t pollute my work laptop with tons of software and after a project is over, I can just delete the Virtual Machine.&lt;/p&gt;

&lt;p&gt;During the OpenHack dry runs, you had people with Macs, PCs or PCs using &lt;a href=&quot;https://docs.microsoft.com/en-us/windows/wsl/about&quot;&gt;WSL&lt;/a&gt;. People used Visual Studio Code, Visual Studio or a combination of the two. Another observation was that people tend to do something that is kind of a pet peeve of mine, which is having tons and tons of tabs open at once :). As a Coach you have to be somewhat knowledgeable about the different types of OSs and tools that people tend to use. Also, I had to really learn to not be judgemental. If someone preferred to use Visual Studio over Visual Studio Code, that is okay. If someone had a ton of tabs open, while helping them troubleshoot, don’t force them to close all of their tabs.&lt;/p&gt;

&lt;p&gt;Because people tend to use a myriad of tools and OSs, I started looking into &lt;a href=&quot;https://code.visualstudio.com/docs/remote/containers&quot;&gt;Visual Studio Code Devcontainers&lt;/a&gt; as a way to get our attendees up and running quickly so they could spend as much time as possible focusing on the core concepts of the OpenHack and not local dev environment issues.&lt;/p&gt;

&lt;h2 id=&quot;learn-to-lean-on-others&quot;&gt;Learn to Lean on Others&lt;/h2&gt;

&lt;p&gt;Another great take away from coaching my first OpenHack is that I had to learn to lean on others and although it sounds arrogant, I “don’t” know everything (the horror!). As I was telling one of the attendees after the first dry run, I was extremely nervous going into coaching my first OpenHack. I have never been a position where I was “formally” seen as a guide and even if I know 99% of the material, I will still zero in on the 1% I feel I don’t know and build up unnecessary panic (can you say &lt;a href=&quot;https://en.wikipedia.org/wiki/Impostor_syndrome&quot;&gt;Impostor Syndrome&lt;/a&gt;!).&lt;/p&gt;

&lt;p&gt;Furthermore, throughout my career, I have always had this weird idea that when you have to ask someone a question that I believe I should know and/or cannot find out on my own, then that is kind of a sign of weakness and the other person will think ill of me.&lt;/p&gt;

&lt;p&gt;This assumption is quite ignorant, arrogant and cannot be further from the truth. During the creation of the Production Fundamentals OpenHack, each coach started to develop specific areas of expertise. During the dry runs, I definitely had to lean on the other coaches when the attendees arrived at challenges that I was less familiar with and vice versa.&lt;/p&gt;

&lt;h2 id=&quot;attendees-may-know-more-than-you&quot;&gt;Attendees May Know More than You&lt;/h2&gt;

&lt;p&gt;Similar to the idea of “I don’t know it all”, in some cases the attendees could be more knowledgeable on a subject than the coach in certain areas. As stated prior, I primarily use Ubuntu for my development environment. While coaching the OpenHacks, I had to lean on the attendees as we troubleshot issues with Macs or &lt;a href=&quot;https://docs.microsoft.com/en-us/windows/wsl/about&quot;&gt;WSL&lt;/a&gt;. During the Production Fundamentals OpenHack, I became extremely comfortable with the fact that some of the attendees knew more than I did on a subject and in some cases, were experts on some of the content.&lt;/p&gt;

&lt;p&gt;But that is okay because during an OpenHack learning doesn’t just flow one way, ie attendees learning from the coaches. On any project, everyone can learn from everyone, even if it is a Tech Lead learning from an Individual Contributor or in the case of an OpenHack, a coach learning from the experiences of the attendees.&lt;/p&gt;
</description>
        <pubDate>Mon, 16 Mar 2020 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2020/03/16/coaching-my-first-openhack.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2020/03/16/coaching-my-first-openhack.html</guid>
        
        <category>career</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>My First Year at Microsoft</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/microsoft-logo-1200x627.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;November 2019 marks my one year anniversary as a Microsoft employee. Similar to what I did when I reached &lt;a href=&quot;https://blog.michaeldeongreen.com/careeradvice/2019/05/11/my-first-six-months-at-microsoft.html&quot;&gt;my first six months milestone&lt;/a&gt;, I wanted to take some time to write a blog entry that reflects my thoughts, experiences and observations at the one year mark.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Travel!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Before joining Microsoft, I had never traveled outside of the United States, not even to Canada or Mexico &lt;em&gt;(which seems odd given that I am from Texas)&lt;/em&gt;. After being at Microsoft for one year, I have been to Munich twice and Mexico City. Also, I had never been to Washington State before and I recently got the opportunity to visit Seattle and the main Microsoft Campus in Redmond while attending CSE OneWeek. All told, in my first year, I have travelled to Kansas City, Boston twice, Munich twice, Mexico City, Chicago/Deerfield, Times Square twice, Redmond and Seattle.&lt;/p&gt;

&lt;p&gt;Traveling has not been that big of a problem for me personally, the only downside is on rare occasions you may get asked to travel on short notice and I don’t sleep well in hotels, so I tend to get very little sleep on the road and there is a sleep “adjustment” period when I get home.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reorgs!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Throughout my career, I have always worked for small companies and before I joined Microsoft, I was working for myself as an Independent Consultant, so I had never gone through a reorg prior to joining Microsoft. I am not sure if reorgs are a “Big Company” thing and/or if they happen a lot within Microsoft, but in my organization, we reorg frequently. When I joined in November 2018, there was a reorg in July and we had just had another reorg in July 2019.&lt;/p&gt;

&lt;p&gt;When a reorg occurs, you may get an email stating that &lt;strong&gt;FILL_IN_MANAGER_NAME&lt;/strong&gt; is your new manager or your team has changed or your role has changed or a combination of the three.&lt;/p&gt;

&lt;p&gt;When we reorged in July 2019, my manager, who was an M1 (I will be discussing the plethora of acronyms at Microsoft later) got promoted to an M2 and we hired our team’s new M1 in November. The news was somewhat bittersweet because on the one hand, I was happy for my former manager but on the other hand, I was just starting to get used to how he managed the team and now we would have to repeat the process and get to know an entirely new manager.&lt;/p&gt;

&lt;p&gt;Reorgs seem to be just a fact of life in my organization, this is why it is very important to always treat everyone with respect and network because you never know who you may be working with &lt;em&gt;(or for)&lt;/em&gt; after a reorg occurs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Diversity &amp;amp; Inclusion!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Diversity and Inclusion &lt;em&gt;(or D&amp;amp;I for short)&lt;/em&gt; is a subject that is talked about &lt;strong&gt;a lot&lt;/strong&gt; at Microsoft. D&amp;amp;I conversations will come up during formal meetings, they are part of the employee review process and many employees talk about D&amp;amp;I at informal gatherings.&lt;/p&gt;

&lt;p&gt;Similar to society in general, D&amp;amp;I is a very &lt;strong&gt;touchy&lt;/strong&gt; subject and I literally have friends at Microsoft that fall on various points of the spectrum ie “We should force D&amp;amp;I on everyone” or “D&amp;amp;I is reverse discrimination” or somewhere in the middle. And to reiterate, yes, I used the word &lt;strong&gt;friend&lt;/strong&gt; because I am very capable of being friends with people that have an opinion that may be completely different than my own, even if I don’t agree with their opinion.&lt;/p&gt;

&lt;p&gt;D&amp;amp;I is such a &lt;strong&gt;touchy&lt;/strong&gt; subject that I debated on whether or not I should even mention it in this blog, although I have written about touchy subjects in the past, like &lt;a href=&quot;https://blog.michaeldeongreen.com/socialjustice/2015/02/15/a-conversation-about-majority-privilege.html&quot;&gt;A Conversation About Majority Privilege&lt;/a&gt;. Ultimately, I decided to at least discuss D&amp;amp;I because I wouldn’t be genuine if I didn’t at least mention the subject, albeit, brief.&lt;/p&gt;

&lt;p&gt;First, from my observation, Microsoft &lt;em&gt;(or more appropriately, the organization that I belong too inside of Microsoft)&lt;/em&gt; is probably the 2nd most inclusive employer that I have worked for when it comes to trying to make an effort to be more diverse and inclusive.&lt;/p&gt;

&lt;p&gt;Second, leadership has enacted tangible initiatives in an effort to make CSE and Microsoft as a whole more inclusive. CSE recently created a D&amp;amp;I Working Group made up of a mix of leadership and employees as another avenue to increase D&amp;amp;I. My former manager told me during my last review that in Fiscal Year 2020, D&amp;amp;I was going to be an even bigger part of the review process. Also, in an effort to be transparent, Microsoft provides a D&amp;amp;I report to all employees with a breakdown of how its D&amp;amp;I efforts are going.&lt;/p&gt;

&lt;p&gt;However, with all the above said, one of the biggest disappointments that I continue to have in the IT industry in general is that there just isn’t a lot of people that look like me in positions of influence such as Executives, VPs, Partners, Managers, Architects, Development and Tech Leads.&lt;/p&gt;

&lt;p&gt;When I am asked about my opinion from co-workers and some in leadership positions, I try to explain that diversity in positions of influence is important for two basic reasons:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;First, a lack of diversity can give off the impression that maybe others that are not apart of the majority that makes up leadership don’t have an &lt;strong&gt;equal&lt;/strong&gt; chance at obtaining those positions&lt;/li&gt;
  &lt;li&gt;Second, if young people that are members of a &lt;strong&gt;Historically Discriminated Against Group&lt;/strong&gt; (a phrase I stole from &lt;a href=&quot;https://martinfowler.com/bliki/HistoricallyDiscriminatedAgainst.html&quot;&gt;Martin Fowler&lt;/a&gt;) rarely see people that look like themselves in positions of influence, they will tend to gravitate towards other industries that are more representative of their demographic, which just serves to perpetuate the cycle.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;D&amp;amp;I is a tough issue to tackle because companies such as Microsoft are dealing with often times, deeply ingrained societal problems that society in general has not been able to solve. I applaud Microsoft for at least trying to solve some of the issue of how do we, as a company become more diverse and inclusive.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Land of Acronyms!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As stated, I have never worked for a company as large as Microsoft, so maybe having tons and tons of acronyms is just a big company thing. Microsoft has a &lt;strong&gt;ton&lt;/strong&gt; of acronyms and when I first started, I felt that some of the conversations were spoken in some encrypted language and you needed some type of decryption device in order to make sense of things.&lt;/p&gt;

&lt;p&gt;People in my organization and Microsoft in general, will have conversations that will include acronyms like CSE, CTE, SEI, M1, M2, M3, ADS, EEST, ESP, WCB, ZR, IR, CSA, AIRS, LT, TPM, SDE, ROB, D&amp;amp;I etc etc and it can be extremely confusing for someone who is new to Microsoft or even new to the organization.&lt;/p&gt;

&lt;p&gt;There are so many acronyms at Microsoft that there is an internal dictionary application available on the Intranet to help people decipher the meaning. Sometimes an acronym can mean several different things, for example, my organization CSE, stands for Commercial Software Engineering but the acronym could get mistaken for &lt;strong&gt;C&lt;/strong&gt;ore &lt;strong&gt;S&lt;/strong&gt;ervices &lt;strong&gt;E&lt;/strong&gt;ngineering.&lt;/p&gt;

&lt;p&gt;After 1 year of service at Microsoft, with respect to all of the acronyms, I believe I have graduated from a Padawan Learner to a Jedi Knight, but quite frequently, I will take part in conversations that use more acronyms that I am not familiar with, which demonstrates that I have a long way to go before becoming a Jedi Master of Microsoft Acronyms &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pound of Flesh!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the things that I thought could be a potential problem when joining a company like Microsoft is that at some point, it would change me into somebody I didn’t recognize. I liked the individual freedoms that came with doing independent consulting work or working for a small consulting company.&lt;/p&gt;

&lt;p&gt;I didn’t really want to become the &lt;em&gt;proverbial&lt;/em&gt; Corporate Animal, which I believe is someone who uses others for their own personal gain, that has &lt;em&gt;contacts&lt;/em&gt;, not friends and &lt;em&gt;plays&lt;/em&gt; the big corporation game just to get ahead.&lt;/p&gt;

&lt;p&gt;One of the biggest issues that quickly arose was that at work, I am an Extravert but in less structured environments, I suffer from social anxiety and this turns me into somewhat of an Introvert, so at past employers, I avoided social gatherings like the plague.&lt;/p&gt;

&lt;p&gt;I had a very &lt;strong&gt;naive&lt;/strong&gt; mindset when joining Microsoft in that I certainly wasn’t going to change this behavior on account of Microsoft because, you know, that would mean I was being fake and well on my way to becoming one of those Corporate Animals I tended to criticize.&lt;/p&gt;

&lt;p&gt;Surprisingly enough, the CSE organization within Microsoft had other plans for me. In CSE, we have a lot of social events and networking is a huge deal. When we would go to Offsites (Conferences), to learn and meet other colleagues in our org, it isn’t your typical &lt;strong&gt;Death by Powerpoint&lt;/strong&gt; meetings, there are tons of social activities, where you &lt;strong&gt;have&lt;/strong&gt; to interact with people that you don’t even know, which was one of my biggest hurdles.&lt;/p&gt;

&lt;p&gt;What I found out about myself was that it wasn’t so much that I had social anxiety but why there was anxiety in the first place. At Microsoft, we have something called the &lt;a href=&quot;https://cloudblogs.microsoft.com/industry-blog/en-gb/cross-industry/2019/05/14/10-inclusive-behaviours/&quot;&gt;10 Inclusive Behaviors&lt;/a&gt; and one of the behaviors revolve around examining assumptions.&lt;/p&gt;

&lt;p&gt;See, I would avoid going to social events because I erroneously assumed that I didn’t have a lot in common with a lot of &lt;strong&gt;those&lt;/strong&gt; people. I would literally think, well most of these people don’t look like me, not from Texas, they probably went to better schools then I did, they are probably smarter than me, I don’t drink blah blah blah and so I just wouldn’t go to social events out of fear of being found out as an impostor, which I spoke about in my blog about &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2018/10/20/my-interview-with-microsoft.html&quot;&gt;interviewing at Microsoft&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;However, I quickly found out that you must give Microsoft a part of you ie a pound of flesh, it literally demands it in the form of being social, networking, examining behaviors and personal growth.. However, as I started to become more social, I realized that many of the assumptions that I was making were flat out wrong and that I had a lot more in common with people than I had originally thought.&lt;/p&gt;

&lt;p&gt;Because I decided to give Microsoft this pound of flesh, I was literally forced to grow in areas that I completely ignored because I didn’t think it was important. Like most engineers, when I saw that I had a problem, I put together a strategy and slowly implemented it to get over some of my fears and put to rest some of the assumptions that I have been making my entire professional life.&lt;/p&gt;

&lt;p&gt;I now attend many social events when we have conferences because I like meeting new people and the key was to examine assumptions and to make it a point to be comfortable being &lt;strong&gt;uncomfortable&lt;/strong&gt; in a setting where I don’t know 90% of the people &lt;em&gt;(remember, we reorg a lot, so the org is constantly changing)&lt;/em&gt;. The legendary motivational speaker &lt;a href=&quot;https://en.wikipedia.org/wiki/Les_Brown_(speaker)&quot;&gt;Les Brown&lt;/a&gt; calls this uncomfortableness, &lt;em&gt;The Danger Zone&lt;/em&gt; and according to him, entering this zone, is the only way for a person to grow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;OpenHacks&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In Microsoft CSE, they have what are called &lt;a href=&quot;https://openhack.microsoft.com/&quot;&gt;OpenHacks&lt;/a&gt;, where you and a group of maybe 4-6 people will work together as a team to solve existing technical problems on a real project and/or work through a set of simulated challenges to acquire new skills.&lt;/p&gt;

&lt;p&gt;Prior to joining Microsoft, I had never attended a hacking conference and I had a lot of preconceived notions about OpenHacks based upon my own &lt;a href=&quot;https://en.wikipedia.org/wiki/Impostor_syndrome&quot;&gt;Impostor Syndrome&lt;/a&gt; complex. I got the opportunity to attend my first OpenHack in October 2019 for DevSecOps and prior to attending, I made a lot of assumptions such as:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Everyone in attendance were all hacking geniuses&lt;/li&gt;
  &lt;li&gt;Everyone would judge you if you didn’t know something and had to &lt;em&gt;google&lt;/em&gt; a solution&lt;/li&gt;
  &lt;li&gt;Everyone would judge you if they felt that you took too long to work through a challenge&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Of course, once I participated in the OpenHack, none of my assumptions were remotely true and I had a lot of fun working as a team, trying to work through technical challenges. The OpenHack Coaches make it a point to tell everyone that the primary goal is for learning and that OpenHacks aren’t a contest. You realize very quickly that the people on your team may have just as little knowledge as you do on a subject and they are just trying to learn just like you are.&lt;/p&gt;

&lt;p&gt;I can be very self-conscious when it comes to people watching me as I work but I got so comfortable during the OpenHack that for the majority of the time, my desktop was shared on the screen for all to see and it didn’t even bother me. OpenHacks are also another great way to network &lt;em&gt;(my teammates were from Brazil, China, Japan and Taiwan)&lt;/em&gt;, meet experts in a particular Tech Domain and find out what new features are about to be released for a particular product.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Words!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;My first year at Microsoft was definitely eventful, stressful, fun and full of growth opportunities. Now that I kind of halfway know my way around the place, I hope to continue to grow as a person and as a professional.&lt;/p&gt;

&lt;p&gt;Picture taken with co-workers and friends, Andrew and Dexter in front of Building 92, as they accompanied a noob like me to the Microsoft Campus in Redmond for the very first time:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/my-first-year-at-microsoft.html-001.jpg&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;br /&gt;
&lt;em&gt;(From left to right: Andrew, Dexter &amp;amp; me)&lt;/em&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 29 Nov 2019 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2019/11/29/my-first-year-at-microsoft.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2019/11/29/my-first-year-at-microsoft.html</guid>
        
        <category>career</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>How to Locally Debug a ASP.Net Core Web API that Receives Messages from Azure EventGrid</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/michaeldeongreen-logo.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;At one our Client Partners here at Microsoft, we are using the &lt;a href=&quot;https://azure.microsoft.com/en-us/services/event-grid/&quot;&gt;Azure EventGrid&lt;/a&gt; to power our event driven application written in ASP.Net Core. In this blog, I wanted to take a moment to demonstrate how to locally debug a ASP.Net Core Web API that receives messages from Azure EventGrid.&lt;/p&gt;

&lt;p&gt;In this tutorial, I will demonstrate how to debug a ASP.Net Core Web API endpoint that receives messages when a new blob is created in an Azure Blob Storage Account. The code used in this tutorial can be found &lt;a href=&quot;https://github.com/michaeldeongreen/azeventgrid-local-debug-aspnet-core-ngrok&quot;&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pre-requisites!&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;https://dotnet.microsoft.com/download/dotnet-core/2.2&quot;&gt;.Net Core 2.2&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;An Azure Subscription&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest&quot;&gt;azure-cli&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Git&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://code.visualstudio.com/&quot;&gt;Visual Studio Code&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Before running any of the commands, always ensure you have logged into azure by executing the following command:&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    az login
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;ngrok&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;First, we need to donwload a tool called &lt;a href=&quot;https://ngrok.com/&quot;&gt;ngrok&lt;/a&gt;. Once you create an account, following the instructions on how to register your authtoken.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Register the Azure EventGrid Provider&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If not already registered, we will need to &lt;a href=&quot;https://docs.microsoft.com/en-us/azure/event-grid/custom-event-quickstart#enable-event-grid-resource-provider&quot;&gt;register&lt;/a&gt; the Azure EventGrid. Open up a terminal and run the following command.&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    az provider show --namespace Microsoft.EventGrid --query &quot;registrationState&quot;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Create Azure Blog Storage Account&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We will clone the &lt;a href=&quot;https://github.com/michaeldeongreen/azeventgrid-local-debug-aspnet-core-ngrok&quot;&gt;sample application&lt;/a&gt; and navigate to the &lt;em&gt;scripts&lt;/em&gt; folder and execute the following command to create our Azure Blog Storage Account and a Blob container called &lt;em&gt;demo&lt;/em&gt;:&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    chmod +x create-az-storage-account.sh &amp;amp;&amp;amp;
    ./create-az-storage-account.sh -r {name_of_resource_group} -l {location} -a {name_of_blob_storage_account}
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;If the script ran successfully, it will return back the message &lt;em&gt;The script has created the Azure Resources&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Debugging!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Open up the ASP.Net Core Web API project in Visual Studio Code and press &lt;em&gt;F5&lt;/em&gt; to run the project. A quick note, for Ubuntu, I had to modify the &lt;em&gt;launchSettings.json&lt;/em&gt; file to use &lt;em&gt;http&lt;/em&gt; to allow ngrok to work.&lt;/p&gt;

&lt;p&gt;In the &lt;em&gt;EventGridController&lt;/em&gt;, place breakpoints in various places to debug the application when a message is received from Azure EventGrid.&lt;/p&gt;

&lt;p&gt;Next, we need to run ngrok. We do this by executing the command below: &lt;em&gt;(note: for Windows user, you need to use the command prompt as I could not get git bash to work)&lt;/em&gt;.&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    ngrok http -host-header=localhost 5000
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Next, we will need to copy the generated url so we can use it to subscribe to events via Azure EventGrid.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-001.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Next, we need to navigate to the &lt;a href=&quot;https://https://portal.azure.com&quot;&gt;Azure Portal&lt;/a&gt; to create the Subscription and upload a file, so we can debug the application.&lt;/p&gt;

&lt;p&gt;In the Azure Portal, we need to find the Azure Blob Storage Account we created when we ran the &lt;em&gt;create-az-storage-account.sh&lt;/em&gt; bash script. Select “Events” and then “Event Subscription”.&lt;/p&gt;

&lt;p&gt;For the &lt;em&gt;Endpoint Type&lt;/em&gt;, we will choose “webhook” and copy the url ngork generated and add “/eventgrid” to the end ie &lt;em&gt;&lt;a href=&quot;https://ngrok-url/eventgrid&quot;&gt;https://ngrok-url/eventgrid&lt;/a&gt;&lt;/em&gt;. See the images below for guidance:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-002.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-003.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-004.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;When we hit the &lt;em&gt;create&lt;/em&gt; button to create the Subscription, for security reasons, Azure EventGrid will validate the endpoint and if you have a breakpoint similar to the picture below, the breakpoint should be activated in Visual Studio Code:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-005.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Also, the new Subscription should be displayed on the Events page of the Azure Blob Storage Account:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-006.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Now let’s upload a file and debug the &lt;em&gt;HandleEventGridEventAsync&lt;/em&gt; Method inside of the EventGridController &lt;em&gt;(make sure you have a breakpoint in the HandleEventGridEventAsync method)&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;In the Azure Portal, we need to find the Azure Blog Storage Account and navigate to the &lt;em&gt;demo&lt;/em&gt; container. Inside of the container, we will press the &lt;em&gt;upload&lt;/em&gt; button. Included in the Git repository root directory is a file called &lt;em&gt;sample.json&lt;/em&gt;, you can choose this file or a file of your own choosing. For guidance, see the pictures below:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-007.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-008.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-009.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Once the file is finished uploading, our breakpoint should be activated in Visual Studio Code:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid-010.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clean Up!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now that we are finished, we can run the &lt;em&gt;delete-az-storage-account.sh&lt;/em&gt; bash script to clean up our resources. Run the following command:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
        &lt;span class=&quot;nb&quot;&gt;chmod&lt;/span&gt; +x delete-az-storage-account.sh &lt;span class=&quot;o&quot;&gt;&amp;amp;&amp;amp;&lt;/span&gt;
        ./delete-az-storage-account.sh &lt;span class=&quot;nt&quot;&gt;-r&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_resource_group&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;If the script ran successfully, it will return back the message &lt;em&gt;The script has deleted the Azure Resources&lt;/em&gt;.&lt;/p&gt;
</description>
        <pubDate>Fri, 13 Sep 2019 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/technology/2019/09/13/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/technology/2019/09/13/how-to-locally-debug-a-asp-net-core-webapi-that-receives-messages-from-azure-eventgrid.html</guid>
        
        <category>Net Core</category>
        
        <category>ASP.Net Web API</category>
        
        <category>Azure EventGrid</category>
        
        
        <category>technology</category>
        
      </item>
    
      <item>
        <title>Independent Consultant Versus Working for a Big Company!</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/michaeldeongreen-logo.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Earlier this year, a former co-worker wanted to talk to me about becoming an independent consultant and leaving the consulting company that we both used to work for. I wanted to take some time to talk about what I believe are the pros and cons of working for yourself versus working for someone else, in particular, a big company.&lt;/p&gt;

&lt;h2 id=&quot;background&quot;&gt;Background&lt;/h2&gt;

&lt;p&gt;In 2017, I decided to leave the consulting company I was working for and work for myself. I did Corp to Corp work for about 2 years before deciding to join Microsoft in November of 2018. In this blog, I want to share some of the advice I gave my friend and former co-worker as he undertakes his journey into the independent consulting world.&lt;/p&gt;

&lt;p&gt;I will first talk about what I perceive as the positives of being an independent consultant and then I will delve into what I perceive to be some of the negative aspects of being an independent consultant. I can definitely appreciate how big of a decision it is to go the independent consulting route, so much so, that even when I joined Microsoft, I kept my LLC because I was not sure if I was making the right decision.&lt;/p&gt;

&lt;h2 id=&quot;positives&quot;&gt;Positives&lt;/h2&gt;

&lt;h3 id=&quot;being-my-own-boss&quot;&gt;Being My Own Boss&lt;/h3&gt;

&lt;p&gt;One of the main reasons I decided to go the Corp to Corp route is because I wanted to have more freedom and be my own boss. I wanted to have a lot more say in who I worked for and what kind of projects that I worked on. Also, when I didn’t have a client, I wanted to spend time working on side projects that I liked as opposed to an employer giving me “busy” work until another client became available.&lt;/p&gt;

&lt;p&gt;When I became my own boss, I became even more disciplined, I started to view things from an “employer’s” perspective and I became incredibly knowledgeable about taxes, payroll and how to run a small business.&lt;/p&gt;

&lt;h3 id=&quot;limited-exposure-to-politics&quot;&gt;Limited Exposure to Politics&lt;/h3&gt;

&lt;p&gt;Another reason why I decided to work for myself was because of Corporate Politics. Let’s be honest, if you are going to deal with people, you will deal with politics, that is just the nature of the beast. However, when you work as an independent consultant, your exposure to politics is a lot less because your client is not your boss, they are just paying you for your expertise for a limited amount of time.&lt;/p&gt;

&lt;p&gt;You will not have to attend any of their corporate meetings, you will not have to do monthly or quarterly reviews, you won’t have to worry about promotions, titles, wage increases or getting a new supervisor.&lt;/p&gt;

&lt;p&gt;When I was my own boss, it felt really good to not have to worry about any of the politics at the client and just focus solely on the tasks that I was brought in for.&lt;/p&gt;

&lt;p&gt;One of the aspects of my professional life that has always bothered me is that there aren’t a lot of people in positions of influence that look like me ie a Black Males. When I decided to work for myself, I found that this lack of diversity bothered me less and less because I now work for myself and I didn’t have to worry about any “bias” in who got promotions, raises or the best projects&lt;/p&gt;

&lt;p&gt;Also, due to Federal guidelines, your client had limitations on how much control that have over how and where you do your work. When I was working for myself, I was 100% remote and I no longer had to go into my consulting company’s office to do remote work for their client located in California. Working remotely greatly reduces the impact Corporate Politics can have on a person’s mental health and personal wellbeing because you are simply not physically present when a lot of it occurs.&lt;/p&gt;

&lt;h3 id=&quot;money&quot;&gt;Money&lt;/h3&gt;

&lt;p&gt;Another great aspects of being an independent consultant is, quite frankly, from a money standpoint, the sky’s the limit. As an independent consulting, you will negotiate your bill rate and you get paid for every “unit” (ie 15, 30 or 60 minutes) you work.&lt;/p&gt;

&lt;p&gt;I remember telling people that immediately after I started working for myself, many activities I didn’t really enjoy as a full time employee, I started to hope for as an independent consultant. For example, at the consulting company I worked for before I went independent, we use to have “brown bags” where we would give talks about a new technology or methodology and I found that if you wanted them to be good, it took quite a bit of time. As an independent consultant, I would now bill for those hours because it was work I was doing for the client.&lt;/p&gt;

&lt;p&gt;Also, when most people start out on their own, they will typically have to go through a 3rd party to find work. The 3rd party, typically a recruiting company or consulting company will take a percentage off the top as a finder’s fee. If someone becomes quite skilled, they can find clients directly and get an even higher bill rate as the 3rd party middleman is no longer needed.&lt;/p&gt;

&lt;h2 id=&quot;negatives&quot;&gt;Negatives&lt;/h2&gt;

&lt;h3 id=&quot;hustling&quot;&gt;Hustling&lt;/h3&gt;

&lt;p&gt;One of the major negative assets to being your own boss is that you are constantly in “hustle” mode. You never know when your client is going to terminate the project you are working on and many times, clients will only sign a 6 month contract with you, so you are always looking for the next “meal”.&lt;/p&gt;

&lt;p&gt;Also, you become very aware of how budgets work and when most companies typically run out of money. When I went independent, I always tried to make sure that I had a project during the months of October through January. What I found was that most companies typically had already used their budget for the year and decision makers were already in “vacation” mode during those months. Also, when your client is slashing budgets, consultants are typically the first ones out the door.&lt;/p&gt;

&lt;p&gt;Furthermore, when you are always hustling, that means you are typically interviewing constantly, unless you have built up a very good reputation in your industry. In my blog &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2018/10/28/the-broken-technical-interview-process.html&quot;&gt;The Broken Technical Interview Process&lt;/a&gt;, I talk about how I feel the Technical Interview Process is broken and how much I loathe interviewing.&lt;/p&gt;

&lt;h3 id=&quot;paperwork&quot;&gt;Paperwork&lt;/h3&gt;

&lt;p&gt;When I decided to go Corp to Corp, I learned a lot about running a business and part of that is paperwork. One of the reasons I why I always hesitated to go independent was I was very fearful about looking for an honest CPA who would ensure that I didn’t get in any trouble with the IRS.&lt;/p&gt;

&lt;p&gt;I had to spend a lot of time trying to find a good name for my LLC, filling out the paperwork, interviewing CPAs, learning software like Quickbooks, the Texas Workforce Commission, Payroll Taxes, Insurance, Contract verbiage and end of the year taxes.&lt;/p&gt;

&lt;p&gt;Also, no matter how honest you think your CPA is, you always want to consistently double check their work to ensure taxing entities are getting paid the right amount and on time because at the end of the day, when something is not paid on time, Uncle Sam is not going to accept the excuse of “Well, I didn’t pay you because my CPA messed up”!&lt;/p&gt;

&lt;p&gt;The deal I struck with my CPA &lt;em&gt;(who is fantastic)&lt;/em&gt; is that he would handle my tax filings and I would do the day to day bookkeeping entries.&lt;/p&gt;

&lt;h3 id=&quot;money-1&quot;&gt;Money&lt;/h3&gt;

&lt;p&gt;On the flip side, there is a negative aspect of money when you go the independent route. Now, when I decided to take a vacation or there was a corporate holiday, I didn’t get paid for those days. If a person is smart, they will bake holidays, vacations and time without a client into their bill rate to ensure they have enough money to maintain their standard of living.&lt;/p&gt;

&lt;p&gt;Also, not to preach, but money isn’t everything but if you end up working with a client on a &lt;a href=&quot;https://en.wikipedia.org/wiki/Death_march_(project_management)&quot;&gt;Death March&lt;/a&gt; project, sure you will make a lot of money but you may also get burnt out and work-life balance will be greatly diminished.&lt;/p&gt;

&lt;h2 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h2&gt;

&lt;p&gt;As I have tried to explain, there are pros and cons to going independent versus working for large companies. Personally, I feel that every person should at least attempt to try to start their own business at least once for the educational value alone.&lt;/p&gt;

&lt;p&gt;I learned quite a bit when I was running my own ship and definitely miss a lot of aspects of being my own boss. However, working for a large companies definitely has some positives but ultimately, one has to make a decision for themselves about what is best for them and their family.&lt;/p&gt;
</description>
        <pubDate>Sat, 07 Sep 2019 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2019/09/07/independent-consultant-versus-working-for-a-big-company.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2019/09/07/independent-consultant-versus-working-for-a-big-company.html</guid>
        
        <category>Consulting</category>
        
        <category>IT</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>How to SSH into an Azure Virtual Machine using Azure DevOps, Azure Key Vault and Bash</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/michaeldeongreen-logo.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;In this blog entry I want to demonstrate how to SSH into an Azure Virtual Machine using an Azure DevOps Hosted Agent, Azure Key Vault and Bash.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prerequisites!&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;azure-cli&lt;/li&gt;
  &lt;li&gt;Azure DevOps&lt;/li&gt;
  &lt;li&gt;Azure Subscription&lt;/li&gt;
  &lt;li&gt;Bash&lt;/li&gt;
  &lt;li&gt;GitHub Account&lt;/li&gt;
  &lt;li&gt;Ubuntu&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Caveats!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This blog entry is not an exhaustive tutorial on Azure, Azure Virtual Machines, Azure DevOps, Azure Key Vault, Bash, Docker, Public Key Encryption or the SSH Protocol. This blog assumes the reader has a fundamental knowledge of the aformentioned technologies and concepts.&lt;/p&gt;

&lt;p&gt;Also, in this blog entry I open up a number of ports on an Azure Virtual Machine. &lt;strong&gt;For brevity and to keep this guide as simple as possible, the “best” security practices are not used when opening these ports and should not serve as an example for a live environment.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I will be using &lt;a href=&quot;https://github.com/michaeldeongreen/azdo-hosted-agent-ssh-dynamic-environment-keyvault&quot;&gt;this&lt;/a&gt; repository, which contains 2 Bash scripts that will install a Private Key on an Azure DevOps Hosted Agent and deploy the &lt;a href=&quot;https://hub.docker.com/_/microsoft-dotnet-core-samples&quot;&gt;ASP.Net Core Sample Docker container&lt;/a&gt; to an Azure Virtual Machine. You will need to clone the GitHub repository.&lt;/p&gt;

&lt;p&gt;Please view the &lt;a href=&quot;https://github.com/michaeldeongreen/azdo-hosted-agent-ssh-dynamic-environment-keyvault/blob/master/README.md&quot;&gt;README&lt;/a&gt; for a detailed description of how the Bash scripts work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Background!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;On my latest project here at Microsoft, we are using &lt;a href=&quot;https://www.terraform.io/intro/&quot;&gt;Terraform&lt;/a&gt; to deploy our infrastructure to the Azure Cloud. One of the resources that is deployed are Virtual Machines that run docker containers and the information about these Virtual Machines &lt;em&gt;(username, ip address etc etc)&lt;/em&gt; is stored in an Azure Key Vault via Terraform. To automate the container deployment process, we needed to create a Azure DevOps Pipeline that would:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Retrieve the username &amp;amp; IP Address of the Virtual Machine from Azure Key Vault&lt;/li&gt;
  &lt;li&gt;Retrieve an SSH Private Key that has been Base64 encoded from Azure Key Vault&lt;/li&gt;
  &lt;li&gt;Install the SSH Private Key on the Azure DevOps Hosted Build Agent&lt;/li&gt;
  &lt;li&gt;SSH into the Azure Virtual Machine and deploy a new version of a Docker container&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Azure DevOps has a built in SSH Task to SSH into a Virtual Machine but unfortunately, the Service Connection this task uses requires you to hard-code the IP Address and Port into the Service Connection which would not work for us because we needed to have these values (along with other values) in an Azure Key Vault, which could be accessed programmically in order to support automating Docker container deployments to an Azure Virtual Machine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Create and Configure Azure Resources!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Log into Azure:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    az login
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Create an Azure Resource Group:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    az group create &lt;span class=&quot;nt&quot;&gt;-l&lt;/span&gt; eastus &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_resouce_group&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;
    
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Create an Azure Key Vault:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    az keyvault create &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_keyvault&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-g&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_group&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-l&lt;/span&gt; eastus &lt;span class=&quot;nt&quot;&gt;--sku&lt;/span&gt; standard
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Now we need to create a Azure Key Vault secret that will contain a Private Key. For brevity, I am using the Private Key stored on my Hyper-V Ubuntu 18.04 development machine. If you are unfamiliar with generating SSH Key Pairs on Ubuntu, please see the tutorial on &lt;a href=&quot;https://www.ssh.com/ssh/keygen/&quot;&gt;ssh-keygen&lt;/a&gt;.&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;# copy private key into a variable, Base64 encode the variable and save it into the azure key vault as a secret
# we Base64 encode the private key to preserve the characters
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    &lt;span class=&quot;nv&quot;&gt;privatekey&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;si&quot;&gt;$(&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;base64&lt;/span&gt; ~/.ssh/id_rsa&lt;span class=&quot;si&quot;&gt;)&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;&amp;amp;&amp;amp;&lt;/span&gt; az keyvault secret &lt;span class=&quot;nb&quot;&gt;set&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_secret&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--vault-name&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_key_vault&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--value&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;$privatekey&lt;/span&gt;&lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;To test that the Private Key was saved, you can run the following command:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    &lt;span class=&quot;nb&quot;&gt;echo&lt;/span&gt; &lt;span class=&quot;si&quot;&gt;$(&lt;/span&gt;az keyvault secret show &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_secret&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--vault-name&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_key_vault&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--query&lt;/span&gt; &lt;span class=&quot;s1&quot;&gt;&apos;value&apos;&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--output&lt;/span&gt; tsv&lt;span class=&quot;si&quot;&gt;)&lt;/span&gt; | &lt;span class=&quot;nb&quot;&gt;base64&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-di&lt;/span&gt;
    
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We now need to create an Azure Virtual Machine, so we can store the username &amp;amp; IP Address in Azure Key Vault:&lt;/p&gt;

&lt;p&gt;Since we will be using SSH, I need to copy “Public” key located on my Hyper-V development machine, which will be copied to the Azure Virtual Machine’s &lt;a href=&quot;https://www.ssh.com/ssh/authorized_keys/&quot;&gt;authorized_keys&lt;/a&gt; directory:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    &lt;span class=&quot;nb&quot;&gt;cat&lt;/span&gt; ~/.ssh/id_rsa.pub
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;In the &lt;a href=&quot;https://portal.azure.com&quot;&gt;Azure Portal&lt;/a&gt;:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Choose Virtual Machine and Add a Virtual Machine&lt;/li&gt;
  &lt;li&gt;Choose Ubuntu 18.04 LTS as the OS&lt;/li&gt;
  &lt;li&gt;Choose a name&lt;/li&gt;
  &lt;li&gt;Choose a Resource Group&lt;/li&gt;
  &lt;li&gt;Copy the “Public” key into SSH Public Key text area&lt;/li&gt;
  &lt;li&gt;Change the size of the Virtual Machine to a “Standard B1ms”&lt;/li&gt;
  &lt;li&gt;Choose to open port 22 (SSH)&lt;/li&gt;
  &lt;li&gt;Choose a Standard HDD&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Once you have done this, review and create the Virtual Machine. We will need to open a few other ports:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Choose Networking&lt;/li&gt;
  &lt;li&gt;Choose “Add inbound port rule”&lt;/li&gt;
  &lt;li&gt;Add an entry for Ports 2376 &lt;em&gt;(docker daemon encrypted communication port)&lt;/em&gt; and 8000 &lt;em&gt;(port used by the ASP.Net Core Sample App)&lt;/em&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;As noted, only do this for &lt;em&gt;learning&lt;/em&gt; purposes and always follow proper security protocols for live environments.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-001.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-002.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;We need to now SSH into the Azure Virtual Machine and install docker. You can find the IP Address of the Virtual Machine in the Overview blade:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-003.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;SSH into the Virtual Machine and install Docker:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    ssh &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;username_of_virtual_machine&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;@&lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;ip_address_of_virtual_machine&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Use the &lt;a href=&quot;https://docs.docker.com/install/linux/docker-ce/ubuntu/&quot;&gt;official&lt;/a&gt; Docker guide to install Docker on Ubuntu.&lt;/p&gt;

&lt;p&gt;We will also want to place the Virtual Machine user in the &lt;a href=&quot;https://docs.docker.com/install/linux/linux-postinstall/&quot;&gt;docker&lt;/a&gt; group:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    &lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;groupadd docker &lt;span class=&quot;o&quot;&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;usermod &lt;span class=&quot;nt&quot;&gt;-aG&lt;/span&gt; docker &lt;span class=&quot;nv&quot;&gt;$USER&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We will need to reboot for the changes to take effect:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;    
    &lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;reboot
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We need to store the Virtual Machine username and IP Address in Azure Key Vault as secrets:&lt;/p&gt;

&lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;
    
    az keyvault secret &lt;span class=&quot;nb&quot;&gt;set&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; vm-ip-address &lt;span class=&quot;nt&quot;&gt;--vault-name&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_key_vault&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--value&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;ip_address&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;


  
  

    
    az keyvault secret &lt;span class=&quot;nb&quot;&gt;set&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-n&lt;/span&gt; vm-ip-address &lt;span class=&quot;nt&quot;&gt;--vault-name&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;name_of_key_vault&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--value&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;{&lt;/span&gt;virtual_machine_username&lt;span class=&quot;o&quot;&gt;}&lt;/span&gt;
    
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Here are the secret names I used:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-006.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Create a Azure DevOps Release Pipeline!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We now need to let Azure DevOps create a Service Principal, which will be used to execute our Bash scripts.&lt;/p&gt;

&lt;p&gt;In Azure DevOps:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Create a new Project&lt;/li&gt;
  &lt;li&gt;Inside the Project, choose Project Settings&lt;/li&gt;
  &lt;li&gt;Choose Service Connection&lt;/li&gt;
  &lt;li&gt;Choose Azure Resource Manager&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Fill in the appropriate information. The end result should be something similar to the picture below:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-004.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;After the Service Principal has been created, select the Service Principal and choose “Manage Service Principal”. You will be taken to the Azure Portal where you can copy the display name of the new Service Principal Azure DevOps created.&lt;/p&gt;

&lt;p&gt;We need to grant the new Service Principal the correct permissions to be able to retrieve values from the Azure Key Vault. In the Azure Portal:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Choose the Azure Key Vault that was created&lt;/li&gt;
  &lt;li&gt;Choose the “Access policies” blade&lt;/li&gt;
  &lt;li&gt;Choose “Add new”&lt;/li&gt;
  &lt;li&gt;Paste the Service Principal name in the search bar to find the Service Principal&lt;/li&gt;
  &lt;li&gt;Grant Get and List permissions, similar to the image below&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-005.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Now let’s create the Release Pipeline that will execute the Bash scripts.&lt;/p&gt;

&lt;p&gt;In Azure DevOps:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Choose Pipelines&lt;/li&gt;
  &lt;li&gt;Choose Releases&lt;/li&gt;
  &lt;li&gt;Create a New Release Pipeline&lt;/li&gt;
  &lt;li&gt;Select the GitHub Repository you cloned as the Artifacts&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We need to create the variables that the “aspnetcoreapp-deploy.sh” uses:&lt;/p&gt;

&lt;p&gt;Under the “Variables” tab, create the following variables:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;docker-image:&lt;/strong&gt; mcr.microsoft.com/dotnet/core/samples:aspnetapp&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;key-install-script-directory:&lt;/strong&gt; $(System.DefaultWorkingDirectory)/{azuredevops_artifacts_directory_name}&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;keyvault-name:&lt;/strong&gt; {key_vault_name}&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-007.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;We now need to create a few tasks. Under the “Tasks” tab, choose “Agent job” and make sure “Hosted Ubuntu 1604” is selected.&lt;/p&gt;

&lt;p&gt;Next, create a Azure Key Vault task (this task will create variables with the same exact name as the secret name in the Azure Key Vault):&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-008.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Next, we will create an Azure CLI task that will execute the Bash scripts:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Choose the Service Connection we created and configured earlier&lt;/li&gt;
  &lt;li&gt;Choose Script path and choose the aspnetcoreapp-deploy.sh Bash script&lt;/li&gt;
  &lt;li&gt;Set the arguments: &lt;em&gt;-a $(docker-image) -v $(vm-username) -i $(vm-ip-address) -k $(keyvault-name) -d $(key-install-script-directory)&lt;/em&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-009.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Run Azure DevOps Release Pipeline &amp;amp; Test ASP.Net Core Sample Application!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now that we have created the Release Pipeline, we can hit the “Create release” button at the top right to create a release.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-010.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-011.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Testing the ASP.Net Core Sample Application by navigating to “http://{virtual_machine_ip_address}:8000”&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash-012.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;
</description>
        <pubDate>Wed, 03 Jul 2019 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2019/07/03/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2019/07/03/how-to-ssh-into-an-azure-virtual-machine-using-azure-devops-azure-keyvault-and-bash.html</guid>
        
        <category>Azure DevOps</category>
        
        <category>Azure Key Vault</category>
        
        <category>Bash</category>
        
        <category>docker</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
      <item>
        <title>My First Six Months at Microsoft</title>
        <description>&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/michaeldeongreen/michaeldeongreen.github.io/master/static/img/_posts/microsoft-logo-1200x627.png&quot; alt=&quot;Blogs - Michaeldeongreen&quot; /&gt;&lt;/p&gt;

&lt;p&gt;I blogged about my experience &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2018/10/20/my-interview-with-microsoft.html&quot;&gt;interviewing with Microsoft&lt;/a&gt; roughly 8 months ago. Even though it was a tough decision, I decided to give up the freedoms of Corp to Corp life and join Microsoft. I joined Microsoft about 6 months ago and I want to take some time to write about some of my experiences.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My Org!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The organization I work for within Microsoft is called &lt;a href=&quot;https://microsoft.github.io/code-with-engineering-playbook/CSE.html&quot;&gt;Commercial Software Engineering (CSE)&lt;/a&gt;. Microsoft is a company of companies and each organization tends to have a different culture, so my thoughts and observations are mainly based upon CSE, in particular CSE Dev Crews.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misconceptions!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When I first joined Microsoft, I had several preconceived notions about the Microsoft Culture and the people who work here.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Arrogance!&lt;/strong&gt; - When I joined Microsoft, one of my biggest preconceived notions was that there were a lot of arrogant Type-A personalities. As stated in my previous blog &lt;a href=&quot;https://blog.michaeldeongreen.com/technology/2018/10/20/my-interview-with-microsoft.html&quot;&gt;My Interview with Microsoft&lt;/a&gt;, I had interviewed with Microsoft in the past and I felt the interviewers were a little arrogant.&lt;/p&gt;

&lt;p&gt;Also stated in my blog about interviewing with Microsoft, this belief started to be dispelled very early in the process. In my first six months at Microsoft, I have not encountered a ton of arrogance. Are there people here who have strong opinions and personalities? Yes, but I haven’t really come across anyone who I felt just thought they were better than everyone.&lt;/p&gt;

&lt;p&gt;To be fair, every company on earth has people that are arrogant and Microsoft is definitely not the exception (and I have been assured by co-workers they exist &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;), I just haven’t come across a lot of it, like I thought I would before joining.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Flaming!&lt;/strong&gt; - Another preconceived notion that I had about Microsoft when I first joined is that they had a culture of flaming. At first, I was very hesitant to reach out to co-workers outside of my team (Dev Crews Dallas) if I had a question because I was worried that I would be flamed, derided and told that my question was stupid.&lt;/p&gt;

&lt;p&gt;I think about a month in, after being encouraged to do so by one of my team mates (Rick R.), I finally had the courage to ask a question on Microsoft Teams and something very interesting happened. Not only did I not get flamed, but my biggest problem quickly became having too many responses &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;. Once you ask a question, you will get a bunch of responses and people will tend to say “I know how to do this, feel free to get on my calendar and I can walk you through it”.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Burning the Candle at Both Ends!&lt;/strong&gt; - Another major preconceived notion that I had about Microsoft is that working 60+ hours a week and having the “whip” cracked on you to meet tight deadlines was the norm. I remember being in our Las Colinas Office until around 7 PM one day as I waited for traffic to settle down and being surprised that it was a ghost town around 6 PM.&lt;/p&gt;

&lt;p&gt;Although I do know that there are organizations that probably work under constant tight deadlines, my experience has been the opposite. Because of my consulting background and personality, I have a habit of “upskilling” on technology on weekends and after work hours. I have been told on several occasions that this isn’t necessary and even warned on a few occasions while on the road, not to go to the hotel and work &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;.&lt;/p&gt;

&lt;p&gt;In CSE, they don’t want you to work a lot of long hours because they don’t want you to get burned out. Also, technology is constantly changes and they realize you don’t know everything, so when we start to engage with our clients, time for “upskilling” on a new technology is expected and accounted for when estimates are given.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Adjustments!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I’ve been doing IT Consulting for the last 8 years (most of it 100% remote) and I was an independent contractor for about 2 of those 8 years, so naturally, I have had to make adjustments and at times, it has not been easy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coming into an Office!&lt;/strong&gt; - On our team, we come in 3 times a week, Tuesday through Thursday. I actually live quite far from our office in Uptown Dallas, so it has been hard to adjust to having to come into an office when I had been 100% remote the last 5 or 6 years.&lt;/p&gt;

&lt;p&gt;Even though I still prefer having a office but going in is optional and the commute is still really tough, I have started to get use to coming in and on some weeks, I come in on days when we are not expected to be in the office.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Structure!&lt;/strong&gt; - As an independent consultant, you are your own boss and you tend to be able to just focus on the project you are working on. As a full time employee of Microsoft, I not only have to focus on doing a good job but I have to also focus on Career Development, All-Hand’s Meetings, Networking and 1 on 1s with Mentors and Managers.&lt;/p&gt;

&lt;p&gt;Even when you are at a consulting company, you tended to only focus on your client and you only dealt with your consulting company if you were trying to move up the ladder or there were mandatory company-wide meetings (which are very few).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Manager!&lt;/strong&gt; - Prior to joining Microsoft, for roughly 8 years, I was working as either a independent consultant or as a consultant for a firm. Similar to my thoughts about &lt;em&gt;Structure&lt;/em&gt;, as a consultant, I had very little interaction with my direct manager and obviously, as an independent consultant, I didn’t have a manager. In most cases, the only time you had interaction with your manager is if you were asking for a raise, promotion or there were some major issues with your client.&lt;/p&gt;

&lt;p&gt;At Microsoft, this is completely 100% not the case. You and your manager will have 1 on 1s every other week, your manager may be leading your project, pairing with you, sitting next to you (at work or on a plane), having impromptu meetings to provide continued feedback, going over their house for Christmas &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt; and of course, preparing your reviews (in Microsoft, manager reviews are called &lt;em&gt;Connects&lt;/em&gt;, they are extremely important as they literally stay with you until you die &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;, even if you leave Microsoft and come back).&lt;/p&gt;

&lt;p&gt;I don’t think this is necessarily a bad thing because Microsoft has 100k plus employees and you have to have some kind of structured system to help employees progress in their career and to make sure an employee doesn’t easily fall through the cracks as this system provides a constant feedback loop.&lt;/p&gt;

&lt;p&gt;To be completely transparent, for someone who comes from an environment where you don’t see your manager that much, who is a self-starter, has led projects, knows how to build their brand and shape their career, this has been a major adjustment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pace!&lt;/strong&gt; - In consulting, the name of the game generally is to stay at a client for an extended period of time. So if a consultant doesn’t quite have a handle on most of the tech stack for a consulting engagement, they will have plenty of time to get up to speed and of course, this should lead to expertise and the ability to write production quality code over time.&lt;/p&gt;

&lt;p&gt;In CSE Dev Crews, we will typically do projects that last about 2-3 months and in my experience, you are expected to create production quality software because they are backed by very strong engineering processes, well documented and a major part of our job is to demonstrate these concepts and practices to our Client Partners. To be fair, my manager has always told me that “upskilling” on an unfamiliar technology is something that is baked into the project estimates and you are not expected to upskill outside of work.&lt;/p&gt;

&lt;p&gt;This really wasn’t that big of an issue on my first project at Microsoft as I probably knew roughly 80% of the tech stack for the portion of the project I worked on. However, on my second project at Microsoft (my current project), I would say I was only familiar with roughly 20% of the tech stack. To be fair, even though I feel like I have contributed to my 2nd project, I am considered a “learner” but me being me, I have high expectations for myself and this tends to lead to putting a lot of pressure on myself to learn the tech stack as fast as possible to be in a strong position to support the team and not be the &lt;em&gt;weak link&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;So for someone like myself, this tends to lead to tinkering with the project tech stack after hours at home or in hotels (also partially due to the fact that I really like learning new things), which is fine in the consulting world because it is part of the “ramp up” phase and of course, you will be at the client for an extended period of time, so as time progresses, working after hours is not necessary.&lt;/p&gt;

&lt;p&gt;However, if you have this mentality and you are in CSE Dev Crews, where you are ramping up on 4-5 projects a year this could likely lead to some problems (burnout, stress, nervousness, unrealistic expectations etc etc) and at Microsoft, they &lt;strong&gt;really&lt;/strong&gt; love to get out front of things before they become major issues.&lt;/p&gt;

&lt;p&gt;I remember we were heading into a 4 day weekend and my manager told me, “I don’t want to see any PRs (Pull Requests) from you any earlier than Tuesday” ie no working on the weekend. And recently while onsite in Boston, he &lt;strong&gt;jokingly&lt;/strong&gt; told me, “I am going to go re-edit your Connect and put, Working too many hours!”.&lt;/p&gt;

&lt;p&gt;I never really argue with my manager over these types of things because he has been at Microsoft for about 14 years and knows &lt;strong&gt;ALL&lt;/strong&gt; the Microsoft initiatives, so when I asked him why is this a bad thing, he will say, “You know how Microsoft is trying to do [INSERT MICROSOFT INITIATIVE HERE]?, your actions are not quite aligned with that!”, in this case, work/life balance.&lt;/p&gt;

&lt;p&gt;Not being in constant “ramp up” mode after hours is another area where I consider my adjustment to be a work in progress and at times, has been a major struggle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Misc. Observations!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Diversity &amp;amp; Inclusion!&lt;/strong&gt; - When you first join Microsoft, one of the first things you will learn is that Microsoft talks about diversity and inclusion a lot, maybe as much as Azure Consumption Rate and that is saying something &lt;img src=&quot;assets/images/smiley.png&quot; alt=&quot;&quot; /&gt;. Currently, Microsoft (and other Tech companies) is trying to be more &lt;em&gt;diverse and inclusive&lt;/em&gt; and they are constantly having internal conversations on what is the best way to go about being more diverse and inclusive.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Travel Days!&lt;/strong&gt; - Typically at most companies, you will travel on Sunday and work 10 hour days to leave on Thursday (&lt;em&gt;gotta get those 40 hours in!&lt;/em&gt;) or leave late Friday night. In CSE, Monday and Friday are considered &lt;em&gt;travel days&lt;/em&gt;. On these days, the only expectation is that you are traveling as Microsoft does not expect that you will travel on weekends except in very rare circumstances. Personal time is very important.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Polls Polls Polls!&lt;/strong&gt; - Similar to their love of Developers, Developers, Developers, one thing I have learned about Microsoft is they really love to do Polls. You will have a poll for on-boarding, you will have polls when you do Off-site Events, there is the annual company-wide MSPoll Poll and team-specific polls like Core Service Engineering (Internal IT for Microsoft). What this tells me is that Microsoft seems to really care about what their employees think, this is why they are always collecting data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mentors!&lt;/strong&gt; - Microsoft is very big on employees having mentors. I myself, currently have 2 mentors with a combined years of service at Microsoft of roughly 27 years. I meet with one of my mentors (Nick D.) roughly every 2 weeks and my latest mentor (Darryl H.),roughly once a month. These individuals have been great (and very patient with me) because you can bounce a lot of things off of them, get career advice and they tend to keep you grounded.&lt;/p&gt;

&lt;p&gt;When you are meeting with mentors 3 times a month, coupled with meeting with your manager several times a month, there is a lot of structure there but also, it puts Microsoft (ie people) in a position to track how someone is doing to make sure that person is being put in the best position to succeed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Words!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;My short career at Microsoft has been interesting, bumpy, exciting, strange and at times a struggle. When I reach my 1 year anniversary, I am sure I will have a lot more observations to share!&lt;/p&gt;
</description>
        <pubDate>Sat, 11 May 2019 00:00:00 +0000</pubDate>
        <link>https://blog.michaeldeongreen.com/careeradvice/2019/05/11/my-first-six-months-at-microsoft.html</link>
        <guid isPermaLink="true">https://blog.michaeldeongreen.com/careeradvice/2019/05/11/my-first-six-months-at-microsoft.html</guid>
        
        <category>career</category>
        
        
        <category>careeradvice</category>
        
      </item>
    
  </channel>
</rss>
