<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bing C on Medium]]></title>
        <description><![CDATA[Stories by Bing C on Medium]]></description>
        <link>https://medium.com/@busycai?source=rss-2588bec2e422------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rVg-UAhOZSi5uWaQbFXZwQ@2x.jpeg</url>
            <title>Stories by Bing C on Medium</title>
            <link>https://medium.com/@busycai?source=rss-2588bec2e422------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:08:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@busycai/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dos and Don’ts in Perf Review as EM]]></title>
            <link>https://busycai.medium.com/dos-and-donts-in-perf-review-as-em-a32c53c41b52?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/a32c53c41b52</guid>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[performance-management]]></category>
            <category><![CDATA[performance-reviews]]></category>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Fri, 26 Aug 2022 01:34:23 GMT</pubDate>
            <atom:updated>2022-08-26T01:34:23.243Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O4KMq8OcdkCCe5Cn" /><figcaption>Photo by <a href="https://unsplash.com/@henry_be?utm_source=medium&amp;utm_medium=referral">Henry Be</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I just wrapped up the perf review recently. From the many perf reviews I have participated in both well-established companies and startups, though the process and practices may vary across different places, I believe there are some common principles there. Below is a brief list from my own experience.</p><h3>Dos</h3><ul><li><strong>Do check with yourself on unconscious bias upfront</strong> (halo effect, recency bias, similarity bias, etc). Take one example, just because Jason exceeded the expectation in prior cycle doesn’t necessarily mean his performance is going to sustain in subsequent cycles.</li><li><strong>Do set the tone early</strong>. If you believe you have gained sufficient artifacts (peer feedback, project progress, etc) to demonstrate that Jason’s perf rating is not going to be great, set the tone early and repeat the message along the way to ensure he is aligned with you on this. It is always idea to deliver someone a low perf rating that they never anticipated.</li><li><strong>Do gather artifacts from your reports</strong> to demonstrate their achievements. Instead of relying on your memory (which is usually unreliable), explicitly asking your reports to summarize what they’ve done. This also helps eliminate subjective bias you may hold due to your visibility on different projects may vary.</li></ul><h3>Don’ts</h3><ul><li><strong>Don’t make any promise when uncertainty still exists</strong>. There are many moving parts out of your control that affect perf ratings, you can share positive words but guaranteeing things upfront may not be a good idea since it will complicate the conversation if the final result is not as good as you promised.</li><li><strong>Don’t forget to look forward. </strong>Perf review is the time to look back on what everyone has done and reward great performers by promotion or compensation lift, etc. It is also a great chance to discuss feedback received from co-workers, identify areas to grow, and set up plans to succeed in the next cycle and beyond.</li><li><strong>Don’t ignore questions from your reports</strong>. As you are delivering the perf results, don’t forget to solicit questions from your reports, and also be prepared to answer any concerns they have. To make it as a bi-directional conversation, you ensure the results are receptive and everyone is aligned.</li></ul><p>This is not an exhaustive list by any means, and it may be subjective since it is from my observation. I’d love to hear if you have different thoughts or anything to add. Please leave your comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a32c53c41b52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A dreadful mistake I ever made as an Engineering Manager]]></title>
            <link>https://busycai.medium.com/a-dreadful-mistake-i-ever-made-as-an-engineering-manager-36c60afc93e7?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c60afc93e7</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Wed, 25 May 2022 23:29:15 GMT</pubDate>
            <atom:updated>2022-05-26T01:21:27.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a2fqVKLkFaMdXZcH" /><figcaption>Photo by <a href="https://unsplash.com/@magdaleny?utm_source=medium&amp;utm_medium=referral">Magdalena Smolnicka</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>My management style is built based upon my personality traits, and has been significantly influenced by the companies I worked for, the leaders I worked with, the knowledge shared by brilliant people, and especially the many mistakes I’ve ever made. In this post, I’d like to share an essential lesson I’ve learned a few years ago, which is transformative and valuable from my own experience.</p><p><strong>TLDR: DON’T ONLY GIVE CONSTRUCTIVE FEEDBACK</strong></p><p>This happened during my first few months after becoming a people manager. Ever since the first day as an EM, I was fully aware that great people managers are supposed to be responsible for team members’ career growth and goals. I fully advocated that and I was so eager to make progress on this end after becoming a people manager. Eventually, I decided to proceed toward this direction by giving feedback to all my team members whenever I saw areas for improvement. I started to put a lot of time on observing their behavior and sharing my suggestions to them in private. I also deliberately framed my feedback in a timely and actionable format, so they can make the best out of it. I felt super excited about my plan.</p><p>My intent by doing this was quite positive, I cared about my team and was really hoping I can give them a bootstrap on personal growth using my observation and experience. I wanted to build a solid team that everyone can thrive with huge impact and responsibility. I pretty much went all-in on this effort.</p><p>Until one day, one of my direct reports (let’s call him J) opened up to me during 1on1. J told me that he felt a bit frustrated by keep hearing “negative” feedback from me, and there were so many of them that he had no idea of where to get started. He was also concerned whether his performance was on track or not. Honestly, I didn’t anticipate this reaction from J, not at all. I thought that I had invested so much time and energy on my team that things should have been better than before, not the other way.</p><p>In retrospect, my empathy saved me. At that moment, I was able to put myself into J’s shoes, and suddenly I completely saw his complaint and feeling. If my manager keeps pouring me on different things that I can perform better, without saying what I’ve done well. I must be terrified.</p><p><strong>The lesson I learned from it is that, make sure your behavior is always aligned with your intent. </strong>You need to act appropriately and consistently to ensure your good intent can be well perceived by people. Don’t take it for granted. In my story, my intent was to accelerate my team growth to the next level by delivering feedback on how they can improve. However, my team member felt frustrated and confused because I was too biased on constructive ones. The misalignment between my intent and my action was the root cause to make this happen.</p><p>In hindsight, I was very lucky because my team member proactively brought it up to me while I was not thoughtful (this indicates that their trust on me is still there). At the time, I was in a full speed toward the direction I desired that I neglected my team’s feeling, which not only failed my goal in itself but also caused confusion to the team. Totally a reverse direction.</p><p>Things that have been working well for me since then,</p><ul><li>Celebrate with / Deliver positive feedback to your team members, in public and in private, do it often.</li><li>Deliver constructive feedback in private by stating your good intent upfront. Be narrative and authentic. One thing at a time: tell your engineers to focus on only one area to improve in every quarter so you guys can go deep.</li><li>Listen, appreciate, value and take actions on the voice heard from your team. Cultivate a psychologically safe vibe so everyone feel confident to open up to you on things not working.</li><li>Think and act thoughtfully. Do yourself a favor by taking a pause and self-checking on a regular basis. Don’t let your eagerness accidentally conceals the landscape view.</li></ul><p>Making mistakes is an inevitable part of our life, they are valuable as long as we gain from them. I am not urging you to make arbitrary mistakes since they may cause negative impact on you and others, but also don’t fear of mistakes and failures because they are an essential part of success. Try to learn as much from other people’s mistakes if you could, it is a fast track.</p><p>So, what is your favorite / shareable / wild mistake? :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c60afc93e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning from TL to EM]]></title>
            <link>https://busycai.medium.com/transitioning-from-tl-to-em-dd5815e825b3?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd5815e825b3</guid>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Tue, 19 Apr 2022 02:48:37 GMT</pubDate>
            <atom:updated>2022-04-19T02:48:37.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FP5oiWMPcpIzVCy4" /><figcaption>Photo by <a href="https://unsplash.com/@chrislawton?utm_source=medium&amp;utm_medium=referral">Chris Lawton</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In my <a href="https://medium.com/@busycai/how-to-build-trust-as-a-new-em-222d13c49675">last</a> article, I shared thoughts on trust building as an EM when you switch to a new team or company. Today, let’s talk about another different yet very common case: you are internally promoted from TL to EM by your managers. More often than not, you will start with a small-sized team (3–5 engineers) and most of your direct reports have been working with you for a certain length of period. Therefore, from a trust building standpoint, it’s more likely to be a warm start because of your demonstrated competency and cultivated relationships in the team. However, in order to make a smooth transition, you, as a Junior EM, still need to pay attention to many places from your early days. I’ve synthesized the following aspects based upon my observations and learned lessons. Without further ado, let’s jump into it.</p><h3><strong>1 Develop TL in your team</strong></h3><p>After being promoted to an EM, the first thing I suggest you to work on, is to start searching for candidates to substitute your prior TL role in the team. There are multiple benefits for you and your team by doing this which I will disclose in a minute. Depending on your team setup and expansion plan, you can either cultivate TL internally or hire from outside. Let me explain why this is important.</p><p>When I was a TL, my primary goal was around project success, for example, ensuring a product feature can be released on time, with high quality and positive user impact. To achieve this goal, most of my time were allocated in the following buckets: technical design, coding / code reviews, cross-team communication, defining roadmap and milestones, periodical check-ins, escalating issues to upper-level leads (e.g. resource). I fully enjoyed this role because I had high visibilities both on the projects and in the organization (In retrospect, my manager did a fantastic job in motivating and empowering me along the way). It was a super rewarding experience, I really loved it.</p><p>However, EM is not just about project success as what TL is. More importantly, EM is responsible for and evaluated by team success. This entails that, you have to set your team up for their success in the first place, then project success is more like an outcome derived from that. This is a fundamental mindset shift.</p><p>The major benefits of growing TL in an early stage are at least in two folds:</p><ul><li>With someone being delegated as TL, you can balance off better between technical work and managerial work (e.g. team assignment, hiring, perf review). This is not easy.</li><li>Engineers get motivated when they are promoted to TL roles at a proper phase which indicate more visibility, responsibility and growth opportunities.</li></ul><h3><strong>2 Put team first</strong></h3><p>At the end of the day, EM’s performance is not evaluated by your personal contribution but your whole team’s performance and growth. There must be a reason for that.</p><p>To put your team first, there are several aspects you should heavily invest your time into,</p><ul><li>Foster psychological safety. As an EM, you want to build a team that everyone feels safe to open up to you for any topics and don’t be afraid of retaliation or penalty. This is the foundation of delegation, feedback and team growth.</li><li>Motivate team members. Finalize your team mission and bind it together with the company/org top strategy, make sure everyone is crystal clear of the high-level picture and their work importance. On the other hand, people get motivated for different reasons, thus, build relationship with your team and understand what really motivates them and attempt to achieve a Triple Win situation on team setup and project assignments.</li><li>Prioritize your team growth. Put more time into coaching and giving/seeking feedback in a recurring and timely manner. When assigning a task/project, think about who can gain the most experience from it instead of just hoping to get it done as soon as possible.</li></ul><h3><strong>3 Build network with other EMs</strong></h3><p>Fortunately, we are not working in silos. Learning from people around you is such an amazing experience that I value a lot when changing jobs. First of all, you can learn from your managers who work closely with you. There are plenty of scenarios that you can either observe how your managers behave in public or share your struggles and solicit advices from them in private. Besides that, I also suggest you proactively connect with EMs outside of your organization or company. Several reasons,</p><ul><li>Good practices vary across workplaces. Connecting with people outside enables you get a diverse set of inputs and insights. These nutritions are naturally good for combating <a href="https://en.wikipedia.org/wiki/Filter_bubble#:~:text=A%20filter%20bubble%20or%20ideological,click%2Dbehavior%20and%20search%20history.">filter bubble</a> in a managerial role.</li><li>Sometimes, you may not feel confident or comfortable to bring up everything to your managers for some reasons. It is a perfect idea to share your stories to a stranger EM and receive professional advices from them.</li><li>It’s a small world. Building network in itself is good for your career.</li></ul><p>In my Google days, there are several channels to facilitate EMs to better connect across product areas and company. I was lucky to gain immensely from the following two programs:</p><ul><li>EM Guru. You can connect with senior leads (Sr EM or Eng Director) by booking 1on1s with them through a specific format. Each lead has a dedicated profile on their industrial experiences and what topics they want to provide guidance for (e.g. transitioning from TL to EM, building team from ground up).</li><li>EM Circle. After you enroll this program, you will be randomly grouped with several EMs (usually ~5 EM outside of your org) to form a circle. You guys meet every month with suggested agenda from the committee (e.g. perf review, conflict resolution), being spontaneous is totally fine as well. Compared with EM Guru, this one feels more like chatting with your EM counterparts who may share similar struggles as you. It’s more like a bi-directional conversation instead of getting coached by gurus.</li></ul><p>Okay. Time to wrap up. Transitioning from TL to EM is like opening a new door. When such an opportunity arises, I definitely encourage you to grasp it or strive for it. Though I did see some folks who switched from TL to EM and then switched back again, being able to figure out that something you intrinsically dislike is also beneficial from a career standpoint. There is really nothing to lose there, go for it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd5815e825b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build trust as a new EM]]></title>
            <link>https://busycai.medium.com/how-to-build-trust-as-a-new-em-222d13c49675?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/222d13c49675</guid>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Sat, 19 Mar 2022 06:59:47 GMT</pubDate>
            <atom:updated>2022-03-19T07:12:37.033Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RGRsgrPp_-uw5Sfk" /><figcaption>Photo by <a href="https://unsplash.com/@lightscape?utm_source=medium&amp;utm_medium=referral">Lightscape</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In late 2021, I decided to make a bold career move from FAANG to startups. This was the first time that I landed in a new company as an EM. Now, it’s has been about almost half a year, and I am thrilled to share that I get survived and start to steer the team toward the desired direction. Though this is just the start of a long journey, it may be a good timing to retrospect and shed light on how to gain trust, which is one of the most critical topics for a new EM, if not the only critical topic.</p><p>So, why trust? Switching jobs has never been easy. Part of the reason is due to large uncertainty and lack of trust. Uncertainty naturally goes down as you gradually familiarize yourself with the surroundings. But trust doesn’t play in this way, you really have to earn it by yourself. What’s even worse is, without trust, you (as an EM) could barely do anything. In a nutshell, my take is, earn your trust, from day one.</p><p>That feels a bit daunting. Isn’t it? Well, you may not have to go through this every single time. There is another scenario, a much easier one, is when you transition from an TL to an EM. This is what I experienced at FAANG a couple of years ago where I was promoted to be a people manager in the same org. In this case, the “<a href="https://en.wikipedia.org/wiki/Cold_start_(computing)">Cold Start</a>” problem that you have to deal with when moving to a new company (or a new team) just does not exist due to your certain tenure and great performance in the team. By the way, transitioning from TL to EM is another topic that I will discuss in a separate article.</p><p>In this article, I will talk about the first scenario and particularly focus on how to build trust with your direct reports. Don’t get me wrong, in the long run, gaining respect and trust from your managers, peers and stakeholders are equally important, if not more. It’s just that, as a new comer, in your first few months, I feel like it is more challenging and more crucial to handle this well within your team. I will explain it a bit later.</p><p>Think of “Building Trust” as a complex systematic project, it takes a spectrum of approaches to tackle it holistically, from both mental and operational perspectives. After pondering for a while, I’ve consolidated my thoughts into a handful of bullet points below.</p><h4>1 Don’t make favorable assumptions</h4><p>You team members are not the group of people who hired you, they may never meet you at all (not every company invites prospective team members into EM interviews). For example, they may already have a profound bond with your manager (i.e. their current direct manager) that they are not happy with adding a new person to their report chain. Even trickier, a senior IC in the team who wished to be in this EM role may not greet you as much as others. The point I would like to make here is not about picturing your team members are all bad people, not at all. The real point is, do not overly simplify things by assuming that everyone in your new team shares the same excitement as you do. More often than not, that is not the case, so please be well-prepared and anticipate sufficiently on hardships which would equip yourself with resilience and power.</p><h4>2 Be mindful on making changes</h4><p>As a new lead, you may have a desire to quickly exhibit your competency and establish your prestige by bringing in new changes such as creating a new code review guidance or switching to a new task management tool. There is nothing wrong about this per se. The problem is, are these the real pains that the whole team is undergoing right now? If the answer is no, then you are not solving a problem as you intended. In contrast, you are slowing the team down by adding new burdens to their plates. This is bad. Hence, every time when you urge to make a change, take a step back and solicit interests from your team, weigh on different voices and then decide what to do. It could never be wrong.</p><h4>3 Trust your team in the first place</h4><p>Your credibility gains as you share the credit with the whole team. Pretty much the same thing for trust. Simply put, it’s unlikely that you could gain respect and trust from the group if you don’t have trust in them upfront. That’s it. But how? First, be real, then pay particular attention on transparency and empowerment. For example, regularly communicate messages from upper levels, provide enough autonomy instead of micromanaging, continue delegating to senior engineers to make decisions before you sort things out, solicit feedback from your team and take actions to resolve them.</p><h4>4 Resort to your manager</h4><p>Don’t feel bad about asking for help from senior leads. At the end of the day, it’s a part of your manager’s responsibilities to fit you in the team. Of course, building trust is in the scope. For example, your team members may not open up to you when they don’t feel safe to do so, by getting a picture of your team morale and performance from your manager can help you identify the areas of improvement. Besides, you can create a 30–60–90 plan with your manager and check it on a regular basis. Moreover, you can share any of your confusions or struggles and seek good practices from your manager. In a nutshell, getting a jumpstart from your manager could lead to a win-win outcome which your manager would be thrilled to see, so go for it.</p><p>I’ve rambled too much. Time to conclude. My thoughts may feel a bit shallow since my experience on this topic is still somewhat limited. At the very least, it does no harm to reflect and share what I’ve learn to spark for more interests and insights. Please feel free to share yours if any and good luck!</p><p><em>[acronyms]</em></p><p><em>EM: Engineering Manager</em></p><p><em>IC: Individual Contributor</em></p><p><em>TL: Tech Lead</em></p><p><em>FAANG: Facebook(Meta), Apple, Amazon, Netflix, Google</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=222d13c49675" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a great software engineering manager?]]></title>
            <link>https://busycai.medium.com/what-makes-a-great-software-engineering-manager-d467a47d2a32?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/d467a47d2a32</guid>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Fri, 04 Feb 2022 22:52:21 GMT</pubDate>
            <atom:updated>2022-02-05T00:24:22.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5vvuVjOIWng1DNun" /><figcaption>Photo by <a href="https://unsplash.com/@aaronburden?utm_source=medium&amp;utm_medium=referral">Aaron Burden</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>EM is a tough job</h3><p>There is no doubt that every EM (Engineering Manager) has their own style which makes it difficult to conclude a standardized role model for this position. Thus there is no single type of great EM, they come in a variety of forms, and I believe everyone has a chance to thrive as an EM (though it may take some time).</p><p>That being said, EM is not an easy job by any means. It actually takes a totally different skillset from being a great software engineer. Some people may feel it is a natural transition from IC (Individual Contributor) to EM as time goes by, which I may have a different opinion based on my experience.</p><h3>My random thoughts</h3><p>I have been an EM for 3+ years in two tech companies in the US so far (one is FAANG, the other is a late-stage startup) and I got a chance to work with many different but awesome EMs. According to my observation and self-reflection, I bring together the following aspects which a great EM should be quite capable of from my standpoint,</p><p>a) Vision. Great EMs are visionaries. They spend a lot of time on strategic thinking on how to bring the team to the next level by envisioning team mission and goals. On one hand, they are crystal clear of the company long-term goals and value proposition. On the other hand, They always think out of the box and are able to tightly bind their team goal/setup with the company mission by conceiving and leading initiatives to roll the snowball. By doing this, EMs depict a clear high-level picture which helps their team members to understand the roadmaps and the rationale. This is critical for team morale and execution.</p><p>b) Authenticity. Great EMs are inherently authentic people and some are vulnerable too. Let me share a story to explain. Say, you are sitting with you manager Ben in a 1on1, Ben tells you that your promo didn’t go through this time, you feel frustrated and disappointed. After checking with your feeling, Ben begins the conversation by sharing his own promo story. He also failed a promo two years ago, at the time, he felt super down especially when he knew some of his peers made it (Ben sends you a message that he was there before, your feeling can totally resonate him). In a similar 1on1, Ben’s manager shared and explained the concerns from the promo committee regarding leadership and impact. They also discussed making a plan to resolve those concerns in the next six months so as to increase promo odds next cycle. Eventually Ben made the promo after 6 months, with a superb perf rating. Ben concluded his story by saying that failing for the first time is not the end of the world, in contrast, it actually can help you on handling failures, and everyone knows failure is inevitable topic in our lives. At the end of the 1on1, Ben says the most important thing is to digest the feedback and create a promo plan for it, he will set up additional 1on1s with you to nail it down and check with you on a monthly basis to ensure everything is on track towards the promo next time (Ben described a very clear path to you and he didn’t make it up, it was from his personal experience, he knows how to succeed). How do you feel if you have an EM like Ben? Being an authentic person is just inherently good for building rapport and trust which has been a fundamental block of building cohesive teams.</p><p>c) Coaching. As stats told, career development and personal growth are critical dimensions that more and more employees start to be keen at. Being an EM, you are the main person to support your team members on this aspect. Great EMs invest significant amount of times with the team on career growth and coach team members by 1) enhancing self-awareness in general, or 2) leading by examples on areas you can improve, or 3) offering timely feedback on specific things. Nothing feels better than that when you see you are making progressive improvements on your desired trajectory under your manager’s guide and support.</p><p>Let me stop here. I think I just scratched the surface because 1) becoming a great EM is a very challenging topic and 2) I would not claim myself as a great manager, there is still a loooong way to go. Meanwhile, there are many other aspects may attribute to great EMs (e.g. decision-making, team setup, conflict resolving, growth mindset, execution, etc). Some of them are even more important than what I mentioned above, it depends on your circumstance.</p><h3>My recommendations</h3><p><strong>Books:</strong></p><p><em>The Making of a Manager (by Julie Zhou)</em></p><p><em>Radical Candor (by Kim Scott)</em></p><p><strong>Podcast:</strong></p><p><em>The Engineering Leadership Podcast by SFELC </em><a href="https://open.spotify.com/show/1wIytRQ4Ub8McXSP1iDwVX"><em>https://open.spotify.com/show/1wIytRQ4Ub8McXSP1iDwVX</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d467a47d2a32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Year Resolution for 2022]]></title>
            <link>https://busycai.medium.com/new-year-resolution-for-2022-722189aab9e2?source=rss-2588bec2e422------2</link>
            <guid isPermaLink="false">https://medium.com/p/722189aab9e2</guid>
            <category><![CDATA[new-year-resolution]]></category>
            <dc:creator><![CDATA[Bing C]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 21:16:09 GMT</pubDate>
            <atom:updated>2022-02-05T00:25:29.012Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rtk-qxAvZ36Bz_83" /><figcaption>Photo by <a href="https://unsplash.com/@sf_mediach?utm_source=medium&amp;utm_medium=referral">Sven Fischer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve been thinking about writing on a regular basis for a while. The problem is, during the last decade, I kicked it off for several times but was never managed to persist. I’d like to pick it up again right now for some reasons. Though I have no clue of what I am gonna jot down, I don’t see it as a big deal. This time, the only hope I have is, to cultivate writing as a habit for myself. What I truly believe is that, habits like physical exercise, reading or writing could invisibly introduce positive influence on your many other aspects (e.g. behavior, mental status, productivity). This is so called “core habit”.</p><p>Let’s do it.</p><p>As only two days left for 2021, it is a perfect timing to do some plannings for the new year. So, let’s start our first post with new year resolution.</p><p>The high-level attitude I have is, I hope to keep learning and growing, but in a healthy manner, I don’t want to make myself too stretched or burned out. During the pandemic, we had a practice to shrink team OKR into top 3 things so as to balance team members’ well being. Let’s copy this notion here.</p><p><strong>Resolution #1: Reading 80 books</strong></p><p>Come on. Why only books? Because I feel differently when reading books vs others (e.g. articles, magazines). It is just intrinsically more engaging and immersive to me.</p><p>One thing I feel like I am doing okay is book reading. I was able to read about 300 books in the past 3 years which took me over 1500 hours, and many of the books(perhaps over 80%) have no direct overlap with my job, which is the part I am pretty satisfied.</p><p>In 2022, I hope to continue, but considering I also wanted to catch up on other ends. Let’s make it 80. Though I don’t think quantity tells the whole story nor the best measurement is, it does make it easy to track and celebrate. So, let’s stick to it.</p><p><strong>Resolution #2: Learning Japanese on a 365-days streak</strong></p><p>When was the last time I started to learn a new language? When I was a junior middle school student which was over 20 years ago! My brain hasn’t get a chance to stimulate by new language learnings for such a long period of time, which is unimaginable.</p><p>Of course, this is just a virtual reason. I have no idea of how my brain could benefit from learning new languages (perhaps worth to check some neuroscience studies to find out). The real reason is, I am currently working for a startup which is headquartered in Japan (though I am based in North California), and I was exposed to Japanese in some scenarios which triggers my curiosity. Other than that, I am also interested in Japanese culture elements (e.g. Japanese Zen ぜん, Fashion &amp; Design, Nintendo &amp; Games, Manga). All of these coming together to make me feel it is a good timing to get into this.</p><p>I don’t have a concrete goal of which level I would like to achieve. Currently I am learning on Duolingo and I like how I have been incentivized by the “N days streak” concept, so let’s say, I am gonna spend time on Japanese on a daily basis throughout the whole 2022.</p><p><strong>Resolution #3: Getting up to speed on Web 3.0</strong></p><p>“Getting up to speed” sounds pretty vague and might not be a good signal for setting up goals. I may be able to write some posts here regarding Web 3.0 or even participate in coding a bit, but neither sounds very clear to me at this point. Along the way, perhaps I will revamp this goal setting to make it more trackable at a certain point. The rough idea behind the scene is, I don’t want to miss out Web 3.0 (plus crypto, blockchain and related excitements) which could be a big deal to make the society function in a more autonomous and efficient way. This is a big deal. I can’t wait.</p><p>That’s pretty much it. I feel excited to finally jot down something for real. Good start for me! If you also have a plan for your 2022, then good luck and enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722189aab9e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>