<?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 Daisuke Fujiwara on Medium]]></title>
        <description><![CDATA[Stories by Daisuke Fujiwara on Medium]]></description>
        <link>https://medium.com/@daisuke.fujiwara?source=rss-decf125492c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tFW30YvSc6UJQZT1jq4l4Q.jpeg</url>
            <title>Stories by Daisuke Fujiwara on Medium</title>
            <link>https://medium.com/@daisuke.fujiwara?source=rss-decf125492c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:28:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daisuke.fujiwara/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[My Team’s Shared Values]]></title>
            <link>https://medium.com/@daisuke.fujiwara/my-teams-shared-values-88b9a2c33b31?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/88b9a2c33b31</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 05:46:04 GMT</pubDate>
            <atom:updated>2019-10-15T05:46:04.062Z</atom:updated>
            <content:encoded><![CDATA[<p>As an engineering manager, I have been interviewing a fair number of candidates recently for my team, and one question I frequently ask is “what do you think are important values of your team?” I think it’s a really great question. There are so many opportunities out there as a software engineer, and it’s not an easy task to find a team that shares the same set of values.</p><p>Even though my team is still new, formed in March 2019, our values have slowly started to materialize. These might evolve over time to be something better or different, but what we have today has built our team’s initial foundation and continues to make the team stronger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cs2EwUx-F5I97d1TUE5uVA@2x.jpeg" /></figure><h3><strong>Sharing knowledge</strong></h3><p>Everyone in the team comes from a different background and expertise. It was a natural thing to create a space where we can share the knowledge that we are collectively accumulating as well as new topics that we are interested in. We formalized this in two ways: “share your knowledge” and “video learning sessions”.</p><p>I have written about “share your knowledge” before, and we currently run this once a month for an hour. It’s essentially an open session where the team gets together to talk about any technical topic that they want to share with the rest of the team. The topics can come from what they did at work, their side projects, or what they read. Besides collectively learning, there are two other benefits to this. First, it certainly pushes the presenter to come with more than a superficial understanding of the topic; they need to understand the topic well enough to share it in a cohesive way. Second, after having enough knowledge of the topic, they must be able to present it in a way that others can understand — a great practice in communication.</p><p>Video learning sessions is exactly what they sound like. Once every other week during lunch, we watch a video and discuss it afterwards. The videos are usually technical, but that’s not a requirement. They are chosen by a team member in a rotation based on their interest, which is designed to cover a wide range of topics. Some videos we have watched recently are “Golang concurrency”, “AR/VR in activism”, and “Unicode in Python”.</p><p>Rather than continuously chasing after tasks for the current project, these team activities provide us an opportunity to step back, take a breath, and enjoy learning in an open environment, which certainly brings the team together.</p><h3>Remote centric</h3><p>Remote work has certainly been a much discussed topic these days. Considering that hiring needs outweigh the rates at which companies are hiring, many companies are expanding their reach to people who aren’t co-located geographically. My team is not an exception; one of us is remote.</p><p>I previously had an experience where one of my team members worked remotely, and I learned that the team dynamics don’t work as well if we treat the remote employee as an exception. So with my current team, we embraced this remoteness wholeheartedly.</p><p>We rely heavily on asynchronous communication tools like Slack to keep everyone in the loop. We update our documents, such as team weekly meeting notes and project specs, as frequently as needed, so that everyone has access to the latest information. Meeting are run using a video conferencing tools like Zoom.</p><p>All of these practices help the team operate effectively despite the fact that we may be in different locations. But we go beyond that. I have encouraged the remote team member to schedule 1:1 with their peers on a regular basis in addition to their manager 1:1s. The aim is to get more individualized touch points from everyone and get a fuller context of what’s going across the team. Even jokes are shared on Slack by default, and we also have a bantering channel.</p><p>Additionally, we recently introduced a concept called “break time”. This is time that happens once a month where all of us go grab a beverage of our choice and sit down to chat via a video conference call. The idea is to have no work related agenda, so that it’s a free form way to catch up with what’s happening with life outside of work.</p><p>All of these considerations help to keep the team as a single cohesive unit and facilitate communication and trust building.</p><h3>Feedback oriented</h3><p>Most people are always looking to improve themselves in a professional environment. That’s what drives them to be successful and to invest time to hone their craft. However, one of the most frustrating things is being uncertain about your own progress. This is why constant feedback is important.</p><p>In my team, I encourage my direct reports to have a feedback session among themselves for every project we finish, which typically runs for 3 months. Additionally because our projects generally involve other teams, we ask for feedback from the individual’s counterpart. For example, my team’s data analyst will be asking for feedback from the data analyst whom they had to work closely with on a different team. The formats that were used to solicit feedback ranged form a survey in Google Forms to informal lunch conversation.</p><p>By requesting 360° feedback, the idea is to get a more comprehensive view into what went well and how we can improve. It’s important to get as many different perspectives as possible and digest that for oneself. Then they bring these digested feedback to our 1:1 for us to discuss. This becomes a good launch spot for me to give any additional feedback and come up with any plans and action items that could help my direct reports. I usually remind my direct reports to start thinking about the feedback cycle a couple of weeks before we wrap up the project during our 1:1s.</p><p>Constant feedback sessions help my direct reports get better at receiving feedback by appropriately framing the feedback request and digesting the responses. A few things I advise my direct reports to do are:</p><ul><li>Ask questions in an open ended way rather than a binary “Did I meet your expectations?” format. This helps open up a deeper discussion</li><li>Even though it’s important to understand what can be improved, it’s equally important to understand what went well. This helps to identify good practices to keep!</li><li>Ensure that feedback is provided in a timely manner. Follow up as needed.</li></ul><p>It also helps them improve at providing feedback to their teammates. Everyone hones their skills of acknowledging others’ good work, encouraging them to keep improving, and sharing constructive criticism in an effective way. Collectively, I believe this makes my team stronger.</p><p>Feedback is a form of art in which everyone should to practice over and over to understand what works and what doesn’t. I want to provide that space for my team to explore this.</p><p>These are the values that we practice as a team. Obviously this is not the entirety of what we care about as the team, but having these codified in this way helps me and my team refer back for clarity. I hope to revisit this blog from time to time as a reminder and to keep it up to date.</p><p>I would love to know if you have any special values that you really care about.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88b9a2c33b31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decision making]]></title>
            <link>https://medium.com/@daisuke.fujiwara/decision-making-c0cadcc16451?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0cadcc16451</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 01:35:25 GMT</pubDate>
            <atom:updated>2018-06-11T01:35:25.390Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first became an engineering manager, I had a solid idea of how I wanted to build up my team, based around the philosophies of mutual trust, shared responsibility / accountability, and consensus. All these points originated from my own experience of being managed and seeing what worked and what didn’t.</p><p>But your responsibilities as a leader of people isn’t only about setting the right goals. You have to practice them, see how the team adopts them, solicit feedback, and course correct as needed.</p><p>In this post, I wanted to talk about how my approach of making decisions evolved as I gained experience as a manager.</p><p>My notion of concensus driven decision making was based on the assumption that people will present different ideas and perspectives, provide supporting evidence, discuss openly as a team, and end with a decision that the team collectively believes to be the best. Sounds perfect, doesn’t it?</p><p>However, in such a simplified view, I overlooked two basic but important things: people’s opinions and emotions. Healthy amount of opinions and emotions are good thing. They drive people to excel and feel a sense of ownership, but they need to be kept in a fine balance. Being too emotionally invested or adamant about one’s opinion leads to cloudy judgement, stalled decisions, or loss of focus and ultimately slows down the entire team.</p><p>In the context of software engineering, people’s opinions and emotions usually come out during technical debates about what architectural patterns to use or which tool to adopt. But simple changes in processes can trigger emotional reactions from your team members as well.</p><p>So what are the concrete steps to facilitate the decision making process in a team setting that don’t polarize the team? Here are some pointers that I have learned along the way:</p><ul><li><strong>Understand the problem</strong>. Without grasping the full context of the issue at the hand, debating about solutions doesn’t yield a great outcome. Equally important to understand is the urgency of the problem. “Is it important to solve this now?” is a valuable question that you should always ask.</li><li><strong>Do your homework</strong>. You have to be sufficiently familiar with the matter in hand both technically and non-technically. Read up on available technologies that claim to solve the particular issue and research if other engineering teams have solved related issues. Note that you don’t have to become an expert in the topic, but obtaining basic relelvant knowledge is a must.</li><li><strong>Listen and ask questions</strong>. By preparing for the discussion, you would inevitably form an opinion of the issue, but do your best not to force it on your team. Asking insightful and challenging questions is a great way to steer the conversation without making the team feel that they have lost control of the decision making process. As a result, the team will more likely to form stronger ownership of the topic.</li><li><strong>Exercise your judgment</strong>, which is the most important part. At one point, the natural flow of the decision making process may come to an end. Your team members hold on to their perspectives, the team loses interest in discussing further, and then the decision stalls. This is the point where you, as a leader, have to step in and take a proactive role. You can ask more questions to keep the discussions going on or make the final call, stating that you have heard everyone and in the interest of the team, you have to choose. Note that not reaching a decision is the worst outcome here. Your team feels like all the effort they put in was wasted and they can’t make any meaningful changes.</li><li><strong>Finally, own the final decision</strong>. Whether you had to call the final shot or not, ultimately you also own the decision that the team made, especially if the result of the decision didn’t pan out as expected — no blaming anyone from your team :) Obviously, if the decision that the team made worked out well, step aside and give the credit to where it’s due. In either situation, co-owning the decision helps foster deeper team trust. You have to practice saying “Sounds good, I believe that’s a good decision. Let’s go with it!”</li></ul><p>I believe that understanding when and how a decision should be made for your team is a big responsibility of a leader. Indecisiveness stalls the team’s momentum, causes the team to lose focus, hurts team’s morale, and ultimately deteriorates the team’s trust.</p><p>Now, the hardest part is that this is not an exact science. It requires finness, bold ownership, and practice. So don’t get discouraged, solicit advice / feedback, and keep at it!</p><p>I have more to learn about the art of decision making and hopefully you can share some of your learnings with me.</p><p>If you enjoyed what you read and want to read more of what I write, please follow me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0cadcc16451" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First time being an engineering manager]]></title>
            <link>https://medium.com/@daisuke.fujiwara/first-time-being-an-engineering-manager-72337280227d?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/72337280227d</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Sat, 09 Jun 2018 05:57:33 GMT</pubDate>
            <atom:updated>2018-06-09T06:36:55.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD7e-gF1H0j_9-bDunKTZg@2x.jpeg" /></figure><p>Recently I came across the question of how a first time manager could fail. Thinking about the time I became a manager for the first time, I didn’t have much formal training or knowledge of dos and don’ts. For me, this question was an interesting thought exercise which made me reflect back to my experience from years ago. I know there is a fair amount of literature written about being a first time manager, but in this post, I would like to share my learnings from my own experiences and mistakes.</p><h3>My first mistake</h3><p>When I first became a manager, a very natural way to process the change was to consider it as an extension of my previous responsibilities. In my case, it was to bolt on the new tasks of managing a team of engineers on top of my daily engineering work.<strong> </strong>This felt natural because I was still capable of writing and deploying code and owned a healthy amount of systems prior to becoming a manager. And why would I stop adding value just because I suddenly have a different role? Yep, that was the mindset I had.</p><p>I didn’t spend enough time to digest what it really meant to become a full time manager. Sure, prior to officially becoming the manager of a team, I was performing managerial tasks such as keeping product and technical specs up to date, triaging issues, unblocking other teammates with code reviews, and mentoring younger engineers. But those were additional tasks that I chose to do on top of my core responsibility, and I kept treating them as such even after my role change.</p><p>Looking back, I should have told my old self to change my mindset. It’s easier said than done because the real question is what mindset to change to.</p><h3>Different mindset</h3><p>It’s not immediately clear why a manager spending time on coding is not effective. You are an engineering manager, so shouldn’t you be on the forefront of engineering pushing code to production? Well, the art of writing software requires focus and dedicated time to produce well written and well tested code. So if you are busy operating at that low and narrow level, you won’t have mental capacity to see the bigger picture. What does this “bigger picture” entail? Many things, actually. Here is my list:</p><ul><li>team building / managing team morale</li><li>task prioritization, scheduling, and unblocking outstanding decisions</li><li>long term strategy / roadmap</li><li>Inter-team communication</li><li>1:1s / career development / training</li></ul><p>There are many things a manager is responsible for and they aren’t as clearly defined as an engineer’s responsibilities. As a manager, you have to look at the entire team’s execution most if not all of the time, not lines of code with a magnifying glass. It’s more about breadth than depth.</p><p>Now that you understand what tasks define the role of an engineering manager, let’s talk about why these are important. It’s not exactly easy to articulate why they have more value than the coding you used to do.</p><h3>Your team is counting on you</h3><p>Being a manager means that you are responsible for the team. You represent the team to other parts of the organization. So it’s really crucial for you to always gather information related to your team. You have to make sense out of the information and craft a coherent narrative. You have to communicate the status, issues, and achievements of your team to your peers, other stake holders, and the upper management. Your team is counting on you to represent them in the most accurate way and chamipon them so that they can focus on what they have to do.</p><p>Equally important, you have to provide new information to your team members with the appropriate amount of context as soon as possible. You are your team’s primary communication channel with the rest of the organization, and clear, timely communication will help them work more effectively.</p><p>And by doing all of those above, you are helping your entire organization run more effectively.</p><p>So, everyone is counting on you to make everyone work better :)</p><h3>Hindsight is 20/20</h3><p>All of what I have learned as a manager are from my own experience making mistakes, getting feedback, and trying different approaches. It wasn’t easy by any means, and I still have a lot more to learn. Management is a very different challenge from coding, but for me, a team collaboratively achieving a goal is such a rewarding experience despite all the challenges that may arise.</p><p>If you liked this post, follow me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72337280227d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My lessons being an engineering leader — team activities]]></title>
            <link>https://medium.com/@daisuke.fujiwara/my-lessons-being-an-engineering-leader-team-activites-82827551b189?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/82827551b189</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 06:27:24 GMT</pubDate>
            <atom:updated>2018-02-27T16:01:00.266Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*shMpAXpWkFHXRbyn6qcVtw.jpeg" /><figcaption>Boba tea from <a href="http://www.bobaguys.com/">Boba Guys</a></figcaption></figure><p>As an engineering leader, you have many responsibilities to keep your team highly efficient, empowered, and motivated. Your responsibilities include but are not limited to:</p><ul><li>Make sure inter-team and intra-team communication channels are established and flowing well. Information can be what makes or breaks a project.</li><li>Be aware of the general operations of day to day and proactively unblock any major issues, but not all issues, you want your team to find a way to unblock themselves.</li><li>Pay attention to your team’s morale. Listen to their feedback and bring swift actions to indicate that their voices are heard.</li></ul><p>That’s your primarily goal — to make your team greater than the sum of all individuals. However, achieving this goal doesn’t have to happen within the four walls of the office. In fact, this blog post is about finding an activity that’s suitable for your team where individual member can participate and enjoy during the working hours. I call it: “team activity”.</p><p>What I am suggesting isn’t a far fetched idea; anyone would instinctively understand why it’s import to have a team activity. But for the sake of this post, let me explain.</p><p>If your team members showed up to work every day on time, focused and finished all assigned tasks for that day, and went home, do you think you have the most resilient and happiest team? Probably not.</p><p>Here are the situations which would challenge the above mentioned team:</p><ul><li>When an issue/fire arises due to how work by multiple engineers collided unexpectedly. Where would the ownership lie? Will other team members be willing to either escalate or support the effort to resolve the issue?</li><li>When someone from the team moves off to a different team or company. How would the hole be filled in by the remaining team? Would anyone be knowledgeable enough to onboard a new member onto the team, knowing that they take a productivity hit.</li><li>When team members have a heated argument. Would anyone involved in the argument step back and reach a mutual agreement? Would anyone not directly involved in the argument step up and be a facilitator?</li></ul><p>In<a href="https://medium.com/@daisuke.fujiwara/my-lessons-being-an-engineering-manager-part-1-426d89b54964"> my previous post</a>, I have discussed my point of view of how important for an engineering leader to gain trust from their team. Well, turns out that it’s as important or more for your team members to trust each other. Google’s extensive research into team dynamics has concluded the most important aspect of a team is psychological safety net — the feeling that no one will negatively judge you.</p><p>Also, if each team member spends the majority of their time investing in themselves, they tend to lose the greater context of how the team as a whole is operating. Some may argue that understanding the broader context is an engineering leader’s responsibility, but I think it creates a rather fragile team. A individually-focused team isn’t a defining characteristic of a high-performing team. For instance what should happen if you, the engineering leader, take a vacation? Should you check in every day during their vacation to ensure that nothing imploded? Clearly, the answer is no.</p><p>I believe team activities cultivate inter-team trust development which leads to more free form information exchange. This then results in individuals feeling empowered and confident to make a right call in different circumstances.</p><p>So how do team activities can help foster trust?</p><p>Let me break it down:</p><ul><li>Outside of the context of doing the actual work, during a team activity, you start to see your fellow co-workers as people who have lives outside of work — sharing what you did over the weekend and learning that two people share similar interests. Much like any social relationship, this is a beginning of something that’s deeper than just being “co-workers”.</li><li>You gain experience of sharing working information.</li></ul><blockquote>“I heard that you were working on the “Big Feature”</blockquote><blockquote>“What exactly is that?”</blockquote><blockquote>“Oh I know that X has done a similar thing before. If you get stuck, you should reach out to him.”</blockquote><ul><li>This is an opt-in activity. No one is going to mandate that everyone participates, but making this conscious decision to join gives a tremendous sense of belonging and helps to build a team identity. With the shared identity, you further establish that you share mutual goals and that naturally leads to deeper trust.</li></ul><p>During my previous role as an engineering leader, my team had a weekly (sometimes more than once a week) trip to near by a <a href="https://en.wikipedia.org/wiki/Bubble_tea">boba/bubble tea</a> shop. It started from my own obsession of the tasty beverage, but slowly over time, it became a team activity (perhaps more like a ritual). The coolest thing was that people from outside of the team shared a similar affinity to the drink and/or thought it was an interesting activity, so they decided to join our activity. What started as an inter-team activity then became an intra-team activity.</p><p>To be honest, as much as the team enjoyed the drink, the best benefit was the walk there to the shop and back. It created space for the serendipitous conversations and helped form a natural bond among teammates.</p><p>Now at my current role, we have a company wide (two full people!) coffee run in the afternoon. I know it’s not as unique as boba tea, but the benefits are there even though I don’t drink coffee. We have ad-hoc brainstorming sessions, talk about current events in the tech world, and just simply get to know each other better.</p><p>You might be wondering if eating lunch together can be an effective team activity. I believe it certainly can help achieve the goal(a team that eats together, sticks together), but it is not the most effective form. I think it’s because lunchtime is universal, so the time and emotional investment is not as high. Also, most people eat around the same time, so it doesn’t feel like you are actively creating a team identity. However, I think there is definitely a similar value in the walk to get lunch, much like what I described in the previous section.</p><p>I hope you are now convinced that a shared team activity is an important aspect of your leadership :) You don’t have be the sole owner, much like anything else. You can start it or facilitate it; the important thing here is that you support the movement.</p><p>It’s such a low hurdle task that you can start and just like anything else you can constantly iterate to suit your team’s preference. It also functions as a break so it generally helps your team to come back to work refreshed and focused.</p><p>It is important to stress that team activities help, but they can’t completely replace a toxic or ineffective working environment. You still have to ensure that priorities are clearly set for the team and communicated, commit to your weekly 1:1s, and go an extra mile to make sure no one is blocked for long.</p><p>One thing I didn’t touch in this post is what would be an equivalent notion for a remote team. Unfortunately, I do not have an extensive experience with a remote team, so I am hoping to gain some insight from the readers with related experience. Regardless, the concept of team activity applies to remote teams especially when the team gets together in one physical location. The frequency of that happening may be less compared to onsite teams, but I believe the team can still reap the benefits.</p><p>If you enjoyed what you read and want to read more of what I write, please follow me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82827551b189" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My lessons being an engineering manager— part 1]]></title>
            <link>https://medium.com/@daisuke.fujiwara/my-lessons-being-an-engineering-manager-part-1-426d89b54964?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/426d89b54964</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[technical-le]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 05:14:22 GMT</pubDate>
            <atom:updated>2017-06-28T05:14:22.027Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*60Ix7TEZIpoguQA80DDwvA@2x.png" /></figure><p>Until recently I had an amazing opportunity to lead a team of mobile engineers at <a href="http://www.nextdoor.com/">Nextdoor</a>. As a first time manager, the experience of going from an individual contributor to one responsible for a team and the greater good was an interesting challenge with lots of learnings. In this series of posts, I would like to share some of my lessons of being a manager first hand.</p><h4>Trust</h4><p>From my experience, trust was the most fundamental thing that makes or breaks the team. You, as a manager, have to gain trust of your direct reports and in turn you have to trust them. Also, you have to maintain the trust throughout the course of your leadership; trust is not a static concept.</p><p>What I have noticed is that without a sense of trust, the members of the team will not discuss important issues openly, especially with you. This leads to superficial consensus, suboptimal decisions, ineffective team dynamics, and a lot of stress on you. Essentially without trust, individuals will focus on themselves; highly optimized individuals don’t necessary lead to the most effective team.</p><p>So as a leader of the team, what’s the best way to gain trust from your team? My best advice is to put your effort into listening to them.</p><p>Listening is a valuable skill to develop since it really gives you what you need the most as a manager — information. Your job then is to analyze that information and provide appropriate feedback and support. This leads to collaboration where your direct reports see that their voices were heard, valued, and acted upon. Additionally, this can be an opportunity for your direct reports to receive feedback and a different perspective from you, which helps them self reflect and improve.</p><h4>1:1</h4><p>Now that you know you have to listen to what your direct reports have to say, what’s the best forum for it? My answer is your weekly 1:1. There are plenty of other sources that emphasize the value of 1:1s, and they are all true. Some managers choose to have them every other week, but my preference is to have it every week and keep it shorter. The important thing here is to commit to a schedule, agree on the time, put it on the calendar, and be there on time. The act of having it on a regular basis is the first step to establishing trust; it shows that you are there for them.</p><p>I don’t have a strong opinion on how 1:1s should be conducted. My preference was to keep it relatively free-form to discuss any relevant topics. However, one thing I asked my direct reports most of the time was their “happiness index”. This was a system that was suggested by one of my direct reports (see I am listening to their feedback :)) which basically gave everyone to come up with a score between 1 and 10 that roughly reflects their professional happiness. This was actually a good conversation starter for following reasons:</p><ul><li>Allows direct reports to remember what happened over the past week. Usually all they have in mind is what is happening right now/today, so giving them a bit of time to reflect is good.</li><li>Facilitates specific conversations about things that are going well and not so well. Usually direct reports can provide context to help you understand the priorities of topics to discuss.</li><li>Sets up for action items for both sides to change/improve things.</li></ul><p>Make sure you keep light weight notes of the 1:1s. This allows you to be prepared for next 1:1 and be on the same page about any open items that you and your direct report agreed to do before the meeting.</p><p>Lastly, it’s totally fine to end the meeting early if there is nothing more to talk about.</p><h4>Importance of following through</h4><p>1:1s are meaningless if things aren’t changing for better. Otherwise your direct reports would much prefer to get their coding done. That’s why following through with any action items from previous 1:1s is critical. Make sure to revisit your notes before your next meeting and set aside some time to get to things you promised.</p><p>Some of the action items I have had to tackle:</p><ul><li>Getting a full team more coordinated because during 1:1s it was apparent that not everyone was on the same page about the project scope.</li><li>Troubleshoot any inter-team conflicts; talk to other people to get a better sense of what’s going on and come up with some suggestions to smooth it out.</li><li>Facilitate any non-engineering matters, including immigration status issues and performance review questions and concerns.</li></ul><p>It’s also a good idea to hold your direct reports accountable for their tasks before the next meeting. Perhaps this may require multiple reminders, but at the end of the day the meeting is most effective if both parties put in effort to improve things.</p><h4>Get to know your direct reports</h4><p>Lastly, your direct reports are people. They have lives outside of work, and they have ups and downs. The more you understand your direct reports and team dynamics, the better you, as a manager, can help your direct reports succeed.</p><p>Some ideas I tried on a regular basis are:</p><ul><li>Go to lunch with them; start a casual conversation and show them that you are just there to have a good time.</li><li>Set up some team activity outside of the office, such as happy hour, movie night, etc. This gives them an opportunity to get to know other team members as well, and this task can be delegated to multiple people; you don’t have to be the one organizing all the time.</li><li>Celebrate their anniversaries and birthdays. You don’t have to go all out with special planning; simply make sure to acknowledge important milestones.</li><li>It’s fine to delve into casual conversations during 1:1s if time permits and your direct reports feel comfortable. No one said 1:1s have to be 100% professional.</li></ul><p>In my tenure as an engineering manager, I focused on the trust aspect the most. I didn’t touch upon any of the project management and/or technical leadership that you may be required to perform in this post, but I feel like those are very specific to each organization. Also there are a lot of relevant posts in those topics. However, I think it’s important to stress that solving people problems is longer lasting than any other types of issues you may encounter.</p><p>If you enjoyed what you read and want to read more of what I write, please follow me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=426d89b54964" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating to Swift 3]]></title>
            <link>https://engblog.nextdoor.com/migrating-to-swift-3-7add0ce0655?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7add0ce0655</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[migration]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Thu, 12 Jan 2017 22:16:42 GMT</pubDate>
            <atom:updated>2017-01-12T22:16:42.254Z</atom:updated>
            <content:encoded><![CDATA[<p>The iOS team at Nextdoor recently migrated our iOS codebase to Swift 3. In this blog post, we wanted to share the approach we took and learnings from this process.</p><h3><strong>Swift Adoption</strong></h3><p>Since our iOS team was small (before 6, now 9 members) and our codebase was relatively young, we decided to adopt Swift at its early age when version 1.2 came out. The team had collectively learned the new language during our <a href="https://engblog.nextdoor.com/co-ops-at-nextdoor-e0d64c2830b2#.mxxsfn5jm">iOS co-op</a>, and once we saw that the language was evolving quickly and the toolchain was getting better, we felt comfortable investing full effort into writing production code in Swift. We set the standard that all new files will be written in Swift.</p><p>Fast-forward a year and a half: today, we have 550 files in Swift, and 20% of our codebase, consisting of production and test code, which made this migration a non-trivial task.</p><h3><strong>Swift 2.2 -&gt; Swift 2.3 -&gt; Swift 3.0</strong></h3><p>When upgrading to Xcode 8, we had to decide whether to go Swift 2.3 or Swift 3. Due to our company priorities and resource constraints at the time, we decided to first migrate to Swift 2.3 to get to Xcode 8 and iOS 10 faster.</p><p>Decoupling Xcode and Swift 3 upgrades was definitely the right choice for us. We were able to troubleshoot iOS 10 specific issues earlier, minimize the impact on other on going projects, and make the workload manageable.</p><p>Once Apple officially announced that Xcode 8.2 would be the last version that supports Swift 2.3, it was time to tackle Swift 3 migration.</p><h3><strong>Preparation</strong></h3><p>After investigating the technical risks of upgrading to Swift 3, we had to make a few decisions:</p><ul><li>Because we couldn’t merge the ongoing migration back to our master branch, we had to decide on the workflow around the migration branch.</li><li>To facilitate code reviews by other developers, we set the rule to break up the migration work into smaller logical commits. This also aimed to avoid any duplicative migration effort since developers were constantly reviewing the ongoing work.</li><li>We have dependencies on third party libraries and internal frameworks that are in Swift. We laid out the order of migration, so that everyone was on the same page and could help out in the appropriate areas of the codebase. Also, once the framework was declared complete, any developers who modified files in the framework were responsible for porting their new work to the migration branch.</li></ul><h3><strong>Learnings to Share</strong></h3><p><em>Note that our codebase is a mixture of Swift and Objective-C. Some of the challenges we faced were due to that fact.</em></p><ul><li>We use Cocoapods as our dependency manager, and because it’s shared among different branches of your repository, it made sense to have a logic in our Podfile to manage different versions of Swift.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7a74f9dad793f8ae05e4030c4c28f3fa/href">https://medium.com/media/7a74f9dad793f8ae05e4030c4c28f3fa/href</a></iframe><p>With the changes above, all you had to do to set yourself up for Swift 3 was:<br>$ SWIFT_VERSION=&#39;3.0&#39; pod install</p><ul><li>Swift 3 introduced new bridged structs for corresponding Foundation classes. For example, NSDate in Objective-C now corresponds to Date in Swift; similarly NSLocale to Locale. We had our own extension on Objective-C classes that we used in our Swift code. Instead of doing casting everywhere, we thought it was best to write Objective-C extension in Swift as follows:</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/361d997c5c5e0a4255d5ed673cdb5fcd/href">https://medium.com/media/361d997c5c5e0a4255d5ed673cdb5fcd/href</a></iframe><ul><li>Using the Xcode migration tool not only took a long time on a bigger project but also made changes that were not necessary. For example, a lot of access control declarations were converted to open from public even though it wasn’t our intention. We decided to make decisions on a case by case basis to keep our integrity of our code rather than completely relying on the migration tool.</li><li>With Swift 3, Objective-C code that is used in Swift now returns optional types instead of force unwrapped optional; ? instead of !. This caused a lot of compilation errors. Instead of taking the shortcut of littering our codebase with !s or if let, we decided to diligently annotate nullability in our Objective-C code to better reflect our intention. You can find an excellent reference about this topic <a href="http://useyourloaf.com/blog/using-nullable-to-annotate-objective-c/">here</a>. Also, Xcode static analyzer does some work to detect incorrect annotation, which is very helpful.</li><li>Because of interoperation with Objective-C, many of our dictionary declaration used to be[NSObject: AnyObject]. With the change outlined in the <a href="https://developer.apple.com/swift/blog/?id=39">Swift blog</a>, the dictionary declaration became[AnyHashable: Any]. Instead of taking the compiler’s suggestions of casting them back to [NSObject: AnyObject] we decided to annotate declaration appropriately.</li><li>Objective-C code complained that method name didn’t match up with what was defined in the Swift code, especially if the protocol was written in Swift. We had to annotate swift methods with @objc(&lt;method signature&gt;) to match up the names in Objective-C. The following snippet from <a href="https://developer.apple.com/library/content/documentation/Swift/Conceptual/BuildingCocoaApps/InteractingWithObjective-CAPIs.html#//apple_ref/doc/uid/TP40014216-CH4-ID35">Apple’s documentation</a> explains what the annotation does.</li></ul><blockquote>In some cases, you need finer grained control over how your Swift API is exposed to Objective-C. You can use the @objc(<em>name</em>) attribute to change the name of a class, property, method, enumeration type, or enumeration case declaration in your interface as it’s exposed to Objective-C code.</blockquote><ul><li>Interestingly, closures no longer accept parameter labels. Even though the compiler suggests an appropriate fix, we thought it was worth noting because it was confusing to us at first. More information can be found in <a href="https://github.com/apple/swift-evolution/blob/9cf2685293108ea3efcbebb7ee6a8618b83d4a90/proposals/0111-remove-arg-label-type-significance.md">this swift evolution proposal</a>.</li><li>There were many other different types of syntactical errors that the compiler did a great job of suggesting fixes.</li><li>Not all compilation errors are reported at once. As we fixed errors, we noticed that Xcode reported new errors, even in the same file that you were working in. This made tracking progress in a large Xcode project difficult.</li></ul><h3><strong>Final Push and Moving forward</strong></h3><p>This migration process was truly a team effort.</p><p>After a couple of developers initially got the code base to build successfully, the entire team helped us to get our CI back to green and eliminate all lint errors and warnings. Our +3,400 unit test suite helped us give confidence in our migration, but the team tested the app, reported issues, and fixed bug in their specific domain areas.</p><p>Ultimately, this migration took around 2 weeks, but it’s really good to be able to declare that we are fully on Swift 3.</p><p>This has set up a good starting point for the team in 2017, where we get to focus on pushing our platform and service forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7add0ce0655" width="1" height="1" alt=""><hr><p><a href="https://engblog.nextdoor.com/migrating-to-swift-3-7add0ce0655">Migrating to Swift 3</a> was originally published in <a href="https://engblog.nextdoor.com/">Nextdoor Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Publishing blogs with Github, CircleCI, and Google Analytics]]></title>
            <link>https://engblog.nextdoor.com/publishing-blogs-with-github-circleci-and-google-analytics-d8872b9e5322?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8872b9e5322</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[circleci]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Thu, 27 Aug 2015 14:16:44 GMT</pubDate>
            <atom:updated>2016-02-22T20:43:26.661Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introduction / Background</h4><p>At Nextdoor, we treat our engineering blog like an independent engineering project. A handful of engineers, forming a committee (co-op), manage the process of publishing a weekly blog entry. The tools that we use to draft a blog, review the entry, and publish to the world are all centered around our main users, engineers. Our goal is to make writing as frictionless as possible for our engineering team so that they can focus on the most important aspect of it — sharing the awesome work we do to help make neighborhoods stronger and safer.</p><h3>How we craft a blog post</h3><p>We publish one blog post every week. We have over 50 engineers and we take turns writing blog posts, which is similar to our oncall rotation — except that you write a blog post once a year, rather than once every 3 months. :)</p><p>Engineers do things in the engineering way. We write posts using Markdown and we manage posts using Github Enterprise, where we have an engblog.git repo. In the repo, each blog post has a separate directory, where there is a Markdown file for post contents, a meta.ymal file for meta data, and a subdirectory for images.</p><p>Oftentimes, more than one engineer works on the same blog post. We’re already used to working together on the same code base, mostly for plain text files. Therefore, we have no problem dealing with Markdown files, which are plain text files, too.</p><p>We work on a new feature branch for each blog post. We create a pull request and add reviewers on Github Enterprise for “code review” before publishing a blog post. We typically include our peer engineers as reviewers, as well as people from the communications team, who are surprisingly happy with such “code review” process on Github Enterprise!</p><p>Here’s how it looks like to “code review” a blog post on Github Enterprise:</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*SEo-AwAPkkkhqC7e.png" /></figure><h3>Continuous integration</h3><p>The published blog would appear on WordPress, so the content still needs to get exported from GHE to WordPress. This is where continuous integration comes in. For regular projects, CI is used to run tests, publish artifacts, etc. For engblog, we leverage CircleCI to create a WordPress draft.</p><p>This script walks through our directory structure looking for <strong>meta.yaml</strong> file and parses out the information required to publish a WordPress blog. Future improvements include automatically uploading images and creating gists from code snippets, but for now we do this manually.</p><p><a href="https://gist.github.com/siminm/430ad49e1fa6061a67c6">The script that publishes the blog to WordPress is here.</a></p><h3>Promoting content</h3><p>Once the content is reviewed and published on our blog site, we use various channels to promote our content.</p><h4>Internal promotion</h4><ul><li>First, we announce the new blog entry in our internal company wide forum. The message contains a brief summary of the blog and encourages our colleagues to read it and share it on various social channels. Also, this helps to raise awareness of the engineering blog and nudge our fellow engineers to be part of the movement.</li><li>Additionally, we have a one page description of the blog that we print out and post in our bathrooms. Surprisingly, this has been a very effective way to spread the word about the blog to the entire company. For example, our CEO, Nirav, mentioned it in one of our all-hands.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*GAmialdWfGGmgz3V.jpg" /></figure><h4>External promotion</h4><ul><li>The members of the engineering blog co-op share the blog through social channels including Facebook, Twitter, LinkedIn, and Hacker News to kickstart the virality. We carefully analyze the effectiveness of each channel and continue to optimize how we promote.</li></ul><h3>Data analysis</h3><p>We want to know our audience — understand what people like to read, when they choose to comment, and why certain posts are more viral than others. Google Analytics is an excellent, off the shelf, free tool we leverage to track out progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*30EKwDXd0EJX0K3x.png" /></figure><p>We meet once a week to take a look at how the most recent blogs have performed. We also look at former blogs that continue to have new readers. This means that the content is widely relevant and has good SEO.</p><h3>Conclusion</h3><blockquote>When engineers start writing, good things happen.</blockquote><p>One of our core values as a company is to communicate openly. With engineering blogging, just like with open source software, we aim to share the tools and the knowledge we have about current technology with the rest of the community.</p><p>We also believe that writing about the great work we do every day promotes a better engineering culture. Not only does it help spread the word about Nextdoor engineering, but writing the blog also allows engineers to feel greater ownership of their work. It’s also great to receive feedback from other developers in the community and gain new perspectives on the problems we tackle. We started to put more emphasis on our engineering blog a few months ago, and it’s amazing how much content we have created so far. Of course, we have so much more to share, so stay tuned and subscribe for more updates.</p><p>Also, if you’re interested in joining us, <a href="https://nextdoor.com/jobs/">we’re hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8872b9e5322" width="1" height="1" alt=""><hr><p><a href="https://engblog.nextdoor.com/publishing-blogs-with-github-circleci-and-google-analytics-d8872b9e5322">Publishing blogs with Github, CircleCI, and Google Analytics</a> was originally published in <a href="https://engblog.nextdoor.com/">Nextdoor Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Share Your Knowledge]]></title>
            <link>https://engblog.nextdoor.com/share-your-knowledge-98119b4f7c4b?source=rss-decf125492c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/98119b4f7c4b</guid>
            <category><![CDATA[nextdoor]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Daisuke Fujiwara]]></dc:creator>
            <pubDate>Wed, 03 Jun 2015 04:32:23 GMT</pubDate>
            <atom:updated>2016-02-22T20:40:22.258Z</atom:updated>
            <content:encoded><![CDATA[<p>A forum to promote continuous learning and knowledge sharing.</p><h4>What is it?</h4><p>At Nextdoor, we strive to encourage continuous learning among engineers. Even though we are busy committing code at a fast pace on a daily basis, we consciously take time to learn new technologies and engineering concepts.</p><p>The “Share Your Knowledge” sessions started when a few of our mobile developers decided to create a space to discuss new learnings on a biweekly basis. This was extremely important for the mobile developers as mobile platforms were and still are evolving at a fast pace every year. After piloting this idea for more than a year, we discovered that the mobile engineers appreciated these sessions as an effective tool for knowledge sharing.</p><p>As we developed “Share Your Knowledge”, our engineering team grew to include many teams working on various focus areas, such as infrastructure and geospatial. We decided to expand the concept to the entire engineering team, because we saw that “Share Your Knowledge” could be a great way to keep the entire team up to date with expertise developing in each area.</p><p>Today, “Share Your Knowledge” covers all aspects of software engineering including:</p><ul><li>Caching best practices in Django</li><li>Image service written in golang</li><li>Client side event tracking system for web and mobile platforms</li><li>Load testing infrastructure using Gatling</li><li>iOS functional testing with KIF</li><li>Site performance monitoring using New Relic</li><li>How to be a Jira power user</li></ul><h4>Format</h4><p>The format of “Share Your Knowledge” is specifically designed to be simple and practical. We assign a couple of presenters beforehand, and they select a particular topic that they want to discuss for 5–10 minutes. They are encouraged to present prototypes, demos, or live coding. The time constraint also forces the presenters to identify key discussion points, and they have the freedom to choose their topics as long as it is related to the theme of the session. At Nextdoor, the topics that have been chosen frequently have nothing to do with presenters’ current work.</p><h4>Sharing with the community</h4><p>We recently hosted the first external “Share Your Knowledge” session with mobile developers in the community. We were excited to see so many participants, and many of them expressed interest in attending future sessions.</p><p>We had five speakers from the following companies present exciting topics for both iOS and Android:</p><ul><li><a href="http://www.nextdoor.com/">Nextdoor</a></li><li><a href="http://www.citizencode.io/">Citizen Code</a></li><li><a href="https://medium.com/">Medium</a></li><li><a href="https://www.apartmentlist.com/">Apartment List</a></li><li><a href="http://www.yelp.com/">Yelp</a></li></ul><p>Here are the materials from the event. <a href="https://vimeo.com/127290584">Video</a> &amp; <a href="https://www.dropbox.com/sh/x1r2bffq2um844k/AAD4UVU0gzp39Aazh3IFmV8ya?dl=0">Slides</a></p><p><a href="https://vimeo.com/127290584">Mobile Share Your Knowledge</a> from <a href="https://vimeo.com/nextdoor">Nextdoor</a> on <a href="https://vimeo.com/">Vimeo</a>.</p><h4>What is next?</h4><p>From now on, we will be sharing our learnings on this blog. So keep an eye out for more entries related to “Share Your Knowledge”!</p><p>We also encourage you to try “Share Your Knowledge” at your company. We would love to hear about your experiences in the comments.</p><p>If this sounds like the place for you, <a href="https://nextdoor.com/jobs/">we are hiring!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98119b4f7c4b" width="1" height="1" alt=""><hr><p><a href="https://engblog.nextdoor.com/share-your-knowledge-98119b4f7c4b">Share Your Knowledge</a> was originally published in <a href="https://engblog.nextdoor.com/">Nextdoor Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>