<?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 Byrne Reese on Medium]]></title>
        <description><![CDATA[Stories by Byrne Reese on Medium]]></description>
        <link>https://medium.com/@byrnereese?source=rss-4230127057b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AJcEjPeY9d6uQ06nQdCSRw.jpeg</url>
            <title>Stories by Byrne Reese on Medium</title>
            <link>https://medium.com/@byrnereese?source=rss-4230127057b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:52:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@byrnereese/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[Summiting the Developer Pyramid: turning builders into advocates]]></title>
            <link>https://medium.com/@byrnereese/summiting-the-developer-pyramid-turning-builders-into-advocates-8ee065585445?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ee065585445</guid>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[developer-program]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 10 May 2024 17:20:37 GMT</pubDate>
            <atom:updated>2024-05-10T17:20:37.894Z</atom:updated>
            <content:encoded><![CDATA[<p>When many set out to build a developer program they think first and foremost of the benefits that come from having developers actively participating in their community: supporting other developers in your forums, building integrations, writing blog articles, hosting meetups and hackathons, helping with documentation, and contributing to open-source projects. The developers who grow into these roles are your advocates, and they bring to our developer programs what we all hope to achieve: scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*u0nL7r8jtyCdyU-nStSA8Q.png" /></figure><p>A common miscalculation is an assumption that these outcomes will happen naturally. While some products and platforms are better situated to achieve these outcomes more organically, the vast majority of platforms need to be much more intentional and conscientious in the creation of their advocacy engine.</p><p>Welcome to the final part of a 3-part series deconstructing the “Developer Pyramid,” a framework resulting from over 15 years of experience with developer programs, that has been guiding our work on the RingCentral Platform, an award-winning UCaaS API and developer program.</p><p>In part one of the series, we worked to understand <a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95">how to support learners within your community</a>. In part two we <a href="https://medium.com/@byrnereese/taking-your-developer-program-to-the-next-level-858a87b01796">explored the builder persona</a>. In this final chapter, we turn our attention to the developer segment from which your platform will extract some of the greatest value: the influencers, experts, and advocates that help fuel the growth of your platform.</p><h3>What sets Advocates apart</h3><p>In order to build programs to support and cultivate advocates, we must first understand what motivates them, and what sets them apart from the other developers your program serves. Let’s take a quick look at the persona of your top developers, those most prone towards advocacy.</p><h4>Advocates are passionate</h4><p>A defining characteristic of all advocates is passion. When we talk about “passion,” often the first thing that comes to mind is the image of a person who is excited, someone who actively shares and expresses their affinity for your product. We love developers like this. They provide us with our testimonials, and they become people we love to introduce our customers to because their passion is infectious.</p><p>Passion however can be expressed in more ways than raw enthusiasm, and knowing this will help you build the tools to help you detect other potential advocates. One of the best ways to measure someone’s passion is in the time they freely give to your product, with little or no expectation of a return. Thinking of passion in those terms opens us up to finding:</p><ul><li>Contributors to your forums and community</li><li>People who submit feature requests and ideas</li><li>Bloggers and publishers</li><li>Meetup and event attendees</li></ul><h4>Advocates have a personal stake</h4><p>Developers who have something personal to gain will gravitate naturally towards advocacy because incentives align easily with their self-interests. One’s personal stake can come in many forms:</p><ul><li>Self-image</li><li>Social status</li><li>Professional reputation or brand</li><li>Economics</li></ul><p>Knowing what incentives a developer is pursuing can help you build programs to deliver those incentives directly to the developer, and in turn, promote greater affinity for your brand and product.</p><h3>Creating an environment in which advocates flourish</h3><p>The secret to summiting the Developer Pyramid lies in the knowledge that we have the power to cultivate the qualities above in those developers who do not possess them naturally or develop them organically through the programs and opportunities we offer. For example, by giving a developer direct benefit for being on the platform, we can give them a personal stake where they didn’t have one before. By so doing, we prime those individuals towards more active forms of advocacy.</p><h4>Build an economy on your platform</h4><p>The most successful and expansive developer communities all share one thing in common: there is an active and vibrant economy that directly benefits those that choose to participate. Those platforms on which developers can fully subsidize their participation through the returns they receive are the ones that grow the fastest and endure the longest because they become self-sustaining, and reward developers directly for devoting more and more of their time to the ecosystem.</p><p>These economies or marketplaces stoke the passion and devotion of their developers as well — especially among those developers that grow to become dependent upon the revenue they generate on the platform. These advocates then attract more developers to the platform who hope to cash in on the marketplace’s potential, creating a positive feedback loop fueled by every new developer who successfully generates revenue on the platform.</p><p>Understand what kind of value exchange your platform is optimized for, and connect your developers to the value you provide. Here are three different “economies” to serve as an example:</p><ul><li>Money, e.g. app stores, and retail</li><li>Customers, e.g. lead generation</li><li>Engagement, e.g. API call volume, traffic, and service utilization</li></ul><h4>Create opportunities for volunteerism</h4><p>With every program or service you offer, design a variety of ways for community members to contribute. Some programs, like community support forums and events, have obvious and inherent ways people can participate. Other programs and services may require more creative thinking in order to manufacture those same opportunities.</p><p>Through participation, however, people have the chance to establish or build upon their status in the community, or to build their “personal brand.” As their reputation grows, so does their confidence and their willingness to take on more responsibility. As they take on more responsibility, the potential for them to be perceived as leaders grows as well, creating a beneficial feedback loop that encourages them to participate more and more.</p><h4>Don’t be afraid to ask</h4><p>Be mindful that many people in your community may want to volunteer, but may hesitate to step forward on their own. Perhaps they lack self-confidence, maybe they are afraid of doing something they think they shouldn’t, or maybe they are simply unaware of the ways they are welcome to contribute. This is all to say that you will be far more successful in recruiting volunteers by simply asking.</p><h4>Fill in gaps in your developers’ experience and knowledge</h4><p>Success on a platform often draws upon a broad base of knowledge and experience across a number of different domains. For example, developers often come to the table with a lot of technical expertise, but with less experience and knowledge of how to drive business outcomes.</p><p>For example, it is obvious that developers need technical documentation to support their software development efforts. But ask yourself, do those same developers know how to best market the products they build? Do they have experience in product marketing and design? And do you have content to support developers who are looking for ways to attract more customers to their product?</p><p>Therefore, support not only their technical education but all of the skills they will need in order to become successful on your platform.</p><h3>Building an Advocacy Engine</h3><p>The<a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95"> first tier</a> of the Developer Pyramid is designed to support individual Learners on your platform. The programs and content you create in service of these learners flow largely in one direction, from you to them. As developers shift their primary focus away from learning and towards building, their needs will start to exceed your capacity to support them directly.</p><p>To support developers in this phase of their growth, you lay the foundations for developers to support each other, creating a more social developer experience.</p><p>Once a developer has successfully brought a product to market on your platform, their focus will shift towards making that product a success. As they do so, opportunities are created for you to turn them into advocates. The third and final tier of the Developer Pyramid comprises the programs and activities you create to help drive your advocacy program and pipeline. Success here is ultimately measured in the time developers give back to you, and in the scale they bring to your programming efforts.</p><h4>Events</h4><p>If your goal is to cultivate individuals in your community with elevated status, who actively promote and speak on your behalf, then hosting an event provides no better opportunity for you to find the potential advocates within your community.</p><p>Hosting an event is no small undertaking. There are many details and logistical concerns that it might be easy to lose sight of why you are hosting the event in the first place. So as you embark on hosting an event, make sure the following is properly prioritized so that you are actively growing your advocacy base.</p><ol><li><strong>Be inclusive</strong>. When we produce an event, it is only natural for us to devote a great deal of time to our content creators and speakers — as we should by the way. But do not let yourself do so at the expense of the many supporting roles advocates can take on as well. Be inclusive of all the different skills people bring to the table, and capitalize on as many as possible.</li><li><strong>Focus on growth</strong>. Events are incredibly labor-intensive to plan and produce, and we are often tempted to lean on a trusted core of advocates and contributors to assist us and reduce the overall load. Resist this urge and strive to strike a balance between recruiting from a pool of usual suspects, and bringing new people into the fold. Introduce newcomers to the veterans, and invite them to support each other as they learn and grow.</li><li><strong>Turn content creators into celebrities</strong>. Filling your roster with speakers and content creators is a milestone that will no doubt bring a great deal of relief to the planning team, as it should. But don’t stop there. Create an engagement plan with your speakers, set reasonable deadlines for intermediate deliverables, and reach out to help them. Assess their technology needs. Provide them with several rounds of feedback on the content they are producing. Bolster their confidence and help them become a celebrity at your event.</li><li><strong>Make advocacy a core metric of success</strong>. We all fantasize about our events becoming the next Dreamforce, Oracle OpenWorld, or WWDC, where attendees overflow into the streets and tickets sell out within hours of being released. As tempting as it is, don’t make the size of your event your only goal and metric you tout to leadership. Keep your focus on recruiting and growing your advocate pipeline, by making it one of your key success indicators. As your base of advocates grows, so can your ambition for future events.</li></ol><h4>Top Developer and VIP Programs</h4><p>Periodically, a developer within your community will rise above the rest, often because their product or integration has struck a chord with your customers or your team. When this happens, return their investment by offering your help, and by creating opportunities to highlight their product and to amplify its success. Finally, measure the impacts of these efforts to inform which of them could be systematized and repeated within the context of a formalized partner program.</p><p>Such programs are important not only to scale your efforts but are essential in attracting corporate advocates to your ecosystem as well. Businesses form a crucial segment of any advocacy network because they are capable of bringing to bear a greater wealth of resources to support your developer program. To attract businesses, you need to offer concrete benefits that have reliable returns in order to help businesses justify their investment.</p><blockquote><strong>Lesson from the field: RingCentral’s Premier Partner Program</strong></blockquote><blockquote>At RingCentral our developer program and community is large enough that we have created a <a href="https://www.ringcentral.com/partner/isv.html">multi-tier partner program</a>. Our Authorized partners receive assistance in promoting their app in our app marketplace. Premier partners gain direct access to a lead capture system associated with the products they build and collaborate with us on Go-To-Market opportunities. Our Elite partners get integrated into our internal Sales materials and receive help from our engineering teams in building and enhancing their products and integrations. A tiered approach like this helps us to better scale our programming efforts and offset the costs associated with a white-gloved support experience.</blockquote><h3>Marketplaces</h3><p>As discussed earlier, intermediating a concrete exchange of value between your developers and your customers is a surefire way to prove your value to developers, and the more value they extract from your platform, the more prone to advocacy they will become. Listed below are some of the ways you can help bring financial benefits to your developers.</p><h4>App Stores</h4><p>Aaaah, the coveted app store. If your platform is in a position where it can exclusively facilitate financial transactions, by all means do it. Not only will developers become dependent upon you, but your developer program will have the potential to become a profit center for your company.</p><p>Unfortunately, successful platform-driven, transactional marketplaces require at least one of two things:</p><ul><li>Massive-scale</li><li>Value exchange baked into the core</li></ul><p>The challenge this presents is that either your marketplace needs to be built into your product from the very beginning, or your platform needs to achieve a level of success seen by very few.</p><p>The advice I most often offer is this: don’t be seduced to build an app store until you have achieved one of the two prerequisites. Until then, focus on establishing and growing other kinds of economies on your platform.</p><h4>Professional Services Networks</h4><p>Many customers, especially in the enterprise market, require custom development to integrate their business with yours, and they are willing to pay for it. To meet this demand and to capture that revenue, companies will often build out an in-house professional services organization.</p><p>If your company has a professional services organization, consider something that may be relatively counterintuitive: don’t soak up all of this revenue for yourselves. Allow at least some of this business to flow out to your developer community. By doing so not only are you helping to directly subsidize your top developers’ work on your platform, but you are also creating an engaged segment of developers who have a personal stake in your platform’s success, as well as the tools, services, and documentation within the ecosystem.</p><blockquote><strong>Lesson from the field: Six Apart and Apperceptive</strong></blockquote><blockquote>At Six Apart we had an enviable, active and vibrant developer community, many of whom worked full-time for one of our most trusted partners. To boost revenue and expand our sales capacity, <a href="http://www.econtentmag.com/Articles/News/News-Item/Six-Apart-Acquires-Apperceptive-Launches-New-Services-48840.htm">Six Apart purchased that partner</a>. At first we celebrated bringing so many of our friends from the community into the fold, but later lamented the unintended consequences to our community. By bringing those resources in house, we decimated our community, and cratered community engagement as once public interactions moved to internal mailing lists, and an open source culture of plugin development succumbed to pressure to make code proprietary. We also began to compete directly with our developer community in our thirst for more professional services revenue. In absorbing that business, we failed to fully appreciate the value that partner and their network of consultants brought to our community, our company and more importantly to our customers.</blockquote><h4>Referral programs</h4><p>Money is not the only currency your platform has to offer — customers are another. And while affiliate and referral programs that generate revenue for developers are notoriously challenging to pull off in a cost-effective manner, that should never deter you from tracking referrals. Not only will this data help you quantify the success of your program, but it also helps establish the value of your platform with external developers and partners.</p><h4>Reward programs</h4><p>Finally, if your developer platform lacks the scale to produce any of the kinds of marketplaces above, there is one last way you can incentivize participation: reward them directly for contributing to the platform. These systems are costly and do not scale well, but they are also very effective at generating engagement. Consider a rewards program if what you need is help getting the flywheel running smoothly once all the other pieces in your program are in place.</p><blockquote><strong>Lesson from the field: RingCentral’s Game Changer Program</strong></blockquote><blockquote>At RingCentral we have deployed an incredibly successful incentive and reward program that has driven a wealth of engagement, and more importantly cultivated our greatest and most devoted advocates on the platform. The <a href="https://developers.ringcentral.com/gamechangers">Game Changers program</a> gamifies advocacy on the platform, rewarding community members for answering questions on the forum, posting blog articles, posting on social media, and contributing open source projects.</blockquote><h3>Conclusion</h3><p>As shared in <a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95">part one</a>, the base of the Developer Pyramid exists to support your Learners. Whether they are experienced developers or novices, they all have a lot to learn when they first arrive. Truth be told? No one ever really stops learning. So, developers will routinely revisit the resources and programs that comprise the base of your pyramid in order to continue their education as they tackle increasingly harder and harder challenges.</p><p>If a developer commits to your platform to help them solve their problems at hand, they will matriculate to the second tier of your pyramid which is designed to support your ecosystem’s <a href="https://medium.com/@byrnereese/taking-your-developer-program-to-the-next-level-858a87b01796">Builders</a>. Inevitably, developers will start to encounter challenges not addressed by your documentation and will begin to turn to each other for assistance. At this stage, your role is to provide the systems your developers need to share their knowledge and experience with each other and to continually re-enforce the base of your pyramid with more specialized and advanced learning materials and developer tools.</p><p>Finally, when developers successfully ship a product on your platform they matriculate to the third and final level of your pyramid. Here you work to help your developers achieve successful outcomes with the product they built. Each success engenders greater trust and appreciation among the developers who benefit. This reveals the second objective of your pyramid: to catalyze their success into advocacy.</p><p>As the adage says, “success breeds success,” and so with each new success and each new advocate your program cultivates, your program can begin to scale allowing you to accomplish more and more with the same number of resources.</p><p>The Developer Pyramid is not a rulebook, but a construct to help you understand the personas within your developer community, what motivates them, and what they need to be successful in each stage of their journey. Like building a pyramid in real life, start at the bottom and work your way up. This helps guide your decision-making in a way that ensures each level has a solid foundation underneath it to make success easier to achieve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ee065585445" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking your developer program to the next level]]></title>
            <link>https://medium.com/@byrnereese/taking-your-developer-program-to-the-next-level-858a87b01796?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/858a87b01796</guid>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[developer-program]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 10 May 2024 16:54:11 GMT</pubDate>
            <atom:updated>2024-05-10T16:54:11.917Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past 15 years of building developer programs, it wasn’t until my work at RingCentral that it all began to crystalize into a framework that others could easily follow in building their own. Welcome to part 2 of a 3-part series deconstructing the “Developer Pyramid,” a tool to help teams build and improve upon developer programs. As discussed in <a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95">part 1</a>, the Pyramid has three levels. The first is devoted to your platform’s <a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95">Learners</a>.</p><p>In part two we discuss the second level, which focuses on supporting the Builders on your platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*-7dW6PxpTBl6vlMT6I687w.png" /></figure><h3>Who are Builders?</h3><p>To support your Builders throughout their journey, let’s take a moment to better understand this persona. What motivates them? What do they need?</p><h4>Builders have intent</h4><p>Builders are developers who have made a conscious decision to go off-script, to venture beyond the safety of a getting-started guide, and to make something of their own design. Almost by definition, Builders have intent, and it is the job of your developer program to help these developers in fulfilling that intent. In other words, you want to help them be successful in building something — arguably, anything that utilizes your platform.</p><h4>Builders are inquiry-driven</h4><p>A Learner, as discussed in <a href="https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95">part 1</a>, has a simple goal: gain enough familiarity and knowledge of a platform to enable them to progress to the next level as quickly as possible, or to complete their evaluation of your platform. That is why Learners are the most likely persona to follow a path set out for them.</p><p>As a Learner transitions into a Builder, they move away from following a path set for them, and towards a path they forge for themselves, one more closely aligned with their ultimate destination.</p><p>Builders, therefore, rely more on search and other forms of inquiry as they begin to piece together a design and ultimately a fully functional product to meet specific goals.</p><h4>Builders are more social</h4><p>By and large, Learners are more solitary in that they can and should be able to meet their learning objectives in a self-service manner. Granted, Learners will occasionally reach out to a community to ask a question, but only because they couldn’t find the answer on their own. Strive to anticipate and pre-empt these setbacks so that you minimize a Learner’s need to seek outside help.</p><p>The nature of a Builder is one of a pioneer — as they venture willingly into uncharted territory. The problems they are trying to solve are harder, more unique, and thus, their solutions naturally increase in complexity.</p><p>Builders, therefore, have a growing need to engage with other developers to collaborate with, share ideas with, and to learn from. What we see, especially in an enterprise context, is that many Builders are part of a team. Depending upon the scale of the project, individual developers may begin building an ad-hoc team of their own. At Roblox, for example, as young developers began building their own games, we saw them reach out to members of the community to pull in talent and skills they lacked themselves. Likewise, individual contributors to open-source projects begin the process of establishing their reputation in the community. In these ways and others, Builders tend to become more and more social, and reliant on others.</p><h3>The Builder’s journey</h3><p>Before we discuss what resources to put in place to support Builders, we should understand their journey in order to provide scaffolding around each step they are expected to take. Bear in mind of course that your mileage may vary, as every developer’s journey is different depending upon their experience, background, and needs.</p><h4>Early Builders</h4><p>Even though Builders have satisfied their basic needs with regard to learning the fundamentals of your platform, they still have tons of questions. In particular, is the following:</p><p>Developers went so far as to try out your platform by building something simple because you succeeded in helping them see your platform’s potential. Now, the rubber needs to meet the road.</p><p>Developers will begin searching for specific code samples, tutorials, and content from which they can begin piecing together a solution. Where there are gaps in their knowledge or architecture that they are unable to fill on their own, they will seek support, either from the community or from your support team.</p><p>If you observe an increase in this behavior, then it is a key signal that a Learner may be transitioning into Builder. It may also mean that a Learner has hit a wall and they are reaching out for help — either way, this is a key time to engage with the developer to ensure they are adequately supported. Another signal is that the developer has begun working on a second project or application, possibly a proof of concept, or even their final solution. Maybe this means they created a second application or project on your platform, but maybe it means they have begun to edit the configuration of the app they built as a Learner. The key is understanding what actions a developer may take on your platform to signal the forging of their own path.</p><h4>Builders in development</h4><p>Having gained confidence in the solution they envision, developers begin the process of building the final product. As a practitioner of developer relations, there is little need to outline the development process here, but bear in mind these questions and challenges developers will inevitably face as you assemble resources to support them:</p><ul><li>How will I authenticate users of my application?</li><li>How will I package, configure, and deploy my application?</li><li>What errors am I likely to encounter?</li><li>How will I monitor my application?</li><li>How will I collect feedback and maintain my application?</li></ul><h4>Builders taking a product to market</h4><p>While it is reasonable to conclude that a developer’s primary journey on a platform ends when they finally ship their product, doing so would rob you of your greatest potential to deliver something the developer may actually value more than your API: customers.</p><p>Your developer program should, therefore, help them not only build their application but promote it as well. At RingCentral, as do many platforms, we provide a marketplace, an <a href="https://www.ringcentral.com/apps/">App Gallery</a>, in which developers can list their products. In addition, we operate a number of partner programs to help us identify solutions relevant to our customers, and to help our developers reach them. For example, we provide partners with access to lead generation data from visitors to our App Gallery, we work with developers on co-marketing collateral to help amplify each other’s benefits, and we provide developers with advertising initiatives to harvest demand in the market.</p><p>Platforms that help developers acquire customers and revenue will be looked upon and talked about very differently in the market. That is why it is so important that a developer’s journey doesn’t end when they finally ship their application. In many respects, it has only just begun.</p><h3>Supporting the Builders’ journey</h3><p>Let’s turn our attention to the various resources and programs you might create to support the developers actively building an application or product for your platform.</p><h4>Forums</h4><p>Builders will need a place to ask questions. Forums are great because every question asked there will leave behind an answer that can help future developers. Forums are also a logical and natural place for developer communities to take root because they provide the means for developers to interface with each other, and establish and promote their expertise and status.</p><p>When contemplating how best to help developers find answers to their questions, consider the following:</p><ol><li>An inactive forum may actually be worse than having no forum at all. If your forums receive very few questions, it may have the unintended consequence of making your community seem inactive — turning some developers off. Therefore, consider relying on email-based support at first, or directing developers to a third-party developer Q&amp;A site like Stack Overflow.</li><li>Who will staff your forums? Everyone yearns for the day when the community begins to answer questions, and not just ask them. Before that day comes, if it ever does, it is crucial that questions never go unanswered. Consider what people from your team will be responsible for supervising your forums, and answering questions community members do not.</li><li>How can your support team make knowledge base articles a more natural by-product of their work? Support agents answer questions all day long, but many of their answers are provided privately. Making those answers discoverable to search engines will go a long way to help you scale your support operation.</li></ol><h4>Personalized support</h4><p>Builders are going to hit walls, and when they do, their instinct will be to turn to you for support. Unfortunately, not every question they have can be answered by the community or already has an answer published online somewhere. The fact of the matter is that the need to provide developers with personalized and private support is inevitable.</p><p>Therefore, hire a capable developer support team early. In the early phases of your program, they will be the backbone of your outbound support initiatives and will work to ensure developers seeking help will find answers. As your program grows, they will assist strategic partners with bringing products to market, they will publish content to help deflect support inquiries, and they can help your engineering team by being a source of early feedback on new features and platform capabilities.</p><p>High-touch support is difficult and expensive to scale. So it is essential to build a strong discipline on the team to document and share everything they learn that could be used by future developers.</p><h4>Tutorials and how-tos</h4><p>The success and scalability of your developer program will correspond closely to your ability to help developers to help themselves. To do that, the top three things to focus on are content, content, and content.</p><p>Almost every interaction with a developer creates an opportunity for new content. We have already discussed how forums and a culture of creating knowledgebase articles can help deflect developer questions away from the support team. However one cannot rely exclusively on this ad-hoc and reactive documentation process.</p><p>Balance your content initiatives with an editorial process that supports developers throughout their entire development process, and not just on the usage of your core platform offering. Do your best to anticipate their needs with content and sample code that many developers will have a common need for that goes beyond answering questions about how to leverage a particular feature. For example:</p><ul><li>Authentication and authorization</li><li>CI/CD integration</li><li>Webhooks</li><li>Debugging and troubleshooting</li><li>Monitoring and quality control</li></ul><h4>Tools</h4><p>As your program matures, and as your library of content is fleshed out, turn your sights to developing tools to help your Builders increase their visibility into their application running on your platform. Create tools that support them throughout their entire journey, from building, testing, and ultimately the acquisition and support of users/customers. Here are some tools you may consider building along the way:</p><ul><li><strong>SDKs</strong>. Identify common design patterns and make implementing them easier.</li><li><strong>Analytics</strong>. Give the developer insight into the API calls being made by the product, highlight potential problems (errors, high latency, low throughout, etc. )</li><li><strong>Token management</strong>. Help developers generate tokens to make calling the API easier. Give them a way of revoking access tokens in use by customers.</li><li><strong>Real-time activity stream</strong>. Help them troubleshoot their development or a customer’s use of the product with a real-time view of API calls generated by their application.</li><li><strong>Error console</strong>. Give developers visibility into the errors (requests and responses) generated by their application.</li></ul><h3>Laying the groundwork for future advocates</h3><p>Having a robust ecosystem of Builders should be the goal of every developer program. However, every Builder has the potential to become something more, something even more valuable to a platform: they can become an advocate.</p><p>Advocates are what help platforms scale. They drive platform growth and mindshare faster and more efficiently than all of your marketing resources combined. So strive to create experiences that resonate with Builders in such a way that they are inspired not only to build something but also stand up in front of a room full of developers to tell them that they should build something on your platform too.</p><h3>Up next</h3><p>In the third and final article in this series, we will finish our climb to the top of the Developer Pyramid, where we will discuss the role of advocates in your platform, and the kinds of support, services, and programs that will help cultivate them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=858a87b01796" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Developer Pyramid: a blueprint for developer programs]]></title>
            <link>https://medium.com/@byrnereese/the-developer-pyramid-a-blueprint-for-developer-programs-e1921d58ee95?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1921d58ee95</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[developer-program]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 10 May 2024 16:36:45 GMT</pubDate>
            <atom:updated>2024-05-10T16:36:45.980Z</atom:updated>
            <content:encoded><![CDATA[<p>I have spent the past 15 years of my career building developer programs, at Six Apart, <a href="https://tokbox.com/developer/">TokBox</a>, <a href="https://uphold.com/en/developer/api">Uphold</a>, <a href="https://developer.roblox.com/en-us/">Roblox</a> and most recently at <a href="https://developers.ringcentral.com/">RingCentral</a>. For most of those companies, I relied upon my experience and intuition to guide me. At RingCentral however, I began to distill that experience down into a framework to help guide me and my team on our path to building an award-winning API and developer program.</p><p>The Developer Pyramid is a simple construct representing how developers learn and engage with a platform, how communities grow around that platform, and how programs are structured to support individual developers, and to nurture communities into maturity. In this article, we will deconstruct the Developer Pyramid to help you understand how it can be applied as a blueprint for building one from scratch, or as a diagnostic tool to improve an existing one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Q3d67iIG5SsPlOTeCEk5g.png" /></figure><p>The pyramid itself is divided into three sections. Each section speaks to a persona it serves, and the infrastructure you need to support that persona. Over the next three posts, we’ll dive deeper into each section one at a time.</p><h3>Laying the Foundation</h3><p>The foundation of your pyramid, and your developer program, is among its most critical parts as the heights your program can reach will depend greatly upon how strong and broad the base of your pyramid is.</p><p>The temptation to build up rather than out is strong and understandable. Program stakeholders think first of the hallmark components of more visible aspects of other more mature programs, such as forums, hackathons, events, social media, open-source, and more.</p><p>However, the reason a pyramid is a good metaphor for a developer program in that it is a structure that can only be built from the ground up. One cannot put in place the apex of the pyramid before everything underneath has already been built, any more than you build the second floor of a building before building the first.</p><p>The lesson, therefore, is: Be. Disciplined. Every second you spend building a strong and broad foundation early on will result in many more benefits and returns down the road.</p><h3>Supporting Learners</h3><p>The base of your pyramid is designed to support the learners within your developer community. We use the term “learner” as opposed to “beginner” or “newcomer” specifically because:</p><ol><li><strong>Not every newcomer is necessarily a </strong><a href="https://dzone.com/articles/10-mistakes-beginner-programmers-make"><strong>“novice” programmer</strong></a>. In fact, it is safe to assume that most developers you encounter will be quite experienced, but every newcomer‘s first need is the same: to learn the basics.</li><li><strong>Not every beginner is necessarily a newcomer</strong>. Throughout a developer’s journey with your product, they will routinely need to return to certain fundamentals: to understand core concepts, to institute best practices, and to learn about new product offerings.</li></ol><p>Developers, by their nature, are perpetual learners, which is yet another reason the base of your pyramid is so important. Whether they are new to your platform or are veterans, whether they are novice programmers or are gurus, whether they are out to learn something new, or looking for a reminder of a method’s inputs and outputs, their reliance on this foundation will never truly diminish.</p><h3>Building the Base of Your Pyramid</h3><p>The raw materials for the foundation of your pyramid will be the resources developers need to successfully build products on your platform.</p><h3>Console</h3><p>Whether you are a downloadable toolkit or a cloud-based platform, your developers will need tools to help them provision, manage and monitor the apps they build. These tools can be collected inside of a console, to perform such functions as:</p><ul><li>Sign-up</li><li>App registration</li><li>Key and access management</li><li>Support</li><li>Debugging and diagnostic tools</li><li>Analytics</li></ul><h3>Learn More About Your Developers</h3><p>When building your developer onboarding process, take that as an opportunity to learn more about your developers. At RingCentral, we ask three simple questions designed to understand the following about every developer we come in contact with:</p><ol><li>Why are they here? Do they have the intent to build something, or are they here merely to kick the tires?</li><li>What products are they interested in building or integrating with?</li><li>What is their preferred programming language?</li></ol><p>The questions you may choose to ask may differ, but they should all serve the same goals: understand who is coming through your funnel, and to help you better support them while they take their first steps.</p><h3>Documentation and Content</h3><p>Content is the lifeblood of almost every developer program, as it fuels the learning of every developer on your platform. As a result, it should be where you devote the greatest amount of energy. There are many types of content you can produce, from blog articles and videos to books and webinars — but the core resource you need to focus on is documentation which can be divided into four rough categories:</p><h3>Reference Material</h3><p>If you could only produce one piece of documentation, then the first and only thing you would produce are the reference materials that define the basic inputs and outputs of your system. Without this, nothing else fundamentally matters because nothing can be built without it.</p><p>Quality here matters because shoddy reference documentation will inevitably lead to a burden on your support team, and will hinder community-driven support down the road. Therefore, build a culture within your company in which engineers take pride in their documentation, and maintain it as a natural by-product of their development process.</p><h3>Getting Started Guides</h3><p>At RingCentral, our getting started content comprises the smallest percentage of our total corpus of content, but it receives the greatest amount of time and attention from the team as we work to optimize it. We value our “Quick Start Guides” because they are the basis of almost every developer’s first impression of our platform. We also see them as instrumental in growing confidence developers need in order to take their next step on their own.</p><p>When building your getting started guides, consider the following principles in your design and approach.</p><ol><li><strong>Make all roads lead to the same starting point</strong>. Try to funnel all developers to start from the same place. So if there is a call to action to get started, lead the developer to the same article.</li><li><strong>Instrument a lot of tracking</strong>. Your getting started funnel is an activation funnel, and optimization of any funnel requires one to track an individual as they achieve key milestones like visiting the site, finding a quick start guide, and making an API call successfully.</li><li><strong>Say “good-bye” to Hello World</strong>. Create content that helps developers perform a fundamental task that not only demonstrates the value of your product but is also relevant in some way to what they may want to build down the road.</li><li><strong>Keep things simple</strong>. The code the developer produces through this content will be largely disposable — so try not to get caught up in the details, or in providing content that exemplifies idealized software engineering practices. Focus exclusively on the smallest set of tasks required for a developer to call your API successfully for the first time.</li><li><strong>Consider the medium</strong>. Text-based guides are a logical place to start, but depending on your audience and your product, other mediums may prove more effective. At Roblox for example, we found that video content was a much more engaging and successful way to help a younger generation to use our tools successfully, and Twilio has created an entire video game framework for learning their platform.</li></ol><h3>Code Samples and Reference Implementations</h3><p>Finally, provide your developers with a few fully functional applications that can serve as a reference for your platform’s best practices. You may be tempted to author fully functional, and arguably useful demo applications. While there is a time and place for these apps, rarely will your developers build on top of these products as frameworks in and of themselves, despite our best intentions. So keep these reference implementations simple, and use them to illustrate:</p><ul><li>How to integrate their apps into a <a href="https://dzone.com/articles/learn-how-to-setup-a-cicd-pipeline-from-scratch">CI/CD framework</a>, how to deploy to the cloud (e.g. Heroku, Google Cloud, or AWS).</li><li>How to integrate with popular frameworks, like Node/Express, Visual Studio, etc.</li></ul><p>As a general rule of thumb, whenever you approach creating a new piece of content, ask yourself, “what is my learning objective?” That will keep you focused on the right thing: what is it you want the developer to learn how to do, rather than trying to steer them towards something you want them to build.</p><p>When all is said and done, the base of your pyramid will start to take shape and should look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I3jDj_WPquNlo_H2XrFqsg.png" /></figure><h3>Building for Scale</h3><p>When people go about building a platform, they dream of the many apps their community will build. This, after all, is why they are building a platform in the first place. It is also one of the key measures of success: what your community has actually built.</p><p>The desire for this outcome will tempt developer relations teams to build the other parts of the pyramid as well: such as forums and blogs, as well as hosting hackathons and events. Fight this temptation early on, and seize the opportunity to build a discipline around making the base of your pyramid easier to grow and maintain.</p><h3>Engineering Culture</h3><p>There is a great risk within every engineering team, especially start-ups where the pressure to ship products is so high, to treat documentation as an afterthought. If there is one and only one piece of advice I wish every product development team would follow it would be to build an engineering culture that values documentation, and that generates it as a natural artifact of the product development process.</p><p>To that end, consider adopting the use of Swagger, or a similar framework for defining your API, and build a development process that requires engineers to take ownership of this resource, and to be accountable for providing sufficient content to allow any internal or external developer to use it successfully.</p><p>Have your development process require engineers to take as much care with defining programmatic interfaces, as it does human/user interfaces. Finally, ensure your process requires engineers to contemplate how changes to those interfaces can disrupt backward compatibility and existing implementations.</p><p>Laying this groundwork early is vital because trying to build this discipline after other habits have set in and codified is exponentially more difficult.</p><h3>Analytics</h3><p>Your ability to tune, and optimize your program and content will depend entirely upon what data you collect about the developers flowing through your program. Granted, you can always add this later, but you will lose an invaluable opportunity to learn about the developers in your program early on — an opportunity that will obviously never come again.</p><p>Plus, you will lose the ability to measure your progress and understand the impact changes you make to your program have, which is essential to proving the value of your work and of the platform as a whole.</p><p>The key milestones to track relating to a developer’s early progression on the platform are similar to other funnels in your organization. They are:</p><ul><li><strong>Account creation</strong>. The first step is simple: create an account, assuming your product requires it.</li><li><strong>Conversion</strong>. Next, you want to know if the developer has successfully engaged with your platform. This may be assessed by their calling of your API or the completion of a tutorial or guide.</li><li><strong>Activation</strong>. Finally, you want to know if the developer went on to do other things on your platform after they successfully got started. There is no prescription for measuring this, as every platform is different, but a good proxy is often the surpassing of some API call threshold.</li></ul><p>Other milestones and signals are key as well, but we will discuss those as they relate to later phases of developer growth on the platform.</p><h3>Automation</h3><p>When you first start, make the effort to support developers directly. Learn from the problems they encounter, and work to eliminate friction from their getting started experience. This will feel very manageable at first as the number of developers flowing through it will be relatively small. If you are successful though, nurturing the learners on the platform will become increasingly difficult and time-consuming.</p><p>That is why building in support for marketing automation tools like HubSpot or Customer.io will ultimately prove to be a very worthwhile investment.</p><p>Early on, use these tools to congratulate the developer as they achieve key milestones, and to point them in the right direction for achieving their next one. As your program grows, use these tools to send helpful and targeted content when developers hit a snag, and to assist developers in elevating the quality of their applications once they have been released.</p><h3>Summary</h3><p>The base of your pyramid is your foundation; and while it may be cliche to say, it is a universal truth: a building is only as strong as its foundation. Therefore, take time to get this right, because it will only help to make building every subsequent layer of your pyramid easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1921d58ee95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a theme optimized for developer documentation]]></title>
            <link>https://medium.com/ringcentral-developers/building-a-theme-optimized-for-developer-documentation-c90ee622863a?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c90ee622863a</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 20:12:08 GMT</pubDate>
            <atom:updated>2019-07-08T19:00:05.649Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Theme Optimized for Developer Documentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rb5oiDagAjccXAKimyyrlw.png" /></figure><p>Over the years I have worked on designing and implementing numerous websites to help developers learn and become successful in building products on top of a company’s platform. I have built and developed websites for <a href="https://tokbox.com/developer/">TokBox</a>, <a href="https://uphold.com/en/developer/api">Uphold</a>, <a href="https://developer.roblox.com/">Roblox</a>, and most recently at <a href="https://developers.ringcentral.com/guide">RingCentral</a>.</p><p>As with many design initiatives, the output of these projects is limited to the website itself. However at RingCentral, where employees are encouraged to share their innovations more openly, I am happy to make available to the developer community <a href="https://byrnereese.github.io/mkdocs-moonstone/">Moonstone</a>, a <a href="https://www.mkdocs.org/">mkdocs</a> theme that incorporates much of what I have learned along the way into a solution that makes it much easier to build, deploy and maintain API documentation and a developer website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GT7xZ4PI74buK2uOfx2Nkg.png" /><figcaption>The newly redesigned RingCentral Developer Guide using Moonstone</figcaption></figure><p>So what were the principle design objectives for the new RingCentral Developer Guide? And how did these manifest in the product we built?</p><h3>Easy to Write and Edit</h3><p>All documentation should be easy to edit by those responsible for doing so. Developer documentation, however, is often unique in that the number of people who might actively contribute to documentation is quite large, e.g. an entire engineering organization, or a developer community. Furthermore, documentation may sometimes reside in external source control systems or swagger specifications for which HTML and other rich text formats present many challenges.</p><p>We wanted documentation to be readable on and off the website. In and out of source control, and in and out of YAML and JSON files. That is why we wanted a system that was designed around markdown — a way of writing simple and readable text documents that can be easily converted into markup/HTML.</p><p>Markdown, however, is not perfect out of the box. If you really care about the design and layout of your content, then you will almost certainly find that markdown’s utility quickly breaks down as you hit the limits of its simplified syntax. Either you must be satisfied with an incredibly limited design palette, or you must embed HTML into your content. Both felt like compromises I would regret making.</p><p><a href="https://www.mkdocs.org/">Mkdocs</a>, however, is a platform written in Python and makes readily available to its users a number of <a href="https://python-markdown.github.io/extensions/">Markdown extensions</a>. Moonstone makes use of a number of these (which you will see later) which convert simple text into more complex UI elements. For example, this custom markdown syntax:</p><pre>!!! warning &quot;Some Alert Title&quot;<br>    More text to display in the admonition box. </pre><p>Produces the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*TlueVEIy7EGMU0lfTCKVjw.png" /></figure><p>With Moonstone, developers get the best of both worlds: pure-markdown documentation and highly styled UI elements.</p><h3>Easy to Update, Easy to Collaborate</h3><p>Creating and more importantly maintaining great developer documentation is a team effort. Whether you are looking to leverage the expertise of an open source community or your company’s engineering team, documentation must be as easy to edit as the source code that powers that which is being documented.</p><p>Mkdocs is a simple documentation framework that can be easily incorporated into any source code repository. Once in place, developers can easily run a copy of the website locally as well making it easy to preview changes before they are published. In addition, having your documentation live alongside your source code:</p><ol><li>Makes it easier for developers to update as they hack on a product.</li><li>Makes it easier for maintainers to process pull requests as they can evaluate code and documentation changes together.</li><li>Makes it easier for teams to share and provide feedback on changes under development.</li></ol><p>In other words, documentation can become an integral part of the change control process rather than being relegated to an afterthought, which is too often the case and ultimately leads to poor and out of date content.</p><p>To help foster a collaborative and team-oriented approach to documentation, we created <a href="https://github.com/byrnereese/mkdocs-git-committers-plugin">mkdocs-git-committers</a>: a mkdocs plugin that allows one to display a list of contributors to any page in the documentation. This small amount of recognition has helped fuel community contributions to vast documentation sites like Microsoft, and it is our hope that it will have similar effects for us and others.</p><h3>Beautiful and Customizable</h3><p>We wanted Moonstone to be beautiful in its simplicity. Plain, but not without personality. We wanted a theme that could stand on its own, or be easily customized to take on the brand of any product or company.</p><p>We started with Bootstrap, a robust CSS framework that not only provides Moonstone with a fully-adaptive, super-clean canvas that works across all browsers and devices but also an <a href="https://getbootstrap.com/docs/4.3/components/alerts/">expansive library of UI components</a> that harmonize well with each other.</p><p>We then bundled additional styles and UI elements commonly used by developers in their documentation so that nothing was overlooked. These include:</p><h4><strong>Syntax highlighting</strong></h4><p>While code highlighting is table stakes for developer docs, we wanted to go one step further by providing <a href="https://byrnereese.github.io/mkdocs-moonstone/styles/code/">optional line numbering and line highlighting</a>, all using a pure markdown syntax.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*csWIdZUmBteJLYoEuasUvw.png" /></figure><h4><strong>Fenced code blocks</strong></h4><p>Stack code samples one on top of the other to create tabbed code panes. Organizing code in this way helps preserve screen real estate, and more easily relate code sample to one another. They are great for allowing readers to toggle between code samples written in multiple languages, or request/response pairs common to APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*PGHevou7DRfpNmTj_mZlmw.png" /></figure><h4><strong>Admonitions</strong></h4><p>Often you need to bring the readers attention to an important detail. <a href="https://byrnereese.github.io/mkdocs-moonstone/styles/admonitions/">Call-outs</a> alert readers to warnings, best practices, or a simple “FYI” to signal where they can go for further reading on a subject.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*wyXY5Vd4hJWUaHiVVMekCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*NXPMX8FFobLEtCrN9tdqog.png" /></figure><p>You can also keep documentation focused and clear, by hiding documentation behind expandable blocks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*2bE3Mmz1VvCj_w3vFZvLZQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*H8mg-_UMZEfRRP4Z4WaC1Q.png" /></figure><p>In keeping with our first design goal of making documentation easy to write and edit, we implemented all of the above using markdown extensions so that your docs are never unnecessarily muddled with HTML. We even created the <a href="https://github.com/byrnereese/mkdocs-bootstrap-tables-plugin">mkdocs-bootstrap-tables</a> plugin to seamlessly convert the bare-bones tables created by markdown, into bootstrap compatible tables so that every aspect of your documentation harmonizes perfectly across your site transparently and automatically.</p><h3>Why Moonstone?</h3><p>For those of us building developer oriented products, like APIs or SDKs, it would be a mistake to think that our products lack a user interface. Our documentation is often the first thing our users encounter, even before they have even actually used our product much less downloaded or installed it. Afterward, our documentation becomes the resource our users consult the most — and one of the largest contributors to our products’ success.</p><p>We created Moonstone because we believe that documentation IS our user interface, and we should take as much pride in our documentation as we do in the products we craft using the SDKs, APIs, and developer tools used to build them.</p><p><em>Byrne Reese is a Platform Product Manager at RingCentral who advocates for Developer Experience, education, and tools.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c90ee622863a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ringcentral-developers/building-a-theme-optimized-for-developer-documentation-c90ee622863a">Building a theme optimized for developer documentation</a> was originally published in <a href="https://medium.com/ringcentral-developers">RingCentral Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get hired as a Product Manager]]></title>
            <link>https://medium.com/42hire-don-t-panic-just-hire/how-to-get-hired-as-a-product-manager-e494352da2c1?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e494352da2c1</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 17:33:54 GMT</pubDate>
            <atom:updated>2017-09-08T18:11:02.853Z</atom:updated>
            <content:encoded><![CDATA[<p>I love product management. Few other roles within a company place a single person at the nexus of so many different teams, and disciplines. For me in the software world I get to work with designers to create compelling user experiences, with engineers on how technology can be brought to bear on innovating new solutions, or making existing solutions scale, with marketing on how to best tell a product’s story, with sales on the delivery of products we build, and of course with customers where I can see how the products and solutions we build help them. It is sometimes hard to imagine doing anything else.</p><p>Finding a job as a product manager, even in the best of circumstances, can take its toll, because even the best candidates face stiff competition in the job market. For starters, product managers are one of the most critical hires a company can make, which means companies are highly selective when placing someone. Add to that the fact that there are simply more people pursuing a PM roles then there are PM roles to be filled, and everyone is bound to experience what I have a several points in my career: a grueling and unforgiving hiring process.</p><p>How we confront this challenge should tell us a lot about the kind of product manager we are, or are going to be. For me, I see it as an opportunity to apply my craft. My craft in this case is to devise frameworks, processes and tools that will lead me one way or another to a successful outcome.</p><blockquote>When looking for a job, consider for a moment that <strong><em>you</em> are the product</strong>. Your job as product manager is to bring yourself to market for a customer that would benefit from your unique skillset and background. You are in essence searching for your own product-market fit.</blockquote><p>What follows is an outline of how I go about structuring my Product Manager job search, which over the years has served me well in landing a PM role at companies I respect and enjoy working for.</p><h3>Know your value proposition</h3><p>Perhaps the most immediate and measurable advice I ever received was from Adam Nash, CEO of Wealthfront, whom I approached years ago after having trouble getting my foot in the door at a number of companies. I had around 6–8 years experience as a PM under my belt at the time, all with good companies, and was confused why I couldn’t seem to get traction. Adam asked where I was applying, took one look at my resume, and quickly offered following assessment: the roles I was pursuing were not “aligned with my personal brand.”</p><p>As I saw it, I could heed his advice and adapt in one of two ways. First, I could rework my resume to better position myself for roles I wanted; or, I could focus on roles that were more closely aligned with the resume/experience I already had. In the end, I tried both; and it did not take long for me to see which strategy worked best, and why Adam’s advice was so perfect.</p><p>When we talk about “brands,” we are talking about something more fundamental than a logo or a resume in this context. We are talking about what is in your DNA as a product manager — about what makes you, <em>you, </em>professionally speaking. While there is no harm in customizing your resume to the job at hand, in the end you must be able to confidently defend your resume as well. So, when I started pursuing opportunities that were more aligned with my experience and passion, rather than trying to align myself with the brands I admired, the stories I told felt more natural, conversations started to flow, my confidence picked up, and I began to progress farther and farther down the hiring process.</p><p>It seems obvious in hindsight, but at the time it revealed to me that I was going about my search backwards. I was approaching companies whose brands I had a high affinity for, rather than structuring my search around companies that were aligned with <em>my</em> brand.</p><p>I start with this piece of advice because as product managers we understand that at the heart of most successful products is a well understood value proposition. That value proposition informs just about everything we do as a team in search of product-market fit. It informs what customers we seek out, what channels we use to acquire those customers, our pricing, and of course what features we build. Knowing your own value proposition as a product manager, will similarly inform every aspect of your job search.</p><h3>Build your conversion funnel</h3><p>When I am bringing a new product to market, one of my first activities is to figure out who my customer is. I typically start with a long list of potential customers, then through research, and trial and error, I slowly work to validate and invalidate my hypotheses, until I am left with is a better understanding of my target market and a profile of my ideal customer within it.</p><p>When looking for a job, I have a similar objective: to hone in on a profile of a company or product for which my personal brand is strongly resonate with. To help me measure this, I turn to a tool familiar to most product managers: a conversion funnel, which in a job search breaks down something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4bdv0O85P7zubyQurdrGg.png" /></figure><p>While I may not employ my job search funnel in the same way I do a conversion funnel for an online registration flow for example, they still have enough in common conceptually to inform my overall process. I need campaigns to fill the top of my funnel with qualified leads, different channels from which to source leads from, and strategies to re-engage with people who churn out. Plus, tracking my funnel helps shed some light on where the weaknesses in my story and process lie, and point me in the right direction when making changes to any of the above.</p><h4>Fill your funnel</h4><p>My search begins by me creating a spreadsheet to track every company I am even remotely interested in speaking to. As I learn more about each company, I begin to sort them based upon their personal appeal, and my confidence that I will be perceived as a good candidate for a role they have open.</p><p>I build my list of companies from a small hand-full of sources:</p><ul><li><strong>LinkedIn</strong>. My first source for leads is almost every company where a friend, or former coworker of mine works, or has recently worked. I research the companies I have never heard of, and add to my spreadsheet the name of every company that catches my eye.</li><li><strong>HireClub</strong>. <a href="https://www.facebook.com/groups/hireclub/">HireClub</a> is an Facebook group dedicated to helping companies and people looking for work find each other. Its strength lies in a community atmosphere where people are genuinely interested in helping each other out. I frequently visit HireClub to browse its feed where individuals post jobs they are hiring for. It is a safe assumption to make that anyone posting there works for a company that is actively growing. So even if people are not posting about product positions specifically, I still make note of their company in my spreadsheet.</li><li><strong>Techcrunch </strong>and<strong> VentureBeat</strong>. These are the leading news sites of the technology and start-up world. The news sites relevant to you may vary. I consult them to see which companies have recently received funding — a strong indication that they are also growing, and to get exposed to a lot of new companies you may not be familiar with. Again, I make note of any company that sparks my interest, and queue it up to be researched more thoroughly later.</li><li><strong>Indeed, ZipRecruiter, and other job sites</strong>. Job sites are also very helpful. I search them specifically for product management roles, which saves me time down the road by helping me to qualify my leads by ensuring that the companies I am interested in, are also hiring product managers.</li></ul><p>I let myself get a little lost in this phase of the process. Learning about what is going on in the industry helps me down the road when interviewing, as I am better able to demonstrate some working knowledge of the industry I am interviewing in, not to mention the competitive landscape as well. More importantly however, the more companies I put into the top of my funnel, the more that will hopefully come out the bottom.</p><h4>Qualify your leads</h4><p>Once I have a list of companies, I need to see which ones are hiring for a role I am interested in. I make note of the role in my spreadsheet, and the URL of the job posting so I can return to it easily. I also like to make note of my interest level in the position, e.g. low/medium/high, and some kind of score indicating how strongly aligned the role is with my brand. These extra fields will help me to prioritize which companies I reach out to first, and where I will devote more of energy.</p><p>If a company I am interested in is not hiring product managers, I still keep them on my list. I just make note, and move them to the bottom of the list. You never know when a company’s hiring needs change, so from time to time, I will revisit my list of companies to check.</p><h4>Get noticed</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*BJYI3bjoWT7ygxYqGv2hvg.gif" /></figure><p>Once I have a list of specific job opportunities to follow up on, now I need to get my foot in the door. My goal here is simple: find a personal connection at the company and get in touch with them personally. Making these connections is where the bulk of my work resides in my job search. It is incredibly time consuming, but it is without a doubt the single most valuable work I engage in. If done successfully, I will have an advocate at the company where I am applying to buoy my candidacy with a recommendation, or at the very least have someone to submit my resume on my behalf — bypassing the company’s public website where most resumes go to die.</p><p><strong>Finding my “in”<br></strong>Successfully finding someone at a company to talk to and refer you depends largely on the size of your network. Bear in mind that your “network” here should encompass not only the people you are connected to on LinkedIn, but should include all of the communities you belong to, like your neighborhood, your alma mater, schools your kids may attend, and other communities, clubs and organizations. If your network is still relatively small, then devote time to growing it by getting out there and meeting people; but I think you will find, that when you take a more encompassing view of your network that it is larger than you give it credit for.</p><p>LinkedIn is my tool of choice for finding my “in” with a company, because it allows to search for companies, view a list of employees, view their job titles, find how I am connected to them, and message with them (even if I don’t have their email address). Therefore, I start by searching LinkedIn for each company in my spreadsheet, and then viewing a list of its employees, filtering out all but my first and second degree connections. If I have any first degree connections to an employee there, that is the person I will reach out to, as chances are they know me personally and can also serve as my advocate.</p><p>If I don’t have any first degree connections, which is often, I see which of my friends might know someone who works there, giving preference to fellow product managers. I then reach out to my friend asking if they might make an introduction.</p><p>If all else fails, I invite the company’s recruiter to connect, or turn to Facebook and ask my friends directly, “do any of my friends know anyone who works at the following companies: …?”</p><p>Remember, at the end of the day all I am trying to do is avoid having to submit my resume via a public website. I don’t need to be close friends with the person, I just need a loose enough connection for them to feel comfortable submitting my resume on my behalf. In my experience, anyone I get in touch with is happy to refer me because they will probably get a referral bonus if I get hired. So I don’t sweat it, and just reach out. I have nothing to lose.</p><h3>Do your research</h3><p>It should be a given that you will want to research the company, and its product before talking to anyone. Going into any interview not knowing these basics is just bad form. So before I hop on the phone with an in-house recruiter, and especially a hiring manager, I take some time getting to know the company’s product as best as I can. I search Google News for the company to understand what industry dynamics may be shaping it. I get to know the company’s competitors, and develop a perspective of my own to share with the people I speak with.</p><p>All of this should be a given, because failing to demonstrate this knowledge, or at least an honest attempt to be prepared will reflect poorly on me as a product manager whose job it is to be expert in these things.</p><p>For the companies I am especially excited about joining my research doesn’t stop there.</p><h4><strong>Positioning yourself for “fit”</strong></h4><p>Teams are going to evaluate candidates on two key axes. The first is based on their skillset and experience. Does this candidate possess the ability to do the job we require of them? Do they have experience with our technology? Have they used our tools and processes before? How deep is their knowledge of our problem and solution space? And so on. If you been diligent in pursuing companies strongly aligned with your brand, then scoring well here should come quite naturally.</p><p>The other axis they are evaluating candidates on is “team fit.” For a product manager, how you get along with others is key, but what team fit is usually about is culture. It is about your style, and approach to problem solving. It is about how you complement the team, and what you bring to it that is different.</p><p>I can guess at these things by going in cold to an interview, or I can do what a good product managers do when trying to better understand the needs of their customers: talk to them, get to know them, and understand how their teams work.</p><p>So, before I am to be interviewed, I like to interview someone at the company first. To get the best and most candid insights, I try to talk to someone I might work alongside, rather than going directly to a hiring manager. I talk to them about what it is like to work at the company, and figure out if it is a place where I would fit in, and be happy at. I am also trying to assess their needs as a team and company, so that I can better position myself as a solution they are looking for. Here are some things I specifically inquire about:</p><ol><li><strong>Company culture</strong>. I ask about the company’s values. Understanding these helps me to understand what they are looking for in a candidate beyond their hard skills, and prompts me to find ways to reflect these values through the stories I tell.</li><li><strong>What makes a PM successful there? </strong>I like to ask what traits are possessed by successful PMs, and are most valued by others on the team. If there are things the team is well known for, then I want to do everything I can to position myself as someone who’ll help preserve, and reinforce them.</li><li><strong>Current challenges</strong>. A strong tendency for interviewers is to evaluate how a candidate they are speaking to will help them address problems they are facing in the right now. In addition to understanding the product challenges I will be tasked to solve, I also try to ascertain what challenges exist with regards to team dynamics and process. If I can present myself as a possible solution to those challenges, I will increase my perceived value to the team ten-fold.</li></ol><h3>Learn and iterate</h3><p>As a product manager, you understand the importance of the iterative cycle of learn/measure/build. This is the process we engage in to focus our efforts effectively to build great products that best service the needs of our customers, and has equal relevance to our job search.</p><p>Every engagement I have with a company is a chance for me to learn, and to improve how I present myself. With each phone call and conversion, with each iteration, I get better at telling my story, I get better at explaining the philosophy and methodologies that drive me as a product manager, and I get more fluent in connecting past experience with the specific questions I am asked. At the end of each interview, I consider what went well, and think critically what didn’t feel or go as smoothly as I would like.</p><h4>Fail early, fail often</h4><p>Early on in my job search, my goal is to get myself out there talking to companies as quickly as possible. I am in a sense my own MVP that I am working furiously to hone.</p><p>Just like with real products, there is often a right time and a wrong time to engage a customer segment to adopt your product. Sometimes you hold off on introducing your product to them to ensure that the product has time to mature; and to increase your confidence that their first exposure to your product will be a positive one.</p><p>I do the same thing in my job search by first pursuing opportunities with companies that are not at the top of my list. That way if and when I don’t get a job offer, I won’t feel the loss as profoundly. This also gives me time to learn and grow in how I answer questions, and tell my own story, so that when I start engaging with some of my favorite companies, I will be more practiced and mature.</p><h4>Learn</h4><p>Be prepared for companies to pass you up. The process is competitive, and hiring practices have been honed to look for very specific candidates. When I learn I am not a good fit for a role, I do two things. First and foremost, I express my gratitude to the recruiter or hiring manager for giving me so much of their time and for the opportunity to learn more about the company and job opportunity.</p><p>Then I ask for feedback.</p><p>Sadly, most companies have policies prohibiting them from sharing their rationale with job candidates. While frustrating, there are <a href="https://www.quora.com/Why-dont-companies-give-interview-feedback">good reasons for companies to adopt this policy</a>. I ask for feedback anyways, expecting few will tell me anything, in the off chance some may provide me with valuable insights.</p><p>If I was referred into the company via a friend, I ask them if they might follow up with the hiring manager or recruiter, and relay what they learn back to me. If I don’t have an advocate who can do that, then I simply ask. I try to keep my request simple, and I avoid any hint that I am wanting to engage the recruiter in a debate about their decision — their worst-case scenario when interfacing with a candidate after they have been rejected. Here is an example email I might send asking for feedback:</p><blockquote>Thank you for letting me know, and thank you so much for the opportunity to learn more about &lt;company name&gt;. I enjoyed speaking with the team.</blockquote><blockquote>Out of curiosity, is there anything more you can tell me about why the team felt like I was not an ideal fit for the role? I like to gather as much feedback and data that I can to assist me in my job search.</blockquote><blockquote>Thank you so much for your time!</blockquote><p>Then, no matter what I hear back, I do not reply except to say thank you. The most important thing you can do is be professional, and be grateful you received any feedback at all.</p><h4>Humble yourself</h4><p>If you are lucky enough to get feedback, the next thing to do is figure out what you can learn from it. Sometimes the feedback will help inform things you can do before the next interview — like learning a new technology, process methodology, or toolset. The hardest feedback to hear however is the kind that hints at an assessment you feel the team got really wrong. You’ll known when you hear it, because you will feel really defensive about it.</p><p>Here is some feedback I received after my first interview in my latest job search:</p><blockquote>Unfortunately, the team is going to pass. We are looking for someone a little more analytical for this role.</blockquote><p>My first reaction was, “are you kidding me?!?” Because honestly, I consider myself to be a relatively successful product manager, and it is hard to spend 10+ years doing this job without being analytical. My instinct was to reply back to plead my case.</p><p>So I shut down my email client, took a deep breath, and asked myself, how could they have arrived at this conclusion? The answer is almost always the same: I failed to communicate effectively in my interview. So in this case, I humbled myself, took myself back to square one, and searched on Google for, “<a href="https://www.google.com/search?q=how+to+demonstrate+analytical+skills+in+an+interview&amp;oq=how+to+demonstrate+analytical+skills+in+an+interview&amp;aqs=chrome..69i57j0l2.283j0j1&amp;sourceid=chrome&amp;ie=UTF-8">how to demonstrate analytical skills in a job interview</a>.”</p><p>I took literal and mental notes as I did more research, and prepared myself to do better next time.</p><h3>Persevere</h3><p>Without a doubt, the hardest part of this process the longer it takes is dealing with the steady stream of disappointment. Jobs you are really excited about get filled, sometimes while you are interviewing for them. You learn that a company isn’t moving forward with your candidacy, sometimes after having invested hours and hours of your time in phone calls, onsite interviews, and take-home exercises. You give everything you have to offer, and get absolutely nothing in return, not even feedback that can help you learn from the experience. Sometimes you just have an off day, and the answers you give in an interview are not as crisp as their should be. The margin of error is very small, and the process can be heartbreaking, can make you question if you are even product manager material, and can at times lead to legitimate <a href="https://medium.com/@byrnereese/on-depression-the-lies-we-tell-ourselves-7f133e4aec6a">depression</a>.</p><p>I have been there. More times than I care to recall. It is hard to offer advice to anyone who finds themselves in this place, as no matter how many others have also struggled and commiserate with you, it is still an incredibly lonely place to be.</p><p>What I can say however, is that hiring processes are highly selective for a reason: a company is trying to find the best candidate to be their product manager. They want the person they select to succeed, and they want them to fit with the rest of the team. So when the day comes when you do get an offer, it is because they see you as someone who will be successful at their company. That should bode well for you, and means that no matter what you ended up at the right place.</p><p>Hopefully, you will find some of the advice from above helpful to you in some way. Even if the process above doesn’t match your style, don’t forget:<strong> in a job search, <em>you</em> are the product.</strong> You job search therefore is just another opportunity to apply your craft, and to keep up on the skills that make you a great product manager. If you are not finding success, then do what any good product manager would do — do the research and analysis to understand why, and keep learning and iterating.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e494352da2c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/42hire-don-t-panic-just-hire/how-to-get-hired-as-a-product-manager-e494352da2c1">How to get hired as a Product Manager</a> was originally published in <a href="https://medium.com/42hire-don-t-panic-just-hire">Don&#39;t Panic, Just Hire</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Skateboard Mindset in Product Development]]></title>
            <link>https://medium.com/@byrnereese/the-skateboard-mindset-in-product-development-ddf3409d5e98?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddf3409d5e98</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 18:45:26 GMT</pubDate>
            <atom:updated>2017-08-04T18:45:26.731Z</atom:updated>
            <content:encoded><![CDATA[<p>By now the term MVP, or “minimum viable product,” is cliche in product circles, with most product and engineering teams buying into the notion that when building a new product or service, it is best to at first focus relentlessly and exclusively on the core idea of the product, or the smallest possible scope necessary to test that the core idea has value to others.</p><p>My perspective on MVPs has been shaped by a few key experiences as a Product Manager, and I have come to believe that what is more important than an MVP, is the mindset you cultivate on a team that leads to MVPs being a natural byproduct throughout your product development process.</p><h3>My first true MVP: ToyTalk</h3><p>When we were first getting started at ToyTalk (now <a href="https://www.pullstring.com/">Pullstring</a>), a company whose mission was to deliver Pixar-quality family entertainment in the form of AI-powered conversation, we had a prototype to prove we could pull it off, but it was a far from a shippable product by any measure. The product in fact was to this day the most ambitious technology challenge undertaken by a company I have ever worked for. Our vision for the product was an iPad app that would act as a kind of magic mirror. The app would use the iPad’s camera and facial recognition to identify a toy placed in front of it, listen with the microphone to the child speaking, and then offer a relevant and entertaining response to the child via the iPad’s speakers. We hired the best technical minds in the industry to begin building that product, and some of the best artists in the world to begin creating the content to fuel the experience.</p><p>It would take a year though before these two components would come together in a meaningful way, so our first challenge was to test that kids would even be entertained by such an experience. So I concocted an iPad stand that would hold two iPads. The first would be what the child was looking at, a scaled back version of the prototype we showed our first investors. The second iPad was placed behind the first, but offset from the first so that its camera could still see the child. The second iPad was connected via Skype to a computer upstairs, where our creative and writing team interacted with the child in real time, supported by nothing more than a few pre-written queue cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BuKIlfQvmHkSNne7Gl8dlA.jpeg" /><figcaption>ToyTalk MVP</figcaption></figure><p>This MVP allowed us to see how children were responding to what we were writing, and allowed us to simulate a number of different scenarios. For example, what might happen if we ignored the child? What would happen if we repeated ourselves over and over? We could really test the limits of the product experience — all before we actually had a fully functional product to put in front of a customer.</p><p>This is first hard lesson to learn about building MVPs: you don’t always need a product to validate an idea. In fact, if you become too focused on the “P” in MVP, you may end up wasting precious cycles building the wrong thing.</p><h3>Skateboards, not MVPs</h3><p>MVP’s are often closely associated with the launch a startup, or a new product or service. An MVP therefore is typically thought of as something you build once, and either continue to iterate upon and expand, or abandon — left to exist only in the company’s origin story as something you pivoted away from.</p><p>When done right however, an MVP is not a thing, it is a mindset. It is a product discipline in which one always asks themselves: is all this I have planned really necessary to test my idea with a customer? If done right, every feature, and every epic has an MVP; and you should endeavor to define this before you embark on building anything.</p><p>At <a href="http://www.buildingconnected.com/">BuildingConnected</a>, there is a great ethos around MVPs, but you will never hear people use the term. Instead, we always spoke of our “skateboard.” This was in reference to the image below which gained popularity among people like me in search of good images to accompany articles and presentations they are making about MVPs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXIr4rEoYwsTLuS2L1-UmQ.png" /></figure><p>A culture at BuildingConnected has been cultivated around this idea, and an environment created in which any designer, engineer or product manager can ask this fundamental question of any request being made of them: “what is the skateboard for this idea?” In so doing, it immediately reframes the discussion around finding the heart of a product request. It helps teams find the simpler version of any idea to start with, if it exists. Furthermore, it creates a culture in which the team is always in an MVP-mindset, better yet, the skateboard-mindset.</p><h3>Your North Star</h3><p>The skateboard-mindset however, if taken too far, runs the risk of sacrificing a larger vision in favor of always pursuing more tactical short-term decisions, or missing an opportunity to do something really innovative. Teams need to be given an opportunity for their Moon Shot — innovation that can only be achieved when someone creates a clear vision for what you are ultimately trying to accomplish, a more encompassing problem to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hzw_8X90Bl7PldKmE74DA.jpeg" /></figure><p>A good product manager does not dictate solutions to their team. They define the problem sufficiently and completely enough to enable their team to design and build a solution to the problem described.</p><p>The challenge for the product manager is in learning how to express the ideas that naturally occur when analyzing a problem without prescribing to the team what to build.</p><p>For the fictional car company behind the skateboard/automobile pictured above, that would most often come in the form of a concept car — a statement about what the future holds. Of course concept cars never get put into production, but they provide the design and engineering team a north star to guide them, and something to draw inspiration from.</p><p>Every product idea is rooted in a larger vision; and a good vision, like the North Star is not a destination, it is a direction.</p><h3>The Mindset</h3><p>Over the years, I have developed an aversion to the term “MVP.” Every word in the acronym seems problematic to me, and too often prone to debate. What is truly “minimal?” How much do you really need build to test an idea? What makes something “viable?” Does it need to functionally viable, or commercially viable, or both, or neither? And what is meant by “product” exactly? Even that, as shown by the ToyTalk example, isn’t always obvious.</p><p>What <em>is</em> important is always knowing at any given time what is the core of your idea. If you get that wrong, everything that follows it will be wrong as well.</p><p>If you approach every problem and every product request in this way, not just your initial product, then it is a lot easier to maintain confidence that your are on the right path, delivering value to customers, and fulfilling your product’s mission.</p><p><em>Byrne Reese is a product manager, maker and father. If you would like to talk to him about joining your team or company, email him at </em><a href="/service/mailto:byrne@majordojo.com"><em>byrne@majordojo.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddf3409d5e98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On depression: the lies we tell ourselves]]></title>
            <link>https://medium.com/@byrnereese/on-depression-the-lies-we-tell-ourselves-7f133e4aec6a?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f133e4aec6a</guid>
            <category><![CDATA[depression]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[personal]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Wed, 26 Jul 2017 21:52:23 GMT</pubDate>
            <atom:updated>2017-07-26T21:52:23.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8EcQFXCRfRuVfBJ_RYNuYA.png" /></figure><p>Last week I lost my job. I work in a do-or-die industry with a relatively brutal hiring and firing ethos — especially if startup founders are doing their job right. It is something I rationally understand and accept by choosing to pursue a career within it.</p><p>Despite departing on good terms with my former employer, this event caught me by surprise, and when combined with other factors in my personal life, not to mention the anxiety I now constantly feel for our country, and our planet, it was for me unbearable.</p><p>For the first time in my life I understood what depression feels like. I told my step-father this, a man who has struggled with depression for much of his life. When I told him of the darkness, of the powerful sense of self-doubt, and most of all the fear, he shared something with me that was profoundly meaningful to me.</p><blockquote>The voices in your head don’t tell the truth. They are determined to be heard, revered, awed; to get you to hear them at all times — to take them very seriously. They want to be looked upon as the voice of God. Nothing modest about them.</blockquote><blockquote>To achieve their goals they lie like crazy. They know you — have been around you a long, long time.</blockquote><blockquote>They know the lies you will buy, the ones you cannot dismiss — they know all your weaknesses and vulnerabilities, and they are going to work on you as only a great Pro can.</blockquote><blockquote>Remember they have your brain so finely tuned, and aware of all your knowledge and insight. They are going play the whole shebang against you.</blockquote><blockquote>They are going to lie to you as you’ve never been lied to before. It’s a crisis and they know how to savage you. This is their chance to take you over, to ground you down into fine nonexistence. To powder.</blockquote><blockquote>So you go into the immediate moment. The taste of a certain of ice cream. The power and glory of walking down the street holding the hands of Harper and Daisy. The awe your brain and its emotional system can pour into your entire being.</blockquote><blockquote>You have to keep repeating the obvious very simple truth: your inner voices are fucking liars big time.</blockquote><blockquote>Every time, you tell them that. And expect that they will up the ante. As I said before you’re up against incredible Pros. This is their time, the moment they’ve been praying and waiting so long for.</blockquote><blockquote>You have a beautiful mind. Now is the time to use it fully. Resist their lies, resist their bull shit. Every time. When they come forward with one more round of “truth,” shoot it down line by line, so called truth by truth.</blockquote><p>Since telling my step-father how I felt, and of the darkness that surrounded me, my friends and family have stepped up and offered tremendous support. Where once there was darkness, I see light.</p><p>I am lucky. I cannot imagine the challenge of dealing with depression long term, and it feels like a trite luxury for me to be able to say that. Almost as if I shouldn’t say anything at all lest I diminish in some way the struggle others have with depression.</p><p>But I found strength in my step father’s words, and through them I was able to punch through the veil of darkness to chart a path forward for myself. I share in the hope that his words may provide a similar strength to others.</p><p><em>From </em><a href="https://www.helpguide.org/articles/depression/depression-symptoms-and-warning-signs.htm"><em>HelpGuide.org</em></a><em>:<br>When you’re feeling depressed or suicidal, your problems don’t seem temporary — they seem overwhelming and permanent. But with time, you will feel better, especially if you get help. There are many people who want to support you during this difficult time, so please reach out!</em></p><p><strong><em>Read</em></strong><em> </em><a href="https://www.helpguide.org/articles/suicide-prevention/are-you-feeling-suicidal.htm"><strong><em>Suicide Help</em></strong></a><em> or call </em><strong><em>1–800–273-TALK </em></strong><em>in the U.S. or visit </em><a href="http://www.iasp.info/resources/Crisis_Centres/"><em>IASP</em></a><em> or </em><a href="http://www.suicide.org/international-suicide-hotlines.html"><em>Suicide.org</em></a><em> to find a helpline in your country.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f133e4aec6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Jedi Must End?]]></title>
            <link>https://medium.com/cinenation-show/the-jedi-must-end-1f79eaac8d0c?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f79eaac8d0c</guid>
            <category><![CDATA[film]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[the-last-jedi]]></category>
            <category><![CDATA[star-wars]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Fri, 14 Apr 2017 18:41:06 GMT</pubDate>
            <atom:updated>2017-04-17T02:31:44.690Z</atom:updated>
            <content:encoded><![CDATA[<h4>What does Episode VIII have in store for the Jedi?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLLI2zzWVBHEFaE0-UBcSg.jpeg" /></figure><p>If you are Star Wars fan, then there is no doubt you have already seen the teaser trailer for <em>The Last Jedi</em>. If you are like me than you may have it playing in the background right now on continual repeat, just taking it all in.</p><p>And you are also probably pondering, what could Luke possibly mean when he says, “I only know one truth, it is time for the Jedi to end.”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzB4I68XVPzQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzB4I68XVPzQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzB4I68XVPzQ%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/26879b1e8266e22c4e206f0a5a41a04f/href">https://medium.com/media/26879b1e8266e22c4e206f0a5a41a04f/href</a></iframe><p>Yes, it is just a movie, but it is a scary thought to consider that my childhood dream of becoming a Jedi might, after all these years, prove to be misguided in some way.</p><p>So, what could it mean? We have eight months to conjecture, starting now.</p><h3>The End of the Jedi</h3><p>Could the Jedi, in spite of being the guardians of peace in the galaxy, somehow be responsible for the very forces they have spent thousands of years fighting against? Could the very notion of two opposing forces, the Light and the Dark, perpetuate the divide that separates us all, and inevitably lead to conflict, pain and suffering?</p><p>A core theme of the Skywalker saga has always been about bringing balance to the Force, which has always conjured in my mind the image of a scale, tipping back and forth between the Light and the Dark. In the original trilogy, the scales tipped in favor of the Dark Side, with the Emperor and Darth Vader on one end, and essentially no one on the other. Until of course, Luke becomes a Jedi, and Darth Vader sacrifices himself to save his son and kill the Emperor. Many believe it is this moment that Anakin fulfilled his destiny as the Chosen One, and brought balance to the Force.</p><p>A more critical eye will observe however, that in that moment, the balance of power shifted from the Dark, to the Light. Balance, or a stable equilibrium, was never achieved. A vacuum of power was created, and the only thing that could establish balance, was an equal, but opposing force in the opposite direction. The seeds of Snoke, and the Knights of Ren were planted in that moment.</p><p>Perhaps it is our devotion to this ideal of balance, that locks us into a cycle of opposition, and the only way true balance can be achieved is to destroy the very scale that pits two opposing forces against each other.</p><p>The same theme exists in <em>Game of Thrones</em>, exemplified by when Daenerys tells Tyrion, that she is going to “break the wheel” — the never-ending struggle for power.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2X8Wb0f9-rY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2X8Wb0f9-rY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2X8Wb0f9-rY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c74ffd6c80afa9d180f6d8db46029218/href">https://medium.com/media/c74ffd6c80afa9d180f6d8db46029218/href</a></iframe><h3>An Allegory for Today</h3><p>What I like about this theory, is that it fulfills an important function of science fiction: to give humanity a mirror or lens through which it can safely view itself from a distance and achieve a more enlightened perspective.</p><p>We as a society are locked in a similar struggle. We are growing more polarized and opposed to one another everyday. It grows harder and harder to empathize with those that we disagree with, and easier and easier to see them as the enemy. The very notion of liberal vs conservative, Republican vs Democrat, capitalist vs socialist, all service one goal: to drive us further and further apart, rather than bringing us together.</p><p>And maybe, just maybe, Star Wars has more lessons it can teach us in this regard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QXYLo6X70kwm9TwzhY4bzA.png" /></figure><h4>Want more from CineNation?</h4><h4>Subscribe, Like, and Follow us on <a href="https://goo.gl/wfUCoK">iTunes</a>, <a href="https://goo.gl/FX1EhR">Facebook</a>, <a href="https://goo.gl/NfCMLI">Twitter</a>, and <a href="https://goo.gl/HLBHpm">Flipboard</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f79eaac8d0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinenation-show/the-jedi-must-end-1f79eaac8d0c">The Jedi Must End?</a> was originally published in <a href="https://medium.com/cinenation-show">CineNation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rogue One: a fan’s take.]]></title>
            <link>https://medium.com/cinenation-show/rogue-one-a-fans-take-7335ac02447b?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7335ac02447b</guid>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[film]]></category>
            <category><![CDATA[star-wars]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Sun, 18 Dec 2016 22:44:25 GMT</pubDate>
            <atom:updated>2016-12-20T03:02:42.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPcXUFm2ErzPsZvutprA8A.jpeg" /></figure><p><strong><em>Spoiler Warning: I am about to ruin this movie for you.</em></strong></p><p><em>Rogue One</em> is finally out, and Disney has finally broken the seal on producing a live action film outside of the core Skywalker saga. Like <em>The Force Awakens</em>, my initial reaction to the film was complicated and conflicted. It took me five viewings of <em>The Phantom Menace </em>for example to finally admit to myself what I knew in my heart all along: that was a really bad movie. After seeing <em>The Force Awakens</em> I didn’t want to make the same mistake: did I like this because it is a good movie, or simply because it is Star Wars? So I was very critical of the film. But was I over compensating in my critique to account for my clear Star Wars bias?</p><p>I felt the same way after seeing Rogue One. I have seen the movie twice now, and have calmed down from the initial excitement of it all, and I think I can finally speak relatively soberly about the movie. And I say “relatively” because at the end of the day I am a fan, and it is hard for me to treat Star Wars just like any other movie. So consider this a fan&#39;s review for fellow fans.</p><h3><strong>A gift to every Star Wars fan</strong></h3><p>What is exciting about this movie at its core, is that it takes us back to the movie that started it all, and makes <em>A New Hope</em>, and arguably the entire original trilogy a richer movie experience in the process. And that is saying something, because <em>A New Hope</em> is iconic to nearly biblical proportions — not just cinematically, but on a deeply personal level for me and so many Star Wars fans of my generation.</p><p>As a result, the stakes couldn’t be higher for this film; a lot could have gone wrong, especially in light of the re-shoots that took place late in the game and the resulting rumors about the integrity of the story. Now that the movie is out, we finally have some sense for the <a href="http://screenrant.com/star-wars-rogue-one-reshoots-changes/">scale of these reshoots</a> and the legitimacy of people’s initial worry, but I think it is safe to say that any anxiety people may had can be put aside. <em>Rogue One</em> works.</p><blockquote><em>Rogue One</em> was a gift to Star Wars fans not just because it lets us revisit so many of our favorite, characters, but because it made Star Wars: A New Hope a better movie in the process.</blockquote><p>The best thing I can say is that <em>Rogue One </em>delivers so much delight for fans without ever being heavy handed about it. It is chock-a-block full of moments that had me pulling on the sleeve of the friend sitting next to me and, whispering, “yeeeees” — from brushing past Dr. Cornelius Evazan, who you may remember as the man Obi Wan cuts down in the Mos Eisley cantina, the paging of General Syndulla on Yavin 4 along with multiple sightings of her ship <em>Ghost</em> from the Star Wars Rebels TV series, to the familiar <a href="http://io9.gizmodo.com/heres-how-rogue-one-got-its-hands-on-unseen-star-wars-f-1790250545">appearances of Gold Leader and Red Leader</a>, to Bail Organa, and of course R2D2 and C3P0.</p><p>And those were just the cameos. There were a number of other notable appearances by major characters as well that no one anticipated. Going into the film, I assumed that these characters would have to have been cleverly edited out or around given that many of the original actors have died, or would obviously have been too old to reprise their role. Then there was that moment when I saw the back of Grand Moff Tarkin’s head and I thought to myself, “I wonder who did they got to play Tarkin?” And then, he turns around and you see Peter Cushing in all his glory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*G8cEPK6L2g6rxv3njwKb0g.jpeg" /></figure><p>In that moment early in the film, I got the immediate sense that this film was going to integrate itself into the core epic in a number of surprising ways. Plus, having virtually resurrected an actor from the dead to reprise a role, I knew then that <em>Rogue One</em> might very well be remembered for having changed filmmaking as we know it.</p><h3>A [better] New Hope</h3><p><em>Rogue One</em> was a gift to Star Wars fans not just because it lets us revisit and experience so many of our favorite, albeit small, characters, but because in some ways it made <em>Star Wars: A New Hope</em> a better movie in the process.</p><h4>The closing of a gigantic whomp rat-sized plot hole</h4><p>Long on the list of palm-to-forehead gripes I have with Star Wars is the gigantic plot hole with how the Death Star was destroyed. The idea, that something so massive, and took so many resources to build could be engineered to have a weakness so absolutely and devastatingly obvious defied all logic. The ease with which a single torpedo blew up the entire Death Star weakened the original film by revealing an amateurish quality to A New Hope’s writing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FagcRwGDKulw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DagcRwGDKulw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FagcRwGDKulw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c0300187e9b49aa590cacd807c3d0dc/href">https://medium.com/media/1c0300187e9b49aa590cacd807c3d0dc/href</a></iframe><p><em>Enter Rogue One</em>. In a couple simple lines of dialogue, the ridiculousness of it all is not just excused, it is completely justified. The weakness was not an oversight of the Empire, or even the result of a poor screenplay, it was purposeful — it was an act of sabotage. Of rebellion, fifteen years in the making.</p><h4>Vader is a bad ass</h4><p>Also on that list of gripes was the fact that the ultimate battle between Vader and Obi Wan was so absolutely flaccid; a fact that was only amplified by the prequels and <em>The Clone Wars </em>in which both Anakin and Obi Wan were portrayed as true masters of their craft. As fans we made excuses like, “well Vader and Obi Wan are older in <em>A New Hope</em>,” to cover up the fact that Lucas made a really lame fight scene.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*1JuKIsA9DPZoLcESZJvniw.gif" /></figure><p>When you think about it: at no point in the original trilogy do we see Vader really show that he is a force to be reckoned with beyond his ability to force choke a few people.</p><p>And then you see the end of <em>Rogue One</em>, and Vader, for the first time he is not only menacing, he is terrifying in his brutality. He is someone to truly fear.</p><h4>Red Shirts no more</h4><p><em>Rogue One</em> takes many of the characters that existed in the background of the original trilogy and gave them a greater depth, and purpose. It gave the audience an appreciation for these relative disposable characters as people who each had their own story, and their own reason to fight. It made me appreciate that all the people in the background on Yavin 4 in A<em> New Hope</em> are people who had, as recently as a couple days ago, lost friends, and as people who have been fighting this war for a long time. It gave all of these characters a little more depth, and their sacrifice more gravity.</p><h3>A different kind of Star Wars</h3><p>I do not envy the challenge Gareth Edwards must have had in making this film. As the first director to create a live-action movie outside the core Skywalker saga, he was setting a lot of precedents. He needed to decide exactly how to break with long established conventions fans love so that he could help define what makes a “Star Wars Story” different from the core epic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*5U6bBnQJJ6RcgfuE4vAIyA.gif" /></figure><p>Gone for example is the opening crawl. The Star Wars theme music is also missing. The typefaces are different. Planets and locations on screen are labeled with text. They even abandoned the iconic wipe transition effect between shots. These may seem small and inconsequential, but as a fan, they preoccupied me, and acted as a kind of subconscious speed bump — pulling me out of the action for a film for a second.</p><p>This is the first of many non-Skywalker Star Wars stories, and I expect each of these movies to push the boundaries of the Star Wars movie template, and strive to differentiate itself from the others. And this is a good thing. <em>Rogue One</em>, however, being the first to break from tradition, has the highest toll to pay in this regard.</p><h4>A two hour prologue</h4><p>What is ultimately disappointing about the film is that it didn’t expand the scope of the Star Wars universe in the ways that the films of the original trilogy, and <em>The Force Awakens</em> did. Those films, in an almost Tolkein-esque way, has these relatively inconsequential lines that teased at larger stories that want to be told. They each left audiences with questions like, what were the Clone Wars? What happened to Han and the bounty hunter on Ord Mantell? Why is there still a Resistance, even though the Rebellion won the war?</p><p>There is almost none of that mystery in Rogue One. It was a movie designed to be fully self-contained. Its boundaries were set, and there was to be no venturing outside them, now or in the future. In this way, <em>Rogue</em> <em>One </em>is little more than a two-hour prologue to <em>A New Hope</em>.</p><h3>In short: a good Star Wars story.</h3><p>For now <em>Rogue One</em> will probably rank relatively high amongst Star Wars fans — older and younger generations alike. While the movie, on its own lacks the mythos and grandeur of the original trilogy, it is now hard to imagine how one could watch <em>A New Hope</em> without watching this one first. Because what I feel is the movie’s greatest weakness, that it is just a well told prologue is ironically also its greatest strength: it brings greater weight and significance to the movie designed to follow it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QXYLo6X70kwm9TwzhY4bzA.png" /></figure><h4>Want more from CineNation?</h4><h4>Subscribe, Like, and Follow us on <a href="https://itunes.apple.com/us/podcast/cinenation/id937849089?mt=2">iTunes</a>, <a href="https://www.facebook.com/cinenation/">Facebook</a>, <a href="https://twitter.com/cinenationshow">Twitter</a>, &amp; <a href="https://flipboard.com/@hunterbarcroft/cinenation-e37vnidbz">Flipboard</a>!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7335ac02447b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinenation-show/rogue-one-a-fans-take-7335ac02447b">Rogue One: a fan’s take.</a> was originally published in <a href="https://medium.com/cinenation-show">CineNation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Internet of Blockchains]]></title>
            <link>https://medium.com/@byrnereese/an-internet-of-blockchains-70eb1c547483?source=rss-4230127057b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/70eb1c547483</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Byrne Reese]]></dc:creator>
            <pubDate>Tue, 18 Oct 2016 17:05:04 GMT</pubDate>
            <atom:updated>2016-10-18T17:05:04.386Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post was originally published in May 2014, and is being republished as I move past content to Medium. I think this remains a relevant in so far as it discusses how major technological paradigm shifts are adopted by users, even though two and half years later, bitcoin (the currency) remains in the same spot: unknown to most. It also foretells of what is common knowledge today, that it is not the currency that will ultimately be the most influential, but the underlying technology of the blockchain.</em></p><p>The blockchain is a hard concept to wrap one’s head around because it describes a system for which no analog exists today, and it runs counter to everything we know about how trust works. In today’s world, trust can only be assigned or transmitted by an individual or organization. The idea that one could safely send money from point A to point B, and have that transaction facilitated by potentially millions of agents without you knowing who those agents are, what motives they might have vis-a-vis your money, whether they are nefarious or not, is an anathema. But that is exactly what the blockchain helps enable.</p><p>With the blockchain, trust stems not from the reputation of an actor or collection of actors, or from a process or set of controls that abstracts power and authority away from individuals. Nor does trust get transmitted through a graph of friends, or from an external auditor who can vouch for a claim. Instead, we place trust in a design pattern.</p><p>But what does that mean, to trust in a design pattern? To answer that, let’s look at another decentralized system we have all grown to trust so much that it has transcended the need for trust entirely, and just <em>is</em>: the Internet. The Internet has no governing body or centralized authority. There is no mastermind responsible for making sure some secret collection of computers are plugged in and working. There is no facility that if compromised could “take down the Internet.” No, the Internet works because of a design pattern that dictates that data should move the same way between networks, as it does within networks. So if a network wants to take advantage of the access and opportunity afforded by the Internet, all it has to do is connect, and in so doing it begins contributing it’s own resources to the benefit of the whole, further decentralizing it, making it faster, and making it more resilient.</p><p>We take all of this for granted without knowing how this system works. But if you look back to your own history, assuming you were around when the Internet had it’s tipping point, I bet you will find a moment where you had to take a leap of faith. A moment when you had to drop AOL for a generic Internet Service Provider who provided no information services of their own. Of course, the later you made this leap of faith the easier the choice was to make because you were entering an increasingly useful and utilitarian landscape of services — companies like CNet, Excite, Yahoo!, Excite, and others. And the more companies that began building their businesses on top of this infrastructure, the less and less people cared about the fundamentals of how it worked. The proof was in the pudding.</p><p>The blockchain today is operating in a time not that dissimilar to the Internet in the 1990’s. Consumers are baffled and confused by how a decentralized finance system could even function, while a growing number of people led by technologists, futurists and entrepreneurs see the potential for ideas and companies that heretofore had been impossible due to the economics of a centralized system. But slowly, as more and more people take their own personal leap of faith, more and more people will stop caring about how it works, and just accept that it does. By then we will no longer be talking about “a blockchain,” but rather an Internet of Blockchains. And no longer will our computers simply connect to the Internet, they will contribute their computing cycles to an untold number of micro-economies that will power far more than even they are aware of.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70eb1c547483" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>