<?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 Stephen Settle on Medium]]></title>
        <description><![CDATA[Stories by Stephen Settle on Medium]]></description>
        <link>https://medium.com/@ssettle3?source=rss-eb492fa399a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*c2nZY2WLak3jF9jn</url>
            <title>Stories by Stephen Settle on Medium</title>
            <link>https://medium.com/@ssettle3?source=rss-eb492fa399a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:21:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ssettle3/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[Terminal Management with Tmux Enhanced by Tmuxinator]]></title>
            <link>https://medium.com/salesloft-engineering/terminal-management-with-tmux-enhanced-by-tmuxinator-61ca93e9cd8a?source=rss-eb492fa399a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/61ca93e9cd8a</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[tmux]]></category>
            <category><![CDATA[tmuxinator]]></category>
            <dc:creator><![CDATA[Stephen Settle]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 18:24:31 GMT</pubDate>
            <atom:updated>2019-09-24T18:40:32.354Z</atom:updated>
            <content:encoded><![CDATA[<p>When a software company continues to grow, thrive, expand and build new things; the development environment gets increasingly difficult to manage and organize. New teams spin up new microservices that handle X, Y, and Z. As a developer, I need those microservices running to complete the feature I am working on. Pretty soon my terminal window can turn from this,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KKVNeVHDwyL8oHB7" /></figure><p>to this,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q5m6vTTOgXYSWIae" /></figure><p>or this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eZ15DaSiGPkhYZyH" /></figure><p>[This] can quickly become overwhelming and confusing; trying to figure out which window is which service and then navigating to the one you had originally sought out can be frustrating and annoying.</p><p>Luckily for you and me, other people have created a solution that greatly helps organize the chaos of development environments using Tmux and Tmuxinator. I want to share how I use these tools to keep my terminal organized and well maintained.</p><p><a href="https://github.com/tmux/tmux">Tmux</a> is a “terminal multiplexer: it enables a number of terminals to be created, accessed, and controlled from a single screen”. It can easily installed with <a href="https://brew.sh/">brew</a>. Once installed, creating a new tmux session can be done via tmux new. This will create an unnamed session (not the most useful thing in my opinion). Once created you will be immediately thrown into that session. It is easy to know if you are in a tmux session as it will have a bright green bar towards the bottom of the terminal window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IwX3k4j_5HORUDcL" /></figure><p>To “get out” or detach (official term) you need to perform what’s called the prefix command; ctrl+b d Overtime its best to just memorize this command, and will just happen naturally over time using tmux.</p><p>Let’s take it one step further in the right direction and create a named tmux session via</p><p>tmux new -t ‘name-of-session’. This way when you run the command to list all your sessions tmux ls, they are easily distinguishable and easy to find!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dFbIyhTz-Er8wgY-" /></figure><p>Now that you have your list of services here simply attach to one of them with the command</p><p>tmux attach -t ‘name-of-session’, and boom you are now in your tmux session. From there you can start your server, run tests, make commits, etc.</p><p>Something that I have done that has made things even faster when messing around tmux is creating shell aliases for each of the tmux commands! For example, tmux attach -t ‘name-of-session’ simply becomes</p><p>ta ‘name-of-session’ via the alias I created in my shell config alias ta=”tmux attach -t $1”</p><p>One last command that I find very useful is the command to navigate between tmux sessions without having to detach from the current one and reattach to another. Always be tmuxing!</p><p><strong><em>ctrl + b (</em></strong><em> , </em>OR <strong><em>ctrl + b )</em></strong> will take to the next session or the previous session that you have running. You can easily know which session you are by looking at the green bar to see the name of your session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*HCo-cuqpYoe4R1xc" /></figure><p>Feel free to go take a look <a href="https://tmuxcheatsheet.com/">https://tmuxcheatsheet.com/</a> for even more commands that you can use to empower you and your use of tmux.</p><p>If you are sitting there thinking this is great, but I still have to run all my servers and start everything manually — let me take you to part 2 — Tmuxinator!</p><p>Tmuxinator is a simple tool that allows you to spin up tmux sessions coupled with creating one or more panes and executing commands for those panes automagically!</p><p>Installation and setup are straight forward <a href="https://github.com/tmuxinator/tmuxinator">https://github.com/tmuxinator/tmuxinator</a>. Once complete the command `mux` is given to you in your shell. From there you are able to create new tmuxinator projects via mux new ‘name-of-project’ and the way tmuxinator works is via .yml files. This command will generate a new .yml stubbed out with various bits of information.</p><p>The important things to take note of are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/257/0*azbhh3cwmyYZW5YQ" /></figure><p>Name is obviously the name of the project. Root is where the tmuxinator project will cd into before creating windows and/or panes. Windows define the quantity of windows you want to create in the tmux session and what you want each window or pane to do in that session. You can get however simple or complex you want. Attach is whether you want to detach the session from your terminal into the background or keep it in the foreground. For me I always detach, as the point of the endeavor for me was to simplify and organize my terminal!</p><p>If you want more than one pane in your tmux session just slightly alter your .yml project file to specify how many panes you want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/265/0*AeSnrUOE4NIjnuxx" /></figure><p>Once you define all your tumixator project yml files you can simply run them by running the following command</p><p>mux start ‘name-of-project’.</p><p>This way all you’ve got to do is run those commands and everything will start for you!</p><p>There is one last thing I would like to share that will help speed things up even more! Currently to start your projects you have to run a single command for each project. So 6 projects would be 6 commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*iH-r_PgiMUkdaTZ2" /></figure><p>The way I would do this is by creating a shell alias that will call start on all of my projects:</p><p>alias start_projects=”mux start project1 &amp;&amp; mux start project2 &amp;&amp; mux start project3”.</p><p>One thing to note about this: If these projects consume a lot of memory and your machine doesn’t have that much to spare, you may not want to do this. Spinning up x number of projects simultaneously may cause your computer to hang up.</p><p>So there you have it. I hope you start using tmux with tmuxinator — it has increased my productivity and helped me stay sane while dealing with the many microservices that we have at SalesLoft.</p><p><em>Stephen Settle is a senior software engineer at SalesLoft on our email integrations team and our resident action movie connoisseur. You can find him at a theater watching the latest, greatest Marvel movie (Marvel &gt;&gt;&gt; DC; don’t @ him).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61ca93e9cd8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesloft-engineering/terminal-management-with-tmux-enhanced-by-tmuxinator-61ca93e9cd8a">Terminal Management with Tmux Enhanced by Tmuxinator</a> was originally published in <a href="https://medium.com/salesloft-engineering">Salesloft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adding React To Angular Using Storybook]]></title>
            <link>https://medium.com/salesloft-engineering/adding-react-to-angular-using-storybook-dfbe85114298?source=rss-eb492fa399a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfbe85114298</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[storybook]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Stephen Settle]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 17:49:32 GMT</pubDate>
            <atom:updated>2018-07-27T17:49:32.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBCGa800fXcDOPmq6MQwXg.png" /></figure><p>Here at SalesLoft, we are actively migrating our AngularJS app to a React app. The process of combining one front-end framework with another, while gradually removing the first can be pretty tricky. One tool that makes the refactoring easier is <a href="https://storybook.js.org/">Storybook</a>. The following rant will be my findings and knowledge of how to add React to angular using Storybook.</p><blockquote>This post is not about how to write React or Angular, it’s about how to integrate them together!</blockquote><p>Step one is getting your React code into an AngularJS app in a semi-elegant fashion. The first thing is to create an angular component. This will serve as your ‘container’ for your react component. Here you will declare its props; functions, booleans, and anything else the component needs to render. Now I imagine you are thinking “why would I write more code to do this? Why can’t I just do all that in the angular controller?” Because hopefully in doing so, you cut functions and logic from it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7kxjHzRMN2v_Rwq9" /></figure><p>There’s nothing better than looking at your controller’s diff (pictured above) and watch how it decreases in complexity by removing code instead of polluting it by declaring props or any specific or new function that the React component will need. This is very important especially when you build multiple React components and put them within the same angular template. It greatly helps reduce complexity and confusion. When you are dealing with brand spanking new controllers it’s even easier to keep them clean.</p><p>Step two, is leveraging Storybook. Using Storybook is not only super cool, but also allows you to develop React components faster. On a high level, you can build full React components in isolation — meaning they run on a different port than your application. This makes Storybook <em>WAY</em> faster to code and easier to view the components you make. Another great benefit of using Storybook is that you can create all the various states that a component could be in by passing various stubbed props to the component. Take a look at the screenshot below. Other than importing React and Storybook into the file the file itself only has two things in it; a function helper to define props and the stories themselves!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/0*T7EMjtzteSMXTU6r" /></figure><p>Inside of the storybook UI you can switch back and forth between these different states with just a click! (pictured below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/0*Jp1taPx_0RxGKbuJ" /></figure><p>Being able to develop your React components and all of their various states without having to set that “scenario” up in your application is huge and helps increase speed and productivity. As I stated above, Storybook runs separately from your app to ensure that your components are completely independent of your application’s styles and javascript so you can truly create reusable React components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/0*l0FV2EOE44XRMk_T" /></figure><p>Well, there you have it! I hope that gives you all some perspective on how I attack integrating React into AngularJS using Storybook. If anyone has any questions I would love to hear from you! Leave a comment or question to start the conversation.</p><p><em>Stephen Settle is a software engineer at SalesLoft on our email integrations team and our resident action movie connoisseur. You can find him at a theater watching the latest, greatest Marvel movie (Marvel &gt;&gt;&gt; DC; don’t @ him).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfbe85114298" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesloft-engineering/adding-react-to-angular-using-storybook-dfbe85114298">Adding React To Angular Using Storybook</a> was originally published in <a href="https://medium.com/salesloft-engineering">Salesloft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>