<?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 @nolim1t on Medium]]></title>
        <description><![CDATA[Stories by @nolim1t on Medium]]></description>
        <link>https://medium.com/@nolim1t?source=rss-21ce4a1595f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*liXRI3FW9cy0t_xOWx2tNA.jpeg</url>
            <title>Stories by @nolim1t on Medium</title>
            <link>https://medium.com/@nolim1t?source=rss-21ce4a1595f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:47:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nolim1t/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[Managing versions across multiple environments]]></title>
            <link>https://medium.com/@nolim1t/managing-versions-across-multiple-environments-2c1f2f7cdb81?source=rss-21ce4a1595f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c1f2f7cdb81</guid>
            <category><![CDATA[configuration-management]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[@nolim1t]]></dc:creator>
            <pubDate>Thu, 28 Apr 2016 06:36:01 GMT</pubDate>
            <atom:updated>2016-04-28T06:36:01.684Z</atom:updated>
            <content:encoded><![CDATA[<p>As a developer it’s important to have a consistent environment for several reasons.</p><ul><li><strong>Working as a team</strong>: In today’s modern work world especially in the BYOC/BYOD culture, or engaging with external people or in startups where they may not provide you with your own hardware because “startup budget” - everyone has different hardware and software setups. This means they will have different system versions of node.js / ruby / python — and also different ways of patching this.</li><li><strong>Standardized production environment</strong>: It’s ideal to have the production environment (version wise) to be exactly the same as the development environment. The closer you can get it, the more bugs you can catch before. More bugs caught = happier customers.</li><li><strong>Better Quality Assurance/Control Processes</strong>: Developers or anyone else are not very good at catching their own mistakes. From a UX point of view if you have better developed product, you would probably want to either have the product owner or a dedicated quality assurance person/team/provider. But to have a good Quality Assurance Process you need to know what sort of versions they need to use and also give exact instructions on how to set it all up.</li></ul><p>Tools you can use (I know there are others, but this is what I use)<br>- Ruby: <a href="https://github.com/rbenv/rbenv">rbenv</a><br>- Node.js: <a href="https://github.com/creationix/nvm">nvm</a><br>- Python: <a href="https://github.com/yyuu/pyenv">pyenv</a><br>- Systems/Infrastructure (and deployment): <a href="https://github.com/puppetlabs/puppet">puppet</a>, <a href="https://github.com/chef/chef">chef</a>, <a href="https://github.com/docker/docker">docker</a></p><p>Using the above tooling let you choose the version that will be run across all environments (as well as not mess up someones local system — personally I do not take too kindly to someone making me install software packages, unless you’re a top paying client)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c1f2f7cdb81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup Weekends for what its worth]]></title>
            <link>https://medium.com/@nolim1t/startup-weekends-for-what-its-worth-f8df86bcc92e?source=rss-21ce4a1595f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8df86bcc92e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[@nolim1t]]></dc:creator>
            <pubDate>Wed, 25 Nov 2015 06:43:35 GMT</pubDate>
            <atom:updated>2015-11-25T06:43:35.750Z</atom:updated>
            <content:encoded><![CDATA[<p>As an attendee of different startup weekends from around the world, I’d like to share why it is a good idea attend one — even if you are working in or another startup, or in a corporate job.</p><p>There’s something for everyone in the startup ecosystem.</p><h4>Networking</h4><p>This point applies to everyone (don’t expect people to work on your idea that you pitch). For those who are working on another startup it’s also a good way to find people that you can work with — as you can see how well they execute, work as a team and work under pressure.</p><p>For those already in (and happy) in a corporate job, you could use the event to scout for talent (but please don’t just go there just for that and not participate — it’s seriously not cool). But also you could also look for some potential standouts and do some angel investing.</p><p>This is my main reason for attending, after going to 3 different startup weekends in different cities/countries you start to get to know your team really well towards the end.</p><h4>Validation of your Idea</h4><blockquote>Pivot/Tweak/change your idea/business or Fail Fast</blockquote><p>As a startup, it is very important that you tweak your idea or fail as quickly as possible — before your runway exhausts itself.</p><p>If you can do it in an intense 54 hour weekend, it’s even better.</p><p>Startup Weekends first focus on validation of the idea, as in you must be prepared to go outside the building to talk potential customers about what they think (so be prepared to research which areas you need to travel to).</p><p>And yes — even as a technical founder who does code, I am still prepared to do the hustle if required.</p><p>Startup Weekends also give you access to a wide variety of mentors in different areas where you can also validate your business with them as well where the insight can be very valuable.</p><p>Last but not least, you can also validate your idea with the other attendees. At the beginning of the night is where people vote on the top ideas which gives you an idea if it was a good idea to begin with (and also how hard it would be to grow your core team).</p><h4>Promotional materials and Support from sponsors</h4><blockquote>Free schwag!!! (and food/drink all weekend).</blockquote><p>No one walks away from a startup weekend empty handed.</p><p>At the very minimum, attendees at startup weekends at least get fed all weekend and provided with a T-Shirt from the event or sponsors.</p><p>At the last two startup weekends I attended, the .co registry was also a sponsor which gives you access to a free domain for your startup for 1 year.</p><p>Then of course, you get a cloud provider such as Google or Amazon who can provide free hosting credits.</p><p>This year, Google Cloud seemed to be the sponsor. Though, I still prefer Amazon Web Services though. The credits seemed to last longer (especially if you’re using an army of micro instances). But it gives me a good opportunity to learn how to use Google Cloud.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8df86bcc92e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>