<?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 Lanetix on Medium]]></title>
        <description><![CDATA[Stories by Lanetix on Medium]]></description>
        <link>https://medium.com/@lanetix?source=rss-3e17f612ce43------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*U4X7lhakT8Y_q13_b3EWPA.png</url>
            <title>Stories by Lanetix on Medium</title>
            <link>https://medium.com/@lanetix?source=rss-3e17f612ce43------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:25:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lanetix/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[ShipIt! Day]]></title>
            <link>https://medium.com/@lanetix/shipit-day-a704e6f9f41d?source=rss-3e17f612ce43------2</link>
            <guid isPermaLink="false">https://medium.com/p/a704e6f9f41d</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Lanetix]]></dc:creator>
            <pubDate>Mon, 22 Feb 2016 00:00:00 GMT</pubDate>
            <atom:updated>2017-08-12T05:20:18.466Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we do the “Company Hackathon” every quarter to unleash creative ideas from our team</h4><p>Lanetix is a young company still in the process of cultivating our culture, yet from the very start our senior-most engineers knew there would be ‘ShipIt Day’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AzvwYF0_k6BgHkvI.png" /></figure><p>Corporate hack days have long been popular among many industry tech giants for being powerful catalyzers of internal innovation, team collaboration, and staff empowerment. Lean startups like ours can also reap these benefits. As our CTO <a href="https://twitter.com/TroyGoode">Troy Goode</a> explains, “Engineers spend so much time building other people’s ideas. They’re brilliant people across the board, and no one is closer to our product every day than our engineers, so why not give every engineer carte blanche to bring their own creativity to the table?” And so Lanetix does! Once we neared the ten engineer mark (now closer to thirty), we’ve held a ShipIt Day once per quarter, totaling three ShipIt Days in the last nine months. We find the practice allows our engineers a free-form way of tackling the challenges they’re interested in, the opportunity to exploring new, risky technologies, and a stage to promote their own business ideas. And seriously, it’s a ton of fun.</p><h3>The Rules</h3><p>While we don’t currently have an official ‘ShipIt Day Charter’, we do follow some general guidelines. The competition starts on a Thursday morning and ends with final demos on the following Friday morning. A panel of judges is assembled often consisting of our CEO, our CTO, a product manager or two, and a customer team member or two. Teams are generally two to six strong, comprised mostly of engineers, with our designers distributed to teams in need. While teams can only begin working on their projects the day of, they are encouraged to do member recruitment and preparatory scoping ahead of time. Teams can work for 24 hours, though this is not necessarily required. Final demos are presented to the entire organization on the following day over breakfast, and each presentation receives a hearty round of applause.</p><p>While evaluation criteria was entirely subjective for the first two ShipIt Days, by the third implementation we established the following benchmarks:</p><ul><li><strong>Ambition</strong>: How aspirational is the scope of the project?</li><li><strong>Short-term Business Impact</strong>: Does the project solve a current problem or have immediate positive customer significance?</li><li><strong>Future Potential</strong>: If the concept is not fully fleshed out now, what will it look like and what impact will it have when it is?</li><li><strong>Technical Difficulty</strong>: How challenging is the implementation of the project?</li><li><strong>Presentation / Completeness</strong>: Is the project presentation comprehensive and indeed ship-able now?</li><li><strong><em>Bonus Points</em></strong><em>: Does it have documentation? Does it have TESTS?</em></li></ul><p>The winners receive mad props, bragging rights, legendary reputations, and their names engraved on a large and incredibly shiny trophy displayed in our main lounge area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FjGhETjNIjJtHdV-.png" /></figure><p><em>ShipIt Day 3 Winners: Engineers </em><a href="https://twitter.com/DannyDouglass"><em>Danny Douglass</em></a><em>, </em><a href="https://twitter.com/sahllt"><em>Sahil Talwar</em></a><em>, </em><a href="https://twitter.com/syntax_on_ice"><em>Antwan Wimberly</em></a><em>, </em><a href="https://twitter.com/apechimp"><em>Mike Atkins</em></a><em>, &amp; </em><a href="https://twitter.com/kyla_farrell"><em>Kyla Farrell</em></a><em>.</em></p><h3>The Gains</h3><p>As an organization we’ve seen a lot of advantages come out of ShipIt Day. These include an immediate injection of high energy in the office, long lasting efficiency gains, and potential revenue expanding business ideas. We’ve also learned a lot in the process.</p><p>Most obviously: it’s fun!</p><p>Our engineering team is generally organized into specified, focused, prioritized teams. ShipIt Day provides engineers an occasion to break out of that structure to team up and share resources and methods with those they don’t typically work with. This is especially important to our company because we have west-coast and east-coast engineering teams. To ensure this live interfacing aspect of ShipIt Day, it is preferably scheduled when the remote office is in town for an all-staff week. Working together in person builds strong foundations for future remote pairing sessions on our ‘actual work’. With all that live collaboration, the team enthusiasm during and following ShipIt Day is noticeably higher.</p><p>On an individual level, ShipIt Day provides engineers paid time and space to explore and play with new technologies. For instance, one engineer took a deep dive into Swift (a language we don’t currently work in) for both ShipIt Day 1 &amp; 2, attempting to write a mobile app from scratch in (collectively) 48 hours. He relished adding a new language to his personal stack, and what he was able to accomplish was impressive.</p><p>Wide stretching impacts:</p><p>Some ShipIt Day projects, for example the runner-up in ShipIt Day 2, completely changed the way we manage our onboarding process and developer workflow. This team wrote scripts that aggregated all the startup commands for each of our microservices, including specifying the proper node version for each respective service, into a two line command line prompt. The result effectively shaved off minutes for each developer each day henceforth (which is actually a lot of minutes). Furthermore, they aggregated and automated much of the setup required of a new engineer, condensing our onboarding process from an entire day into two hours, again with a simple two word command prompt. And the cherry on top? It was all backed by clear, organized documentation for future new engineers to follow step-by-step. (And if you’re thinking this team should have won first place, half our company would agree with you!) This story keeps going too: other engineers have continued adding scripts long after ShipIt Day ended (e.g. git pull updating all our repos at once), adding growing functionality and improving everyone’s workflow.</p><p>Prioritizing unprioritized work:</p><p>We’re still a lean startup, and we can’t always prioritize all the work we’d really like to do. ShipIt day enables us to start chipping away at some of these ‘if-only’s, or sometimes even completely smash one off the docket! For instance, the winners of our most recent ShipIt Day addressed and solved a longstanding internal issue we faced whenever our customer team needed to provision a demo environment for presentation to potential new subscribers. Throughout the history of our company, the process traditionally looked like this:</p><ol><li>A customer team member would spend time trying to determine which engineer was the best to ask to create the demo environment, or would put out a general request in our shared Slack channel, which may not be answered immediately.</li><li>An engineer (or perhaps an engineer three asks down the line) would interrupt their current, prioritized work to create a new github ticket and address the request to spin up the demo environment.</li><li>Lastly, there would often be some back and forth regarding the correct permissions, feature flags, and other implementation details that may differ or have been updated from the original ask.</li></ol><p>In response, the ShipIt Day team developed a complete UI accessible to our customer team, allowing any of our customer team colleagues to create the exact demo environment they need immediately themselves. This new process completely bypasses both the need to locate and request the time of an available engineer, as well as the wait until it was completed. Furthermore, the customer team can go back and modify the environment directly at anytime, including once the potential subscribers become current subscribers.</p><p>Establishing an internal UI for exactly this purpose is an idea we’d been talking about for nearly a year. However our priorities to maintain existing customer-facing features and to build new subscriber-requested features ever delayed its implementation. ShipIt Day provided us the opportunity to finally accomplish this goal, and the increased efficiency it brings to our internal processes will undoubtedly have long lasting impacts on both our internal and external facing teams.</p><h3>Some Lessons Learned</h3><p>Continuous learning, a concept familiar to engineers, applies to ShipIt Day as well. The company learned to provide an extra meal to those staying late. Teams learned to read the docs ahead of time for any new technologies they plan on using. We’ve all learned to stash ideas as they occur, sometimes even months before the actual day. But far and away the biggest of these lessons learned is to not actually ship anything during ShipIt Day.</p><p>During the second ShipIt Day, my team won in part because our project was fully functional and already deployed (while feature flagged of course!) in production by demo time. We integrated <a href="https://www.twilio.com/">Twilio</a> into our app so that anytime a phone number appeared on the screen our subscribers could click a little phone icon and connect a call between their mobile phone and the number displayed. We rocked the demo by having two of the judges’ phones ring and connect, and frankly, it was downright impressive. Our customer team was dazzled and enticed with the idea of marketing this as a separate, chargeable add-on service to our subscribers. However, once ShipIt Day concluded, our team dispersed back to our original squads and continued working on our previous projects. There was no planned ongoing support to enhance and further develop this feature and it remains hidden behind feature flags in our code, unmarketed. Regrettably, our engineers still occasionally get messy console logs and benign errors popping up in our development environment because of some of the hastily implemented code aiming for a win.</p><p>Come our third ShipIt Day, this experience prompted us to agree as an organization that ShipIt Day should not actually result in shipping anything the day of. This is undoubtedly an improvement, as eager and competitive teams are no longer encouraged to push directly to master after one of their own teammates gives a hasty emoji approval or before there are any tests.</p><p>Lastly, this project also illustrated we have yet to improve by figuring out how best to support further development on great ShipIt Day ideas beyond the actual competition.</p><h3>ShipIt Day for Everyone!</h3><p>We at Lanetix are cementing ShipIt Day into our company culture and highly recommend the process to a company of any size. While prioritized work takes a hit for a day, the benefits of the process can be more than worth it: from increased collaboration and a greater sense of teamwork to improved workflow and efficiency gains. And as we continuing growing, we are looking forward to further supporting and developing great ShipIt Day product ideas with potential to create huge opportunities for our business.</p><p>BONUS POINTS</p><p><em>Lanetixers advising their future ShipIt Day selves:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/235/1*wZ9BmuABe8f-Pe0UM4uM-w.jpeg" /></figure><h4>Taylor Hesselgrave</h4><p>Software Engineer<br><a href="http://twitter.com/taygrave">@taygrave</a><br><a href="https://www.linkedin.com/in/thesselgrave">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a704e6f9f41d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yet more PostgreSQL libraries for node]]></title>
            <link>https://medium.com/product-dev/yet-more-postgresql-libraries-for-node-a1d05b0f811e?source=rss-3e17f612ce43------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1d05b0f811e</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Lanetix]]></dc:creator>
            <pubDate>Tue, 21 Jul 2015 00:00:00 GMT</pubDate>
            <atom:updated>2017-08-12T05:19:11.655Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*pSLgYPzOrb3qoSTi_L6VXg.png" /></figure><h4>Leveraging PostgreSQL in the JavaScript world</h4><p>I tend to have a hard time using ORMs for reasons which would turn this blog post into more of a tirade than I’m willing to write. Regardless, I find myself just using <a href="https://github.com/brianc/node-postgres">node-postgres</a> whenever I want to access a database from node.js. Unfortunately, I also find myself trying to match up spaces and + when I have a multiline string in js, and even if I manage to surmount that, once I deploy that application to production and it starts getting used, I find that it all suddenly stops working because the connection pool is full because I forgot to let node-postgres know that I was done with a connection.</p><p><a href="https://github.com/lanetix/node-pg-require-sql">pg-require-sql</a> gets around the lack of multiline string literals in javascript by allowing you to create a bunch of .sql files in some directory and turn that directory into an object with methods you can use to execute those sql files. This is very similar to <a href="https://github.com/NGPVAN/preql">preql</a>, <a href="https://github.com/robconery/massive-js">massive-js</a> and <a href="https://github.com/ngourley/node-require-sql">require-sql</a>, but this has an api which works better when used with <a href="https://github.com/lanetix/node-pg-connect">pg-connect</a>, just handles loading files, and doesn&#39;t use deprecated features, respectively.</p><p><a href="https://github.com/lanetix/node-pg-connect">pg-connect</a> provides a much harder to screw up connection pooling api than in node-postgres. It doesn’t actually change how the connection pooling mechanism works, just provides a module for the <a href="https://github.com/petkaantonov/bluebird/blob/master/API.md#resource-management">resource management patterns in bluebird</a> applied to node-postgres.</p><p>When you put these two modules together with a project laid out like |- index.js |- sql-directory |- get-record.sql</p><p>and get-record.sql as</p><pre>SELECT name FROM records WHERE id = $1</pre><p>the following will execute the sql in get-record.sql</p><pre>var Promise = require(&#39;bluebird&#39;) var path = require(&#39;path&#39;) var getConnection = require(&#39;pg-connect&#39;)(connectionString) var requireSql = require(&#39;pg-require-sql&#39;) var sql = requireSql(path.join(__dirname, &#39;sql-directory&#39;)) Promise.using( getConnection(), sql.getRecord([&#39;foo&#39;]) ). then(function (results) { console.log(&#39;foo&#39;, results.rows[0]) })</pre><p>which will log out the name of the record, foo.</p><p>You’ll notice that in this example I didn’t have to do any careful manipulation of spaces in multiline js strings and never closed any connections explicitly. In spite of that, the sql still executes as expected and this won’t leak connections, so if, like me, you can’t trust yourself to cleanup connections or get spacing correct in multiline strings, but still don’t want to use an ORM, give <a href="https://github.com/lanetix/node-pg-connect">pg-connect</a> and <a href="https://github.com/lanetix/node-pg-require-sql">pg-require-sql</a> a try.</p><h4>Mike Atkins</h4><p><a href="http://twitter.com/apechimp">@apechimp</a><br>I mostly write javascript nowadays.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1d05b0f811e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-dev/yet-more-postgresql-libraries-for-node-a1d05b0f811e">Yet more PostgreSQL libraries for node</a> was originally published in <a href="https://medium.com/product-dev">Lanetix Product Development</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>