<?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 Joe Jobes on Medium]]></title>
        <description><![CDATA[Stories by Joe Jobes on Medium]]></description>
        <link>https://medium.com/@jmrjobes?source=rss-9ac4482b2a7b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tjXZsEL2EieaRGA1M7lciw.jpeg</url>
            <title>Stories by Joe Jobes on Medium</title>
            <link>https://medium.com/@jmrjobes?source=rss-9ac4482b2a7b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:58:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jmrjobes/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[Contributing to Caravan]]></title>
            <link>https://medium.com/@jmrjobes/contributing-to-caravan-42f07f320820?source=rss-9ac4482b2a7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/42f07f320820</guid>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Joe Jobes]]></dc:creator>
            <pubDate>Tue, 22 May 2018 13:58:21 GMT</pubDate>
            <atom:updated>2018-05-22T14:26:42.532Z</atom:updated>
            <content:encoded><![CDATA[<p>Being my first time entering the open source scene, I had a little trouble looking for projects where I felt I could add something of substance. There are many tags for beginner friendly issues on certain open source projects, so how do you go about choosing which one to dive into first? Depending on the issue, you might have to take a deep dive on the inner workings of the app, which even if you didn’t need to for a certain issue, it’s best to know what the app is doing.</p><p>Luckily I was working with a great team, Andrew Jeffery, Matt Milton, and myself, to find an open source project that had interesting issues. One of the teammates, found an app called Caravan, which provides people with the ability to record and report the status of local transportation stations and lines. The app was birthed at a Chicago hackathon and later implemented into their local civic tech meeting Chi Hack Night. It was at a sweet spot for being large enough to require some deep diving into the code base, but not so big that it was monolithic. Overall a good place to start adding in some contributions.</p><p>Upon looking through the issues, there were three that seemed easy to knock out. One issue was asking for a template for the pull requests and issues, another was asking for a seed file so that people could run the app locally on their machine, and the last was asking for test coverage to be brought above 90%. One teammate tackled the templates, while another teammate and I decided to pair up on the seed file.</p><p>After looking into the other pull requests we found that someone had already created a seed file and made a pull request, but the Travis CLI build was failing. This piqued our interest, so we copied the what was in the pull request onto our machines and ran the seed, after getting it all set up. Immediately the seed failed. The first failure in the seed file had to do with a joins model, that didn’t exist, which to the both of was rather odd, so we decided to dive into the schema to have a look at what exactly was being seeded.</p><p>As we were going through the schema we saw a hefty number of tables dealing with lines, stops, issues, vehicles, users, and settings. To better help visualize the schema we also began building out a schema visualization with the help of SQL Designer, another open source project for creating nice visual representations of schema. As we went through and made the schema we found that the settings table was not linked to anything, but seemed to have a thing_type and thing_id column. This was rather perplexing, but for the sake of creating a seed file, this was not needed, so we focused our attention on the rest of the schema.</p><p>After creating the visual we went and had a look at the models, and to our surprise, we found no model for the joins table. Instead we realized that the many-to-many relationship was set up using a has_and_belongs_to_many ActiveRecord association, which eliminated the need for creating a model for the joins table. This explained why the seeds file was failing, and showed us that the previous contributor probably didn’t do that much code diving, let alone testing, before putting in the pull request.</p><p>Once we had a better understanding of what was needed in the file, we went about refactoring the seed file so that it would pass. Along the way we came into some errors with mismatching data types and odd behavior with the faker gem, but in the end we were able to refactor the file to both seed and pass Travis CLI build.</p><p>After finishing up the seed file, I decided to tackle the testing since it didn’t look all that difficult and there were only two controllers that were not really being tested. What I did not expect was that the app was using ActiveDispatch for integration tests. I had only worked with minitest and rspec in the past, so this was rather foreign to me, but the documentation on the Rails site was thorough and had many examples to reference. After a bit of toying around with the test suite, I finally hit a nice groove and added in tests for all the actions in the issues controller and the lines controller, bringing the tests up from 64% coverage to a nice 95%.</p><p>After our work was done, we all reviewed each others work and made a pull request to the main repository detailing all the contributions we made with the referenced issue numbers.</p><p>In all this little foray into open source contributions was rather fun, and provided me with a greater sense of empathy for the developers in question. I could have decided to rewrite all the tests in rspec, implement capybara, and factory bot, but that would have not been very empathetic to the original creators. Instead I decided to learn what the app was working with and see if I could add to the existing code base without changing too much of the behavior.</p><p>Trrransition… Overall great time. Solid 5/7.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42f07f320820" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Brief History on the Origins of Blockchain]]></title>
            <link>https://medium.com/@jmrjobes/a-brief-history-on-the-origins-of-blockchain-6210ce345a21?source=rss-9ac4482b2a7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6210ce345a21</guid>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Joe Jobes]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 14:18:37 GMT</pubDate>
            <atom:updated>2018-02-26T21:49:12.802Z</atom:updated>
            <content:encoded><![CDATA[<p>The story of Bitcoin has become rather prevalent as of late. With the recent popularity in cryptocurrency running wild, there seems to be a neglect of the underlying technology that helps the entire cryptocurrency world function. This technology, while not making many headlines in the news, is increasingly becoming a hot topic among industry leaders for applications other than cryptocurrency. It could be used in preventing fraud in our voting machines, increase the security and efficiency of online banking, provide a standard for tracking warehouse shipments, and much much more. This technology is blockchain.</p><p>Now the purpose of this blog is not to explain blockchain right off the bat. That will be for later installments in this blog. Instead I want to touch upon the history that brought this technology to the forefront of todays tech sector. There are many blogs and publications on the different types of blockchain and it’s function, but very few will mention exactly how it came about. Who developed it? Where did it come from? How long has this technology been around? I will try to answer all of these to the best of my abilities.</p><p>So. Who came up with the blockchain? Well, many people who have been interested in cryptocurrency, specifically bitcoin, will point to the elusive creator Satoshi Nakamoto. In a 2008 paper, “Bitcoin A Peer-to-Peer Electronic Cash System”, Nakamoto describes the concept of bitcoin and the underlying mechanisms by which it works. In this paper Nakamoto never once used the term blockchain. Instead, block and chain were used separately to explain the concept of many blocks, each containing data on transactions, all connected in a chain. Over the years blockchain would become the standard term used for this technology, but as stated above, Nakamoto had never termed it this.</p><p>While Nakamoto would ultimately put forth the idea of using a blockchain to record a list of transactions for Bitcoin, this is technically not the beginning the concept of a blockchain. For that we have to go back to 1991, where in a paper written by Stuart Haber &amp; W. Scott Stornetta entitled, “How to Time-Stamp a Digital Document”, the concept of time stamping digital documents was proposed, to ensure transactions were ‘signed’ at a certain time. The following year, Haber &amp; Stornetta, implemented a Merkle Tree, otherwise known as a hash tree, in each ‘block’ to store multiple transactions.</p><p>Later, during 1996, another cryptographer from Cambridge University, Ross Anderson, described in a paper, entitled “The Eternity Service”, a decentralized storage system with the inability to delete any updates made to the system. This was considered, at the time, a revolutionary paper on developing more secure peer-to-peer systems, which was directly inspired by the shutdown of the Finland’s penet remailer, by the Scientologists.</p><p>Two years later, B. Scheier &amp; J. Kelsey would write a paper detailing another method to secure logs from untrusted machines using cryptography. In this paper, the Scheier &amp; Kelsey describe a method in which computer can prevent attackers from modifying or tampering with any previous logs made, while at the same time making any logs unreadable to the an attacker.</p><p>One of the big developments for creating the blockchain occurred in 2002 when another pair of cryptographers named, David Mazières and Dennis Shasha, would propose a network file system with a decentralized trust. This was a proto-blockchain in that the writers to this file system would trust one another, but not the system itself. Instead they would digitally sign, with a SHA256 encryption or similar hashing function, commits and append it to a chain of others housed in a Merkel Tree.</p><p>Three years later, 2005, Nick Szabo, a prolific cryptocurrency advocate and developer, would create another version of a simplified blockchain, and introduce it alongside his proto-cryptocurrency bit gold.</p><p>All of this leads up to 2008 with Satoshi Nakamoto. Within the first installment of blockchain can be seen the influence of each of these cryptographers and researchers, including others that were not named. To this day blockchain has continued to evolve, in which now, blockchain 2.0 has emerged. With it, the ability to write software on top of the blockchain has been introduced, which can include anything from smart contracts to little apps.</p><p>As blockchain continues to evolve and become more robust, prolific, and ubiquitous among industries, there is no telling what new application can be envisioned for it.</p><p>In later blogs we will go into what exactly a block chain is and how it can be used in different industries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6210ce345a21" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>