<?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[DevRev - Medium]]></title>
        <description><![CDATA[We built Computer, the only AI with native “shared memory”. So you get answers &amp; actions you can really trust. - Medium]]></description>
        <link>https://medium.com/devrev?source=rss----a185accbab1d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>DevRev - Medium</title>
            <link>https://medium.com/devrev?source=rss----a185accbab1d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:18:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/devrev" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Three key use cases of Product-led (PLG) companies]]></title>
            <link>https://medium.com/devrev/three-key-use-cases-of-product-led-plg-companies-7e5887b84e32?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e5887b84e32</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[plg]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[crm]]></category>
            <dc:creator><![CDATA[Madhukar Kumar]]></dc:creator>
            <pubDate>Mon, 27 Jun 2022 18:39:46 GMT</pubDate>
            <atom:updated>2022-06-27T18:39:46.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0gUpRpBGC9EyLK21lHNzw.jpeg" /></figure><p>At DevRev, we believe that any business can adhere to some essential principles to become a PLG or product-led company. We understand that there are several technologies and tools that companies today have adopted to become product-led. These apps and tools are typically stitched together with bespoke work that gets incredibly expensive and complex to manage over time. Our vision and mission are to build an operating system for PLG to help these companies become product-led more efficiently and simply. We call this PLG operating system (OS) the Developer Customer Relationship Management platform, or Dev CRM for short.</p><p>A typical company focused on building a digital product, a product driven by code, can be divided into two main groups of people and processes working in cohorts — front office and back office. The front office typically consists of efforts and workflows aimed at acquiring new customers, supporting them, and getting them to renew their subscriptions periodically. The back office, on the other hand… <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/three-use-cases-of-plg-companies"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e5887b84e32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/three-key-use-cases-of-product-led-plg-companies-7e5887b84e32">Three key use cases of Product-led (PLG) companies</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learnings from using GitHub templates at DevRev]]></title>
            <link>https://medium.com/devrev/learnings-from-using-github-templates-at-devrev-7f254b846b86?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f254b846b86</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Shivansh Rai]]></dc:creator>
            <pubDate>Mon, 28 Mar 2022 16:24:09 GMT</pubDate>
            <atom:updated>2022-03-29T09:32:14.846Z</atom:updated>
            <content:encoded><![CDATA[<h3>Learnings from using GitHub template repositories at DevRev</h3><p>By <a href="https://shivansh-rai.medium.com/">Shivansh Rai</a> and <a href="https://prabath.medium.com/">Prabath Siriwardena</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bNPlx4hBsA7RV2xt_qT5Lw.jpeg" /></figure><p>At <a href="https://devrev.ai/">DevRev</a>, we use a GitHub template repository as the basis for almost all the projects within the organization. It contains deployment configurations and boilerplate code for building gRPC services. This template repository generates new repositories with the same directory structure, branches, and files. However, GitHub doesn’t preserve commit history in new repositories and squashes all commits from the template into one. This proves problematic when propagating changes from the template to its generated repository as git pull¹ no longer works.</p><p>We occasionally upgrade the template repository’s dependency versions to include new features and bug fixes. Unfortunately, these version changes had to be propagated manually to downstream repositories, which was tedious and error-prone. As a result, our engineers tended to ignore these chores leading to a lag between dependency versions of the template and its generated repositories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RR5-P1U00QwYwJn4" /><figcaption>Image by<a href="https://unsplash.com/@synkevych?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"> Roman Synkevych</a> on<a href="https://unsplash.com/s/photos/github?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"> Unsplash</a></figcaption></figure><h3>Why git doesn’t work</h3><p>git allows comparing files in different repositories and evaluating their diff. Let’s consider the task of synchronizing go.mod files between a template and its generated repository. Go’s dependency management system uses go.mod² files for managing dependency version information.</p><p>For simplicity, this blog post will use the following terminologies -</p><ul><li><em>upstream</em> as the template repository</li><li><em>downstream </em>as the repository generated using the template repository</li><li><em>diff</em> as the output of git diff</li><li><em>cloning</em> as the process of generating a repository out of a template repository</li></ul><p>The files upstream/go.mod and downstream/go.mod belong to the upstream and downstream, respectively. They contain the dependency version information of the respective version-controlled Go projects upstream and downstream.</p><pre>$ cat upstream/go.mod<br>module upstream</pre><pre>go 1.17</pre><pre>require go.uber.org/zap v1.21.0 // upgraded after cloning</pre><pre>$ cat downstream/go.mod<br>module downstream</pre><pre>go 1.17</pre><pre>require (<br>        github.com/google/go-cmp v0.5.7 // added after cloning<br>        go.uber.org/zap v1.20.0<br>)</pre><p>The minor version³ of the dependency go.uber.org/zap was upgraded from v1.20.0 to v1.21.0 in upstream after cloning downstream, causing it to be missing from downstream/go.mod. Also, we added the dependency github.com/google/go-cmp to downstream after cloning it.</p><p>Since these go.mod files belong to different repositories, we will use git diff --no-index⁴ to evaluate their diff -</p><pre>$ git diff --no-index downstream/go.mod upstream/go.mod | tee diff.patch</pre><pre>diff --git a/downstream/go.mod b/upstream/go.mod<br>index 6b7d801..ca017e7 100644<br>--- a/downstream/go.mod<br>+++ b/upstream/go.mod<br>@@ -1,8 +1,5 @@<br>-module downstream<br>+module upstream</pre><pre>go 1.17</pre><pre>-require (<br>-       github.com/google/go-cmp v0.5.7 // added after cloning<br>-       go.uber.org/zap v1.20.0<br>-)<br>+require go.uber.org/zap v1.21.0 // upgraded after cloning</pre><p>We switch the working directory to downstream before applying⁵ the patch so that we’re in the working tree controlled by git -</p><pre>$ mv diff.patch downstream<br>$ pushd downstream<br>$ git apply -p2 diff.patch<br>$ popd</pre><pre>$ cat downstream/go.mod<br>module upstream</pre><pre>go 1.17</pre><pre>require go.uber.org/zap v1.21.0 // upgraded after cloning</pre><p>The final state of downstream/go.mod is the result of the following modifications -</p><ol><li>The module name is modified to upstream.</li><li>The version of the dependency go.uber.org/zap is upgraded to v1.21.0.</li><li>The dependency github.com/google/go-cmp, which was introduced downstream after cloning, is lost.</li></ol><p>Modifications 1 and 3 are invalid.</p><p>The above strategy would’ve been ideal if modifications were never introduced downstream after cloning. However, practically this is not the case, and applying the diff will overwrite all such changes.</p><p>In this example, we intentionally did not use go get -u to manipulate dependency versions of downstream as we wanted to propagate these version changes from upstream.</p><p>The shortcomings of this approach give an idea of the challenges to be dealt with, described below -</p><ol><li>New rules introduced downstream after cloning should be preserved.</li><li>We cannot consider all upstream changes valid and should analyze them before applying.</li><li>We need to preserve modifications introduced downstream after cloning, but not always. For example, if a user manually upgraded the downstream dependency version to v0.0.2, but the same dependency in upstream points at v0.0.3 later, we should upgrade the downstream version regardless the user modified it after cloning.</li><li>The overall diff size should be minimal to allow easy code reviews.</li></ol><h3>AST to the rescue</h3><p>Let’s consider Bazel⁶, a common build tool used extensively at DevRev. Bazel uses WORKSPACE⁷ files for managing external dependency versions. We can translate the problem at hand to these files.</p><p>The buildtools⁸ project by Bazel provides a parser for converting a Bazel file into an Abstract syntax tree⁹ (AST), a sequence of nodes representing Bazel expressions and statements. The Wagner-Fischer algorithm¹⁰ allows us to compute the edit distance between upstream and downstream ASTs. So, instead of dealing with a string of characters, as is usually the case, we deal with an array of AST nodes. However, the AST nodes need to be comparable for the algorithm to work. As we’ll see later, this happens to be true.</p><p>After calculating the edit distance, we can utilize the 2-D matrix used for the same to evaluate the shortest transformation sequence. The <a href="https://en.wikipedia.org/wiki/Wagner%E2%80%93Fischer_algorithm#Calculating_distance">(hoverable) examples</a> in the Wikipedia page demonstrate this process.</p><p>A single AST node will carry the following contextual information about the Bazel rule, which will turn out helpful -</p><ul><li>name of the rule</li><li>fields of the rule</li><li>the span of the rule (starting and ending line numbers)</li></ul><p>The shortest transformation sequence for converting downstream AST to upstream AST will be of the following form -<br>d₁, <strong>-d₂</strong>, d₃, <strong>+u₁</strong>, d₄, <strong>+u₂</strong>, d₅, <strong>-d₆</strong> …</p><p>where dᵢ and uⱼ are downstream and upstream AST nodes, respectively. As noted previously, this transformation sequence needs to be processed further.</p><p>Assuming … represents a sequence of unchanged downstream nodes, we can generalize the transformation sequence under the following cases -</p><ol><li><strong>-dᵢ</strong>, …<br>implies that dᵢ is dropped from downstream</li><li><strong>+uᵢ</strong>, …<br>implies that uᵢ from upstream is added to downstream</li><li><strong>-dᵢ</strong>, …, <strong>+uⱼ<br></strong>implies that uⱼ from upstream replaced dᵢ from downstream. If dᵢ and uⱼ correspond to the same Bazel rule, an equivalent rearranged transformation sequence which reduces diff size is - …, (<strong>-dᵢ, +uⱼ</strong>), …</li><li><strong>+uᵢ</strong>, …, <strong>-dⱼ<br></strong>implies that uᵢ from upstream replaced dⱼ from downstream. If uᵢ and dⱼ correspond to the same Bazel rule, an equivalent rearranged transformation sequence which reduces diff size is - …, (<strong>+uᵢ, -dⱼ</strong>), …</li></ol><p>Cases 3 and 4 allow rearranging the transformation sequence to reduce the diff size. So instead of getting two separate entries in the diff (one for deletion and addition each), we get a single entry for modification. We will only rearrange if d₂ and u₁ (similarly u₂ and d₆) correspond to the same Bazel rule. The diff size will reduce because the same constituent fields among the rules (like name) will not contribute to the diff, allowing easier code reviews.</p><p>We can retrieve the Bazel rule name from the AST node and use it to ignore modifications to rules that aren’t supposed to be modified, such as workspace(name = &quot;foo&quot;).</p><p>We need to preserve the user-introduced downstream nodes. The AST node contains the line numbers it spans, which we can use with git blame to derive whether the node was introduced downstream after cloning.</p><h4>Comparing AST nodes</h4><p>We can compare AST nodes based on whether they belong to different Bazel rules and use the name field to compare the nodes belonging to the same rule. For example, the expressions below belong to the same rule http_archive but contain different name fields.</p><pre>http_archive(<br>    name = &quot;com_google_protobuf&quot;,<br>    sha256 = &quot;1c11b325e9fbb655895e8fe9843479337d50dd0be56a41737cbb9aede5e9ffa0&quot;,<br>    strip_prefix = &quot;protobuf-3.15.3&quot;,<br>    urls = [&quot;<a href="https://github.com/protocolbuffers/protobuf/archive/v3.15.3.zip">https://github.com/protocolbuffers/protobuf/archive/v3.15.3.zip</a>&quot;],<br>)</pre><pre>http_archive(<br>    name = &quot;golink&quot;,<br>    sha256 = &quot;ea728cfc9cb6e2ae024e1d5fbff185224592bbd4dad6516f3cc96d5155b69f0d&quot;,<br>    strip_prefix = &quot;golink-1.0.0&quot;,<br>    urls = [&quot;<a href="https://github.com/nikunjy/golink/archive/v1.0.0.tar.gz">https://github.com/nikunjy/golink/archive/v1.0.0.tar.gz</a>&quot;],<br>)</pre><h4>Diff validation</h4><p>While synchronizing, old dependency versions from upstream should not overwrite new versions from downstream. When we encounter a node modification in the transformation sequence, we extract the semver from the urls field and use it for comparison. The upstream change is accepted if it promotes the dependency version.</p><p>A few things to be kept in mind while using this validation strategy -</p><ul><li>Not all dependencies follow semantic versioning in their URLs</li><li>A particular rule can have multiple entries in the urls field</li></ul><h3>Architecture</h3><p>We can break the process of evaluating diffs and publishing them into the following three phases -</p><ul><li>Retrieving data from upstream and downstream (crawling)</li><li>Processing the data (parsing)</li><li>Propagating the changes to downstream (publishing)</li></ul><p>The components below describe these phases and are designed to be extensible and pluggable. So, for example, we can use turbolift¹¹ for the publishing phase.</p><h4>Crawler</h4><p>The tool accepts a YAML¹² configuration file, described below -</p><pre>author_name: devrevbot<br>author_email: <a href="/service/mailto:bot@devrev.ai">bot@devrev.ai</a><br>commit_message: &quot;chore: sync with upstream template repository&quot;<br>org: devrev<br># Personal access token with scopes: [&#39;repo:all&#39;], [&#39;read:org&#39;]<br>token:</pre><pre># Entries under allowlist are taken into consideration and PRs<br># sent for those. PRs are not sent for entries under blocklist.<br># allowlist and blocklist are considered iff onlylist is empty.<br># Otherwise, PRs are created only for entries under onlylist.<br>templaterepos:<br>  - name: upstream-template<br>    allowlist:<br>    blocklist:<br>      - downstream-repo<br>    onlylist:</pre><p>The crawler reads the configuration file and uses GitHub API to find the repositories generated by the provided templates. Then, it clones the downstream repositories to allow running git blame. Finally, the crawler provides the downstream Bazel files and their upstream counterparts to the parser.</p><h4>Parser</h4><p>The parser implements the AST-based approach described above and evaluates the final state of the downstream file, which is provided to the publisher.</p><h4>Publisher</h4><p>The publisher prepares a patch from the file received by the parser and uses GitHub API to create a downstream pull request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CTJPeY_kc9203hdS-cJPBw.png" /><figcaption>High-level architecture</figcaption></figure><h3>Results</h3><p>We ran the tool on our internal projects to synchronize WORKSPACE files across upstream and downstream. We noticed that the tool introduced a few incorrect modifications by rolling back the dependency versions of downstream, whose semver was not easy to extract from the urls field. We identified these errors easily during code reviews. However, the tool could pull in all the new modifications from upstream. These modifications would otherwise have been tedious and error-prone to propagate manually.</p><h3>Conclusion</h3><p>This blog post described an algorithm for synchronizing WORKSPACE Bazel files between a template and its generated repositories. The algorithm is not limited to Bazel and will work for any file for which ASTs can be generated. We reduced the scope for human-introduced errors while boiling down the entire process to a single command-line invocation.</p><p>[1]: <a href="https://git-scm.com/docs/git-pull">git-pull Documentation</a></p><p>[2]: <a href="https://go.dev/blog/using-go-modules">Using Go Modules — The Go Programming Language</a></p><p>[3]: <a href="https://semver.org/">Semantic Versioning</a></p><p>[4]: <a href="https://git-scm.com/docs/git-diff">git-diff Documentation</a></p><p>[5]: <a href="https://git-scm.com/docs/git-apply">git-apply Documentation</a></p><p>[6]: <a href="https://bazel.build/">Bazel</a></p><p>[7]: <a href="https://docs.bazel.build/versions/main/external.html">External dependencies — Bazel main</a></p><p>[8]: <a href="https://github.com/bazelbuild/buildtools">GitHub — bazelbuild/buildtools: A bazel BUILD file formatter and editor</a></p><p>[9]: <a href="https://en.wikipedia.org/wiki/Abstract_syntax_tree">Abstract syntax tree — Wikipedia</a></p><p>[10]: <a href="https://en.wikipedia.org/wiki/Wagner%E2%80%93Fischer_algorithm">Wagner–Fischer algorithm — Wikipedia</a></p><p>[11]: <a href="https://github.com/Skyscanner/turbolift">Skyscanner/turbolift: A simple tool to help apply changes across many GitHub repositories simultaneously</a></p><p>[12]: <a href="https://yaml.org/">YAML.org</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f254b846b86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/learnings-from-using-github-templates-at-devrev-7f254b846b86">Learnings from using GitHub templates at DevRev</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Six ways you can use GitHub data to stop the meeting madness]]></title>
            <link>https://medium.com/devrev/six-ways-you-can-use-github-data-to-stop-the-meeting-madness-639d0426676c?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/639d0426676c</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[devrev]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Bhavana Thudi]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 14:43:36 GMT</pubDate>
            <atom:updated>2022-06-13T20:22:19.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_89v589T7QN0DQe4HR3dhA.png" /></figure><p>I love meeting people, don’t get me wrong. Especially as things open up, I cherish every connection and conversation more than ever before. Simple things like meeting for coffee, taking a stroll, and a good old fashioned phone call are the highlights of my day. This article is not about these kinds of meetings. Rather, meetings that are useless, especially when they can be automated by machines. Join our mission to end useless meetings… <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/six-ways-you-can-use-git-hub-data-to-stop-the-meeting-madness"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=639d0426676c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/six-ways-you-can-use-github-data-to-stop-the-meeting-madness-639d0426676c">Six ways you can use GitHub data to stop the meeting madness</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 software development principles that power a Dev CRM]]></title>
            <link>https://medium.com/devrev/10-software-development-principles-that-power-a-dev-crm-2da19e874f03?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/2da19e874f03</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Anindya Misra]]></dc:creator>
            <pubDate>Sat, 26 Feb 2022 00:40:55 GMT</pubDate>
            <atom:updated>2022-06-13T20:22:34.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DevRev Illustration" src="https://cdn-images-1.medium.com/max/600/0*EmzO1eKdWWquvFmC" /></figure><p>SaaS coupled with free pricing options has created a market for developers where they can quickly iterate with customers through their code to create apps at the speed of light. All you need is GitHub for your code, Slack for collaboration, and AWS to host your service. These intuitive developer first tools have enabled thousands of startups to reach millions of people across the globe with their new ideas. An engineer with the right APIs can build features and integrations which previously required several project teams to execute for years. And imagine if you have a thriving community of customers and developers who are collectively building your product- the possibilities of a customer-led product development are limitless… <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/10-software-development-principles-that-power-a-dev-crm"><strong><em>here.</em></strong></a><strong><em> </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2da19e874f03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/10-software-development-principles-that-power-a-dev-crm-2da19e874f03">10 software development principles that power a Dev CRM</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub with DevRev, Creativity at its Best]]></title>
            <link>https://medium.com/devrev/github-with-devrev-creativity-at-its-best-5fc4fe1d2acc?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/5fc4fe1d2acc</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[devrev]]></category>
            <category><![CDATA[devcrm]]></category>
            <dc:creator><![CDATA[Bhavana Thudi]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 20:55:03 GMT</pubDate>
            <atom:updated>2022-06-13T20:01:45.207Z</atom:updated>
            <content:encoded><![CDATA[<h3>GitHub with DevRev, creativity at its best</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*v7vOQXgR1tg8yJbvfZpOgg.jpeg" /></figure><p>She brought a whole new meaning to living in harmony with nature. Following ancient tradition and making the most of each season’s givings, she grew her own food, crafted furniture, dyed clothes, and redefined ‘from scratch’. She mastered the art of sustainable living and brought her stories to millions around the world. She made everything and could be anyone — a chef, an engineer, a farmer, a carpenter, a gardener, and a creator.</p><p>As I watched <a href="https://www.youtube.com/channel/UCoC47do520os_4DBMEFGg4A">Li Ziqi</a> over the years, experiencing an ideal lifestyle with nature in the deep countryside of rural Sichuan, I appreciated The Simple Life, and found peace and greatness. She bolsters my belief that the individual, as a creator, holds more power than any time in the past. The rise of the individual is real…<em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/git-hub-with-dev-rev-creativity-at-its-best"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fc4fe1d2acc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/github-with-devrev-creativity-at-its-best-5fc4fe1d2acc">GitHub with DevRev, Creativity at its Best</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eight things I learned in eight months as an engineer at a tech startup]]></title>
            <link>https://medium.com/devrev/eight-things-i-learned-in-eight-months-as-an-engineer-at-a-tech-startup-ed4217a955c2?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed4217a955c2</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[devrev]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[violex]]></dc:creator>
            <pubDate>Tue, 25 Jan 2022 18:41:49 GMT</pubDate>
            <atom:updated>2023-03-13T15:20:04.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kxaKbi_nBR9tqf9-DywtQ.jpeg" /></figure><p>8 is a lucky number in Chinese; It’s pronounced [bah] which sounds like the character for generating wealth [fah]. While my first 8 months at DevRev have not yet generated wealth in the traditional sense ($$$), it has generated wealth in other ways. And since I figured it was finally time to stop saying I would write and start actually writing, here are the top 8 things that have generated the most “wealth” for me in the last 8 months at DevRev.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bxGzYwzOVv0hQago" /><figcaption>The characters for “eight” and “generate wealth”</figcaption></figure><p><strong>1. Read and comprehend</strong></p><p>Yeah, I know, super basic, but I couldn’t exclude it.</p><p>Growing up, I was one of those kids that would go to the library once a week, check out 8–10 books, read them, then return the books and repeat the process the next week. Unfortunately, by the time I got to high school, I read a lot less and my tolerance for reading long periods of time dropped. Towards the end of my college career, I decided to pick up reading again. While I found that my reading speed was still quick, my comprehension skills were abysmal; I often had to reread text once or twice before truly understanding it.</p><p>You might be thinking “But Violex, you’re a software engineer. Why do you even need to read? Just write your code.”, which is a fair enough argument. However, all the best software engineers I know have high reading comprehension skills and tend to be avid readers as well. Think about it: while writing code is integral to my job, I can’t do that well if I don’t understand the codebase first. Writing code without understanding the existing codebase is like trying to put in a puzzle piece blind; you don’t even know if your piece is part of the puzzle, let alone what it looks like in the grand scheme of things.</p><p>In addition to reading the codebase (or at least some of it), reading comprehension also comes in when doing code reviews. Since I am in my early career, I’m not requested to review that much code, but every time that I am, I find that the more I work towards reading and comprehension, the quicker and more pain-free the process is. By working on reading comprehension, I’ve been able to do my job more and more efficiently.</p><p><strong>2. Build solid habits</strong></p><p>When I was in college, my life was in disarray; I would sleep at odd hours, exercise sporadically, and nothing about my lifestyle ever seemed consistent. While it worked for me at that point in my life, after I started at DevRev, I realized that I seriously needed to establish solid habits because the effects of my habits were no longer isolated to me. Having solid habits is the foundation of having a healthy and productive lifestyle.</p><p>While there is certainly no one-size-fits-all in terms of habits, I’ve found that establishing habits around integral parts of my existence (sleeping, eating, and exercising) has not only improved my quality of life but has also made establishing more complex habits easier. I’ve learned a lot of what I practice from various books but the one I recommend the most is James Clear’s Atomic Habits. Clear clearly (haha) breaks down how to establish habits and build them up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hkNhfvU_DuEzSKtF" /><figcaption>Image credit James Clear, author of Atomic Habits</figcaption></figure><p>If I could offer one piece of advice though, it would be to <strong>never skip habits twice in a row</strong>. Nobody is perfect, certainly not me, so having days of skipped habits is going to happen. However, if I skip a habit, like working out, two days in a row, I’m far more likely to continue skipping it, which builds up a habit of not exercising. Technically, everything and anything can be considered a habit, as long as you do it <strong>consistently.</strong></p><p><strong>3. Put everything in your calendar</strong></p><p>Yes, everything. While you don’t need to tell your coworkers you are getting a colonoscopy between 2 pm and 4 pm next Tuesday, you should at least block it out with an event titled “busy” in your calendar to signal that you are busy. I even put personal events that occur outside of 9–5 in my calendar. Because <a href="https://devrev.ai/">DevRev</a> is a global company, blocking out time for personal things is sometimes necessary as my personal time may be another person’s working time.</p><p>Another trick I’ve found to be useful is to set up working hours. As much as I love my job and coworkers, I refuse to have meetings before 8 am and after 8 pm and working hours lets my colleagues know when I am officially on and off the clock. (It’s still possible for someone to schedule a meeting with me but they are forced to acknowledge that it’s outside of my working hours.)</p><p>In addition to work benefits, having an organized and updated calendar also helps me visualize my work life balance; Google Calendar has even come out with insights about time spent in meetings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/0*lKLzKJEErmrYTps8" /><figcaption>Google calendar insights</figcaption></figure><p>Making sure my calendar is up-to-date helps others be respectful of my time and vice-versa. It also helps me be respectful of my own time :)</p><p><strong>4. Listen more than you speak</strong></p><p>I believe it was one of our co-founders, Dheeraj Pandey, who said that one should listen two times more than one speaks. This holds particularly true for me at this point in my career. Because I work at a startup that values ownership and believes in the power of youth, I am often asked for my opinion, which I’ll happily give. However, it’s when I hear the opinions and thoughts of others that I gain the most; I am surrounded by people who usually have at least a decade of experience on me and each time they voice their opinions, I gain insight. The colleagues that I most look up to actively practice listening more than speaking as well. I think it’s human nature to want to hear yourself talk and in this day and age, being loud is often equated with being important or being correct, but this is very anti-productive. Think about it: you already know what you think so if you truly want to gain information or insight, you should shut up and listen to what others think. This isn’t to say you have to agree with them or even value their input but how will you know if they have valuable input if you don’t even listen to them speak?</p><p><strong>5. Say goodbye to comfort zones</strong></p><p>I am a self-proclaimed backend developer. Unless you count copy-pasting code from StackOverflow to cobble together a website as frontend development, I have zero frontend experience. Despite this, I have spent the last two weeks working on our product’s frontend. While I won’t get into why, I will say that this is one of many times where I’ve stepped out of my comfort zone and each time it happens, I learn something new. For example, after three weeks of working on the frontend code, I’ve developed not only more respect for our frontend team who tirelessly work to build something beautiful and usable, but also a far better understanding of the relationship between frontend and backend. I’ve been able to see where the backend code I normally write fits in and this allows me to be a better developer overall. For the tech industry in general (and I’m sure other industries as well but I only speak to what I know), staying in comfort zones actually results in not just a stagnant but a declining career; if you’re not willing to step out and learn and experience more, then you’re outdated.</p><p><strong>6. Take ownership</strong></p><p>At DevRev, the <strong>owner’s mindset</strong> is really emphasized. At its core, having an owner’s mindset means that you are <strong>personally invested</strong> in the product and the product’s success, or lack thereof, reflect on you. While this may sound like the opposite of work-life balance, it really isn’t; having an owner’s mindset means that you want to work to better your product because it belongs to you.</p><p>The owner’s mindset doesn’t just stop at the product; it also applies at the company level as well. Owners don’t just follow examples; they lead by examples. Whether it means owning up to mistakes, taking on new responsibilities and projects, or even making new colleagues feel welcome, for me, being an owner means being personally invested.</p><p>Even though I’ve only been working at DevRev for eight months, I’ve done my best to get my hands on and contribute towards a little bit of everything. This hasn’t just meant working on frontend things as a backend engineer — this has also meant owning things in realms like publicity and hiring, which are both outside of what a “traditional” SWE does. However, by taking ownership of these things as well as my “normal” duties, I’ve gained a higher sense of clarity about both DevRev as a company and as a product. This heightened clarity allows me to perform better and hopefully inspire others to do the same.</p><p><strong>7. Be stretchy</strong></p><p>This is directly taken from the book <a href="https://www.scottsonenshein.com/stretch/">“Stretch” by Scott Sonenshein</a>. In this book, Sonenshein breaks down two concepts: stretching vs. chasing. Essentially, stretching makes the most of resources while chasing exhausts resources in the pursuit of more. While DevRev is not exactly a “typical” startup thanks to a <a href="https://techcrunch.com/2021/07/14/former-nutanix-execs-launch-new-startup-with-50m-seed-round/">hefty seed round</a>, we are consistently reminded to stretch and not chase. Having a stretchy mindset leads to innovation because making the most of resources often means utilizing those resources in nontraditional ways.</p><p>Prior to DevRev, I definitely leaned more towards chasing; if I needed to hammer in a nail and didn’t have a hammer, I’d buy a hammer. However, after joining DevRev and learning more about stretching, I’ve realized that I’ve wasted countless resources because of self-imposed limitations. Who’s to say that a shoe or a tape dispenser or a book can’t be a hammer?</p><p>While there are some things in life that I believe are worth chasing (my personal picks are gold jewelry and leather goods), pivoting to stretching instead of chasing day-to-day has meant that my resources (whether it be money, time, energy, or something else) have increased since the resources I do possess have increased in use and as a result, I’m spending less resources overall to pursue wealth.</p><p><strong>8. Fail often and fail fast</strong></p><p>There was some cheesy quote on my middle school science teacher’s wall, something about how Ben Franklin didn’t fail 1000 times before making a working light bulb but how the light bulb just took 1001 steps to make. Ben Franklin controversy aside, I actually really like that quote. (Another quote I like also came from a middle school classroom wall: “Shoot for the moon and land amongst the stars”… but I digress.) Without trying to be too deep, the light bulb quote is essentially saying that failure is not just part of the process, but integral to the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*89RVy74cNFhOR9WE" /><figcaption>Photo credit to Qimono on Pixabay</figcaption></figure><p>One thing that quote doesn’t cover, however, is failing fast. This is tangentially related to being stretchy as it’s also about conservation of resources; failing fast means that when something isn’t working, then it’s best to cut losses and move on. This doesn’t always mean entirely pivoting away from a goal; sometimes this can just mean re-evaluation of the current methods to reach that goal. In the context of the lightbulb quote, out of the 1000 failures, there should be at least 400 unique failures.</p><p>For example, theoretically, if you throw a ball at a wall infinite times, it is bound to pass through once. However, reality isn’t theoretical and if you sat throwing a ball at a wall over and over again hoping for it to go through, you’d realistically be an idiot. Essentially, failing over and over again by repeating the same process is a huge waste of time and resources. Ideally, you should learn from each failure and every new iteration should be different in some way. The last eight months have been a whirlwind; in addition to starting work at DevRev, I also graduated from university, moved to a new city, and got a dog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mPIN-AtW6lLNZcmG" /><figcaption>Ranger!</figcaption></figure><p>However, despite all the changes in my life, the eight things that I shared with y’all today have helped me stay centered, focused, and productive, giving me more energy and motivation to work on a product that will generate wealth for developers everywhere. However, that is yet to come so I hope you’ve at least gained some wealth in reading this article :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed4217a955c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/eight-things-i-learned-in-eight-months-as-an-engineer-at-a-tech-startup-ed4217a955c2">Eight things I learned in eight months as an engineer at a tech startup</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My journey from CRM to DevCRM]]></title>
            <link>https://medium.com/devrev/my-journey-from-crm-to-devcrm-7e7bc01d0300?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e7bc01d0300</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[devrev]]></category>
            <category><![CDATA[devcrm]]></category>
            <category><![CDATA[crm]]></category>
            <dc:creator><![CDATA[Michael Machado]]></dc:creator>
            <pubDate>Tue, 04 Jan 2022 01:52:07 GMT</pubDate>
            <atom:updated>2022-06-13T20:00:13.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*poKUhJ2Cohwjks4eA7drMQ.png" /></figure><p><strong>Becoming a DevReveler</strong></p><p>Having spent nearly a decade building enterprise software, I continue to be motivated by the impact technology enables. My passion will always lead me to find ways to create products of lasting value that transform the way people work.</p><p>I am optimistic that the biggest opportunity for work transformation lies in connecting the <strong>maker toolchain</strong> to <strong>customers</strong>. That is what drove me to join DevRev and lead the Product Management organization. My role is to help us rev from zero to one, as we create a new product category which enables developers to build products, support customers and grow their businesses in today’s product-led world… <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/my-journey-from-crm-to-dev-crm"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e7bc01d0300" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/my-journey-from-crm-to-devcrm-7e7bc01d0300">My journey from CRM to DevCRM</a> was originally published in <a href="https://medium.com/devrev">DevRev</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 Build a Product-Led Operating System]]></title>
            <link>https://medium.com/devrev/how-to-build-a-product-led-growth-plg-operating-system-cdffff8f47e6?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/cdffff8f47e6</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[devcrm]]></category>
            <category><![CDATA[plg]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Madhukar Kumar]]></dc:creator>
            <pubDate>Tue, 21 Dec 2021 01:16:29 GMT</pubDate>
            <atom:updated>2024-11-14T12:46:55.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CDZlwjcMhtr6R-Em4peNog.png" /></figure><h4>I have written about the “Why” of Product-led Growth (PLG) and some fundamental principles in action in my previous blogs. In this article, let’s look at the “What” and the “How.” In other words, how do we go about building an operating system that powers PLG?</h4><p>Before we get into the architecture details, though, I like to start with defining what problems we are trying to solve and, consequently, the requirements to solve those problems. In the end, as PLG practitioners, we are looking to drive more users to discover our product, become users of the free tier or trial, and eventually, become long-term customers.</p><p>In my mind, to build an operating system that helps us achieve this, there are three main requirements:</p><ol><li>A <strong>website</strong> that is easy to update and manage that you can use effectively to engage with your users and customers.</li><li>A single and real-time view of <strong>visitors and customers</strong> and their activities.</li><li>A way to <strong>orchestrate</strong> actions based on users’ activities and attributes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aK5Ve9qUrzn1XoXC.png" /></figure><h3>Three legs of a PLG architecture</h3><h3>Website</h3><p>If we further decompose the requirements for a website, I feel the following ones are a must:</p><ol><li>A <strong>fast</strong> website where changes can be made as many times as possible in a day without downtime, whether these changes are code fixes and improvements by the developers or content changes made by the marketing team.</li><li>An automated <strong>workflow</strong> to review, test and publish the changes with the ability to roll back on an on-demand basis.</li><li>Finally, a way for website visitors and customers to talk to humans when they need help on an on-demand basis.</li></ol><p>In my past experiences, I struggled with Content Management Systems (CMS) that most marketing organizations use because it becomes increasingly difficult to make quick changes over time. I remember having discussions with web marketing teams that required three-four weeks of lead time even for creating and rolling out a simple landing page. This is primarily because there is little separation between code and content, both managed by two different sets of teams with different skill sets that leads to complexity around deployment. In addition, as the tech stack gets bulkier over time, the performance of the web pages starts to suffer.</p><p>To solve for separation between code and content, you can use a headless CMS to store all your content with a visual UI allowing content writers to make agile changes without requiring any development skills. There are quite a few headless CMSes out there, but the one we at <a href="https://web.archive.org/web/20220524052951/https://devrev.ai/">DevRev</a> love is an open-source project called <a href="https://web.archive.org/web/20220524052951/https://strapi.io/">Strapi</a>. It is a NodeJS based app that you can use out of the box with easy-to-use UI and support for Markdown and effectively create content types within minutes.</p><p>When it comes to the rest of the web stack that consumes the content from the headless CMS, I am a big fan of the JAM (Javascript, API, and Markup) stack. There are several good frameworks for this architecture, like <a href="https://web.archive.org/web/20220524052951/https://gohugo.io/">Hugo</a>, <a href="https://web.archive.org/web/20220524052951/https://jekyllrb.com/">Jekyll</a>, <a href="https://web.archive.org/web/20220524052951/https://nextjs.org/">NextJs</a>, and my personal favorite, <a href="https://web.archive.org/web/20220524052951/https://www.gatsbyjs.com/">Gatsby</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QRHVcXqacJadb1GB.png" /></figure><p>Some of the JAM Stack choices</p><p>At DevRev we settled on using Gatsby because it is a NodeJS based framework that allows you to write your entire site in React, and at build time, Gatsby creates static HTML, CSS, JS files. There are some significant advantages with this architecture-</p><ol><li><strong>Hosting</strong> these files is dead simple — you can take the output files and dump them in an S3 bucket or host it on an extremely fast web server or use a CDN deployment like Fastly.</li><li>Since the website is a bunch of static files, the performance is <strong>crazy fast</strong>, which is also great for SEO. In addition, with JS includes you can easily integrate with systems like Intercom that enable conversational functionalities on your website.</li><li>If your code is on Github, you can create a build time pipeline that does an <strong>automatic build and deployment</strong> of your entire site. We have set this up so that when a Pull Request (PR) is approved, it kicks off a build and deploys the site only when the build is successful. This also enables a zero-downtime deployment,</li><li><strong>Separation of code and content</strong> — You can make REST calls to your headless CMS to grab all content at build time. This means your developers can just focus on code (Gatsby) while your content writers can work on content through UI or Markdown. When a change is made either in code or content, you can trigger a workflow to kick off a deployment so your website can up be updated as many times as you want in a day with zero downtime.</li><li>Finally, since the site is built of React components, you can still create dynamic functionalities by making API calls to your internal systems or using Server-Side Rendering (SSR) functionalities.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-nrboI0Ne3FfS0_9.png" /></figure><p>Website architecture with separation of code and content and zero downtime deployments</p><h3>Data</h3><p>Now that we have looked at the tech stack’s website portion let’s try and address the second requirement — a single and real-time view of your visitors and customers.</p><p><strong>In my opinion, in an ideal PLG OS, you should be able to not only look at real-time user data (all visitors + customers) but also orchestrate in-app and off-app actions based on segments of your users’ activities and attributes.</strong></p><p>This category is unfortunately heavily crowded with too many confusing choices. On the one hand, you have tools like <a href="https://web.archive.org/web/20220524052951/https://www.fullstory.com/">FullStory</a>, <a href="https://web.archive.org/web/20220524052951/https://marketingplatform.google.com/about/analytics/">Google Analytics</a>, and <a href="https://web.archive.org/web/20220524052951/https://www.hotjar.com/">Hotjar</a> that give you heatmaps and funnel metrics around your web visits and visitors. On the other, you have tools like <a href="https://web.archive.org/web/20220524052951/https://www.drift.com/">Drift</a> and <a href="https://web.archive.org/web/20220524052951/https://www.intercom.com/">Intercom</a> that enable you to add chatbots and get details around user behavior. My issue with all these tools is that typically they want you to use their app as the customer master. Eventually, however, you now have more place for a growth user, including valuable user data disconnected from your multiple customer databases like your CRM, support system, and or your app’s identity database.</p><p><strong>It has taken me years to appreciate the fact that you don’t necessarily need one place where all your customer data resides, rather a way to bring in different portions and views of your users’ data in real-time to perform different actions across multiple end points.</strong> These actions may include re-targeting, personalization within the app, notifications, and finally, data analysis over time. You can, of course, potentially build something like this with Redis Streams or Kafka, but nowadays, there are solutions like <a href="https://web.archive.org/web/20220524052951/https://segment.com/">Segment</a> or <a href="https://web.archive.org/web/20220524052951/https://rudderstack.com/">Rudderstack</a>with features built on top of similar data architecture like Kafka.</p><p>With Segment, for example, you can potentially start collecting data from any data source that can do a POST, and you can send that data, with or without any additional processing, to any other data source. More importantly, you can create cohorts or segments of users based on their attributes (for example, location) or their actions (all users who signed up in the last 1 hour and did not start the onboarding tasks) and send them to different destinations to execute actions.</p><p>Here is an example of what your data flow architecture may look like -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vr1RWBCFBpOgTyPo.png" /></figure><p>Data flow architecture with a Time series data assimilator</p><h3>Orchestration</h3><p>Finally, the last piece of the puzzle is to be able to perform automated, scalable actions based on some rules you can create on your own. Typically, you have a rules-based task engine in email and marketing automation tools like Marketo. However, those rules are specific to the data available only on those platforms. Ideally, you want one rules engine to act on data collected across multiple systems like your website, app, ad platforms, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tav1xSDDpu-5r99s.png" /></figure><p>The three pillars of an orchestration engine</p><p>There are a few choices here that allow you to listen to events, have triggers that kick off the action, and the action itself, which is a simple lambda function-like entity.</p><p>For us, we have been using a NodeJS based system called Pipedream. It allows us to listen to webhook events and run a function that uses data changes or schedules as triggers. With the web, data, and orchestration now in place, the architecture looks like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Dd-dKzmxc38nvN9.png" /></figure><p>The complete picture</p><h3>Summary</h3><p>In summary, a tech stack or OS for PLG architecture requires an extremely agile website, a good data strategy, and a flexible orchestration engine. Once you have these in place, you can view, nudge, and deliver personalizations in real-time to drive growth for your product. One of the things we did not cover in this blog is <strong>where does your traditional CRM fit in this picture</strong> or even how to create real time dashboards and reporting based on this architecture. Stay tuned as we cover those in future blogs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdffff8f47e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/how-to-build-a-product-led-growth-plg-operating-system-cdffff8f47e6">How to Build a Product-Led Operating System</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why AI won’t replace developers]]></title>
            <link>https://medium.com/devrev/why-ai-wont-replace-developers-11ff07e9b6f7?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/11ff07e9b6f7</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[violex]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 17:29:33 GMT</pubDate>
            <atom:updated>2022-06-13T20:23:40.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGcLeQ-1MzL-8ZgfClwsGA.png" /></figure><h4>And why it will make our lives better</h4><p>By <a href="https://twitter.com/violexming">Violex Ming</a></p><p>When someone brings up artificial intelligence, often what comes to mind are uncanny valley robots who are secretly plotting to overthrow their human overlords. The reality isn’t quite as glamorous and at least for the foreseeable future, will never be like that. While artificial intelligence has come a long way since the 1950’s, we won’t ever reach a point in time where developers are obsolete, no matter how advanced AI gets… <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/why-ai-won-t-replace-developers-and-why-it-will-make-our-lives-better"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11ff07e9b6f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/why-ai-wont-replace-developers-11ff07e9b6f7">Why AI won’t replace developers</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Why and What of DevRev]]></title>
            <link>https://medium.com/devrev/the-why-and-what-of-devrev-f0485e0b97dc?source=rss----a185accbab1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f0485e0b97dc</guid>
            <category><![CDATA[devrev]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[plg]]></category>
            <category><![CDATA[devcrm]]></category>
            <dc:creator><![CDATA[Madhukar Kumar]]></dc:creator>
            <pubDate>Wed, 20 Oct 2021 17:32:41 GMT</pubDate>
            <atom:updated>2022-06-13T20:10:43.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaUAGzrzQf58y6qocp6XpA.png" /></figure><p>By <a href="https://twitter.com/madhukarkumar">Madhukar Kumar</a> and <a href="https://twitter.com/michaelemachado">Michael Machado</a></p><p>Not very long ago something seemingly trivial like making phone calls across the globe required complex processes and integrations with different phone companies. Today, you can not only make phone calls but even video calls in an on-demand fashion from anywhere.</p><p>A lot has happened since the telecom industry went digital and today we live in an era where anything, from a car to a meal, can be ordered instantaneously, with notifications and real-time tracking ensuring the user always knows its ‘status’.</p><p>A similar thing happened when it came to payments... <em>Read the rest of the blog on the DevRev website</em><strong><em> </em></strong><a href="https://devrev.ai/blog/the-why-and-what-of-dev-rev"><strong><em>here</em></strong></a><strong><em>. </em></strong><em>[We have moved our blogs to our website.]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0485e0b97dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devrev/the-why-and-what-of-devrev-f0485e0b97dc">The Why and What of DevRev</a> was originally published in <a href="https://medium.com/devrev">DevRev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>