<?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 Foxbox Digital on Medium]]></title>
        <description><![CDATA[Stories by Foxbox Digital on Medium]]></description>
        <link>https://medium.com/@foxboxdigital?source=rss-c94703220ba9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-EEiRdKrc_5wct4n.jpg</url>
            <title>Stories by Foxbox Digital on Medium</title>
            <link>https://medium.com/@foxboxdigital?source=rss-c94703220ba9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:35:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@foxboxdigital/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[18 Of The Best Elixir Resources Available Online in 2020]]></title>
            <link>https://medium.com/@foxboxdigital/18-of-the-best-elixir-resources-available-online-in-2020-75c5e9b45e50?source=rss-c94703220ba9------2</link>
            <guid isPermaLink="false">https://medium.com/p/75c5e9b45e50</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[elixir]]></category>
            <dc:creator><![CDATA[Foxbox Digital]]></dc:creator>
            <pubDate>Tue, 19 May 2020 18:23:57 GMT</pubDate>
            <atom:updated>2020-05-19T18:23:57.192Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our collection of the most useful resources to become an Elixir expert</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IsB6kdPkblm0EYEfQ_vIzg.jpeg" /></figure><p>We used Ruby on Rails as our primary web application framework for quite a bit.</p><p>But when Elixir grew in popularity, we were quickly dazzled by its resemblance to Ruby, the language we already loved. The more we learned about Elixir, the more we understood its strength over Ruby and how it could tremendously benefit our business.</p><p>Fast-forward to present day, and we have switched completely to Elixir (<a href="https://foxbox.com/blog/elixir-vs-ruby/">here’s why we think that Elixir is better than Ruby</a>).</p><p>We wanted to share with the Elixir community the top resources that helped us along the way.</p><p>Here they are.</p><h3>Tutorials</h3><h4>1. ElixirConf Youtube Channel</h4><p><a href="https://www.youtube.com/channel/UC0l2QTnO1P2iph-86HHilMQ/videos">All of the videos of speakers from ElixirConf</a> starting back from 2017. Lots of great information and different perspectives.</p><p>Here below a video we particularly liked on the tradeoffs between type systems and contract system:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ftpo3JUyVIjQ%3Fstart%3D43%26feature%3Doembed%26start%3D43&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dtpo3JUyVIjQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Ftpo3JUyVIjQ%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/a71931494cfc6fddf91a92c28eae3fa6/href">https://medium.com/media/a71931494cfc6fddf91a92c28eae3fa6/href</a></iframe><h4>2. Elixir Forum</h4><p>An active <a href="https://elixirforum.com/">Elixir only forum</a> where you can get quick and valuable feedback from engineers working in Elixir.</p><h4>3. Hackr.io</h4><p>A mixture of <a href="https://hackr.io/tutorials/learn-elixir">free and paid training classes</a> on Elixir by hackr.io.</p><h4>4. Elixir School</h4><p><a href="https://elixirschool.com/en/">Elixir School</a> is a destination for newbie and experienced Elixir programmers.</p><h4>5. Programming Elixir 1.6 (Book)</h4><p>If you’re an experienced programmer looking for a comprehensive written resource on programming in Elixir, <a href="https://pragprog.com/book/elixir16/programming-elixir-1-6">then this book is for you</a>.</p><h4>6. Elixir Training on Github</h4><p><a href="https://github.com/dwyl/learn-elixir">Learn the Elixir programming language on Github</a> to build functional, fast, scalable and maintainable web applications.</p><h4>7. Slack Bot Tutorial</h4><p>Discover <a href="https://blog.kiprosh.com/developing-a-slack-bot-in-elixir-phoenix/">how to develop a Slack bot</a> with Elixir and Phoenix.</p><h4><strong>8. Elixir for Javascript Developers</strong></h4><p>Some <a href="https://blog.bitsrc.io/how-to-learn-elixir-for-hipster-javascript-developers-f0352e579ac3">great basic concepts of Elixir</a> to getting started if you already have a knowledge of Javascript.</p><p><a href="https://blog.bitsrc.io/how-to-learn-elixir-for-hipster-javascript-developers-f0352e579ac3">How to Learn Elixir for Hipster Javascript Developers</a></p><h4>9. Learn Elixir in Y minutes</h4><p>A high-level overview of Elixir <a href="https://learnxinyminutes.com/docs/elixir/">on one page</a>.</p><h4>10. How We Learned Elixir</h4><p><a href="https://www.monterail.com/blog/learning-elixir-tutorial-guide">A great story, with examples,</a> about how engineers at a company learned Elixir, together with some tutorials for beginners</p><h4>11. Ten Advanced Elixir Tips</h4><p>Ten Medium posts with ten different tips. <a href="https://medium.com/blackode/10-killer-elixir-tips-2a9be1bec9be">This is the first one</a>.</p><p><a href="https://medium.com/blackode/10-killer-elixir-tips-2a9be1bec9be">10 Killer Elixir Tips #1</a></p><h4>12. Elixir: The power of truly distributed systems</h4><p>How to <a href="https://medium.com/unbabel/elixir-the-power-of-truly-distributed-systems-c4c79ed9f97d">scale</a> with the help of Elixir.</p><p><a href="https://medium.com/unbabel/elixir-the-power-of-truly-distributed-systems-c4c79ed9f97d">Elixir: The power of truly distributed systems</a></p><h4>13. Elixir for Rubyists</h4><p>How <a href="https://thoughtbot.com/blog/elixir-for-rubyists">some Ruby features</a> are represented in Elixir.</p><h4>14. Write Better Elixir Code</h4><p>This <a href="https://medium.com/blackode/write-better-elixir-code-4bcf12062fd5">article</a> comprises of some good coding techniques in Elixir.</p><p><a href="https://medium.com/blackode/write-better-elixir-code-4bcf12062fd5">Write Better Elixir Code</a></p><h3>Case Studies</h3><h4>15. Discord adoption of Elixir</h4><p>From the beginning, Discord has been an early adopter of Elixir. <a href="https://blog.discordapp.com/scaling-elixir-f9b8e1e7c29b">Here’s a great article</a> on how Discord scaled Elixir to 5,000,000 concurrent users.</p><p><a href="https://blog.discordapp.com/scaling-elixir-f9b8e1e7c29b">How Discord Scaled Elixir to 5,000,000 Concurrent Users</a></p><h4>16. How Elixir helped Bleacher Report handle 8x more traffic</h4><p>Bleacher Report has gone from 150 servers to just five, thanks to its decision to move to Elixir Phoenix. <a href="https://www.techworld.com/apps-wearables/how-elixir-helped-bleacher-report-handle-8x-more-traffic-3653957/">Here’s how</a>.</p><h4>17. Elixir Companies</h4><p>A <a href="https://elixir-companies.com/en">collection</a> of companies using Elixir in production.</p><h3>Interview</h3><h4>18. The One Who Created Elixir</h4><p>A <a href="https://www.welcometothejungle.com/en/articles/btc-elixir-jose-valim">video interview</a> with José Valim, the creator of Elixir.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FdPRt5pOIFHk%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DdPRt5pOIFHk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FdPRt5pOIFHk%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/3c7714bb8ebc8b8b55fa5d2f8c48040e/href">https://medium.com/media/3c7714bb8ebc8b8b55fa5d2f8c48040e/href</a></iframe><h3>In Conclusion</h3><p>We believe Elixir was created specifically for programmer happiness. However, this doesn’t mean you should drop everything and rewrite all of your apps in Elixir. There is a time and place for everything.</p><p>In the end, Ruby is still a great language — we just feel Elixir is a better language. It would be a good idea to consider Elixir on your next project. I hope the resources above will help with your decision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75c5e9b45e50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Reasons Why Elixir Is Better Than Ruby]]></title>
            <link>https://medium.com/better-programming/6-reasons-why-elixir-is-better-than-ruby-8f5ef8edc40e?source=rss-c94703220ba9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f5ef8edc40e</guid>
            <category><![CDATA[elixir]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Foxbox Digital]]></dc:creator>
            <pubDate>Sat, 18 Jan 2020 02:15:26 GMT</pubDate>
            <atom:updated>2020-01-21T09:55:06.721Z</atom:updated>
            <content:encoded><![CDATA[<h4>How and why Elixir is designed for programmer happiness</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EL9lo3QX2jWbD2mH" /><figcaption>Photo by <a href="https://unsplash.com/@maxcodes?utm_source=medium&amp;utm_medium=referral">Max Nelson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Our team has been using Elixir for the past 24 months, and I thought it’d be a good idea to write down my thoughts on Elixir vs. Ruby and why our engineering team decided to stop programming with Ruby altogether and put all of our efforts behind Elixir.</p><p><a href="https://foxbox.com/blog/elixir-vs-ruby/">I talk in full detail about our Elixir vs. Ruby experience here</a>, but for this piece, I want to focus on the following:</p><ol><li>Development velocity</li><li>Safety and correctness</li><li>Performance</li><li>Easy concurrent programming</li><li>Maturity</li><li>Hiring quality</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*arZ5JxkjH3E6ODAjMxdt1Q.jpeg" /></figure><h3>1. Development Velocity</h3><p>Let’s be honest — we’re excited about Elixir’s effortless handling of concurrency, but it’s not the main reason we stick with it. Elixir is a highly productive language. Here are some reasons for that claim:</p><p><strong>Simplified development setup</strong> — Utilizing the BEAM virtual machine, one can expect to have a consistent development experience on almost any machine — even Windows. While this can also be true for Ruby, as a project progresses, a typical web application in Ruby accumulates more dependencies that make it increasingly difficult to get it up and running, while an Elixir web application would remain relatively easy to set up.</p><p><strong>Predictable codebase</strong> — Elixir enforces true lexical scoping and encourages explicit codes. What this means at the code level is Elixir makes data transformations, code organizations, and application interfaces much more predictable and easier to reason with — thus saving a lot of development time.</p><p><strong>Lightweight and fast testing</strong> — This is probably the most undermentioned yet powerful benefits of using Elixir. Elixir provides developers access to super-fast, concurrent testing with relatively minimal impact on hardware performance. Ruby testing, on the other hand, can be painfully slow and hardware-intensive — to the point it could bog down the whole system for those with underperforming machines. Elixir completely takes away the headache by making tests faster.</p><p><strong>Useful built-in features</strong> — We‘ ha’ve used Elixir to build a quick MVP project to building large-scale projects. In both scenarios, Elixir provides powerful built-in features to satisfy the requirements for a typical modern web application, such as caching, background processing, and process monitoring. On a platform such as Ruby on Rails, these solutions usually come with tightly coupled dependencies on services, such as Redis, Resque, and Foreman.</p><p>I’ll admit, at first, I was extremely frustrated with Elixir.</p><p>I struggled with pattern matching, which was touted as this revolutionary new concept. After getting used to it and all of the other advantages of Elixir, though, I’ve found myself coding with less effort and frustration to achieve the same exact output as Ruby. There are two reasons for this.</p><h4>It’s a functional language</h4><p>Functional languages, as opposed to object-oriented languages like Ruby, are beautiful and simplify programming. I greatly favor functional languages for several reasons:</p><ul><li>They lead to coding faster and more predictably</li><li>No state to keep track of. States make it extremely difficult to track down problems. There are no reference errors. Everything is a pure function, which is wonderful.</li></ul><h4>It has pattern matching</h4><p>One of the biggest advantages and differentiators of Elixir is pattern matching. Pattern matching comes from its Erlang roots and is one of those things you wish was also incorporated into other languages.</p><p>One of our very talented engineers <a href="https://gist.github.com/fschuindt/d1174ac8f490bfdef8abf9629fa8ecaf">put together a code-sample comparison</a> between Elixir and Ruby using a simple ranking example.</p><p>In that example, pattern matching makes the code more elegant, expressive, and easier to read. It may seem like a small thing, but I find myself using pattern matching any chance I get.</p><h3>2. Safety Features Result in Fewer Bugs</h3><p>Programming is a mixture of fun and frustration. I find Elixir to be slightly more fun and a lot less frustrating than Ruby. Elixir, a dynamically typed language, has type-safe and guards built-in, along with pattern matching, which significantly reduces the bugs.</p><p>This results in fewer compiler errors. And for the bugs that do exist, they’re easier to find because of the compiler. Compiled code is a huge safety feature. In Ruby, bugs can remain hidden until someone hits them; in Elixir, the compiler will find most of them.</p><p>In summary:<br>Safety → Fewer bugs → Easier to track down bugs → More fun → Happier team → Happier me</p><h3>3. It’s Fast — Real Fast</h3><p>Elixir compiles into BEAM bytecode, so it inherits all the performance benefits of Erlang with almost zero penalties. On the other side, Ruby requires an interpreter that reads its code line by line during runtime. While choosing the right kind of production-ready Ruby interpreter for your application is already an uphill task by itself, squeezing more performance out of Ruby often requires strict adherence to Ruby’s dos and don’ts. Want to concatenate strings? Sure. Want to make it run faster? Use string interpolation instead.</p><p>Elixir liberates programmers from having to carefully craft their codes based on an endless list of best practices for the sake of making their codes run just a tiny bit faster and focuses more on producing codes that satisfy the needs of your business.</p><p>To be fair, Elixir may also have a similarly long list of performance best practices, but they come at a much later stage of development. Moreover, since Elixir is a compiled language, most performance issues can be caught by the compiler automatically, reducing the time and effort needed to write efficient, performant code.</p><h3>4. Easy Concurrent Programming</h3><p>Remember how I said Elixir was fun?</p><p>Well, the way concurrency is handled in Elixir is one of the reasons I don’t see myself programming in other languages (unless I absolutely need to).</p><p>If you’ve ever had to deal with <a href="https://web.mit.edu/6.005/www/fa14/classes/17-concurrency/">concurrency</a>, you can understand how frustrating it is. The same program can generate different results if not handled correctly. You have to deal with locking, race conditions, and bugs that are difficult to solve.</p><p>The beautiful part of Elixir is concurrent libraries are built into the language. You won’t need third-party dependencies to achieve scalable, safe, concurrent programming.</p><p>These two reasons are a huge selling point for Elixir.</p><h4>Easy-to -rocess data at scale</h4><p>WhatsApp, built on Elixir, <a href="https://www.cnet.com/news/whatsapp-65-billion-messages-sent-each-day-and-more-than-2-billion-minutes-of-calls/">has over one billion active users, and it processes over 65B messages per day</a>.</p><h4>Cheaper to run: achieve more with less hardware</h4><p>Ruby applications take up a lot of memory on a server because you have to run many instances of that app to handle multiple requests. Why? Ruby is effectively single-threaded because it has something called the <a href="https://realpython.com/python-gil/">Global Interpreter Lock</a> that enforces only one thread run at a time.</p><p>Elixir applications can handle magnitudes more requests per instance because it’s concurrent and compiled (much quicker execution time). You can run a single instance of an Elixir application on a server to handle a huge number of requests. That lowers your memory utilization considerably.</p><p>When it comes to data processing, both Elixir and Ruby are considered expensive solutions in terms of memory compared to languages such as C, Rust, and Go. But in the world of concurrent data processing, Elixir and Erlang have a robust prebuilt infrastructure.</p><p>With the smaller door (Ruby), you’ll have to wait longer for people in front of you to get in. On a wider door (Elixir), more people can get in at the same time.</p><p>Elixir handles concurrency in a really efficient way, allowing for more concurrent connections with the same hardware.</p><h3>5. It’s Mature</h3><p>Elixir is built on top of Erlang, a battle-tested 40-year-old language. Erlang runs highly concurrent applications like WhatsApp.</p><p>This headline and quote from <em>Wired</em> is a great Erlang case study:</p><p><a href="https://www.wired.com/2015/09/whatsapp-serves-900-million-users-50-engineers/">“Why WhatsApp Only Needs 50 Engineers for Its 900M Users</a>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*aQuijK5g2SOSFvaZ.jpg" /></figure><p>Additionally, Elixir has Phoenix, a world-class web framework for modern web apps modeled on Rails, which we all know and love.</p><p>Elixir has a <a href="https://hex.pm/packages">large ecosystem of packages</a> you can leverage while building your application. Not everything is available in an Elixir package, and for those cases, you can run any Erlang package natively from your Elixir application.</p><p><a href="https://www.hntrends.com/2019/oct-no-sign-of-react-falling-back.html?compare=Ruby&amp;compare=Elixir&amp;compare=&amp;compare=">It’s also growing</a>. It hasn’t caught up to Ruby in terms of job posts on Hacker News, but it’s trending upward while Ruby is trending downward.</p><h3>6. Hiring Quality</h3><p>From my experience, since Ruby has been around for much longer and is easier to learn, there are a lot of great Ruby programmers and many who have a lot to learn. This makes it a little bit harder to hire Ruby engineers since you’ll have more candidates to filter through.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f5ef8edc40e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/6-reasons-why-elixir-is-better-than-ruby-8f5ef8edc40e">6 Reasons Why Elixir Is Better Than Ruby</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why CTOs Should Choose React Native as Their Mobile Development Platform]]></title>
            <link>https://medium.com/@foxboxdigital/why-ctos-should-choose-react-native-as-their-mobile-development-platform-ad4682591e28?source=rss-c94703220ba9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad4682591e28</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Foxbox Digital]]></dc:creator>
            <pubDate>Mon, 11 Nov 2019 15:57:49 GMT</pubDate>
            <atom:updated>2019-11-11T15:57:49.257Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 Reasons Why CTOs Should Choose React Native as Their Mobile Development Platform</h3><h4>With React Native, you have a best-in-class framework that is optimal for 95% of all business use cases.</h4><p><em>By Rob Volk, Foxbox CEO</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Gc0ClG-aLXdYLmkx-g5Fw.jpeg" /><figcaption>Source: <a href="https://foxbox.co/blog/react-native-ctos/">https://foxbox.co/blog/react-native-ctos/</a></figcaption></figure><p>Native apps are considered the gold standard and offer the best overall performance, user experience, and access to hardware-related features such as support for multi-touch gestures, access to the camera, GPS, calendar, accelerometer, and much more.</p><p>But now the mobile world has moved on and React Native is the right decision for many companies.</p><p>React Native has transformed the whole dualistic notion of iOS vs. Android by creating beautiful apps for both platforms from one codebase-without compromising on the UX and UI. On a React Native app, everything you see and touch is native.</p><p>So unless you are Uber or Airbnb and can afford to spend money and time on exclusive native mobile development, your business really should be using React Native as its development platform of choice.</p><p><strong>The reason is fairly straightforward. With React Native, you have a best-in-class framework that is optimal for 95% of all business use cases.</strong></p><p>React Native is especially good news for CTOs and VPs of Engineering because instead of hiring two additional development teams for Android and iOS, you can leverage your existing web development team to build your mobile app.</p><p>React Native represents the best organizational choice for CTOs and VPs today: here below, five reasons why react native could be good for your next digital project.</p><h3>1# Mature and growing framework</h3><p>React Native was introduced in 2015 and underwent the initial stable release in July 2019. Over the past four years, it has become a robust worldwide open-source community with over <a href="https://github.com/facebook/react-native">2000</a> contributors on GitHub-and, of course, with the backing of Facebook. It’s also the <a href="https://github.com/search?q=stars%3A%3E0&amp;s=stars&amp;type=Repositories">17th most starred</a> GitHub repository and had the <a href="https://facebook.github.io/react-native/">second-highest number</a> of contributors for any repository on GitHub in 2018.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q28SeXjeH3zUyiHQHATpcg.jpeg" /><figcaption>Source: <a href="https://github.com/search?q=stars%3A%3E0&amp;s=stars&amp;type=Repositories">https://github.com/search?q=stars%3A%3E0&amp;s=stars&amp;type=Repositories</a></figcaption></figure><p>React Native developers are continually building new libraries, updates, and projects. With cross-platform compatibility, shorter development cycles, faster releases, live code pushes and updates, and overall performance improvements, many have come to see React Native as the future of mobile development.</p><h3>2# You get to manage familiar technology</h3><p>Facebook originally developed React Native as a hackathon to support its cross-platform needs.</p><p>The beauty of React Native is that, unlike “hybrid” mobile app solutions, it uses native UI elements instead of rendering the entire application inside of a WebView. Your business logic is run in a separate JavaScript thread, which then controls the native UI elements. In the “old days,” companies had to develop native apps for both Android and iOS from scratch.</p><p>React Native allows developers to write code in just one language, JavaScript, then build binaries for Android and iOS. It eliminates the need to hire both iOS and Android developers to write dual applications, and this represents a huge benefit in terms of productivity, costs, and time to market. Not to mention the reduced hiring burden!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/0*BQxumff-QKPR1bXy.png" /><figcaption>Source: <a href="https://medium.com/react-native-development/a-brief-history-of-react-native-aae11f4ca39">https://medium.com/react-native-development/a-brief-history-of-react-native-aae11f4ca39</a></figcaption></figure><h3>3# Improved operational efficiency</h3><p>As a CTO, you’re most comfortable managing a company you understand. If you happen to be an “Android guy” and need to hire an iOS developer, you’re not speaking the same language and have to work extra cycles to get everyone on the same page. This can easily lead to operations hang-ups and production slowdowns.</p><p>Being able to write once and port across each major platform means a considerable improvement in the operation of your organization. The ability to place resources on different projects and not have to worry about skillsets and whether a developer can write Swift, Objective-C, Kotlin, or Java is a huge relief.</p><p>Nearly 67% of all developers use JavaScript already, so it’s an easy sell for using React Native to improve operational efficiency across the enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*2vl2FwzNdAXMlbWc.png" /><figcaption>Source: <a href="https://medium.com/react-native-development/a-brief-history-of-react-native-aae11f4ca39">https://medium.com/react-native-development/a-brief-history-of-react-native-aae11f4ca39</a></figcaption></figure><h3>4# Great overall ROI</h3><p>There are many ways React Native saves organizations time and money.</p><p>Obviously, the “<em>one code for all</em>” is a huge advantage as it cuts down on the learning curve and the number of hands on deck required for developing an application. It’s also open source and has a robust and growing community of ready-made components and support.</p><p>In fact, something like 95% of the React Native codebase is shared between iOS and Android.</p><p>These are just some of the many reasons why React Native leads to significant improvements in ROI over hiring native developers.</p><h3>5# Very few trade-offs</h3><p>As good as React Native is for all-around performance, cost savings, and portability, a few use cases will stand out that require a pure native look and feel. These are going to be the high-end enterprises, such as Airbnb and Uber that have money to spend on super-polishing their native application.</p><p>For the “rest of us,” which means 90%-95% of the business use cases, React Native will provide your organization with a highly engaging enterprise application. In other words, the reasons for not using React Native are going to be negligible.</p><p>In terms of cost-savings, increased efficiencies, and the overall native look and feel that users experience, React Native is a no-brainer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UHCD8FIrFQSG2aUO.jpg" /></figure><h3>Bonus — When You Shouldn’t Use React Native</h3><p>Yes, not every app should be built with React Native. Here are some reasons to go full native:</p><ul><li>You’re creating something with complex animations and interactions, like an interactive game.</li><li>You’re building something that’s CPU intensive, like editing photos. In that case, you could either go full native or write the complex logic in native and bridge it to React Native.</li><li>You’re creating something out-of-the-box with unconventional UI patterns. Native might be a better choice in that case.</li></ul><h3>What next?</h3><p>For CTO’s, quickly getting the right products to market is all that matters.</p><p>As a “<em>learn once, write everywhere</em>” framework, React Native cuts down enormously on the cycles required to develop and deploy user-friendly and engaging products to market. React Native is arguably one of the biggest breakthroughs in mobile application development in recent years.</p><p>Backed by Facebook and spawned by <a href="https://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest-mistake-with-mobile-was-betting-too-much-on-html5/">Zuckerberg’s own concession</a>, this cross-compatible platform has transformed the way companies develop enterprise-grade applications-with less learning curves, shorter development cycles, faster releases, and overall cost savings.</p><p>We’ve been using React Native since I founded the company and aren’t looking back anytime soon.</p><p><em>P.S. If you’re trying to decide between React Native and other cross-platform mobile frameworks, </em><a href="https://foxbox.co/blog/react-native-vs-ionic-vs-cordova-vs-phonegap/"><em>read this</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://foxbox.co/blog/react-native-ctos/"><em>https://foxbox.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad4682591e28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile & Scrum: How to Build Better Products, Faster in 2020]]></title>
            <link>https://medium.productcoalition.com/agile-scrum-how-to-build-better-products-faster-in-2020-6a56f626533?source=rss-c94703220ba9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a56f626533</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Foxbox Digital]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 15:33:00 GMT</pubDate>
            <atom:updated>2019-11-12T09:59:02.463Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Jasmine Slivka</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8WbIs_7c8qHbso6TBgyKw.jpeg" /></figure><p>The <a href="http://www.agilenutshell.com/">idea of Agile</a> is an iterative approach to software development that builds software incrementally instead of trying to deliver it all at once with an arbitrary deadline (as with traditional “waterfall” approaches).</p><p>Agile works by breaking projects down into little bits of functionality, usually called user stories, prioritizing them, and then continuously delivering them in short cycles called Iterations or Sprints. These cycles typically span one to two weeks.</p><p>Digital companies today rely on Agile methodologies to stay ahead of their competition and deliver innovative products to market faster than ever. But Agile is not a one-size-fits-all solution. There are various flavors and approaches to Agile transformation.</p><p>Kanban and Scrum are two of the most popular versions of Agile in use today. In fact, here at Foxbox Digital, we have adopted a hybrid of both Kanban and Scrum as a successful framework for product development.</p><p><em>In what follows, we’ll highlight the Agile tools, best practices, and methods we’ve successfully adopted to build innovative digital products that customers love.</em></p><h3>A Hybrid Agile Approach With Scrum</h3><p>Scrum and Kanban are two <a href="https://foxbox.co/services/agile-coaching-and-agile-transformation/">Agile methodologies we use at Foxbox Digital</a> in order to bring our customers the best value possible. The two methods share many similarities but also have some <a href="https://www.cmswire.com/information-management/agile-vs-scrum-vs-kanban-weighing-the-differences/">subtle differences</a>.</p><p>Scrum is a lean software development methodology that focuses on just-in-time delivery of functionality and managing the amount of work in progress (WIP). The key to our successful delivery of projects begins with our two-week sprint and proceeds through the full lifecycle of story-telling in a layout, within <a href="https://about.gitlab.com/">GitLab</a>, where we build the user stories, story-point them based on an assigned numbering sequence (consisting of a Fibonacci sequence to estimate the size and complexity of a user story), and prioritize them across a Kanban board.</p><h3>Principle #1 — Run Two Week Sprints</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cdl0wwgQA0NO3O_eNXfkGw.jpeg" /><figcaption>Image source: <a href="https://foxbox.co/blog/better-products-agile-scrum/">Agile &amp; Scrum: How to Build Better Products, Faster in 2020</a></figcaption></figure><p>Two weeks for us seems to be short enough to develop in a very concise and iterative fashion with our features. But it’s also a long enough time to allow the engineers to build something that has real value.</p><p>Sprints are more than just cycles of development, we also have several recurring meetings around our two-week sprints. Before a sprint begins, Foxbox will host a Backlog Refinement meeting with the client to ensure designs are reviewed and ready, and we have a clear understanding of the business requirements for each piece of functionality.</p><h3>Principle #2 — Manage Your Engineers’ Time and Let Them Focus on the Right Tasks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYZ9U22TNJBpH8mYBY8Jng.jpeg" /></figure><p>Engineers want to engineer, not sit in meetings all day or debate what feature should be built and when. To improve development velocity, managing your engineers’ time is a critical task. Here’s how we do it:</p><ul><li><strong>Start each sprint with a planning call</strong>: The planning call will outline the goals of the sprint and discuss the breakdown of issues within that sprint.</li><li><strong>Outline specific goals</strong>: We queue up issues in order of priority and across a Kanban board. Our planning calls focus on the issues ready to go in “Current.” Any engineer can self-assign themselves an issue in Current, and our general rule of thumb is they work on issues from top to bottom.</li><li><strong>Clarify the priority of tasks</strong>: And now we introduce Kanban. We don’t hard-cut everything and say, “Okay, here are the 10 issues we need to do over the next two weeks.” We like to ensure the developers know which activities are the most important. There is always an ongoing workflow, where priorities are continually ordered and updated.</li></ul><h3>Principle #3 — Simple Issues Drive Clarity (Avoid Complexity)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPEDECE5RxltD5NshkwK_w.jpeg" /></figure><p>The goal is to drive clarity on what exactly needs to be built and how long it may take. The less confusion the better off everyone will be. To do this, we identify all the issues we’ve queued up and:</p><p><strong>Estimate issues and track velocity</strong></p><p>During a planning session, our engineers will agree on a level of complexity for each issue. That level of complexity is represented by what we call “story points.” Story points give us a way to track how much effort will be needed to create a feature and generally are not correlated with an estimation of time.</p><p>The reason we do not estimate time with story points is for the same reason a salesman cannot give an estimate for how many sales they’ll close in a month, because there are too many variables to account for when estimating.</p><p>The reason to use story points is because you can track how many a team does per sprint, and then take an average over a number of sprints to find their “velocity.” Velocity will tell us on average what a team can get done per sprint.</p><p>We track our total points for each sprint because having an idea of our historical velocity will give us context for what we can achieve in the current sprint and also manage project deadlines and expectations.</p><p>We adopt a Fibonacci sequence for point estimations (1–3–5–8). This is more of a democratic process. The team will typically vote and build consensus around the complexity of an issue.</p><p>We use T-shirt sizes, so a 1 is a small issue, 3 is a medium issue, and a 5 is a large issue. A 1 doesn’t necessarily mean 4 hours of work, some projects are much more complex and a 1 can take longer (or it could take less). If an issue is voted as an 8 or larger, that means it’s our responsibility as a project manager to break it down into smaller iterative chunks.</p><h3>Principle #4 — Use Kanban Boards to Harmonize Your Sprints</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ecxj6GERwX99cpIgOv9weQ.jpeg" /></figure><p>Every <a href="https://leankit.com/learn/kanban/kanban-board-examples-for-development-and-operations/">Kanban project board</a> goes from right to left, so this represents the flow of development:</p><ul><li>Always look top to bottom for priorities.</li><li>QA review means it’s done and ready for user testing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PnhJri1qoL3TIzl_3cYodw.png" /></figure><h3>Principle #5 — Create Your User Stories to Answer “Why Are We Building This?”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wadrx_Qbh32j_Ox0aJgxBg.jpeg" /></figure><p><a href="https://searchsoftwarequality.techtarget.com/definition/user-story">User stories</a> are ways to describe features that customers might like to see in their software. A user story describes the type of user, what they want, and why. In other words, user stories are a starting point to a conversation that establishes the real product requirement.</p><p>But why can’t we just give a simple statement for what to create instead? Well, here are some examples of why that does not provide the same information and flexibility as a user story.</p><p>User stories are useful exercises. They help ensure you’re writing stories that deliver value (if you can’t achieve a value statement, check if you have a really good user story). The stories remind engineers about “Why are we building this?” If you can’t write it as a good user story, is it ready for development?</p><h3>Principle #6 — Measure Progress (Sprints, Tracking Velocity, and Burndowns)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qd0yeb7YEnaoXPCfL473UQ.jpeg" /></figure><p>It’s important to know how we measure progress. We’re using GitLab to setup sprints, which is how we track our sprints. We will add issues to each sprint and monitor the progress, so you can see the burndown chart for the sprint fix. GitLab serves as a good little analytics tool for tracking your burndown.</p><p><strong>Tracking Velocity and Burndown</strong> — Shows where you are in a sprint and where you should be. We track points closed for every sprint (i.e. two weeks). Sprint 1: 10 points. Sprint 2: 15 points. Sprint 3: 7 points. By using a rolling average (i.e. right now it is ~10 points), that’s what we expect to see in our current sprint. Velocity becomes a lot more valuable after a few sprints by helping us understand what’s working and what’s not, as well as give an estimate for how much work we are on track to complete per sprint and beyond.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*a6AAgrgUt413Jv1rXDi6PQ.png" /></figure><p><strong>Reprioritizing Tasks</strong> — If tasks don’t get done, they roll over into the next sprint and get reprioritized. But it’s very rare if we haven’t finished something that I would deprioritize it because it was prioritized for a reason (so we just continue on to the next sprint handling that issue).</p><h3>Principle #7 — Host Retros</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luSbKlpd_Hx6SkfaZvXQ2w.jpeg" /></figure><p>Each recurring meeting is an important part of Agile development. While in pure Scrum all meetings are held within a sprint, one of the meetings we do after is called a retrospective, or a “retro.” A retro allows the team to reflect on what we did really well, what we did not do so well, and how we can improve.</p><p>It’s an internal meeting because we want the team to feel they’re in a safe place to share their thoughts about progress or things that have hindered them. It’s kind of a knowledge-sharing session where we talk about process improvements.</p><h3>Principle #8 — Communicate Early, Often, and Consistently</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BO8Om98n1zI4xVntRbw9Kg.jpeg" /></figure><p>We send weekly updates to clients, and they can always access us on Slack. We want them to know they can communicate with us directly whenever they need to. We also host a bi-weekly meeting, usually in-person, with the client where we demo our progress and elicit feedback.</p><p>Our meetings often turn into a prioritization meeting. We discuss what was done, we show-and-tell features, we have them test live with us, we get some feedback in real-time, and we put together a game plan for future sprints.</p><h3>Wrap Up</h3><p>In the “old days” of waterfall software development, user features were scoped out upfront, requirements identified, and then everything was handed to engineering teams who would deliver back, after several months, a complete app that everyone was sure the customer would love. But without testing and iterating on feedback during the process, the “finished product” would often land far off the mark.</p><p>Agile has become the prescribed framework and methodology for building innovative digital products that customers love. The Agile process is comprised of a complex series of iterations, sprints, and stories, organized sequentially to identify and solve clients’ business problems.</p><p>—</p><p><em>Special thanks to Matt Chen for edits and revisions to this article.</em></p><p><em>Originally published at </em><a href="https://foxbox.co/blog/better-products-agile-scrum/"><em>https://foxbox.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a56f626533" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/agile-scrum-how-to-build-better-products-faster-in-2020-6a56f626533">Agile &amp; Scrum: How to Build Better Products, Faster in 2020</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>