<?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 Devin Robichaux on Medium]]></title>
        <description><![CDATA[Stories by Devin Robichaux on Medium]]></description>
        <link>https://medium.com/@devinrobichaux?source=rss-952cdc6d52a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oEN0-ldw6lxB4AIHMBAzMQ@2x.jpeg</url>
            <title>Stories by Devin Robichaux on Medium</title>
            <link>https://medium.com/@devinrobichaux?source=rss-952cdc6d52a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:48:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@devinrobichaux/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[What Impact Will A Website Redesign Have On My Business?]]></title>
            <link>https://medium.com/@devinrobichaux/what-impact-will-a-website-redesign-have-on-my-business-600065358efd?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/600065358efd</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Fri, 17 May 2019 17:03:55 GMT</pubDate>
            <atom:updated>2019-05-17T17:03:55.827Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*rLShhhEZN-cNt5ugdOnAPQ@2x.jpeg" /></figure><p>As a developer focused on web design, I hear this question a lot. And I get it — a website redesign requires time, money, and resources. Your business wants to be assured that your investment will have a definite effect on your business — that the investment is worth it.</p><p>What influence will a redesign have on my business? So, here’s my answer:</p><p>While it’s tough to predict the exact ROI a redesign will generate, a brand new website (done well) will result in a host of advantages, including a boost in search engine ranking and the generation of interest from potential clients and customers. Prospects and customers will react adversely to an optimised website, and we often see a positive impact on a company’s bottom line due to the resulting factors (seen below).</p><h4>Impact a redesign can have on a business:</h4><ul><li>Search visibility — Improved SEO can be a meaningful advantage to a website redesign. We often see an uptick in search rankings as a result of a site refresh. Search engines like Google love new content and updated websites. Freshness is a factor in search results, and a website redesign often requires updating the content structure and mobile responsiveness. These changes can help quicken growth in search engines, which can have a clear and substantial benefit in lead generation, brand clarity and sales.</li><li>Build trust with clients and supporters — A new website shows growth and makes people see your business as viable, vibrant and relevant. Although this impact on judgment may seem soft, the change in perception will have an increase in confidence, which can directly impact lead generation, sales and competitiveness.</li><li>Accessibility and user-experience — Technology and trends develop swiftly. Websites will naturally fall out of sync with the advances in technology. Any company that launched their website in a pre-mobile-responsiveness time will understand this. A website redesign helps modernise your business website and allows it to meet the requirements and behaviours of users today. Mobile responsiveness alone can expand your potential audience, decrease bounce rate and increase customer/lead outreach.</li><li>Higher conversion rate — As you upgrade your website, your company has an opportunity to learn from the past. By studying web analytics, you can learn what content, calls-to-action and pages help drive users to a sale. Consider redesigning calls-to-action, change the presentation of value propositions, and improve the alignment of offers. With a web design project, your company has a chance to radically upgrade your conversion rate — allowing for increased leads, partnerships, sales and revenue.</li></ul><p>‍</p><p>The key to ensuring an impressive ROI on your website redesign is to concentrate on the characteristics customers care most about — because that is what will have the greatest impact.</p><p>If you enjoyed reading this blog, please leave a like and follow! More content to come!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=600065358efd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Advantages Of Having A Website For Your Business]]></title>
            <link>https://medium.com/@devinrobichaux/7-advantages-of-having-a-website-for-your-business-97399a2a08e7?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/97399a2a08e7</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[small-business-marketing]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Fri, 17 May 2019 16:58:39 GMT</pubDate>
            <atom:updated>2019-05-17T21:16:14.632Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/327/1*JbNNgumYwsuPXSyO4d9I3g@2x.jpeg" /></figure><p>Do you have a business and not a website to go with it? If you said yes, the most likely scenario is that your business won’t survive. In this modern era, people are on the internet for information and to find things out. Why do you think people visit a website? It’s primarily to find out information. And if you’re in the business world, information is critical. A website is a must thing for your clients and customers. It needs to contain information about what you can do for them and how you can do it. Read on to find out a few of the advantages of having a website for your business.</p><h4>Less Expensive</h4><p>Have you ever promoted your business through various forms such as printed media, radio or by other means? It’s expensive! Investing in advertising is essential, but it requires a lot of capital. Having a website will make advertising your business less expensive.</p><h4>Advertising</h4><p>A website is more environmentally friendly when it comes to advertising and marketing. There are many ways to promote your products or services online. One example is Facebook ads, an advertising feature provided through Facebook. Another one is called SEO, short for Search Engine Optimisation. This is a major benefit for your business. Having good SEO can boost the ranking of your website which quickly results in increased sales and larger profits.</p><h4>Accessibility</h4><p>Have you ever encountered having to turn customers or clients away because it’s closing time? Well, you don’t have to shut the doors of your website. A website can be visited at any time of the day or night. People will look to your site instead of going to your shop because it is more convenient. Just make sure to put out enough information about your products and services.</p><h4>Increase Sales</h4><p>If you are a business owner, more traffic leads to more potential sales. That’s how your website will benefit you. You can drive more people to your website by consistently refreshing and advertising the contents of your site. The more informative your site has, the greater the possibility of increasing your sales.</p><h4>Opportunity</h4><p>A website provides you the opportunity to prove your credibility and reliability. You have to show your customers why you deserve their trust through your site. This can receive positive feedback for your service and products.</p><h4>Satisfaction</h4><p>Having a website will be more convenient for your customers and clients. Make it simple enough for your customers to purchase from you! Many will be more inclined to visit your website, rather than travelling to your physical location. From a customer’s point of view, it’s better for them if they don’t have to ask anything. They can just find what they’re searching for on your website.</p><h4>Access to Info</h4><p>Did you know that if you have a website, you can actually track most things that are happening on it? You can even look for information that will tell you how many people visited your site, or how many people messaged or emailed you. You can access the growth of your website and view the metrics for each page. You can even make a change anytime, making it much cheaper than printed material.</p><p>In conclusions, it is mission critical to establish a digital footprint for your business or brand to properly engage consumers or clients in this new era of technology. Those who ignore these very simple but important concepts are sure to face the same fate of those in history that have drowned in the wave change rather than riding it.</p><p>If you enjoyed reading this blog please give me a like and share. More content on the way!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97399a2a08e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps 101: Git Branching]]></title>
            <link>https://medium.com/@devinrobichaux/devops-101-git-branching-880f46fb4139?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/880f46fb4139</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[jenkins]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Tue, 05 Jun 2018 15:05:31 GMT</pubDate>
            <atom:updated>2018-06-05T15:05:31.981Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-PvXkWHU22azT2HkN42hFw.jpeg" /></figure><p>Why DevOps? Faster deployments and feedback loops get to the heart of what developers want: code gets from their laptops into users’ hands much faster and continuous delivery enables rapid iteration and improvement. There are certain strategies and practices that make this process less daunting and intimidating. I will share some of the strategies and practices that I integrated into our culture to make CI/CD a breeze.</p><p>As a consequence of its simplicity and repetitive nature, branching and merging are no longer something to be afraid of. Version/Release control tools are supposed to assist in branching/merging more than anything else.</p><p>Enough about the tools, let’s head onto the development model. The model that I’m going to present here is essentially no more than a set of procedures that every team member has to follow in order to come to a managed software development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRBcvzItnywMnNWgRyDqqA.png" /><figcaption><strong>Decentralized but centralized</strong></figcaption></figure><p>The repository setup that we use and that works well with this branching model, is that with a central “truth” repo. Note that this repo is only <em>considered</em> to be the central one (since Git is a DVCS, there is no such thing as a central repo at a technical level). We will refer to this repo as origin since this name is familiar to all Git users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*XJCXW17fsK98oYxBPzGcCw.png" /></figure><p>Each developer pulls and pushes to origin. But besides the centralized push-pull relationships, each developer may also pull changes from other peers to form sub teams. For example, this might be useful to work together with two or more developers on a big new feature, before pushing the work in progress to origin prematurely. In the figure above, there are sub teams of Alice and Bob, Alice and David, and Clair and David.</p><p>Technically, this means nothing more than that Alice has defined a Git remote, named bob, pointing to Bob’s repository, and vice versa.</p><p><strong>The main branches</strong></p><p>At the core, the development model is greatly inspired by existing models out there. The central repo holds two main branches with an infinite lifetime:</p><ul><li>master</li><li>develop</li></ul><p>The master branch at origin should be familiar to every Git user. Parallel to the master branch, another branch exists called develop.</p><p>We consider origin/master to be the main branch where the source code of HEAD always reflects a <em>production-ready</em> state.</p><p>We consider origin/develop to be the main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release. Some would call this the “integration branch”. This is where any automatic nightly builds are built from.</p><p>When the source code in the develop branch reaches a stable point and is ready to be released, all of the changes should be merged back into master somehow and then tagged with a release number. How this is done in detail will be discussed further on.</p><p>Therefore, each time when changes are merged back into master, this is a new production release <em>by definition</em>. We tend to be very strict at this, so that theoretically, we could use a Git hook script to automatically build and roll-out our software to our production servers everytime there was a commit on master.</p><p><strong>Supporting branches</strong></p><p>Next to the main branches master and develop, our development model uses a variety of supporting branches to aid parallel development between team members, ease tracking of features, prepare for production releases and to assist in quickly fixing live production problems. Unlike the main branches, these branches always have a limited life time, since they will be removed eventually.</p><p>The different types of branches we may use are:</p><ul><li>Feature branches</li><li>Release branches</li><li>Hotfix branches</li></ul><p>Each of these branches have a specific purpose and are bound to strict rules as to which branches may be their originating branch and which branches must be their merge targets. We will walk through them in a minute.</p><p>By no means are these branches “special” from a technical perspective. The branch types are categorized by how we <em>use</em> them. They are of course plain old Git branches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*gFUL2Xc0L10SIpOnewgHJQ.png" /></figure><p><strong>Feature branches</strong></p><p>May branch off from:</p><pre>develop</pre><p>Branch naming convention:</p><pre>anything except master, develop, release-*</pre><p>Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into develop (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment).</p><p>Feature branches typically exist in developer repos only, not in origin.</p><p><strong>Creating a feature branch</strong></p><p>When starting work on a new feature, branch off from the develop branch.</p><pre># git checkout -b myfeature develop</pre><pre>Switched to a new branch &quot;myfeature&quot;</pre><p><strong>Incorporating a finished feature on develop</strong></p><p>Finished features may be merged into the develop branch to definitely add them to the upcoming release:</p><pre># git checkout develop</pre><pre>Switched to branch &#39;develop&#39;</pre><pre># git merge --no-ff myfeature</pre><pre>Updating ea1b82a..05e9557</pre><pre>(Summary of changes)</pre><pre># git branch -d myfeature</pre><pre>Deleted branch myfeature (was 05e9557).</pre><pre># git push origin develop</pre><p>The –no-ff flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature. Compare:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*5iR6CAYpTy7NzDAnP1ET2w.png" /></figure><p>In the latter case, it is impossible to see from the Git history which of the commit objects together have implemented a feature — you would have to manually read all the log messages. Reverting a whole feature (i.e. a group of commits), is a true headache in the latter situation, whereas it is easily done if the –no-ff flag was used.</p><p>Yes, it will create a few more (empty) commit objects, but the gain is much bigger than the cost.</p><p><strong>Release branches</strong></p><p>May branch off from:</p><pre>develop</pre><p>Must merge back into:</p><pre>develop and master</pre><p>Branch naming convention:</p><pre>release-*</pre><p>Release branches support preparation of a new production release. They allow for last-minute dotting of i’s and crossing t’s. Furthermore, they allow for minor bug fixes and preparing meta-data for a release (version number, build dates, etc.). By doing all of this work on a release branch, the develop branch is cleared to receive features for the next big release.</p><p>The key moment to branch off a new release branch from develop is when develop (almost) reflects the desired state of the new release. At least all features that are targeted for the release-to-be-built must be merged in to develop at this point in time. All features targeted at future releases may not — they must wait until after the release branch is branched off.</p><p>It is exactly at the start of a release branch that the upcoming release gets assigned a version number — not any earlier. Up until that moment, the develop branch reflected changes for the “next release”, but it is unclear whether that “next release” will eventually become 0.3 or 1.0, until the release branch is started. That decision is made on the start of the release branch and is carried out by the project’s rules on version number bumping.</p><p><strong>Creating a release branch</strong></p><p>Release branches are created from the develop branch. For example, say version 1.1.5 is the current production release and we have a big release coming up. The state of develop is ready for the “next release” and we have decided that this will become version 1.2 (rather than 1.1.6 or 2.0). So we branch off and give the release branch a name reflecting the new version number:</p><pre># git checkout -b release-1.2 develop</pre><pre>Switched to a new branch &quot;release-1.2&quot;</pre><pre># ./bump-version.sh 1.2</pre><pre>Files modified successfully, version bumped to 1.2.</pre><pre># git commit -a -m &quot;Bumped version number to 1.2&quot;</pre><pre>[release-1.2 74d9424] Bumped version number to 1.2</pre><pre>1 files changed, 1 insertions (+), 1 deletions (-)</pre><p>After creating a new branch and switching to it, we bump the version number. Here, bump-version.sh is a fictional shell script that changes some files in the working copy to reflect the new version. (This can of course be a manual change — the point being that <em>some</em> files change.) Then, the bumped version number is committed.</p><p>This new branch may exist there for a while, until the release may be rolled out definitely. During that time, bug fixes may be applied in this branch (rather than on the develop branch). Adding large new features here is strictly prohibited. They must be merged into develop, and therefore, wait for the next big release.</p><p><strong>Finishing a release branch</strong></p><p>When the state of the release branch is ready to become a real release, some actions need to be carried out. First, the release branch is merged into master (since every commit on master is a new release <em>by definition</em>, remember). Next, that commit on master must be tagged for easy future reference to this historical version. Finally, the changes made on the release branch need to be merged back into develop, so that future releases also contain these bug fixes.</p><p>The first two steps in Git:</p><pre># git checkout master</pre><pre>Switched to branch &#39;master&#39;</pre><pre># git merge --no-ff release-1.2</pre><pre>Merge made by recursive.</pre><pre>(Summary of changes)</pre><pre># git tag -a 1.2</pre><p>The release is now done and tagged for future reference.</p><p><strong>Edit:</strong> You might as well want to use the -s or -u &lt;key&gt; flags to sign your tag cryptographically.</p><p>To keep the changes made in the release branch, we need to merge those back into develop, though. In Git:</p><pre># git checkout develop</pre><pre>Switched to branch &#39;develop&#39;</pre><pre># git merge --no-ff release-1.2</pre><pre>Merge made by recursive.</pre><pre>(Summary of changes)</pre><p>This step may well lead to a merge conflict (probably even, since we have changed the version number). If so, fix it and commit.</p><p>Now we are really done and the release branch may be removed, since we don’t need it anymore:</p><pre># git branch -d release-1.2</pre><pre>Deleted branch release-1.2 (was ff452fe).</pre><p><strong>Hotfix branches</strong></p><p>May branch off from:</p><pre>master</pre><p>Must merge back into:</p><pre>develop and master</pre><p>Branch naming convention:</p><pre>hotfix-*</pre><p>Hotfix branches are very much like release branches in that they are also meant to prepare for a new production release, albeit unplanned. They arise from the necessity to act immediately upon an undesired state of a live production version. When a critical bug in a production version must be resolved immediately, a hotfix branch may be branched off from the corresponding tag on the master branch that marks the production version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*c-5X7TwntUlB9VTYArVbtA.png" /></figure><p>The essence is that work of team members (on the develop branch) can continue, while another person is preparing a quick production fix.</p><p><strong>Creating the hotfix branch</strong></p><p>Hotfix branches are created from the master branch. For example, say version 1.2 is the current production release running live and causing troubles due to a severe bug. But changes on develop are yet unstable. We may then branch off a hotfix branch and start fixing the problem:</p><pre># git checkout -b hotfix-1.2.1 master</pre><pre>Switched to a new branch &quot;hotfix-1.2.1&quot;</pre><pre># ./bump-version.sh 1.2.1</pre><pre>Files modified successfully, version bumped to 1.2.1.</pre><pre># git commit -a -m &quot;Bumped version number to 1.2.1&quot;</pre><pre>[hotfix-1.2.1 41e61bb] Bumped version number to 1.2.1</pre><pre>1 files changed, 1 insertions(+), 1 deletions(-)</pre><p>Don’t forget to bump the version number after branching off!</p><p>Then, fix the bug and commit the fix in one or more separate commits.</p><pre># git commit -m &quot;Fixed severe production problem&quot;</pre><pre>[hotfix-1.2.1 abbe5d6] Fixed severe production problem</pre><pre>5 files changed, 32 insertions(+), 17 deletions(-)</pre><p><strong>Finishing a hotfix branch</strong></p><p>When finished, the bugfix needs to be merged back into master, but also needs to be merged back into develop, in order to safeguard that the bugfix is included in the next release as well. This is completely similar to how release branches are finished.</p><p>First, update master and tag the release.</p><pre># git checkout master</pre><pre>Switched to branch &#39;master&#39;</pre><pre># git merge --no-ff hotfix-1.2.1</pre><pre>Merge made by recursive.</pre><pre>(Summary of changes)</pre><pre># git tag -a 1.2.1</pre><p><strong>Edit:</strong> You might as well want to use the -s or -u &lt;key&gt; flags to sign your tag cryptographically.</p><p>Next, include the bugfix in develop, too:</p><pre># git checkout develop</pre><pre>Switched to branch &#39;develop&#39;</pre><pre># git merge --no-ff hotfix-1.2.1</pre><pre>Merge made by recursive.</pre><pre>Summary of changes)</pre><p>The one exception to the rule here is that, <strong>when a release branch currently exists, the hotfix changes need to be merged into that release branch, instead of develop</strong>. Back-merging the bugfix into the release branch will eventually result in the bugfix being merged into develop too, when the release branch is finished. (If work in develop immediately requires this bugfix and cannot wait for the release branch to be finished, you may safely merge the bugfix into develop now already as well.)</p><p>Finally, remove the temporary branch:</p><pre># git branch -d hotfix-1.2.1</pre><pre>Deleted branch hotfix-1.2.1 (was abbe5d6).</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=880f46fb4139" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native for Dummies: Get Started With Your First React Native Application.]]></title>
            <link>https://medium.com/front-end-weekly/react-native-for-dummies-b02c4a603687?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b02c4a603687</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 31 Jan 2018 13:06:01 GMT</pubDate>
            <atom:updated>2018-01-31T15:37:46.049Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why React Native</h3><p>React Native is is a framework that enables you to build cross-platform mobile applications using React and JavaScript. It enables you to use the same components on iOS and Android platforms. The UI components can also be customized for each platform.</p><h3>What we will be building</h3><p>This guide would walk you through building a to-do application in React Native with features like:</p><ul><li>Adding a new to-do item.</li><li>Deleting a to-do item.</li><li>Marking a to-do item as done and undone.</li></ul><h3>Before you begin</h3><p>Follow the instructions <a href="https://facebook.github.io/react-native/docs/getting-started.html">here</a> to set up your React Native development environment for your development OS (macOS, Windows, or Linux) and target OS (iOS or Android).</p><h3>Tools used.</h3><ul><li>React Native: This will be used to build our mobile application (iOS or Android) in JavaScript.</li><li>React Native Vector Icons: This contains icons that will be used in our React Native mobile application.</li></ul><h3>Project setup.</h3><p>Navigate to a specific directory on your machine and run the following commands to generate a new React Native project.</p><pre>react-native init todo</pre><p>Navigate to the project directory and start your React Native application by running the following command. Ensure you have your virtual device or emulator running.</p><pre>cd todo<br>react-native run-android</pre><p>If all things worked properly, you should have a screen like this displayed on your Android emulator or device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/0*h4YBD1YvTBANlyL4." /></figure><p>Create the src directory containing the components and styles subfolder.</p><p>The components folder will contain all of our React components while the styles folder will contain all of our stylings for the components.</p><pre>mkdir -p src/{components,styles}</pre><h3>Adding new to-do items</h3><p>Create a todoStyles.js file in the src/styles directory. This will contain all of the styles for our Todo component that we will create later. Add the code below to the file.</p><p>src/styles/todoStyles.js</p><pre>import { StyleSheet } from &#39;react-native&#39;;<br><br>const styles = StyleSheet.create({<br>  container: {<br>    flex: 1,<br>    flexDirection: &#39;column&#39;,<br>    padding: 10,<br>    backgroundColor: &#39;white&#39;<br>  },<br>  inputContainer: {<br>    height: 50<br>  },<br>  separator: {<br>    borderBottomColor: &#39;#d1d0d4&#39;,<br>    borderBottomWidth: 1<br>  }<br>});<br><br>export default styles;</pre><p>Create a todo.js file in the src/components directory and add the code below to the file.</p><p>src/components/todo.js</p><pre>import React, { Component } from &#39;react&#39;;<br>import { TextInput, View } from &#39;react-native&#39;;<br>import styles from &#39;../styles/todoStyles&#39;;<br><br>class Todo extends Component {<br>    constructor(props) {<br>        super(props);<br>        this.state = {<br>          text: &#39;&#39;,<br>          todos: []<br>        };<br>      }<br>      onSubmit = () =&gt; {<br>        if (this.state.text) {<br>          this.setState(prevState =&gt; ({<br>            text: &#39;&#39;,<br>            todos: [...prevState.todos,<br>              { title: prevState.text, done: false }]<br>          }));<br>          this.textInput.setNativeProps({ text: &#39;&#39; });<br>        }<br>      }<br>    render () {<br>        return (<br>        &lt;View style={styles.container} &gt;<br>            &lt;TextInput<br>              selectionColor=&quot;black&quot;<br>              underlineColorAndroid=&quot;black&quot;<br>              placeholder=&quot;What needs to be done&quot;<br>              onChangeText={text =&gt; this.setState({ text })}<br>              onSubmitEditing={this.onSubmit}<br>              ref={(component) =&gt; { this.textInput = component; }}<br>              autoFocus<br>              /&gt;<br>        &lt;/View&gt;<br>        )<br>    }<br>}<br>export default Todo;</pre><p>The todo.js file will contain most of our application code. The View React Native component acts as the container for other child components.</p><p>The TextInput is a component that enables a user to enter text. The onChangeTextprop on the TextInput takes a function that is called each time the text changes. this.setState({ text }) is called in the anonymous function passed to the onChangeText prop to change the value of the text property in the state of the todo component.</p><p>The onSubmitEditing prop on the TextInput takes a function that is called each time the text is submitted. The onSubmit method in the todo class adds a new to-do item to the todos array in the state and changes the text property in the state to an empty string. An update function is passed to this.setState here because the update/new value of state depends on the current value. It enables us to always access the most updated version of the state.</p><p>A ref was added to the text input to enable us to use setNativeProps props to clear the input every time it is submitted. A ref enables us to directly manipulate elements.</p><p>Replace the contents of the App.js file in the root directory with the code below. This imports our Todo components and renders it as a child of the App component.</p><p>App.js</p><pre>import React from &#39;react&#39;;<br>import {<br>  StyleSheet,<br>  Text,<br>  View<br>} from &#39;react-native&#39;;<br>import Todo from &#39;./src/components/todo&#39;;<br><br>const App = () =&gt;<br>  (<br>    &lt;View style={styles.container}&gt;<br>      &lt;Text style={styles.welcome}&gt;<br>          React Native Todo App<br>      &lt;/Text&gt;<br>      &lt;Todo/&gt;<br>    &lt;/View&gt;<br>  );<br>  <br>const styles = StyleSheet.create({<br>  container: {<br>    flex: 1<br>  },<br>  welcome: {<br>    fontSize: 20,<br>    textAlign: &#39;center&#39;,<br>    margin: 10,<br>  },<br>});<br>export default App;</pre><h3>Displaying our to-do items</h3><p>Create a todoItemStyles.js file in the src/styles directory. This file will contain all of the styles for our TodoItem component which we will create later. Add the code below to the todoItemStyles.js file.</p><p>src/styles/todoItemStyles.js</p><pre>import { StyleSheet } from &#39;react-native&#39;;<br><br>const styles = StyleSheet.create({<br>  container: { flex: 1, flexDirection: &#39;row&#39; },<br>  text: {<br>    flex: 1,<br>    marginHorizontal: 10,<br>    textAlignVertical: &#39;center&#39;,<br>    fontSize: 18<br>  }<br>});<br><br>export default styles;</pre><p>Create a todoItem.js file in the src/components directory. This file will contain the component that would display our to-do items. Add the code below to the file.</p><p>src/components/todoItem.js</p><pre>import React from &#39;react&#39;;<br>import { Text, View, TouchableHighlight } from &#39;react-native&#39;;<br>import styles from &#39;../styles/todoItemStyles&#39;;<br><br>const TodoItem = ({item}) =&gt;<br>  (<br>    &lt;View style={styles.container} &gt;<br>      &lt;Text style={styles.text}<br>      &gt;{item.title}<br>      &lt;/Text&gt;<br>    &lt;/View&gt;<br>  );<br>export default TodoItem;</pre><p>Import our TodoItem component in src/components/todo.js. Import the FlatList React Native element too.</p><pre>...<br>import { TextInput, View, FlatList } from &#39;react-native&#39;;<br>import TodoItem from &#39;../components/todoItem&#39;<br>...</pre><p>Add the FlatList React Native component to the return value of the render method in the Todo class in src/components/todo.js. The Flatlist react-native element would be used to display our list of to-dos.</p><pre>...<br>         &lt;FlatList<br>            ItemSeparatorComponent={this.separator}<br>            data={this.state.todos}<br>            renderItem={this.renderItem}<br>            keyExtractor={this.keyExtractor}<br>          /&gt;<br> ...</pre><p>Add the methods below to the Todo class in src/components/todo.js.</p><pre>...<br> keyExtractor = (item, index) =&gt; index;<br>      <br> separator = () =&gt; &lt;View style={styles.separator} /&gt;;<br>      <br> renderItem = ({ item, index }) =&gt; (<br>            &lt;TodoItem<br>              item={item}<br>              index={index}<br>              markAsDone={this.markAsDone}<br>              onPressRemove={this.onPressRemove}<br>            /&gt;<br>    );<br> ...</pre><p>The renderItem method returns our TodoItem component that is rendered for each item in the todos array in our Todo component&#39;s state. The separator method returns a component that is used to separate each item in the FlatList. The key extractor tells the FlatList view to use the index of the item as unique identifiers of each item in the view.</p><p>Updated src/components/Todo.js</p><pre>import React, { Component } from &#39;react&#39;;<br>import { TextInput, View, FlatList } from &#39;react-native&#39;;<br>import TodoItem from &#39;../components/todoItem&#39;;<br>import styles from &#39;../styles/todoStyles&#39;;<br><br>class Todo extends Component {<br>  constructor(props) {<br>    super(props);<br>    this.state = {<br>      text: &#39;&#39;,<br>      todos: [{ title: &#39;test&#39;, done: false }]<br>    };<br>  }<br>    onSubmit = () =&gt; {<br>      if (this.state.text) {<br>        this.setState(prevState =&gt; ({<br>          text: &#39;&#39;,<br>          todos: [...prevState.todos,<br>            { title: prevState.text, done: false }]<br>        }));<br>        this.textInput.setNativeProps({ text: &#39;&#39; });<br>      }<br>    }<br>    keyExtractor = (item, index) =&gt; index;<br><br>    separator = () =&gt; &lt;View style={styles.separator} /&gt;;<br><br>    renderItem = ({ item, index }) =&gt; (<br>      &lt;TodoItem<br>        item={item}<br>        index={index}<br>      /&gt;<br>    );<br>    render() {<br>      return (<br>        &lt;View style={styles.container} &gt;<br>          &lt;TextInput<br>            selectionColor=&quot;black&quot;<br>            underlineColorAndroid=&quot;black&quot;<br>            placeholder=&quot;What needs to be done&quot;<br>            onChangeText={text =&gt; this.setState({ text })}<br>            onSubmitEditing={this.onSubmit}<br>            ref={(component) =&gt; { this.textInput = component; }}<br>            autoFocus<br>          /&gt;<br>          &lt;FlatList<br>            ItemSeparatorComponent={this.separator}<br>            data={this.state.todos}<br>            renderItem={this.renderItem}<br>            keyExtractor={this.keyExtractor}<br>          /&gt;<br>        &lt;/View&gt;<br>      );<br>    }<br>}<br>export default Todo;</pre><p>Our to-do items should now be visible after they are submitted in the TextInput.<br>Our app on the Android emulator should now look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/0*JKX-lg3ZJAurLyMI." /></figure><h3>Deleting todo items</h3><p>Run the following command to install react-native-vector-icons and link it to our application.</p><pre>npm install --save react-native-vector-icons<br>npm install<br>react-native link</pre><p>We will need to restart our application after this.</p><pre>react-native run-android</pre><p>Add the method below to the Todo class insrc/components/todo.js. This method will handle the removal of to-do items from the todos array in our components state. It filters out the array item with the index passed it as an argument from the todos array in the state.</p><pre>...<br>    onPressRemove = (index) =&gt; {<br>      this.setState(prevState =&gt; ({<br>        todos: prevState.todos.filter((_, i) =&gt; i !== index)<br>      }));<br>    }<br>...</pre><p>Update renderItem method in the todo class to include the onpressRemove property on the TodoItem component.</p><pre>...<br>  renderItem = ({ item, index }) =&gt; (<br>      &lt;TodoItem<br>        item={item}<br>        index={index}<br>        onPressRemove={this.onPressRemove}<br>      /&gt;<br>    );<br> ...</pre><p>Update our todoItem.js file with the code below.</p><pre>import React from &#39;react&#39;;<br>import { Text, View, TouchableHighlight } from &#39;react-native&#39;;<br>import styles from &#39;../styles/todoItemStyles&#39;;<br>import Icon from &#39;react-native-vector-icons/FontAwesome&#39;;<br><br>const TodoItem = ({item, index , onPressRemove}) =&gt;<br>(<br>  &lt;View style={styles.container} &gt;<br>    &lt;Text style={styles.text}<br>    &gt;{item.title}<br>    &lt;/Text&gt;<br>    &lt;TouchableHighlight<br>        onPress={() =&gt; onPressRemove(index)}<br>      &gt;<br>        &lt;Icon name=&quot;remove&quot; size={30} color=&quot;#d75452&quot; /&gt;<br>    &lt;/TouchableHighlight&gt;<br>  &lt;/View&gt;<br>);<br>export default TodoItem;</pre><p>The TouchableHighlight is a React Native element that enables us to handle touches. The TouchableHighlight React Native element onPress prop takes a function that is called each time it is pressed. The Icon from React-Native-vector-Icons enables use of hundreds of customizable icons in our application.</p><p>Save all changes and reload the application. Our application should now look like this. Clicking the remove icon should remove the to-do item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/287/0*VWmnMTrq6H0P7eln." /></figure><h3>Marking to-do items as done</h3><p>Add the method below to the Todo class in src/components/todo.js. This method will change the value of done key of a to-do Item object with a particular index to true or false and update our component&#39;s state.</p><pre>...<br> markAsDone = (index) =&gt; {<br>        this.setState(prevState =&gt; ({<br>          todos: prevState.todos.map((item, i) =&gt; {<br>            if (i === index) {<br>              item.done = !item.done;<br>              return item;<br>            }<br>            return item;<br>          })<br>        }));<br>      }<br>...</pre><p>Update the renderItem method in the Todo class in src/components/todo.js to pass the prop markAsDone to the TodoItem component.</p><pre>...<br> renderItem = ({ item, index }) =&gt; (<br>            &lt;TodoItem<br>              item={item}<br>              index={index}<br>              markAsDone={this.markAsDone}<br>              onPressRemove={this.onPressRemove}<br>            /&gt;<br>          );<br>...</pre><p>Update the todoItem.js with the code below.</p><p>src/components/todoItem.js</p><pre>import React from &#39;react&#39;;<br>import { Text, View, TouchableHighlight } from &#39;react-native&#39;;<br>import Icon from &#39;react-native-vector-icons/FontAwesome&#39;;<br>import styles from &#39;../styles/todoItemStyles&#39;;<br><br>const TodoItem = ({<br>  item, index, onPressRemove, markAsDone<br>}) =&gt;<br>  (<br>    &lt;View style={styles.container} &gt;<br>      &lt;TouchableHighlight<br>        onPress={() =&gt; markAsDone(index)}<br>        underlayColor=&quot;white&quot;<br>      &gt;<br>        { item.done ?<br>        &lt;Icon name=&quot;check-square-o&quot; size={30} color=&quot;#5fb660&quot; /&gt; :<br>        &lt;Icon name=&quot;square-o&quot; size={30} color=&quot;#808080&quot; /&gt;<br>      }<br>      &lt;/TouchableHighlight&gt;<br>      &lt;Text style={[<br>            styles.text, {<br>              textDecorationLine: item.done ? &#39;line-through&#39; : &#39;none&#39;,<br>              color: item.done ? &#39;#808080&#39; : &#39;black&#39;<br>          }]}<br>      &gt;{item.title}<br>      &lt;/Text&gt;<br>      &lt;TouchableHighlight<br>        onPress={() =&gt; onPressRemove(index)}<br>      &gt;<br>        &lt;Icon name=&quot;remove&quot; size={30} color=&quot;#d75452&quot; /&gt;<br>      &lt;/TouchableHighlight&gt;<br>    &lt;/View&gt;<br>  );<br><br>export default TodoItem;</pre><p>A second TouchableHighlight is added here, which is used to mark a to-do item as done.<br>There is conditional rendering being used in this component. It renders the check-square-o Icon when the to-do item is marked as done and renders the square-oicon when the to-do item is marked as undone.</p><p>The text-decoration and color style property of the todoItem text is also changed based on the status of the done property of the to-do item. When the to-do item is done, the text color is gray and the text-decoration is lined-through, otherwise the text-decoration is none and the text color is black.</p><p>Clicking the square-o Icon should mark a to-do item as done and vice versa.</p><p>Once done, our final application should look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/287/0*uQK0PnAEa3UZcNPH." /></figure><h3>Conclusion</h3><p>Our application is now complete! If you have any questions or comments, please add them to the comments section below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b02c4a603687" width="1" height="1" alt=""><hr><p><a href="https://medium.com/front-end-weekly/react-native-for-dummies-b02c4a603687">React Native for Dummies: Get Started With Your First React Native Application.</a> was originally published in <a href="https://medium.com/front-end-weekly">Frontend Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should use React Native on your next cross-platform application.]]></title>
            <link>https://medium.com/@devinrobichaux/why-you-should-use-react-native-on-your-next-cross-platform-application-88bcb7083c6d?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/88bcb7083c6d</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 13:31:01 GMT</pubDate>
            <atom:updated>2018-01-24T13:41:33.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*JR_Y7g40F9HuDP4olQt4aQ.png" /></figure><p>With constant evolution and awe-inspiring innovations in technology, the world of mobile apps is not an exception either and is tremendously changing as well. The boom in the number of smartphone users is triggering huge demand of mobile apps as they are the gateway to achieve maximum outreach. With a huge demand and diversity of users and devices, it is conspicuous that the mobile apps need to be compatible to various platforms i.e. they need to be Cross Platform. The cross platform development allows an app to have same features and functionality on multiple platforms and thus can be termed as the need of the hour.</p><p>React Native is a JavaScript Framework, introduced by Facebook, for writing such cross platform applications. Currently, it supports iOS and Android but has the potential to expand to future platforms as well. In a very short span of time, React Native has gained high popularity. Some of the most popular apps built with React Native include <strong>Facebook Ads Manager,</strong> <strong>Bloomberg, AirBnB, Gyroscope, Myntra, and UberEats. </strong>The major highlights of React Native can be listed as:</p><h3>Native saves time</h3><p>Native apps are the apps that are written in the languages that the platform supports. For example, the native android applications are written in java whereas the native iOS apps are written in Objective-C or swift. Unlike other approaches to write cross platform code, which wrap the JavaScript code in a web view, react native components are independent. It can render mobile UIs for both iOS and Android. Thus, apps written in React Native are needed to be built once and deployed on both iOS and Android.</p><h3>The State Store: Redux</h3><p>Redux is one of the major benefits of React Native. It enables the developer to define a global state for the app. Fetching and management of state with redux is an easy and more sensible option. The global state defined with redux is common to both android and IOS which saves a lot of time and effort.</p><h3>Components</h3><p>Components break the complex User Interface into smaller parts. A simple React Native component looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*P99zTMMzQ9Gnhbc2zxicyQ.png" /></figure><p>The related elements are wrapped into a component. Such components can be used anywhere in the app by simply exporting and importing them. Thus, code can be reused as many times as needed.</p><p>Importing a Component</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*RlzgzvXx4g6IKqUdFY1fUQ.png" /></figure><p>Using an Imported Component</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*JNIS841-9piYTklvBiBrMA.png" /></figure><h3>Hot and Live Reloading</h3><p>Every developer hates re-building or re-deploying the app just for the sake of previewing a one-line UI change. React Native solves this issue with the help of hot reloading and live reloading. Hot reloading refreshes the files that were changed recently, whereas, live reloading refreshes the entire app when any of the files are changed. These concepts save a lot of developer time. I used Expo with React Native and found the experience to be extremely enjoyable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oj3ldt8M3jWu2guqSjU0MA.png" /></figure><p>React Native has both the advantages of native applications (performances, native look and feel) and Web Hybrid applications (reuse web developers skills, fast iteration, real-time preview).</p><p>With React, you can have a single engineer or a team of engineers specialized in cross-platform mobile. The development is fast, and the resulting applications are smooth in iOS and Android with 80% shared code.</p><p>You can also update the already deployed applications in real time with tools like <a href="https://microsoft.github.io/code-push/">CodePush</a>, which is not possible with native apps.</p><h3>Familiar territory for Web Devs</h3><p>For Web developers, the transition from web to mobile app development is hard. But with React Native the transition is quite painless. As React Native is a JavaScript Framework, Web Developers can easily build mobile applications with it. They will enjoy a steep learning curve with React Native thanks to their familiarity with JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NwJUH1wRt1t6CM3xkCv0Kw.png" /></figure><h3>Look and Feel</h3><p>React Native gives a consistent and native look-and-feel to the apps i.e. the User Interface of a react native app is not any different for Android and iOS from the native platform apps.</p><h3>Use Native APIS</h3><p>Coding in Javascript does not mean you do not get to use native API or native widgets. Actually, each React Javascript component uses a specific bridged module on the native side.</p><p>Some API/Widgets are already available in the React Native framework. The React Native ecosystem is growing every day and when you need to use some API or Widgets that do not exist in the base Framework you will easily <a href="https://www.native.directory/">find an open source project to fulfill your needs</a>..</p><h3>Conclusion</h3><p>The popularity of React Native is growing very fast and so is the community. In the future, many advancements in the framework will be witnessed for sure. In the end, we can say that React Native has a bright future in cross platform mobile application development.</p><p>Users are very demanding about applications. They expect responsive, smooth experience and reliable apps. When it doesn’t work the first or second time, they will delete your app immediately or never open it anymore.</p><p>So which framework or technology should you use next? Unfortunately, the answer is not black or white. It depends on use cases, context, available resources and skills. But I am convinced that you should give React Native a try for all the reasons mentioned in this article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88bcb7083c6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Start Guide: Node Server on EC2 Instance]]></title>
            <link>https://medium.com/@devinrobichaux/quick-start-guide-node-server-on-ec2-instance-e5e7beebcd0b?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5e7beebcd0b</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[ec2]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 05:04:59 GMT</pubDate>
            <atom:updated>2018-01-17T05:04:59.409Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the course of the past few weeks, I was tasked with deploying a few web applications and a react native app using AWS. Here’s a quick start guide to get a node server up and running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XrCLmaZEex00Hw6PCef5qA.jpeg" /></figure><h3>Set up new EC2 Instance</h3><h4>Launch Ubuntu Instance</h4><p>Create an AWS account and log into your EC2 console.</p><p>Assign an elastic IP address to your new instance before you <strong>ssh</strong> into your instance using your preferred method. (I recommend puTTY for windows users)</p><h4>Update your new computer</h4><p>Once your new instance is up and running, login and update the computer:</p><pre>$ sudo apt-get update <br>$ sudo apt-get -y upgrade</pre><h4>Install some build tools</h4><pre>$ sudo apt-get install build-essential <br>$ sudo apt-get install libssl-dev <br>$ sudo apt-get install git-core</pre><h4>Build node</h4><p>You can view the entire node installing instructions here: <a href="https://github.com/joyent/node/wiki/Installation">https://github.com/joyent/node/wiki/Installation</a></p><pre>$ wget http://nodejs.org/dist/node-latest.tar.gz <br>$ tar xzf node-latest.tar.gz <br>$ cd node-v0.4.7 <br>$ ./configure --prefix=/usr <br>$ make <br>$ sudo make install</pre><p>–prefix=/usr will install <strong>node</strong> on the existing <em>PATH</em>.</p><p><em>Warning: Installation can take a while.</em></p><h4>Install node package manager</h4><pre>$ cd ~ <br>$ git clone http://github.com/isaacs/npm.git <br>$ cd npm <br>$ sudo make install</pre><h4>Install a web server</h4><pre>$ sudo apt-get install nginx</pre><p>Edit the <strong>nginx</strong> default configuration file replacing the root (/) location section</p><pre>$ sudo vi /etc/nginx/sites-enabled/default</pre><p>Use a proxy passengry entry. This will forward your requests to your <strong>node</strong> server</p><pre>location / { proxy_pass http://127.0.0.1:3000/; }</pre><p>Restart <strong>ngnix</strong></p><pre>$ sudo /etc/init.d/nginx restart</pre><h3>Time for a new server!</h3><h4>Create a new directory for your new server</h4><pre>$ mkdir ~/www <br>$ cd ~/www</pre><h4>Create your server</h4><pre>$ cat &gt; server.js  </pre><pre>var http = require(&#39;http&#39;); <br>http.createServer(function (req, res) {<br> res.writeHead(200, {&#39;Content-Type&#39;: &#39;text/plain&#39;}); <br> res.end(&#39;Hello World\n&#39;); <br>}).listen(3000, &quot;127.0.0.1&quot;); <br>console.log(&#39;Server running at http://127.0.0.1:3000/&#39;);</pre><p>Start your server with node server.js</p><h3>Bring in source git source control</h3><p>Let’s leverage the power of <strong>git </strong>to deploy our new server code</p><h4>Initialize a bare repository for project</h4><p><em>make sure you’re outside of the www folder</em></p><pre>$ mkdir ~/repo <br>$ cd ~/repo <br>$ git init --bare</pre><h4>Create a post-receive hook</h4><p>This will copy over new commits after its been pushed to the repository</p><pre>$ cat &gt; hooks/post-receive  </pre><pre>#!/bin/sh <br>GIT_WORK_TREE=/home/ubuntu/www <br>export GIT_WORK_TREE git checkout -f  </pre><pre>$ chmod +x hooks/post-receive</pre><h4>add this remote repository to your LOCAL repository:</h4><p>On your <strong>local</strong> development machine, setup a repository for your new server</p><pre>$ mkdir helloworld <br>$ cd helloworld <br>$ git init <br>$ git remote add deploy ssh://ubuntu@your.static.ip/home/ubuntu/repo</pre><h4>create a local HelloWorld node server</h4><pre>$ cat &gt; server.js  <br>var http = require(&#39;http&#39;); <br>http.createServer(function (req, res) {<br> res.writeHead(200, {&#39;Content-Type&#39;: &#39;text/plain&#39;}); <br> res.end(&#39;Hello World\n&#39;); <br>}).listen(3000, &quot;127.0.0.1&quot;); console.log(&#39;Server running at <a href="http://127.0.0.1:8124/&#39;);">http://127.0.0.1:3000/&#39;);</a></pre><h4>add and commit it to your local repository</h4><pre>$ git add server.js <br>$ git commit -m &#39;first&#39;</pre><h4>push our local code changes to the remote repository:</h4><pre>$ git push deploy</pre><h4>test your new server</h4><p>Test in a browser by navigating to <a href="http://your.static.ip/"><em>http://your.static.ip/</em></a></p><h3><strong>That’s it!</strong></h3><p>Please share and leave a clap if you found this guide helpful. If you have any question please feel free to leave a comment and I’ll get back to you as soon as possible! Thanks for making it this far. Be sure to check out my next blog on having your node server run forever!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5e7beebcd0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL and RDBMS: The tech that stands the test of time.]]></title>
            <link>https://medium.com/@devinrobichaux/sql-and-rdbms-the-tech-that-stands-the-test-of-time-5de4ad6d9940?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5de4ad6d9940</guid>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 10 Jan 2018 01:53:56 GMT</pubDate>
            <atom:updated>2018-01-10T01:58:18.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*DudHWTJgtnFloK1MKSKK3Q.png" /></figure><p>SQL and relational database management systems were both invented in the early 1970s. E. F. Codd invented the RDBMS while Donald D. Chamberlain and Raymond F. Boyce developed SQL.</p><p>Not only were both of these technologies created in the early days of computing, but still to this day for 90% of the time storing and retrieving vast amounts of data are solved using this implementation. You no longer need to be a relational theorist to realize solutions for handling data. The problem no longer exists.</p><p>It’s like how Github has become synonymous with web-based git version control repository hosting. If you want to work with data you use RDBMS and SQL. In fact, there often needs to be a reason not to use. Just like there needs to be a good reason not to use GitHub for hosting repositories, or for PayPal for sending money to a loved one via the internet.</p><p>But people do use other web-based git repository hosting and payment solutions, just like people use NoSQL or other non-relational databases. Yet even with other database technology available, SQL/RDBMS still reigns supreme. Let’s look at some of the reasons why:</p><h3>Math.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ILv1AB5YhsF8EUALrLbwbw.png" /></figure><p>Structure Query Language is based on two core forms of mathematics developed specifically for relational databases: relational algebra and tuple relational calculus. Thanks, Mr. Codd.</p><p>Being that SQL was designed specifically for the handling of data, it comes at no surprise that it is unsurpassed for organizing and accessing data.</p><h3>Tried and True.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-P99dA0xM-5nGEfpErzJQ.png" /></figure><p>RDBMS have been around for a few decades and have been used in many scenarios. Heavily modified SQL databases have a centralized role in supporting inconceivably vast amounts of data for global platforms like Facebook. With standing countless millions of hours of persisting data with incomparable reliability, RDBMS and SQL are battle-tasted.</p><h3>It’s everywhere.</h3><p>Ubiquity isn’t always a bad thing in the software/database world. This creates a strong foundation for knowledge and community. And due to its decades of relevance and simplicity. SQL is almost common knowledge among developers and those they work with.</p><p>This is great for developers because it gives us a skill set thats able to transcend industries. On the other side of the token, this gives employers to procure talent that is more or less readily available. This inspires creation and community growth.</p><p>The ubiquitous nature of SQL databases has formed a beneficial circular model for growth.</p><h3>Community.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*eA4F3D5HKW-5P4cKkWH_RA.png" /></figure><p>The longer things around, generally, the more knowledge is built up around those things. SQL and RDBMS are no different. Vast amounts of documentation, active communities, and plenty of technical talent around for support does a lot to keep a technology around. Naturally, this leads businesses to gravitate towards this technology.</p><p>Because people gravitate towards the technology the community grows and the level of knowledge deepens and is shared with new adopters.</p><p>Over the years, this is what’s happened with SQL.</p><h3>SQL/RDBMS and NoSQL/DBMS databases play different roles.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*x2FlluE1Sha_Ms6IxH7NMA.png" /></figure><p>Relational databases are fantastic when you need to express relationships in a system when you can’t predict all possible permutations of data combination, aggregation, or usage. And, honestly, most systems fall into this category. Plus the SQL language itself offers a user-friendly way to organize data in the way you need it.</p><p>SQL/RDBMS are just one of many tools for a specific job — and just so happen to be a perfectly feasible tool for many jobs. And when consistent data integrity is essential (for example, in finance or healthcare), they are the best.</p><p>SQL databases have their drawbacks and aren’t the best choice for certain jobs. But for a vast majority of cases they simply blow every other NoSQL solution out of the water.</p><p>In regards to scalability, realistically only a tiny percentage will ever need to worry about scaling a RDBMS. You can still have millions of users with a SQL database and have no issues.</p><h3>Conclusion.</h3><p>Despite countless other database systems and technologies, and their growing popularity, SQL databases are undoubtedly here to stay — at least for the foreseeable future. With the advent of big data, deep learning, and IoT it wouldn’t be surprising if SQL databases thrive and expand for another 43 years.</p><p>SQL databases have their drawbacks, true. But for most use-cases the extensive community, simplicity of the language, and fundamental structure of RDBMS make it one of the better choices for database technology.</p><p>Why do we still use SQL after 43 years? Because it works and gets the job done 90% of the time. As developers with an increasingly complex landscape of technology and integrations, you can’t ask for much more than that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5de4ad6d9940" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postico: the killer PostGreSQL GUI]]></title>
            <link>https://medium.com/@devinrobichaux/postico-the-killer-postgresql-gui-590aca0c2209?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/590aca0c2209</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 03 Jan 2018 13:52:52 GMT</pubDate>
            <atom:updated>2018-01-03T13:52:52.569Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFuTzLxOrWGsX1uGU_kHLA.png" /><figcaption>Postico Logo</figcaption></figure><p>Last week I was granted the task of creating a relational database for a web application. Being more familiar with non-relational databases like MongoDB, I was a bit intimidated by the task. However, with the help of the Postico client, created by the team at Egger Apps, over the extremely powerful PostGreSQL database, I was able to format my database within MINUTES.</p><h3>Postico makes using PostgreSQL a breeze.</h3><p>Postico provides an extremely Mac friendly interface. This is tailored for an experience that is beneficial for newcomers and relational theorist alike. It’s as simple as a connecting to database to being working with tables and views. Once you familiar yourself with the structure and content of your tables, constructing advanced tables and design logic could not be easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kXr7KiHwGTZh-YQVy3vwdw.png" /></figure><h3>Get a live analysis of the content of your database.</h3><p>The killer feature for me is being able to get a live look at the contents of your database without having to use a command line or advanced queries. You can create, read, update, and destroy data from Postico. The GUI also grants the ability to view images and extremely long within the the app. You can view related rows from referenced tables. Postico allows you to filter rows, sort them, rearrange columns. You can even change multiple rows at once. Batch saving (with SQL preview) lets you commit changes to multiple rows in a single transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsA_MvQdEVUizzjDlzvisg.png" /></figure><h3>Query, Enquire, Investigate.</h3><p>PostGreSQL offers many tools for robust data analysis like recursive queries, filter aggregates, common table expressions, and window functions. Postico flexes an extremely powerful query view that supports multiple result sets. The editor has all the standard features you expect, like syntax highlighting and automatic indentation.</p><h3>Conclusion</h3><p>Download Postico for your Mac if you need to exploit the true power of PostGreSQL. I can see my self using this application for all of my database needs. You shouldn’t have to have a degree in relational theory to be able to harness the capabilities of one of the most powerful databases accessible..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=590aca0c2209" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The benefits of the MEAN stack approach to robust web application development.]]></title>
            <link>https://medium.com/@devinrobichaux/lean-and-mean-b7202dad307?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7202dad307</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[mean-stack]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angularjs]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 20 Dec 2017 14:34:37 GMT</pubDate>
            <atom:updated>2017-12-21T15:13:33.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*jj5enPFec_YB_a5PXzNN7A.png" /></figure><p><strong>MEAN</strong> is an acronym for MongoDB, ExpressJS, AngularJS and Node.js.</p><p>The term <strong>MEAN Stack</strong> refers to a collection of JavaScript based technologies used to develop web applications. From client to server to database, <strong>MEAN</strong> is full <strong>Stack</strong>JavaScript.</p><p><strong>MongoDB — M</strong> stands for <strong>MongoDB</strong>, the world’s foremost NoSQL database. The database that stores its data into a formatted JSON-like binary file called BSON. It’s easy to use, and for JavaScript developers it should be as simple as working with JSON.</p><p><strong>Express JS — E</strong> stands for <strong>Express</strong>, a lightweight, simple framework built for Node.js. It has been created for APIs, web applications, and comes with HTTP facilities for the developer.</p><p><strong>AngularJS — A</strong> stands for <strong>AngularJS</strong>, the Model-View JS framework created by Google. AngularJS makes API consuming very simple, so for every developer using it as the client-side of MEAN is very helpful. Moreover, AngularJS is used for mobile development.</p><p><strong>Node.js — N</strong> stands for <strong>Node.js</strong>, the base of Express. It runs on Chrome’s V8 engine and is able to do non-blocking, event-driven I/O. The Node.js application can handle multiple requests on a single service without blocking each-other.</p><h3>It’s all just Javascript…</h3><p>Well, now that you know how and why is it named MEAN, let us discuss some of the most important benefits of MEAN development. This will help you know the reason behind its growing popularity. So, here are the advantages of using MEAN stack:</p><ul><li>One of the most important benefits of all is that, it lets the developer write the entire code in JavaScript; from client to server. This is like a blessing for the JavaScript developers who have invested their time and money in learning JavaScript for the client side tasks.</li><li>It supports the MVC (Model View Controller) architecture.</li><li>The MEAN components are open source; which means the stack gets updated regularly. In addition to it, it is easy and flexible to understand and use which helps the developers to customize as per your needs.</li><li>Other advantages are the huge module library of node.js and the use of JSON to transfer the data.</li></ul><p>As every technology has its own advantages and disadvantages, you do not have to be a slave of the acronym. Any technology mentioned in the stack can be easily used in combination with other as per the requirement. But consider the MEAN stack, If you want a stack that’s rapidly improving, easy to collaborate around and easy to learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7202dad307" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby on Rails vs Node.js]]></title>
            <link>https://medium.com/@devinrobichaux/ruby-on-rails-vs-node-js-42d6218b6b76?source=rss-952cdc6d52a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/42d6218b6b76</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Devin Robichaux]]></dc:creator>
            <pubDate>Wed, 13 Dec 2017 14:31:29 GMT</pubDate>
            <atom:updated>2017-12-20T16:59:19.137Z</atom:updated>
            <content:encoded><![CDATA[<p>With so many options out there, it can be hard for a programmer to choose the right language for development. One of the biggest rivalries in full-stack development is between Node.JS and Ruby on Rails. So, let’s take a look at some of the pros and cons between the two!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*6C6KG2AJj3-v6I3_vzmNYA.png" /></figure><h4>Ruby on Rails Pros:</h4><ul><li>It is <strong>flexible and IDE friendly</strong> framework.</li><li><strong>Database migrations</strong>. It will be easily portable to any platform.</li><li><strong>Easy functions</strong> and manipulations.</li><li>It is <strong>consistent</strong> with structure and methodology.</li><li>The <strong>language</strong> is very powerful and expressive. It’s easy to express application logic in an intuitive way.</li></ul><h4>Ruby on Rails Cons:</h4><ul><li>Best programming skills are required so top notch programmers with <strong>high pay</strong> are required.</li><li>Much <strong>trickier</strong> if making large projects.</li><li><strong>Documentation</strong> is only for popular frameworks</li><li>More <strong>computing resources</strong> are required.</li><li><strong>Performance</strong>. Rails is slow as hell, and this bubbles up to the experience of the end user.</li><li><strong>Large stack frames</strong>. The fact that Rails has so many layers of abstraction makes debugging a pain.</li></ul><h4>Node.JS Pros:</h4><ul><li><strong>Powerful underlying libraries</strong>. libuv, the library behind Node that handles non-blocking I/O, is super awesome and wicked fast.</li><li><strong>Full stack</strong>. From HTTP server to templating engine, Node.JS is the whole package. Rails relies on something like Nginx or Apache with mod_rails (aka Passenger) in order to actually work.</li><li><strong>High market demand</strong> and very popular in startups at this time.</li><li><strong>Same language</strong> on client and server side.</li><li>Easy to <strong>monitor, deploy and support</strong>.</li><li>Page load is <strong>faster</strong> across the site. (Our tests showed that websites are usually 2 or 3 times faster with node.</li></ul><h4>Node.JS Cons:</h4><ul><li>Node is not suitable for <strong>processor intensive tasks</strong>.</li><li><strong>Unstable API</strong>: The Node API has a habit of changing in backwards-incompatible ways from release to release, and frequent changes to your codebase are required to keep things running on the latest version. That said, things are supposed to be more stable since 0.2.0 has been released.</li><li>Because it’s new and very hot, there are <strong>fewer developers</strong> in market for node.js.</li></ul><h4>Conclusion</h4><p>If your application has items that absolutely needs Node.js, then this is an easy decision and you should use Node.js + Express. If it has needs that Ruby on Rails is more geared towards or all else is equal, favor the stable choice — Ruby on Rails. The truth is that with either of these frameworks, there’s potential for things to go wrong. Do not pick a framework based on hype and because all the cool kids are doing it. Determine what the application should do and then pick the framework that does that best in a reasonable amount of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42d6218b6b76" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>