<?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 Tre Grisby on Medium]]></title>
        <description><![CDATA[Stories by Tre Grisby on Medium]]></description>
        <link>https://medium.com/@Trewaters?source=rss-343424191c7e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UCfpdAYB6ODEEOMh.jpg</url>
            <title>Stories by Tre Grisby on Medium</title>
            <link>https://medium.com/@Trewaters?source=rss-343424191c7e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:09:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Trewaters/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[Security Readme Files — SECURITY.md]]></title>
            <link>https://medium.com/@Trewaters/security-readme-files-security-md-cb34803afcff?source=rss-343424191c7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb34803afcff</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Tre Grisby]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 19:43:04 GMT</pubDate>
            <atom:updated>2018-11-27T19:45:14.420Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Security Readme Files — SECURITY.md</strong></h3><p><em>“Security is not about speed but finding help when there is a security issue should be.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*rheBMT6Pk6ss7BgaqTf4Dg.jpeg" /><figcaption>attribution ( <a href="https://www.emerson.com/en-sg/automation/measurement-instrumentation/wireless-security">ht</a><a href="http://bit.ly/2ShyOfx">http://bit.ly/2ShyOfx</a> )</figcaption></figure><p>The <strong>“tl;dr”</strong>… <a href="https://github.com/Trewaters/security-README">Security readme file</a> has the project’s “security policy” and “vulnerability reporting” (A.K.A — “responsible security disclosure policy”) in a separate file. The security readme file is in the root directory of an open source project. Security readme files for open source repositories should be a <a href="https://opensource.guide/">new guideline</a>.</p><p>I am asking the JavaScript ecosystem to use a “SECURITY.md” (also referred to as a “security readme file”) to their repositories. My goal is to improve open source security by making policies more accessible and reporting security vulnerabilities easier for everyone.</p><p>This isn’t a new thought! While giving a talk at <a href="https://www.meetup.com/sfnode/">SFNode</a> about <a href="https://3waters.org/2018/11/sfnode-meetup-nov-2018-talk/">“Node.js Security best practices”</a> I realized <a href="https://github.com/securitytxt/security-txt">“security.txt”</a> functions in a similar way. Unfortunately, the “security.txt” file is not intended for humans to read. This is a standard for websites and servers to use in the wild ( A.K.A — the intra/internet ). BUT the idea is the same, provide a route for contributors to report a security issue easily.</p><p>Thank you to <a href="https://github.com/Trott">Rich Trott</a> of <a href="https://nodejs.org/en/">Node.js</a> for taking <a href="https://3waters.org/2018/11/sfnode-meetup-nov-2018-talk/">my talking point</a> and <a href="https://github.com/nodejs/node/commit/472a3d890bcd1c6799658d72bb813626a16d0adc">running with it</a>. I also want to take a moment to thank <a href="https://github.com/Trewaters/security-README#credit">these other projects</a> for already using security readme files (SECURITY.md).</p><p>Visit my GitHub repository “<a href="https://github.com/Trewaters/security-README">security-README</a>”. I welcome comments to this idea so we can make the open source community a better place than we found it.</p><p><em>link to post is here ( </em><a href="https://3waters.org/2018/11/security-readme-file-security-md/"><em>https://3waters.org/2018/11/security-readme-file-security-md/</em></a><em> )</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb34803afcff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“NoSQL” databases have had a surge in popularity lately.]]></title>
            <link>https://medium.com/@Trewaters/nosql-databases-have-had-a-surge-in-popularity-lately-bd331d3ad382?source=rss-343424191c7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd331d3ad382</guid>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Tre Grisby]]></dc:creator>
            <pubDate>Wed, 27 Dec 2017 20:48:23 GMT</pubDate>
            <atom:updated>2017-12-27T20:48:23.704Z</atom:updated>
            <content:encoded><![CDATA[<p>“NoSQL” databases have had a surge in popularity lately. The “No” in “NoSQL” refers to the fact that these databases aren’t using the specific SQL language. “SQL” stands for “Structured Query Language”. NoSQL databases use a query language with its own structure. A more accurate name might be “Non-relational databases”, but not as catchy.</p><p>A NoSQL database allows for quicker development up front. Developers that are used to relational databases expect more planning before any data storage can begin. In a relational database database designers need to have an idea of the data types to be stored, and the amount of data expected. But how can a developer know this for a new project. Nothing has been created, at best they have a plan but no product. The first design of the tables in a SQL database are more like a draft that will be rewritten multiple times before it is truly sufficient for the project. NoSQL cuts through this step like a hot knife through butter. There will be other challenges with NoSQL, but at least the project can spool up quickly. Some NoSQL databases are designed to use Javascript and JSON objects. That is the main reason I like MongoDB.</p><p>There many reasons to use MongoDB. The main reason is the amount of support it has from the community and other developers. MongoDB has worked to create a company that improves to keep their database viable. When MongoDB started there was no certainty it would turn into the major database company it has become. MongoDB gives a full solution from the start. MongoDB is lightweight with a small download size. It can be used on a local machine for fast development. Later it can moved to production with replication and sharding. If moved to their Atlas cloud solution a company can deal with sudden growth spikes using the cloud pay-for-what-you-need model, changing processing power on the fly. MongoDB has done all this and listened to the development community, questions get answered quickly.</p><p>Another NoSQL database I would like to talk about is RethinkDB. This database allows a developer to subscribe to data, then the data is pushed to the application. This makes the data real time and always fresh. I heard about RethinkDB at a meetup in 2016, but never used it myself. While researching for the Berkeley Javascript Dojo meetup I found that RethinkDB had closed its doors in October 2016. RethinkDB is an open source project, but there haven’t been any commits to the github code base since it closed.</p><p>There are lots of projects, frameworks, and modules in the current Javascript environment. Things change quickly. How can you choose the right product with confidence? Developers get overwhelmed when trying to start out in Javascript. Below are a few questions to help navigate the maze of options.</p><ol><li>Does the code you want to use have community support? Look for forums, websites, stackOverflow, slack, discuss or any communication outlet for users to get help.</li><li>Are there developers still working to improve the code base? Try searching for their twitter, LinkedIn, or github accounts. Look for recent commits to the code base.</li><li>If the code base is on github how many issues are open? How long does it take for developers or contributors to respond and close issues, especially critical ones? Count how many issues are open.</li></ol><p>I have never used Couchbase so I need to research it a bit. But I suggest you use some of the techniques I have outlined above to evaluate Couchbase for your next project. Below are some other NoSQL javascript databases that came up while I was looking for topic material.</p><ul><li>Npm nosql ( <a href="https://www.npmjs.com/package/nosql">https://www.npmjs.com/package/nosql</a> )</li><li>LokiJS ( <a href="http://lokijs.org/">http://lokijs.org/#/</a> )</li><li>PouchDB ( <a href="https://pouchdb.com/">https://pouchdb.com/</a> )</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd331d3ad382" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>