<?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[Commit Engineering - Medium]]></title>
        <description><![CDATA[Commit is built to enhance the career experience for entrepreneurial engineers. This is our blog. Visit commit.dev to learn more. - Medium]]></description>
        <link>https://medium.com/commit-engineering?source=rss----ed8993761bc2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Commit Engineering - Medium</title>
            <link>https://medium.com/commit-engineering?source=rss----ed8993761bc2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:55:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/commit-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Forced back to the office? Three steps to resigning gracefully from your job.]]></title>
            <link>https://medium.com/commit-engineering/forced-back-to-the-office-three-steps-to-resigning-gracefully-from-your-job-1ee916704314?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/1ee916704314</guid>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Noel Pullen]]></dc:creator>
            <pubDate>Sat, 05 Jun 2021 00:33:49 GMT</pubDate>
            <atom:updated>2021-06-05T00:38:57.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8DWJl2h9IniOoVz4l11Pig.jpeg" /></figure><p>Some employers want to <a href="https://news.ycombinator.com/item?id=26983085">end working from home</a> (WFH) even though many of us love this flexible, asynchronous, commute-less way of working.</p><p><a href="https://www.linkedin.com/in/lizkislik/">Liz Kislik</a> wrote an excellent HBR article titled “<a href="https://hbr.org/2021/01/what-to-do-if-your-team-doesnt-want-to-go-back-to-the-office">What to Do If Your Team Doesn’t Want to Go Back to the Office.</a>” She wrote from the perspective of a middle manager and outlines seven actions you can try to help others see the benefits of knowledge workers, like us, working from home.</p><p>The one action she doesn’t address is how to exit gracefully if all other efforts fail.</p><p>So, if you’re ready to <a href="https://www.bloomberg.com/news/articles/2021-06-01/return-to-office-employees-are-quitting-instead-of-giving-up-work-from-home">quit your job instead of giving up working from home</a>, here’s Commit’s guide on resigning gracefully.</p><p><strong>#1 Prepare an exit plan</strong></p><p>A graceful resignation allows you to practice empathy, adds to your library of templates for future departures, and ensures continuity for your team.</p><ol><li>How much notice is required? Err on the side of generosity. Two weeks minimum, but four weeks is better, especially if you are in a critical role.</li><li>Write scripts for the conversation you will have with your manager and the discussion you will have with your team. These conversations can be emotional — a script ensures you stay on track and convey your points. Run your scripts through Grammarly, then share them with a trusted advisor — ideally, someone who has received resignations before — so they can edit it for tone and content. Include the reasons you are leaving and a handoff plan (see item 3) to show your team and your manager that you’re handling your exit professionally.</li><li>As part of your call script, include a handoff plan, which should include:</li></ol><ul><li>Who can take over your responsibilities and be a point of contact to field questions about your work after you’re gone?</li><li>Which playbooks and documents (FAQs are helpful) will you write to ensure your team can self-serve after leaving.</li><li>Provide your contact information and willingness to help in case of an emergency. Timebox your availability to one month. Why? It’s kind to help. If you find yourself being asked too often or for things that are too demanding, politely decline.</li></ul><p>4. Write your resignation letter. Again, run it through <a href="https://app.grammarly.com/">Grammarly</a> and by a trusted advisor. I like <a href="https://www.thebalancecareers.com/resignation-email-messages-examples-2063071">this article and the examples</a> from <a href="http://thebalancecareers.com/">The Balance</a>.</p><p><strong>#2. Carry out that exit plan and handoff plan</strong></p><ol><li>Resign in person or over video. Follow your call script.</li><li>Make any adjustments to your exit plan based on your conversation.</li><li>Follow up by email with your letter of resignation.</li><li>Begin executing your handoff plan. Please make a point of going through your handoff plan with your designated point of contact, telling your team about it, and making it publicly available.</li></ol><p><strong>#3. Now the fun stuff</strong></p><ol><li>Write LinkedIn recommendations for your colleagues and publish them before you leave. They are a public way to recognize your team members and crystallize your respect for their attitude and work.</li><li>Inform peers, managers and direct reports that you respect that you are willing to be a reference for them.</li><li>Draft a goodbye note to your team and your organization. Thank them for the opportunity to learn from them and about them, recognize any particular individuals who made a significant contribution to your experience and growth, wish them luck, and indicate how they can stay in touch with you.</li><li>Reflect on your experience. Write down the hard and soft skills that you want to take away from your time at this organization. Often we learn best by identifying what we don’t like about a product, culture, technology, etc. Take some time to articulate those, as they can be helpful directional guides for you.</li></ol><p>I hope you found this guide helpful; it’s one of many that we provide to engineers in our <a href="https://commit.dev/">Career Transition Program</a>.</p><p>Thank you to <a href="https://www.linkedin.com/in/sarahmarion/">Sarah Marion</a>, <a href="https://www.linkedin.com/in/elainelam01/">Elaine Lam</a>, <a href="https://www.linkedin.com/in/beiercai/">Beier Cai</a>, <a href="https://www.linkedin.com/in/reachryanabbott/">Ryan Abbott</a>, <a href="https://www.linkedin.com/in/ashleyjanebrookes/">Ashley Brookes</a>, and <a href="https://www.linkedin.com/in/gunnr/">Greg Gunn</a>.</p><p><a href="https://www.linkedin.com/in/noelpullen/"><em>Noel Pullen</em></a><em> leads the Engineering Experience at Commit.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ee916704314" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/forced-back-to-the-office-three-steps-to-resigning-gracefully-from-your-job-1ee916704314">Forced back to the office? Three steps to resigning gracefully from your job.</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I shouldn’t have joined Commit.]]></title>
            <link>https://medium.com/commit-engineering/why-i-shouldnt-have-joined-commit-780788bdd8a0?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/780788bdd8a0</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[dreams]]></category>
            <category><![CDATA[purpose]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Danielle Strang]]></dc:creator>
            <pubDate>Fri, 04 Sep 2020 19:28:02 GMT</pubDate>
            <atom:updated>2020-09-04T19:28:02.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytMHEQlqqOXY8UHv2fkxmA.jpeg" /></figure><h3>I’ve spent the last 13 years of my life playing the game. Following the “shoulds” towards someone else’s version of success. Living my life for the next promotion, the next title change, the next bump in my salary hoping that happiness would be just around the corner. I’ve done everything that a rational, competent person SHOULD do to achieve success, and yet I’ve never felt more hopelessly lost, uninspired and, ultimately, completely caged in.</h3><p><strong>The opportunity to shift.</strong></p><p>Like many other people right now, I’ve found myself in a new role at a new company during this pandemic. Let me be clear, it <em>wasn’t</em> the result of a layoff, salary reduction or any other unpredictable change. I had a Director-level role at a growing startup that was secure, stable, comfortable. So when I found myself entertaining a position at a significantly <em>smaller</em> organization — <a href="https://medium.com/commit-engineering">Commit</a> — that had only been around for just over a year, I wrestled with emotions and insecurities that have never surfaced before.</p><p>I was waking up at 2:00 am, guts wrenching, mind racing. It’s not that I was miserable at work — I was <em>complacent, on autopilot, a zombie.</em> To complicate things, my husband was recently laid off. The stress of winning bread and supporting our family was officially on my shoulders. Mine alone.</p><p>So I did what any reasonable person would do in this situation: I consulted my trusted group of friends, mentors and advocates. The people who know me best. The people who would shine a light on my limiting behaviours and fears, and give me the kind of advice that would help me make a decision with confidence. Here’s what they had to say:</p><p>“Don’t join Commit.”</p><p><strong>The reasoning.</strong></p><p><em>There is a global pandemic going on! The adult thing to do, the responsible thing to do, is play it safe. Your family income has been cut in half. Leaving your current job would be irresponsible.</em></p><p><em>How does Commit make money? Will the company even be around a year from now?</em></p><p><em>You just got back from mat leave. Aren’t you planning on having more kids? You should just put up with your current job and stay if you’re planning on getting pregnant again. Why change jobs when you’re in the middle of having children?</em></p><p><em>Wait — your husband was laid off? How are you even entertaining changing careers?</em></p><p><em>You went from having a big team to leading no one. That sounds and looks like a big step backwards. You need to stay the course to get to VP. This change sounds like career sabotage.</em></p><p><em>Work sucks for everyone — it’s just a fact of life. When you have the title and the salary, then you have the time to discover life/passion/hobbies.</em></p><p><strong>The realization.</strong></p><p>The last advice-seeking conversation I had was with a dear friend and former colleague, just days before I received my offer from Commit. I reached out to him because he is one of the smartest people I know. He’s built several startups, and I knew he would help me explore the really important questions that would help me <strong><em>rationally</em></strong> explore this opportunity: <em>How does Commit make money? Is their leadership team aligned? Is there enough demand for the value they are offering? Essentially: just </em><strong><em>how viable</em></strong><em> is this opportunity?</em></p><p>We answered all of my rational questions and built a predictable pro/con list. Just when I was giving into complacency and comfort, opting to “stay the course” and reject the Commit offer, he said something that shook my perspective.</p><blockquote>“Danielle, we can <strong><em>rationally</em></strong> explore this as long as you need. But I’ve known you long enough to look at this from another angle. I think you need to accept this offer to break free from what’s been holding you back. Do it for yourself. Maybe now is the time to embrace a little irrational action in your life.”</blockquote><p>I realized he was totally right, and I had known it all along.</p><p><strong>The unlearning</strong></p><p>No one has been able to explain how I’m feeling better than Glennon Doyle in her recent book <a href="https://www.amazon.ca/Untamed-Glennon-Doyle/dp/1984801252/ref=sr_1_1?crid=2UV8Y1RZ9QMOL&amp;dchild=1&amp;keywords=untamed+glennon+doyle&amp;qid=1597776753&amp;sprefix=untamed%2Caps%2C189&amp;sr=8-1">Untamed</a>:</p><p>“There is a voice of longing inside every woman. We strive so mightily to be good: good mothers, daughters, partners, employees, citizens, and friends. We believe all this striving will make us feel alive. Instead, it leaves us feeling weary, stuck, overwhelmed, and underwhelmed. We look at our lives, relationships, and world, and wonder: <em>Wasn’t it all supposed to be more beautiful than this?”</em></p><p><strong>YES! YES! YES! 1000 times YES!</strong></p><p>It IS supposed to be more beautiful than what I’ve experienced. And that’s just what I’m setting out to discover. <strong>No more settling, no more striving for someone else’s benefit, no more living in fear to make the changes I know I need to make.</strong></p><p>And that’s exactly why I told my fears to shove it — and I JOINED Commit.</p><p>I knew I wouldn’t survive if I didn’t take the leap. I’m not talking about literal survival. I’m talking about a <em>gradual fading away</em>. If I kept doing what I was doing, I would lose my fire, the spark that kept me curious, hungry, vibrant….alive! So I went for it. I accepted the offer and I haven’t looked back.</p><p>What have I gained? The opportunity to use my story as a roadmap for others. I’m setting out on a journey to build a revolutionary <a href="https://medium.com/commit-engineering/my-job-at-commit-is-to-create-an-incredible-experience-for-engineers-b5e46bc85abe?source=friends_link&amp;sk=74a612440c786cbae4d794dbab25a713">Engineer Experience</a> at Commit — and I couldn’t be more ignited. It’s officially my job to help our engineers <em>unlearn</em> the structures, thinking and processes that hold them back. To unlock their biggest potential. To embrace a model that hasn’t forgotten that working for any particular company isn’t their dream — that it’s only a chapter in the bigger novel of their life. We’ve put engineers back in the driver’s seat and we’re only getting started.</p><p><em>Danielle Strang is building the ‘Engineer Experience’ and community at Commit. She’s relentlessly focused on the future of work and how to inspire passion and purpose for software engineers.</em></p><p><em>Thank you to </em><a href="https://www.linkedin.com/in/noelpullen/"><em>Noel Pullen </em></a><em>and </em><a href="https://www.linkedin.com/in/beiercai/"><em>Beier Cai</em></a><em> for seeing the potential in all of my wild ideas, to </em><a href="https://www.linkedin.com/in/gunnr/"><em>Greg Gunn</em></a><em> for encouraging me to speak openly about my experiences and to </em><a href="https://www.linkedin.com/in/reachryanabbott/"><em>Ryan Abbott</em></a><em> for helping me find my written voice.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=780788bdd8a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/why-i-shouldnt-have-joined-commit-780788bdd8a0">Why I shouldn’t have joined Commit.</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committed to Success: Lillian Liang, Plastiq Inc.]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-lillian-liang-plastiq-inc-ef7648db4194?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef7648db4194</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[employee-experience]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Danielle Strang]]></dc:creator>
            <pubDate>Fri, 14 Aug 2020 22:27:24 GMT</pubDate>
            <atom:updated>2020-08-14T22:27:24.785Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Lillian Liang is a Commit engineer who joined </em><a href="https://www.plastiq.com/"><em>Plastiq</em></a><em> earlier this year. We talked to her about her journey to Commit and Plastiq.</em></p><p><strong>Can you tell us a bit about your journey to Commit?</strong></p><p>I studied computer science at the University of British Columbia and graduated in 2014. Since then, I worked at a trucking management company for around two years, working with desktop applications, then I joined a social media management company, where I met a lot of people who now work at Commit. I joined Commit at the end of 2019.</p><p><strong>What drew you to Commit?</strong></p><p>Commit’s partnership model! I really like how Commit matches engineers to a variety of projects on three- to six-month contracts, allowing us to be fully immersed in each startup’s culture, discover our interests, and contribute right away. It takes the pressure off joining a company full time and gives us opportunity to find the right fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqHzq6uxQVNOFs6kpA2qRQ.jpeg" /></figure><p><em>“Normally, joining a company full-time is a big commitment. There’s a huge investment of time and energy, up front. As a result, there’s inherent risk — if it doesn’t work out, you have to start again from scratch with another company.”</em></p><p><strong>How did you get connected to Plastiq? Were they your first project through Commit?</strong></p><p>Plastiq was my second project at Commit. I had a really good experience at the first, which was also in fintech, but I wanted to try another one to see what it was like. Plastiq really stood out to me because of their team. I really enjoy working with my team and with the greater Plastiq team. We have a really good set of engineers and the leadership group is really great. They’re very open, honest and direct when communicating with the company. I really enjoy working with React, and the core services and back-end are in Node. I feel confident in the work I’m doing and the impact I’m making.</p><p><strong>How do you describe Plastiq to your friends and family?</strong></p><p>Plastiq enables customers and small businesses to make any type of payment via credit card where they may typically not be able to. It allows small businesses to make use of their high credit limits and reap the benefits of any reward system or a point system their credit card offers.</p><p><strong>What’s been the best part of working with Plastiq so far?</strong></p><p>The variety of work I’ve been involved with has allowed me to work with many different engineers in our company, which is pretty amazing. I’ve worked on migrations, and some core product features in our product, and features in our internal product. So the variety has been great.</p><p><strong>What do you think about Commit’s mission and model?</strong></p><p>The leadership team and everyone at Commit is super supportive. That’s number one. And the projects we get to work on, the start-ups — I’ve been with two — they’ve both been really good experiences. I like how Commit does project matching, how you get paired with a project and get to test it out to see if you enjoy it and gel with the team.</p><p>Normally, joining a company full-time is a big commitment. There’s a huge investment of time and energy, up front. As a result, there’s inherent risk — if it doesn’t work out, you have to start again from scratch with another company. Commit’s model, where you get to test out projects and companies, ensures the fit is great for both parties.</p><p><strong>What would you say to other engineers who are considering joining Commit?</strong></p><p>I’d say definitely go for it. Everyone is very supportive and you’ll find a project that fits your capabilities, and you always have the support of the Commit community: those who have graduated, like me, and those who are still employed by Commit. And the community continues to grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef7648db4194" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-lillian-liang-plastiq-inc-ef7648db4194">Committed to Success: Lillian Liang, Plastiq Inc.</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committed to Success: Will Casarin, The Steamoji Team]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-will-casarin-the-steamoji-team-5d1d7e89e01c?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d1d7e89e01c</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[stem]]></category>
            <dc:creator><![CDATA[Noel Pullen]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 21:55:02 GMT</pubDate>
            <atom:updated>2020-07-09T22:19:17.454Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/william-casarin-baab44143/"><em>Will Casarin</em></a><em> is a Commit engineer who joined the STEAM educational startup </em><a href="https://www.steamoji.com/"><em>Steamoji</em></a><em> earlier this year.</em></p><p><strong>Can you tell us a bit about your journey to Commit?</strong></p><p>I feel like I’ve only ever worked at startups. I joined a record label called <a href="https://www.monstercat.com/">Monstercat</a>. Everybody from Monstercat moved out here to Vancouver — so that’s how I got here. It was a small startup, there were about five of us, and I was the CTO. Now they have almost 100 employees. I eventually got into Bitcoin, and I quit to try my own bitcoin startup. That didn’t work out, but Bitcoin led me to Commit.</p><p>Beier [Commit’s co-founder] was into Bitcoin at the same time. We talked, and he shared his idea for Commit. It was a really rough idea about a cooperative — that was the term he used — for engineers. It sounded like a pretty cool idea, so I thought I would try it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*XSXqc-wRRaGMRj6piZwo1A.jpeg" /><figcaption>Will Casarin</figcaption></figure><p><strong>How did you get started as a software engineer?</strong></p><p>I started programming when I was around 10 years old. When I got to college, I found they were teaching stuff I already knew. I didn’t get much value out of it, so I dropped out and joined a startup before finishing.</p><p><strong>What drew you to Commit?</strong></p><p>I heard that many people on board at Commit were originally Hootsuite employees, and had a unique set of skills that they’ve built up. I figured I’d probably learn from them, and it turns out I did. That’s one of the interesting things about the Commit model: there’s a lot of different people with different backgrounds and different experiences, and you can leverage all of that to learn and help each other out.</p><p><strong>How did you get connected with Steamoji?</strong></p><p>I got on a pilot project with them. As a father, it was something I found interesting. <a href="https://www.steamoji.com/">Steamoji</a> is introducing an afterschool-style program at a maker studio where kids learn <a href="https://en.wikipedia.org/wiki/STEAM_fields">STEAM skills</a> through immersive projects like coding, digital arts, and fabrication. We want to replicate this model with franchises around the world. I would want to do it with my kids, and if I want to do it, I’m sure a lot of other people do too.</p><p><strong>What’s your role at Steamoji? What are you working on?</strong></p><p>I’m building all the front-end, back-end, and iOS apps. Full-stack in the truest sense.</p><p><strong>How has Commit continued to support you as you joined Steamoji?</strong></p><p>Sometimes when you move on from one company to another, it feels like they’re kicking you out the door, and you never talk to them again. You get locked out of their Slack rooms, lose your email address, and things like that. Commit is different. I’m still in their Slack channels, I still have my email address, and I still talk with other Commit graduates. I have the feeling that I will always be welcome at Commit.</p><p>When I first joined, I was kind of skeptical of the model. I wondered if I was just a contractor, and they’re just getting value out of me. Now I know that Commit is trying to make the best experience for engineers, and it truly shows.</p><p><strong>What would you say to other engineers who are considering joining Commit?</strong></p><p>If you like the startup experience, but you feel overwhelmed or anxious about the financial risks, job security, or lack of people to learn from, Commit is definitely a much better experience. You get the benefits of building companies from scratch, but with a salary from Commit. It’s a lot more friendly, and there’s a supportive group of people to help you out.</p><p>I think that people should be doing more of this. There should be more Commits around the world.</p><p># # #</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d1d7e89e01c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-will-casarin-the-steamoji-team-5d1d7e89e01c">Committed to Success: Will Casarin, The Steamoji Team</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Passing the baton, lessons learned from handing projects over to clients]]></title>
            <link>https://medium.com/commit-engineering/passing-the-baton-lessons-learned-from-handing-projects-over-to-clients-6b761a5ec73b?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/6b761a5ec73b</guid>
            <category><![CDATA[contractors]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[handover]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[client-relationship]]></category>
            <dc:creator><![CDATA[Shah Newaz Khan]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 03:45:33 GMT</pubDate>
            <atom:updated>2020-06-30T16:11:06.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>Passing the baton, lessons learned from handing projects back to teams</h3><p>Change is the norm now: new companies, new teammates, new roles every couple of years. To be effective at our software engineering jobs, we have to be comfortable learning new systems and processes quickly, but we also need to learn to leave positions gracefully. The last thing we want as software engineers is for our hard work to be for naught because the people picking up where we left off can’t decode our code. It’s up to us to work out loud: to document and share our logic and thinking to ensure a smooth transition when we’re gone.</p><p>This is especially true for <a href="https://commit.dev/">Commit</a> engineers. Commit’s model is to connect engineers with startups, offering opportunities for both groups to know each other and work together before either commits to a long-term opportunity. By its very nature, this creates many transitions in and out of organizations. As I’ve progressed in my career, working with many different teams and startups, I’ve given thought to how best to pass the baton to the team members I’m leaving behind, so there is no loss of knowledge when I go. Here are the ways I work to ensure a seamless transition when I’m gone.</p><p><strong>Documentation</strong></p><p>Believe it or not, it starts with your on-boarding. When I start at a new position, I like to “work out loud,” to document what I’m doing and why, right from the get-go. I set up folders in the organization’s tool of choice (for example, Confluence or Notion) and start writing <a href="https://en.wikipedia.org/wiki/Request_for_Comments">RFC documentation</a> for the high-level components I’m designing, whether it’s front end, back end, DevOps, etc. I also like to map out data flow diagrams to visualize the systems we’re planning and building as it makes it easier to build a mental map when talking about the systems with colleagues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*gb3O_w7V3-7JJkh7-j8Zxg.png" /><figcaption>Dataflow diagram included in RFC documentation and linked to the repository README.md</figcaption></figure><p>From here I link my design/POC tickets back to these documentations. The key is to document what I’m thinking and the logic behind my decisions, so that when I leave, someone can step in and continue the work with little or no time getting up to speed.</p><p>Roughly two weeks before the end of a fixed-term contract, I’ll review the documentation I have in place and formalize what’s there. But I strategically leave gaps in it. Then I meet with team members to discuss the hand-off process and have them review the documentation and fill in the gaps. This is a way for them to get their hands on the work, instead of just reading about it, and to gauge their understanding of the components. If they can fill in the gaps, great, they clearly understand the processes. If not, it’s an indication that we need to sit down and discuss it in more detail.</p><p><strong>Tooling</strong></p><p>Another way to help smooth the process of exiting from an organization is to use tooling to automate processes. It’s almost like you’re still getting work done, but you’re not there to do it.</p><p>When my time in a particular position is coming to an end, I review the internal tools I’ve helped configure and write shell scripts to automate as many processes as possible. Examples include packaging CLI tools such as <a href="https://docs.confluent.io/current/app-development/kafkacat-usage.html">kafkacat</a>, <a href="https://aws.amazon.com/cli/">AWS CLI</a> and <a href="https://octant.dev/">Octant</a> into a Docker container, so it’s easy for others to start using them without having to deal with installation for Windows, OSX or Linux environments. In addition, I make non-sparing use of <a href="https://www.gnu.org/software/make/manual/make.html">Makefiles</a> and shell scripts to encapsulate steps like introspecting a cluster, deploying a local dev environment, and setting up a database.</p><p><strong>Training</strong></p><p>The third approach to setting a company up for success when you’re on your way out is to train the people who will take over from you. This is especially relevant for complex processes and systems, where documentation and tooling provide a great start, but more direct knowledge-sharing is necessary.</p><p>On one of my recent contracts, we introduced <a href="https://kubernetes.io/">Kubernetes</a>, known to be a rather complex, heavyweight application. Soon after we got it running, my contract was coming to an end. We had set up documentation describing the processes and practices involved, and automated as many processes as possible through tooling, but we realized that direct training would be needed to ensure the organization would be up to speed on operating the system. We held two four-hour training sessions, introducing the entire 25-member engineering team to Kubernetes, including hands-on sections on how to perform end-to-end deployments and operate the system using the tooling we created to deploy applications and perform rollbacks and disaster recovery.</p><p><strong>Build bridges that last</strong></p><p>Of course, leaving a position or a company isn’t just about preserving the knowledge you’ve gained and the processes you’ve helped build. The relationships I’ve built are usually the most meaningful part of every job I’ve had: the people I’ve met, the communities I’ve been part of. Preserving those relationships is important to me, not as a career-development strategy (though that’s admittedly relevant), but simply because these personal connections are what makes the work worth doing.</p><p>There are ways to keep your friendships and professional relationships strong even if you stop working with people. You can join Slack channels and other communication networks, you can set up monthly Zoom calls or social events. One thing I like to do is write LinkedIn recommendations for my colleagues. It’s a perfect pairing of professional promotion and personal positivity that proves productive for all parties.</p><p>And it’s just a nice thing to do.</p><p>Do you have tips for leaving a role in great shape when you leave? Let me know in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b761a5ec73b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/passing-the-baton-lessons-learned-from-handing-projects-over-to-clients-6b761a5ec73b">Passing the baton, lessons learned from handing projects over to clients</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Source Sundays — gqlgen: A schema-first Go library]]></title>
            <link>https://medium.com/commit-engineering/open-source-sundays-gqlgen-a-schema-first-go-library-515494224271?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/515494224271</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[Bill Monkman]]></dc:creator>
            <pubDate>Sun, 14 Jun 2020 20:32:14 GMT</pubDate>
            <atom:updated>2020-06-14T20:32:14.844Z</atom:updated>
            <content:encoded><![CDATA[<h3>Open Source Sundays — gqlgen: A schema-first Go library</h3><p><em>Every so often, on Sundays (obviously), Commit engineering partners share an open source software tool they use to make their work and life easier. This week’s feature on gqlgen is by </em><a href="https://www.linkedin.com/in/billmonkman/"><em>Bill Monkman</em></a><em>, a Commit software developer with over 20 years of experience in backend development, DevOps, distributed systems and system architecture.</em></p><p><strong>What is gqlgen?</strong></p><p><a href="https://github.com/99designs/gqlgen">gqlgen</a> is a Go library used to build GraphQL servers. It takes a schema-first, code-generation-heavy approach, which eliminates a lot of boilerplate. <a href="https://graphql.org/learn/">GraphQL </a>is a query language for APIs. It provides a fully typed, complete and understandable description of the data in your API, giving clients the power to ask for exactly what they need and nothing more. That makes it easier to evolve APIs over time and enables powerful developer tools.</p><p><strong>Who is it good for?</strong></p><p>People interested in GraphQL who want to write less REST and less custom documentation. Because GraphQL exposes its schema to users of your API, including any comments you’ve attached, it effectively describes the available operations and properties, as opposed to REST, where all the documentation has to be provided separately and often becomes out of sync with reality. People who are writing code in Go will likely appreciate the schema-first, code-generation approach taken by gqlgen.</p><p><strong>What companies or products are using it?</strong></p><p>Based on a thread in their GitHub repository, notable users include Bench Accounting, DigitalOcean, Khan Academy and Kyma.</p><p><strong>Is there a story behind who created it and why they created it?</strong></p><p>It was led by Adam Scarr <em>(</em><a href="https://github.com/vektah"><em>vektah</em></a> on GitHub) with plenty of community contributions. In his work as a developer with 99designs, he was frustrated by the lack of type safety in REST as they were moving from Javascript to Typescript and React, which was a major motivation to move to GraphQL. But they couldn’t find a GraphQL server that fit their needs.</p><p><strong>How did you find this tool, and why did you choose it over others?</strong></p><p>I evaluated a bunch of Go libraries while I was at Bench Accounting and really liked the approach of gqlgen. I’m a fan of code generation, and the idea of being able to specify my schema based on the existing design of my system and generate almost everything was appealing. We’ve used it in a few different Commit projects now.</p><p><strong>How does it work?</strong></p><p>The workflow with gqlgen is typically to create a YAML file that tells it where to find your schema files, where to put generated code, and any mappings of objects in your schema to existing structs in your Go code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cdf79a4ed663cfd5d67b36be26d31148/href">https://medium.com/media/cdf79a4ed663cfd5d67b36be26d31148/href</a></iframe><p>This can be very handy, because if you have existing models you’re using for data access, or return values from some other internal API, you can reference them here, and you’ll be able to return these structs directly from your resolvers. Any models not mapped to existing structs will be generated for you by gqlgen.</p><p>Next, create your GraphQL schema to expose the data you want to be available to users of your API.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/44c3b86bbeb3094ee1d572dadfd1ac40/href">https://medium.com/media/44c3b86bbeb3094ee1d572dadfd1ac40/href</a></iframe><p>Then run the following to generate code based on your schema:</p><pre>go run github.com/99designs/gqlgen</pre><p>At this point it will have created stub resolvers for you to fill in.</p><p>In GQL terminology, a <a href="https://graphql.org/learn/execution/">resolver </a>is a function that contains the logic required to fill in part of your graph. Basically, since you have provided the schema that describes all the types of data available and the relationships, the resolvers are what actually fill in the right data for those types based on a given query.</p><p>Here’s an example resolver:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0e757b056a919ddef100958fdb2e7abb/href">https://medium.com/media/0e757b056a919ddef100958fdb2e7abb/href</a></iframe><p>Notice that since we mapped a model to an existing struct, we were able to immediately return the struct we got back from the database. In other cases, you may want to do some transformation or change the type of return data. You can do that in the resolver. If the struct you provided doesn’t match the definition in the schema precisely, additional resolvers will be created for you to be able to massage the data into the correct format. Or, you could have gqlgen generate a model for you, and in your resolver you can create an instance of that and fill it in from whatever data sources you like.</p><p>It’s extremely easy to get started. Just go into an empty directory and run:</p><pre>go mod init github.com/&lt;your_name&gt;/gql<br>go run github.com/99designs/gqlgen init<br>go run ./server/server.go</pre><p>And you’ll have a local gql playground to explore. It will generate the files I mentioned earlier (gqlgen.yml, graphql.schema and resolver.go), which you can easily edit to see how it feels to fill in resolvers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nT9nZB5Cjued-YKE" /></figure><p>gqlgen takes the convenience and flexibility that GraphQL provides developers a step further by:</p><ul><li>Guiding people towards more thoughtful system design through a schema-first approach</li><li>Reducing the overhead of implementing such a system by generating most of the boilerplate for you</li><li>Ensuring integrity by enforcing type-safety</li></ul><p>If you’re interested in Go or GraphQL, <a href="https://github.com/99designs/gqlgen">check it out</a>.</p><p><em>Stay tuned for future Open Source Sundays, and have a look through the </em><a href="https://medium.com/commit-engineering"><em>Commit blog</em></a><em> for more interesting content.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=515494224271" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/open-source-sundays-gqlgen-a-schema-first-go-library-515494224271">Open Source Sundays — gqlgen: A schema-first Go library</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committed to Success: Sim Brar, Plastiq]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-sim-brar-plastiq-3c349dbff9e3?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c349dbff9e3</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[career-paths]]></category>
            <dc:creator><![CDATA[Noel Pullen]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 23:18:12 GMT</pubDate>
            <atom:updated>2020-06-14T21:47:41.414Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Sim Brar is a Commit engineer who joined </em><a href="https://www.plastiq.com/"><em>Plastiq</em></a><em> in 2019 as a Principal Software Engineer. We talked to him about his journey.</em></p><p><strong>Can you tell us a bit about your background before joining Commit?</strong></p><p>I geared my education toward startups. I studied entrepreneurship, design and programming so I could be well-versed in tech startups, and I’ve always been pretty deep into the startup philosophy and space. After school, I joined a company that had the feel of a late-stage startup and was there for about four years. I kind of got sick of the corporate-ish, slow-moving, steady-ship situation, so I quit and went to go hack on some projects for six months, and travel. And then I joined Commit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JYks4ccCdpVJshj3" /></figure><p><em>“The opportunity to grow at Commit is awesome — you can take on stuff that you don’t have a background in, and do it at a pretty damn high level.”</em></p><p><strong>What appealed to you about the Commit model?</strong></p><p>I was at a point where I needed to figure out what I wanted to do. I tend to make decisions very systematically and I like the idea of being able to try before I buy. When you join a company you typically have an interview process and you get invested for at least six months. I wanted to do more than that — I wanted to try three or four projects, to get a sense of the team and the work. With Commit, that’s exactly what I got to do. That model was appealing, as was the opportunity to develop other skill sets. I got to level up skills that I wanted to work on and do it on real projects.</p><p><strong>How did you get connected to Plastiq?</strong></p><p>I started a 3-month pilot project with Plastiq around the end of November. I knew within the first month that I could work there. I liked the team, I liked what we were working on, I liked my fit, in terms of being able to leverage my skill set. I felt like I could make an impact. I let my manager know that I liked it there and they got the ball rolling. Three months later I joined full-time.</p><p><strong>What drew you to Plastiq?</strong></p><p>There are a lot of things, but it starts with the people. The culture and people are great. In a traditional early-stage startup, you’re figuring out the culture, and that’s great, but at Plastiq it’s more established and continues to get better. Also, Plastiq is well-positioned. They have a sound product-market fit, which a lot of early-stage startups are scrambling to find. And from a technology perspective — I think this is my big one — they were in a place where they had worked for a few years to get something to the market and make sure it fits, and now they are investing heavily in quality and reliability. I felt like I could leverage what I knew and what I had experienced at other good companies and contribute that with Plastiq.</p><p><strong>What advice would you give to other entrepreneurial engineers like yourself who are considering joining Commit?</strong></p><p>Everyone’s in a different situation, and if you don’t really know what you want to do or what you’re interested in, Commit is a good place to help you figure it out. With Commit, you get to try different things. That self-discovery is really great. You can try different projects, different industries, different tech stacks. You can cater your career to your specific interests and skillsets. The opportunity to grow at Commit is awesome — you can take on stuff that you don’t have a background in, and do it at a pretty damn high level, which is rare.</p><p># # #</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c349dbff9e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-sim-brar-plastiq-3c349dbff9e3">Committed to Success: Sim Brar, Plastiq</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Know Your People]]></title>
            <link>https://medium.com/commit-engineering/know-your-people-9364b9343621?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/9364b9343621</guid>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[Noel Pullen]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 23:13:53 GMT</pubDate>
            <atom:updated>2020-07-17T05:04:43.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Y7W9hejKxw4qF4GsL-f-bg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Headway</a> on <a href="https://unsplash.com/@noelpullen/likes?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Get some perspective</strong></h3><blockquote><em>“An attempt to understand the mind of another person, whether a stranger, your spouse, or your customer, is unlikely to benefit from imagining yourself in that person’s shoes and guessing what that person feels or wants. Accurately understanding other people requires getting perspective, not simply taking it. To understand the mind of another person, we need to rely on our ears more than our intuition.” </em>— Tal Eyal, Mary Steffel and Nicholas Epley <a href="https://hbr.org/2018/10/research-perspective-taking-doesnt-help-you-understand-what-others-want">Perspective-Taking Doesn’t Help You Understand What Others Want</a>, HBR, October 2018</blockquote><p>At <a href="https://commit.dev/">Commit</a>, our engineers are the heart of our company. My job is to <a href="https://www.linkedin.com/pulse/my-job-commit-create-incredible-experience-engineers-noel-pullen/">create an incredible experience for them</a>. I start this through conversations to <em>get</em> their perspective and begin to earn their trust.</p><p>I begin each exchange by explaining why we’re talking, focus the discussion entirely on them, listen to understand, and take notes. I make every effort to make them feel safe so they can share problems or concerns without feeling embarrassed.</p><h3><strong>What I learned</strong></h3><p>I ask questions that help me understand each individual. I watch and listen as they comment about Commit’s culture, processes and systems, to see what makes them smile and nod, or cringe and shake their heads. All in 55 minutes. Here’s what I’m learning from a few of the “get to know you” questions.</p><p><em>Q: Why did you join Commit? What pulled you here? What made you say to yourself, “I’m in!”?</em></p><p>When we change our situations, everyone has something that pushes them away from present circumstances and pulls them towards new conditions. A universal pull towards Commit was the flexibility to work remotely, learn, and grow through exposure to the various challenges that arise in building a startup. With respect to learning, two comments stood out in particular: the chance to ‘try more stuff’ by adding to the breadth of their skillset by <a href="https://medium.com/@jchyip/why-t-shaped-people-e8706198e437">developing the top bar of their “T”-shape</a>, and the chance to learn from an unfailingly helpful and kind community of peers and mentors at Commit. With respect to growing, Commit provides our engineers all the upside, excitement, and elevated responsibility of joining a startup without the financial risk. They also rely on us to find them a startup placement that matches their interests and growth objectives.</p><p>An unexpected but thoughtful tidbit about interviews came up too. We offer to represent them in negotiating all the aspects of their placements with startups, so they were delighted that Commit would be their last technical interview.</p><p>Our engineers cited all of the above as reasons they stay at Commit. That’s good news. Now, how can we do better?</p><p><em>Q: How can we improve at Commit?</em></p><p>Onboarding: our new engineers explained the program we use to welcome people to Commit needed better direction and organization because it felt too ad hoc. Other areas to improve are overall visibility of our engineer locations and projects, what placements are available and upcoming, and more options for startup placements. Engineers asked more ways to connect with other engineers, and our alumni asked for more frequent communication and coaching.</p><p><em>Q: How do you describe Commit to people? How did you explain it to your partner, friends, or family when you told them you joined?</em></p><p>This question elicited a variety of responses. Every single person had a slightly different answer. We need to dedicate more effort to our value proposition since our model is novel, serves a two-sided market, and is continuously under slight experimentation.</p><h3><strong>Time for action</strong></h3><p>Where to start?</p><p>First, fix the most urgent and quickly addressable issues frustrating to our engineers. Our first step has been rejigging our onboarding. Part of that rejigging has been to implement retrospectives for each new cohort so we can continue to listen to how things are going and continuously make the process better. Providing more visibility into upcoming and available placements is next on our list.</p><p>Second, invest heavily in the things they love about Commit. It’s easy to get caught up in fixing little annoyances, but those aren’t the reasons they join and stay at Commit. We plan to prioritize growing and scaling the things which engineers crave and benefit from <em>more</em> than fixing irritations. According to <a href="https://www.fastcompany.com/40472116/the-power-of-moments-why-certain-experiences-have-extraordinary-impact">research</a> collected by Dan and Chip Heath, to delight customers, chasing perfection is not the right approach. Instead, deliver moments that make an experience memorable. We want to play to our strengths and provide memorable experiences around our key promises of financial stability, an individualized career path, and a community to learn from and with.</p><p><a href="https://www.linkedin.com/in/noelpullen/"><em>Noel Pullen</em></a><em> is Commit’s Chief Experience Officer.</em></p><p><em>Thank you to all the engineers at Commit for their inspiration. Thank you to </em><a href="https://www.linkedin.com/in/lindsay-staniforth-6566323/"><em>Lindsay Staniforth</em></a><em>, </em><a href="https://www.linkedin.com/in/reachryanabbott/"><em>Ryan Abbott</em></a><em>, and </em><a href="https://www.linkedin.com/in/gunnr/"><em>Greg Gunn</em></a><em> for their counsel and editing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9364b9343621" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/know-your-people-9364b9343621">Know Your People</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My job at Commit is to create an incredible experience for engineers]]></title>
            <link>https://medium.com/commit-engineering/my-job-at-commit-is-to-create-an-incredible-experience-for-engineers-b5e46bc85abe?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/b5e46bc85abe</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[commit]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Noel Pullen]]></dc:creator>
            <pubDate>Mon, 01 Jun 2020 05:18:32 GMT</pubDate>
            <atom:updated>2020-07-17T05:12:52.627Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by ThisisEngineering RAEng on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*_JiAsarSZmVIakKpaXXwIA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thisisengineering?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">ThisisEngineering RAEng</a> on <a href="https://unsplash.com/s/photos/software-engineer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Do you love road trips?</strong></h3><p>One August in the 1990s, I drove across Canada, from Calgary to St. John’s, Newfoundland, with a good friend. I have so many fond memories of the journey: our debates about how to solve the world’s problems, the lengthy and reflective conversations, and the notable random people we met along the way. On that trip, we challenged each other to live lives where we would seek out significant experiences, and today it stands out in my memory as a foundational experience that helped guide my career and my life.</p><p>That trip helped teach me that experiences — especially when shared with others‚ are so valuable. They are the best way to grow, to deepen friendships, to understand ourselves, to learn what we want, and to realize what we’re capable of. That’s why I’m so passionate about creating experiences today.</p><h3><strong>What is Commit’s mission?</strong></h3><p>Commit was founded to design meaningful work opportunities for a group of entrepreneurial engineers. Entrepreneurial engineers need more than the standard “dual career” track offered today because they have broader interests and ambitions than management or specialist roles can satisfy. They excel at solving a breadth and depth of problems — like a Swiss Army knife. Startups offer the ideal type of work for talented entrepreneurial engineers. Commit’s purpose is to find them an opportunity to thrive at a mission-driven startup, one that matches their passion and maximizes their special skill sets.</p><h3><strong>What’s my role?</strong></h3><p>That’s where I come in. My role is to help our engineers grow their entrepreneurial careers, to provide a delightful experience, and to match their passion with exciting projects by connecting them to startups all over the world. As Chief Experience Officer or CXO, my focus is entirely on the engineer’s experience with Commit. I like how Denise Lee Yohn describes it in an <a href="https://hbr.org/2019/06/why-every-company-needs-a-chief-experience-officer">article</a> in the Harvard Business Review: “The sum of all interactions an employee has with an organization.” From how engineers feel about Commit before they join us, to when they become a part of our community, through their journey as alumni after they graduate to join a startup.</p><h3><strong>Who am I?</strong></h3><p>I joined Commit because I trust and respect the founders, and I love working with engineers. The future of work is remote and project-based, and Commit offers the best way to match world-class engineers with world-changing startups.</p><p>I love to help high-potential technology startups scale by building unforgettable cultures, data-driven ways of working, and effective operations. Recently, someone described my area of expertise as “cultural engineering.” That’s a pretty good two-word description.</p><h3><strong>Why is my role integral to Commit?</strong></h3><p>Commit’s business model relies on providing an experience that attracts entrepreneurial engineers. We make a point of calling our engineers Engineering Partners (EP), to recognize the vital role they play in building our business and contributing to the culture at Commit.</p><p>Commit’s key operating principle is “Prioritize the Engineering Partner Experience.” Every decision we make and every action we carry out, in every facet of Commit, is about doing what’s best for our engineers. We use a single metric, Engineering Partner Net Promoter Score, to measure how motivated our EPs are to tell their friends about Commit.</p><p>We’ve grown from zero to 30 Engineering Partners through word of mouth alone. My job is to ensure we grow to well over 100 EPs while maintaining a fantastic culture and outstanding quality.</p><h3><strong>What do I want to achieve?</strong></h3><p>I want the entrepreneurial engineers who join Commit to believe that it was the best decision they made in their career. Three years after they join, I want Commit EPs to feel like they’ve been in a fruitful, long-term partnership. This is possible if we help them manage the financial risk of joining a startup while they pursue their passion, bring them into a community of like-minded people, make lifelong friends, learn and grow along an individual career path, and experience memorable <a href="https://www.fastcompany.com/40472116/the-power-of-moments-why-certain-experiences-have-extraordinary-impact">moments</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUmo1TC7s8dFJqbPHNSy2w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@priscilladupreez?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Priscilla Du Preez</a> on <a href="https://unsplash.com/s/photos/people-together?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>How am I going to achieve it?</strong></h3><p>I’m going to take Commit’s foundational elements that have driven our positive word of mouth and scale our culture and our programs in a positive and participatory way, while our company grows in size and breadth. These programs include hiring, onboarding, graduation, and re-entry; learning and skill development; mentorship; an alumni program for EPs that have graduated to startups; thought leadership and personal branding.</p><p>I’m also going to add some of my own magic around collaborative experimentation, coaching, and community building. In particular, one of my missions is to “work out loud” and enable others to share and promote our culture, technology, practices, tools, challenges, and accomplishments with the global engineering community. Doing this benefits our whole community. And, as a byproduct, Commit will improve our capabilities and diversity by attracting and retaining outstanding engineers who share our philosophies and practices.</p><h3><strong>Where am I going to start?</strong></h3><p>By talking to the people at the heart of our culture and company, our Engineering Partners. So far, I’ve had conversations with all of them. I’m using these conversations to define a strategy and a plan to build on our EPX foundations, so we can make our EPs ridiculously happy and do what’s best for them at scale.</p><p><a href="https://www.linkedin.com/in/noelpullen/"><em>Noel Pullen</em></a><em> is Commit’s Chief Experience Officer.</em></p><p><em>Thank you to all the EPs at </em><a href="https://commit.dev/"><em>Commit</em></a><em>, </em><a href="https://www.linkedin.com/in/beiercai/"><em>Beier Cai</em></a><em>, </em><a href="https://www.linkedin.com/in/gunnr/"><em>Greg Gunn</em></a><em>, </em><a href="https://www.linkedin.com/in/shanegearon/"><em>Shane Gearon</em></a><em>, </em><a href="https://www.linkedin.com/in/lindsay-staniforth-6566323/"><em>Lindsay Staniforth</em></a><em>, and </em><a href="https://www.linkedin.com/in/reachryanabbott/"><em>Ryan Abbott</em></a><em> for their inspiration, counsel, and editing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5e46bc85abe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/my-job-at-commit-is-to-create-an-incredible-experience-for-engineers-b5e46bc85abe">My job at Commit is to create an incredible experience for engineers</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committed to Success: Eric Normant, VP Engineering, Plastiq]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-eric-normant-vp-engineering-plastiq-bebb63acb310?source=rss----ed8993761bc2---4</link>
            <guid isPermaLink="false">https://medium.com/p/bebb63acb310</guid>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Greg Gunn]]></dc:creator>
            <pubDate>Tue, 19 May 2020 18:24:23 GMT</pubDate>
            <atom:updated>2020-05-19T18:24:23.043Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Eric Normant is the VP of engineering for </em><a href="https://www.plastiq.com/"><em>Plastiq</em></a><em>, a bill-pay service for savvy consumers and businesses seeking an edge. We sat down with Eric to hear about what it’s like to work with Commit.</em></p><p><strong>Can you tell me a bit about Plastiq?</strong></p><p>At Plastiq, our mission is to empower growing small businesses to take control of their finances and preserve cash on hand by enabling them to pay virtually any business expense with a credit card. We provide them with new tools, insights and options to make more informed, intelligent decisions to maximize every opportunity.</p><p><strong>What are some of the typical challenges you face when hiring engineers?</strong></p><p>At Plastiq, hiring top talent is one of our highest priorities. From an investment perspective, it’s extremely important to find the right talent with the right skill set. It takes significant time and energy from multiple employees to source, interview and select the best engineers. Commit is a great channel to have because they do all of this themselves, which gives time back to our people to focus on engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uza6CZ85nUNmiOyU-qhaBg.jpeg" /><figcaption>“Commit’s mission and purpose to connect remote-first engineers to Silicon Valley startups resonated with us.”</figcaption></figure><p><strong>What support were you looking for when you came to Commit?</strong></p><p>We are always looking for the right partner to support our efforts to become the company we strive to be. The support Commit has provided aligns with our expectations and expansion efforts. Widening our reach for amazing talent beyond our current locations, in San Francisco and Boston, and identifying great talent in other areas are a few ways they have been there for us.</p><p><strong>What has it been like working with Commit?</strong></p><p>The Commit intake process is really rigorous. Instead of us spending most of a day interviewing a candidate through a standard approach, we’re comfortable getting to know an engineer from Commit for about an hour, to make sure we feel they’re the right fit. Then we kick off a pilot project with the intention that it could lead to a full-time employment opportunity.</p><p>Commit’s mission and purpose to connect remote-first engineers to Silicon Valley startups resonated with us. The passion and energy that Commit has demonstrated and the authenticity behind their business model is very meaningful to all of us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9esfTWOzLkOHLMCmbOs_Q.jpeg" /><figcaption>Plastiq helps businesses pay virtually all of their expenses using <br>existing credit cards even when cards are not accepted.</figcaption></figure><p><strong>How have the Commit engineers performed?</strong></p><p>We’ve brought on four engineers from Commit and all four have been strong. We have an extremely high bar for the engineers we hire, and all of the Commit engineers have met that bar.</p><p><strong>What has it been like working remotely with the Commit engineers?</strong></p><p>It’s been seamless working with the Commit engineers, because Plastiq already has a friendly remote culture. Our team members are generally located on both coasts, San Francisco and Boston. And now, with the help of Commit, we have a new hub in Canada as well.</p><p><strong>What would you say to other startups considering working with Commit?</strong></p><p>I would encourage other startups to learn about Commit’s mission and purpose as well as the value they can bring to a company in need of great talent. If that’s meaningful to them, as it is for us, then it’s definitely worth having a conversation with them.</p><p><em>Eric Normant is the Vice President of Engineering at Plastiq. The Bay Area fintech startup partnered with Commit to open a remote engineering hub to help grow and scale. Commit Engineering Partners Sim Brar and Mihai Listov joined Plastiq in 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bebb63acb310" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-eric-normant-vp-engineering-plastiq-bebb63acb310">Committed to Success: Eric Normant, VP Engineering, Plastiq</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>