<?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 Paul Brohman on Medium]]></title>
        <description><![CDATA[Stories by Paul Brohman on Medium]]></description>
        <link>https://medium.com/@pbrohman?source=rss-876ec8c52da5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VKR6K1sjMql4muc0.jpeg</url>
            <title>Stories by Paul Brohman on Medium</title>
            <link>https://medium.com/@pbrohman?source=rss-876ec8c52da5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:45:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pbrohman/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[Mastering the Art of Mentoring Developers]]></title>
            <link>https://medium.com/@pbrohman/mastering-the-art-of-mentoring-developers-25213e1ab8e1?source=rss-876ec8c52da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/25213e1ab8e1</guid>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[team-leader]]></category>
            <dc:creator><![CDATA[Paul Brohman]]></dc:creator>
            <pubDate>Sun, 15 Sep 2024 18:03:37 GMT</pubDate>
            <atom:updated>2024-09-15T18:03:37.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1s7XP55gJs0dtDrIYI7xQ.jpeg" /></figure><p>In the rapidly evolving world of technology, the role of a mentor is more crucial than ever. Effective mentoring not only accelerates the growth of individual developers but also drives the overall success of teams and organizations. However, mentoring isn’t just about sharing technical knowledge; it’s a nuanced skill that involves guiding, inspiring, and fostering a supportive environment for growth.</p><p>In this blog post, we’ll explore key strategies for effective mentoring that can help you nurture talent, enhance skills, and build a thriving development team. Whether you’re a seasoned tech leader or a developer stepping into a mentorship role, these principles will provide a solid foundation for fostering a productive and engaging mentorship relationship.</p><p>In the last decade or more I have had the privilege of being in a mentorship role at various companies. Over this time, I have identified a few key concepts that drastically improved my ability to successfully mentor others in a technical space.</p><ol><li><strong>Understanding the Mentee’s Needs and Goals</strong></li></ol><p>Effective mentoring begins with understanding where your mentee stands and where they want to go. Each developer has unique strengths, weaknesses, and career aspirations. Conduct initial assessments to identify their current skill levels, areas for improvement, and long-term goals. This personalized approach ensures that your guidance is relevant and impactful.</p><p>Start with a comprehensive assessment to gauge your mentee’s current skill level and career objectives. This could involve:</p><ul><li><strong>Skills Assessment</strong>: Have your mentee complete a self-assessment or a technical skills evaluation. For instance, if they’re a junior developer, they might be tested on core programming languages, problem-solving abilities, and familiarity with development tools. Tools like coding challenges or pair programming exercises can help identify their strengths and areas for improvement.</li><li><strong>Career Goals Discussion</strong>: Schedule a one-on-one discussion to understand their long-term career goals. Are they aiming for a role in a specific technology stack, or do they aspire to move into a leadership position? For example, if a mentee expresses a desire to become a software architect, your mentorship can focus on strategic thinking and architectural design principles.</li></ul><blockquote>Create a safe, fun and transparent environment around assessments &amp; goal definitions!</blockquote><p><strong>2. Establishing Clear Objectives and Expectations</strong></p><p>Setting clear, achievable objectives is crucial for both the mentor and mentee. Define what success looks like for your mentoring relationship, and outline specific goals, milestones, and timelines. Clear expectations help keep both parties aligned and provide a framework for measuring progress.</p><p>Clear goals provide direction and motivation, while well-defined expectations help prevent misunderstandings and ensure that the mentoring process is productive.</p><blockquote><a href="https://www.atlassian.com/blog/productivity/how-to-write-smart-goals">SMART</a> goals are Specific, Measurable, Achievable, Relevant, and Time-bound. This framework helps in setting objectives that are clear and actionable</blockquote><p><strong>3. Fostering a Growth Mindset</strong></p><p>Encourage a growth mindset by focusing on continuous learning and improvement. Emphasize that skills can be developed through dedication and hard work, rather than being innate talents. Share experiences of overcoming challenges and learning from mistakes to inspire resilience and a positive attitude towards learning.</p><p>A growth mindset is essential for fostering a culture of continuous learning and improvement. As a mentor, you can play a key role in helping your mentees develop this mindset by encouraging resilience, learning from failures, and embracing challenges</p><blockquote>Help your mentees view challenges as opportunities for growth rather than obstacles.</blockquote><p><strong>4. Providing Constructive Feedback</strong></p><p>Effective feedback is essential for development. Offer constructive criticism that is specific, actionable, and delivered with empathy. Highlight what the mentee is doing well, as well as areas for improvement, and provide guidance on how to address these areas. Regular, balanced feedback helps build confidence and promotes growth.</p><p>Constructive feedback should be clear, actionable, and supportive. It’s not just about pointing out what’s wrong but guiding your mentee toward improvement while also acknowledging their achievements.</p><blockquote>Vague feedback can be confusing and unhelpful. Providing specific and actionable feedback ensures that your mentee knows exactly what to work on and how to improve.</blockquote><p><strong>5. Encouraging Independence and Ownership</strong></p><p>While guidance is important, fostering independence is equally crucial. Don’t forget you are the GPS here and not the driver. Encourage your mentee to take ownership of their projects and solutions. Provide support and advice, but allow them to make decisions and learn from their experiences. This approach helps build their problem-solving skills and confidence.</p><p>Helping your mentees develop the ability to learn and problem-solve independently is fundamental to their growth. As a mentor, your role is to provide the tools and strategies they need to take initiative and manage their own learning process.</p><p><strong>6. Sharing Resources and Networking Opportunities</strong></p><p>Share valuable resources, such as books, online courses, or industry articles, that can aid in their development. Additionally, introduce them to professional networks, events, and communities that can broaden their horizons and provide further learning opportunities.</p><p>Providing access to high-quality resources helps mentees stay updated with industry trends, learn new skills, and solve problems more effectively.</p><p>Mentoring is a powerful tool for personal and professional growth, and as mentors, our goal is to guide and support our mentees in a way that empowers them to achieve their full potential. Throughout this blog post, we’ve explored several critical aspects of effective mentoring, each essential for nurturing successful developers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25213e1ab8e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How GIFs Have Improved Our Company’s Developer Culture]]></title>
            <link>https://medium.com/@pbrohman/how-gifs-have-improved-our-company-s-developer-culture-cf7d5f4a608d?source=rss-876ec8c52da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf7d5f4a608d</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Paul Brohman]]></dc:creator>
            <pubDate>Wed, 22 Jul 2015 19:20:50 GMT</pubDate>
            <atom:updated>2015-07-22T20:12:06.276Z</atom:updated>
            <content:encoded><![CDATA[<p>Reviewing code is a terrible task — but really doesn’t need to be.</p><p>From the time it takes away from your own productivity, to the delicate balance of being objective, truthful, and constructive with your peers — or complete strangers in the case of an open source project.</p><p>When you work with people day in and day out, it can be hard to create a trusting and empowering environment by pointing out problems in their work. And if nothing is wrong, how should you effectively reward that same person? How do you celebrate small wins everyday and build a stronger team bond or developer culture?</p><p>At <a href="http://popkey.co/">PopKey</a> — a micro-content distribution platform and makers of the world’s first GIF keyboard — we love GIFs (obviously). To the point that we’ve made it a central part of our developer culture with our <a href="http://popk.co/1MaysBx">desktop app</a>. Each pull request involves a GIF. Our HipChat rooms are also filled with them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*R2efy3tDbpBhvWftyjRS-Q.gif" /><figcaption>Man, you even included the unit tests this time— well done!</figcaption></figure><p>GIFs just seem to have a natural, carefree way, of helping to break the ice and bring up delicate subjects. They help enhance communications across teams, regions, and even language barriers.</p><p>Bigger and more established companies probably don’t have this luxury, but as a small startup and scrappy dev team, we do. And it’s working.</p><h3>Mike Coutermarsh on Twitter</h3><p>1. make it work #2. make it fast #3. spend an hour picking out a gif for the pull request</p><p>Whether it’s good or bad news, a GIF helps to get the point across without coming off as malicious. There’s a certain naiveté with GIFs that make it fun, carefree, and harmless — but that can also communicate a huge win, a celebration, and something truly special.</p><p>We definitely aren’t the first company to adopt this — <a href="https://fourword.fourkitchens.com/article/bringing-smiles-pull-requests-github-selfies">GitHub Selfies</a> were among the first to help start this trend — but we’re big time evangelists after seeing the shift in morale, team bonding, and plain old fun around our office.</p><p>Try it for yourself — check out PopKey <a href="http://popkey.co/">web</a> or <a href="http://popk.co/1MaysBx">desktop</a> (Mac &amp; Windows) and add some fun into your company’s developer culture.</p><p>Here’s a quick how-to GIF — of course ;)</p><h3>Fabien Doiron on Twitter</h3><p>Easily add GIFs to your pull requests! How I use @getpopkey for Desktop with @GitHub. http://popkey.co/send-gifs pic.twitter.com/85zeCMo2Lb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf7d5f4a608d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>