Skip to content

From Learning to Code to Open Source Advocate: Brian Douglas, First Hire at Netlify and First Dev Advocate at GitHub

Tracy Lee and Brian Douglas chat about coding, self-learning, open source, and developer relations in this episode of Just Ship IT.

Brian's coding journey started in 2013 during a challenging period when his son was born prematurely, requiring a prolonged hospital stay. He sought a way to locate churches near the hospital and realized the need for a church review app. This sparked his determination to learn to code.

Brian highlights many successful developers didn't follow the traditional college route but instead found their way through self-learning and unwavering dedication. Brian's path to coding was largely self-guided. He utilized various online tutorials and courses to acquire the skills he needed. His learning adventure led him to the world of Ruby on Rails. Tracy and Brian emphasize the difference between self-motivated learners and those who treat coding as a checkbox item. They discuss the significance of immersing oneself in the learning process to truly grasp the fundamentals.

Brian worked at Netlify for about two years, a journey that began when he switched to Netlify for hosting. Eventually, Matt from Netlify reached out, offering Brian a role that would help shape the JAMstack landscape.

This diverse role at Netlify involved both front-end engineering and DevRel activities. Brian shares the story of creating This tool exemplifies his dedication to empowering the open source community.

Brian has made significant contributions in open source. He discusses the importance of mentoring others to contribute to open source projects and foster a culture of collaboration. The evolution of open source metrics is brought up, emphasizing that there's more to success than just star counts. Metrics like commit velocity and issue-to-PR conversion offer deeper insights into a project's health and growth.

Brian and Tracy conclude their conversation with a discussion on developer relations (DevRel). They stress that DevRel professionals should prioritize engagement and building relationships over focusing solely on metrics and numbers.

This Dot Labs is a development consultancy that is trusted by top industry companies, including Stripe, Xero, Wikimedia, Docusign, and Twilio. This Dot takes a hands-on approach by providing tailored development strategies to help you approach your most pressing challenges with clarity and confidence. Whether it's bridging the gap between business and technology or modernizing legacy systems, you’ll find a breadth of experience and knowledge you need. Check out how This Dot Labs can empower your tech journey.

You might also like

Behind the Scenes at CodePen & CSS Tricks with Chris Coyier  cover image

Behind the Scenes at CodePen & CSS Tricks with Chris Coyier

In this episode of Just Ship It, Tracy Lee chats with Chris Coyier, known for CSS Tricks and CodePen. CSS Tricks, a staple in the development community, was founded in 2007 as a blog. Chris reflects on how it all began and how this project has evolved over the years. One of the significant milestones in CSS Tricks' history was its acquisition by Digital Ocean about a year ago. Chris expresses his satisfaction with the fact that the team and content have been preserved, ensuring that the valuable knowledge and community of CSS Tricks continue to thrive. Chris and Tracy touch on Chris's early work and how he got started with CSS Tricks. He worked at SurveyMonkey while concurrently managing CSS Tricks. Chris outlines the birth of CodePen, a platform that revolutionized the way developers embed code demos directly into their blog posts. He sheds light on how CodePen secured $1 million in funding and how that investment played a pivotal role in expanding the team and facilitating growth. The discussion covers the intricacies of fundraising for startups and the advantages and challenges that come with it. CodePen has been in operation for over a decade with over 10 million page views per month, peaking at a staggering 12 million. It has become an integral part of documentation sites for popular technologies like React, Vue, Smashing Magazine, and MDN. Social media, especially Twitter, played a crucial role in driving CodePen's growth. Tracy mentions platforms like Seesmic and Omegle, highlighting how trends from the past can resurface and gain popularity once again. The conversation then shifts towards personal branding in the tech industry and how it has evolved over time. They explore the challenges faced by developers who strive to maintain a strong personal brand in the modern era. Chris and Tracy emphasize the importance of starting a blog without overthinking it, pointing back to their early days of blogging about topics they were passionate about. They reflect on the freedom and creativity that comes with not knowing too much, allowing individuals to share their genuine excitement and discoveries. Chris shares some decisions he would have made differently, such as creating separate editors for CodePen. They discuss the complex nature of adding features that initially seem promising but eventually become maintenance nightmares. The conversation touches on the pressures of blogging, from the desire to always be right to the potential for making accessibility mistakes. They highlight the importance of embracing the journey, learning from mistakes, and continually evolving. Chris mentions that his success with CSS Tricks undoubtedly contributed to the marketing and growth of CodePen. As CodePen continues to evolve, the team is hard at work developing the next version of the platform to take it to the next level....

