<?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 Kristóf Dombi on Medium]]></title>
        <description><![CDATA[Stories by Kristóf Dombi on Medium]]></description>
        <link>https://medium.com/@Kristof0425?source=rss-bb4db6149075------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mmet_QjbnHGlJMMvBjFj4A.jpeg</url>
            <title>Stories by Kristóf Dombi on Medium</title>
            <link>https://medium.com/@Kristof0425?source=rss-bb4db6149075------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:46:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Kristof0425/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[I made my first $5 on the internet ]]></title>
            <link>https://medium.com/hackernoon/i-made-my-first-5-on-the-internet-a277b421990?source=rss-bb4db6149075------2</link>
            <guid isPermaLink="false">https://medium.com/p/a277b421990</guid>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[os-x]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[my-first-5-dollars]]></category>
            <dc:creator><![CDATA[Kristóf Dombi]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 11:01:02 GMT</pubDate>
            <atom:updated>2019-04-30T08:19:43.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uNkim67NdSMMrObQljMPqg.jpeg" /></figure><h4>I created a volume limit app for OSX with no prior experience of native development under one month. 💻</h4><p>It is a pleasing moment in life when you can feel your work is appreciated. But to get to the point of appreciation, there is a journey ahead of every one of us. It contains lots of things to be fulfilled and plenty of experience to be gained. I feel <a href="https://earsafe.io/">Earsafe</a> (the app I wrote) is one of my first <em>milestones</em> in my journey. 🛫</p><p>With this piece of content, I’d like to share with you how I started out and what I learned along the way. <strong>So now sit back, relax, and enjoy your reading!</strong> 🍿</p><h3>TL;DR — for the lazy ones 😉</h3><p>I’m a regular guy, who made his first $5 through the <a href="https://hackernoon.com/tagged/internet">internet</a> by selling an <a href="https://hackernoon.com/tagged/osx">OSX</a> app he has made.</p><p>Here you can find my <strong>learnings</strong> and <strong>experience</strong> what I got during the last month while I was building/launching the app in a <em>digestible, 30 seconds format</em>:</p><ul><li><strong>⚡ ️Take commitments fast to achieve your goals</strong> — it worked for me (eg.: I bought my domain ~5 minutes after the idea came. 👉 motivation)</li><li>🏎 <strong>Make shortcuts and keep moving </strong>— simplify everything you can, as fast as you can</li><li>👌 <strong>Worry less, do more! Problems will get sorted out either way — </strong>just as Bob Marley said… if you feel overburdened, don’t hesitate to relax a bit</li><li>🐶 <strong>Eating your own dog food — </strong>using your own product on a daily basis is worth it for the long run</li><li>🛳 <strong>Ship as quickly as you can — </strong>don’t just move fast, ship fast and validate, like the big boys do</li><li>💰<strong>Validate your product by selling it for real — </strong>You’ll only know your product is worth $5 if you sell it for $5.</li></ul><h4>Two sentences about me — so you’ll be in the context 👨‍💻</h4><p>I’m a frontend developer from Hungary, who is part of the <a href="https://indiehackers.com/">indie hackers community</a> and <a href="https://wip.chat/">wip.chat</a>. I always have ideas (or side-projects), which I’m working on, constantly jumping between them and making my girlfriend crazy about this. 🤦‍</p><h4>Genesis of Earsafe 💡</h4><p>As I’m keen on The Verge’s Youtube content, I’ve come across a <a href="https://youtu.be/zGG3YsKpe88">video</a> of theirs, which was about how dangerous it is to listen to loud music for long hours through your earbuds. 🎧</p><p>I immediately came up with the idea after watching the video. It was about implementing a menu bar application, which takes care of your ears. 👂</p><p>Well, the next step was obvious, let’s check it out on Google, whether it already exists. This is what I’ve found: 🧐</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GqFqs6drPhSMG1OaQV-NWg.png" /></figure><p>So the bottom line is that I bought the domain after <strong>~5 minutes</strong> of watching the video.</p><h3>What I’ve learned / experienced:</h3><h4><strong>Take commitments fast to achieve your goals ⚡️</strong></h4><p>We have already reached my first learning by buying the domain so quickly. Taking commitments fast did the trick for me. I got focused so much on the project that I was able to overcome my fears of inexperience in native development. I jumped straight to Google, typing “<em>How to write a menu bar app for OSX?</em>”. 🛠</p><p>Although I have never written any line of code nor in Swift, nor in Objective-C, I could find a decent tutorial from where I could take off. 🚀</p><h4>Make shortcuts and keep moving 🏎</h4><p>The initial idea I had of the app was way more difficult than the actual output turned out to be. I had to leave out certain features to keep the <em>MVP</em> a truly <em>minimum viable product</em>. 📦</p><p>At first, I wanted to display the actual decibel level of the main output, but I had to let it go as it was way above my current knowledge. I couldn’t even find any helpful StackOverflow questions, so I felt it wasn’t worth the time to implement. ⏳</p><p>I had to move on. I didn’t want to spend more than a month just on the implementation as I had done with my earlier projects. 🛑✋</p><h4>Worry less, do more! Problems will get sorted out either way. 👌</h4><p>Sometimes you may find yourself in front of obstacles that block you from progressing or decreases your motivation towards the project. It happened to me as well with the decibel problem I’ve just mentioned. I was also afraid of native development at first. But I figured that <strong>less hesitating profits in more output</strong>. 📈</p><p>Just step back for a moment and relax, you’ll always have other options, solutions. 😴</p><h4>Eating your own dog food 🐶</h4><p>If you’re building something on your own, I highly recommend to use it on a daily basis. I started using <a href="https://earsafe.io/">Earsafe</a> as soon as I could and I’ve been using it since then.<br>You’ll find the biggest pain points in your product way faster this way. Even your early-adopters are just going to meet with edge-case bugs (hopefully 🤞) by the time of launching.</p><h4>Ship as quickly as you can 🛳</h4><p>As I wrote earlier, it’s a good practice to keep your pace on a higher level. Your biggest advantage as a solo “<em>maker</em>” is, that you can make decisions way quicker than companies can. 🏢</p><p>If you’re thinking of “<em>adjusting one of your features</em>” or “<em>repolishing the design of your landing page</em>”, <strong>you’re probably just making excuses not to ship</strong> <strong>your product and playing with your own time</strong>. 😟</p><p>I’m telling you this, because I have done the same with <a href="https://earsafe.io/">Earsafe</a>. In the end I figured out that I was just afraid of other people’s opinion (such a unique problem, right? 😀). I’m probably making this mistake over and over again. 🔄</p><p>It’s a tough thing to overcome your fears, but it’s a must in order to succeed. As far as I’m concerned, I’ll definitely need to improve in letting go my fears.</p><h4>Validate your product by selling it for real 💰</h4><p>I didn’t spend too much time to price Earsafe. ⏱ I saw other hackers pricing other menu bar apps around my price, so I sticked with that. 💵</p><p><strong>You’ll only know your product is worth $5 if you sell it for $5.</strong> It’s that simple.<br>The worst case scenario is that you’ll refund the money to your unsatisfied customer. But then you have a chance at least to get to know why you had failed, which is nice. 👍</p><h3>To sum it up:</h3><p><a href="https://earsafe.io/">Earsafe</a> is my first product, which I’m launching and I earned my first $5 by selling it. I have a long road ahead of me and plenty of things to do to get where I’d like to become, but I consider this sale as a good first step. 💪<br>I hope these highlights of my first milestone have been valuable to you to read.</p><p>Feel free to DM me on <a href="https://twitter.com/kristof0425">Twitter</a> if you are in the same shoes as me, I’d love to hear your story! ❤️</p><p>…Oh and don’t forget that if you’re a Mac user and you’d like to keep your hearing till your older ages, check <a href="https://earsafe.io/"><strong>Earsafe</strong></a> out! 👂🔊</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a277b421990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/i-made-my-first-5-on-the-internet-a277b421990">I made my first $5 on the internet 🔥</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I open sourced 3 modules from Airbnb]]></title>
            <link>https://medium.com/dailyjs/i-open-sourced-3-modules-from-airbnb-614bc5a2a51d?source=rss-bb4db6149075------2</link>
            <guid isPermaLink="false">https://medium.com/p/614bc5a2a51d</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[airbnb]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Kristóf Dombi]]></dc:creator>
            <pubDate>Thu, 24 Aug 2017 11:21:26 GMT</pubDate>
            <atom:updated>2017-08-24T11:21:26.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eEh5GzjOtU1aBzvV9PHJCg.png" /></figure><h4>…and here is how it helped me</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4877k4Hq9dPdtmvg9hnGFA.jpeg" /></figure><h4>Background</h4><p>As I was reading <a href="https://medium.com/u/a0d352b51c4d">Adam Neary</a>’s story of <a href="https://medium.com/airbnb-engineering/rearchitecting-airbnbs-frontend-5e213efc24d2">Rearchitecting Airbnb’s Frontend</a>, I came across two React components, which have really aroused my interest as a rookie frontend developer.</p><p>To name them, they are called <a href="https://github.com/kristof0425/react-hide-at">&lt;HideAt/&gt;</a> and <a href="https://github.com/kristof0425/react-show-at">&lt;ShowAt/&gt;</a>. I had several reasons, why I got interested in them so much:</p><ul><li>I wanted to create my very first NPM module, but I didn’t want to make it, just for having one. I’ve always wanted to give value to the community by creating it.</li><li><a href="https://github.com/kristof0425/react-hide-at">&lt;HideAt/&gt;</a> and <a href="https://github.com/kristof0425/react-show-at">&lt;ShowAt/&gt;</a>, they solve a problem and I even think there are more potential in them.</li><li>They seemed easy to replicate, although at first sight, I didn’t have a clue how I should start implementing them.</li></ul><p>From the words of <a href="https://medium.com/u/c12a87767986">Adam</a>, <a href="https://github.com/kristof0425/react-hide-at">&lt;HideAt/&gt;</a> and <a href="https://github.com/kristof0425/react-show-at">&lt;ShowAt/&gt;</a> are:</p><blockquote>They are responsive utilities, which allow us to dramatically alter what the user experiences at different screen sizes without having to hide and show using CSS. This leads to much leaner pages.</blockquote><h4>Implementation</h4><p>As a starting point I went to <a href="http://airbnb.com/">airbnb.com</a>, opened up the React Dev Tools and searched for either <a href="https://github.com/kristof0425/react-hide-at">&lt;HideAt/&gt;</a> or <a href="https://github.com/kristof0425/react-show-at">&lt;ShowAt/&gt;</a>, I can’t remember now. 🙃 <br>Soon I realised, I have to implement 3 modules and not 2, since they were wrapped into a HOC called, <a href="https://github.com/kristof0425/react-with-breakpoints">withBreakpoints</a>. (<strong>Fun fact</strong>: <em>When I first encountered them, I didn’t even know exactly what a HOC is.</em>)</p><p>After this, I tried to copy the behaviour of the 3 modules from Airbnb’s website with the best of my knowledge and with the help of Google.</p><p>These three modules, taught me a few things:</p><ul><li>Reading the docs is always the <strong>shortest</strong> path</li><li>Before you’re about to create a new npm module, it’s useful to look for competition on the market, <strong>don’t reinvent the wheel</strong></li><li>It pays off <strong>reading your competitor modules’ source code</strong> (if there is one of course)</li><li><strong>Don’t hesitate</strong> so much on the How?, <strong>just start doing</strong> it and eventually you’ll get there</li><li><strong>Use </strong><a href="https://npms.io/"><strong>npms.io</strong></a> and take a look at how they are ranking your module, it can really <strong>provide you</strong> with some <strong>helpful insights</strong></li></ul><p>From the technical aspect:</p><ul><li>What HOCs are and why they are useful</li><li>Configuring babel and eslint</li><li>Getting familiar with test writing with jest, enzyme and Node‘s assert</li><li>Using coverage with coverall and Travis CI</li></ul><p>In the end, I was ready with all the 3 components featurewise. I was able to publish them, but I still didn’t have any unit tests written for them, nor a continuous integration service set up for the repos.</p><p>As I use quite a few npm modules from day to day, I tend to prefer those, which have tests written and own 💯 coverage percentages or rather 90% &lt;. <br>So all in all, I had work to do, the hard work to do… at least I thought so.</p><p><strong>Travis:</strong><br>The ease of setting up Travis CI (<em>the integration service I chose to use</em>) was a <strong>pleasant surprise </strong>for me. I just had to create a .travis.yml with the following snippet:</p><pre># .travis.yml</pre><pre>language: node_js<br>node_js:<br>  - 6<br>  - 7<br>notifications:<br>  email:<br>    on_success: never</pre><blockquote><strong><em>TIP</em></strong><em>: The </em><em>notifications property is optional, but with declaring it, you can </em><a href="https://docs.travis-ci.com/user/notifications/"><em>configure your notifications</em></a><em> from Travis. In the above code snippet you can see that I prefer getting emails only about my failing builds.</em></blockquote><p><strong>Unit tests:</strong></p><p>Read the docs, read the docs and read the docs. 😃</p><p>No, but seriously, I haven’t written any unit test before, I didn’t even know the concrete difference between jest and enzyme. So you can imagine how I started this challenge. 😱</p><p>And after I read the docs carefully, suddenly I realised that this was a pleasant surprise as well. You can pick up unit test writing really quickly — of course I’m talking here about some basic things like, “component is able to receive and change its props”, but my message just tries to suggest that <strong>test writing is totally not hard to learn</strong>. 😊</p><p>To sum it up, these two were the ones, which seemed to me the biggest painful points in the implementation. I just wanted to tell you, that how wrong I was.</p><h4>More potential</h4><p>In my opinion <a href="https://github.com/kristof0425/react-hide-at">&lt;HideAt/&gt;</a> and <a href="https://github.com/kristof0425/react-show-at">&lt;ShowAt/&gt;</a> has more potential then just being responsive utilities. Combined with <a href="https://github.com/kristof0425/react-with-breakpoints">withBreakpoints</a> and <a href="https://medium.com/u/cc2eaf4f2cd2">James Kyle</a>’s <a href="https://github.com/thejameskyle/react-loadable">react-loadable</a> they could provide truly leaner webpages, by importing only the bundles the client-side needs.<br>For example, when you open a page on mobile, the tablet view bundle and the PC one could be left out, since they are unnecessary/redundant in that context. Those bundles could be imported in asynchronously, only when resize happens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4877k4Hq9dPdtmvg9hnGFA.jpeg" /></figure><h4>Final words</h4><p>If you got interested about these components, you can reach them via the links and if you were there, feel free to open issues or fork them. 🙂</p><p>Last but not least, I’d like to thank <a href="https://twitter.com/ruffle1986">Tamas Fodor</a> for mentoring me on these projects, <a href="https://medium.com/u/78b6281cf144">Jakub Juszczak</a> for your medium post about how to publish npm modules, and <a href="https://medium.com/u/a0d352b51c4d">Adam Neary</a> for creating <strong>that</strong> medium post and sharing these components, now they are shared with the whole React community. 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZrJKJqBsksWd-8uKM9OvgA.png" /></figure><p><em>Please hit or hold that little 👏 icon, if you liked my little story of my first 3 npm modules, and thank you for reading this!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=614bc5a2a51d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dailyjs/i-open-sourced-3-modules-from-airbnb-614bc5a2a51d">I open sourced 3 modules from Airbnb</a> was originally published in <a href="https://medium.com/dailyjs">DailyJS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>