Mastering Performance: How Misko Hevery is Transforming Development! cover image

Mastering Performance: How Misko Hevery is Transforming Development!

Open source software has become an integral part of the tech industry, powering countless applications and frameworks that developers rely on daily. In a recent episode, Tracy Lee chatted with Misko Hevery, known for his work on Qwik and Angular, about his insights into open source development. The episode began with a discussion of Qwik, a framework designed to simplify lazy loading and enhance performance. Misko highlighted the problem developers face when optimizing large applications and emphasized the importance of frameworks taking the responsibility of making applications faster. Qwik aims to do just that by providing a seamless lazy loading experience for developers, eliminating the need for extensive optimization efforts. They also touched on the challenge of convincing stakeholders to prioritize performance improvements over new features, a common struggle for developers. Misko shared valuable advice for aspiring open source contributors, emphasizing the significance of deeply caring about the problems you aim to solve. He also stressed the importance of aligning the mental model of a framework with developers, making it easier for them to get started and be productive from day one. This aligns with the success of popular frameworks like React, which are known for their straightforward mental models. The conversation shifted into the evolving landscape of open source sustainability. Misko pointed out that open source is not entirely free and that contributors need to be compensated for their time and effort. While there has been progress in this area, with platforms like Patreon and GitHub Sponsors enabling developers to receive funding, the culture surrounding financial support for open source projects is still evolving. Vue.js, a framework backed by a strong community and creator Evan You, was mentioned as a standout example of open source success. Misko highlighted that Vue.js is unique because it is not backed by a corporation, unlike many other frameworks. This independence has allowed Vue.js to thrive and become a leading framework in the front-end world. The episode wrapped up with a call to action for the industry to better support sustainable open source projects. Misko encouraged companies benefiting from open source projects to find ways to contribute back to the community. He expressed the need for the ecosystem to mature and develop a culture of financial support for open source maintainers....

Software Team Leadership: Risk Taking & Decision Making with David Cramer, Co-Founder & CTO at Sentry cover image

Software Team Leadership: Risk Taking & Decision Making with David Cramer, Co-Founder & CTO at Sentry

In this episode of the engineering leadership series, Rob Ocel interviews David Cramer, co-founder and CTO of Sentry, delving into the importance of decision-making, risk-taking, and the challenges faced in the software engineering industry. David emphasizes the significance of having conviction and being willing to make decisions, even if they turn out to be wrong. He shares his experience of attending a CEO event, where he discovered that decision-making and conflict resolution are struggles even for successful individuals. David highlights the importance of making decisions quickly and accepting the associated risks, rather than attempting to pursue multiple options simultaneously. He believes that being decisive is crucial in the fast-paced software engineering industry. This approach allows for faster progress and adaptation, even if it means occasionally making mistakes along the way. The success of Sentry is attributed to a combination of factors, including market opportunity and the team's principles and conviction. David acknowledges that bold ideas often carry a higher risk of failure, but if they do succeed, the outcome can be incredibly significant. This mindset has contributed to Sentry’s achievements in the industry. The interview also touches on the challenges of developing and defending opinions in the software engineering field. David acknowledges that it can be difficult to navigate differing viewpoints and conflicting ideas. However, he emphasizes the importance of standing by one's convictions and being open to constructive criticism and feedback. Throughout the conversation, David emphasizes the need for engineering leaders to be decisive and take calculated risks. He encourages leaders to trust their instincts and make decisions promptly, even if they are uncertain about the outcome. This approach fosters a culture of innovation and progress within engineering teams. The episode provides valuable insights into the decision-making process and the challenges faced by engineering leaders. It highlights the importance of conviction, risk-taking, and the ability to make decisions quickly in the software engineering industry. David's experiences and perspectives offer valuable lessons for aspiring engineering leaders looking to navigate the complexities of the field....