<?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 Ignacio Alonso on Medium]]></title>
        <description><![CDATA[Stories by Ignacio Alonso on Medium]]></description>
        <link>https://medium.com/@ignacio-al?source=rss-2ed015ac9f39------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fhg09JJ6KXLY40lx_5v8FQ.jpeg</url>
            <title>Stories by Ignacio Alonso on Medium</title>
            <link>https://medium.com/@ignacio-al?source=rss-2ed015ac9f39------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:06:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ignacio-al/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[Tips to get a developer job after a coding bootcamp]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@ignacio-al/tips-to-get-a-developer-job-after-a-coding-bootcamp-78bffe013ca9?source=rss-2ed015ac9f39------2"><img src="https://cdn-images-1.medium.com/max/1400/1*NIgxjFZRU-oRAx0_1TdFPw.jpeg" width="1400"></a></p><p class="medium-feed-snippet">The next paragraphs are where I tell you a little bit about my story, where I was, where I wanted to be and the things I started to do to&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@ignacio-al/tips-to-get-a-developer-job-after-a-coding-bootcamp-78bffe013ca9?source=rss-2ed015ac9f39------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@ignacio-al/tips-to-get-a-developer-job-after-a-coding-bootcamp-78bffe013ca9?source=rss-2ed015ac9f39------2</link>
            <guid isPermaLink="false">https://medium.com/p/78bffe013ca9</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[Ignacio Alonso]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 00:00:05 GMT</pubDate>
            <atom:updated>2020-09-28T00:00:05.642Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How To Measure Your Product by Suhail Doshi]]></title>
            <link>https://medium.com/@ignacio-al/how-to-measure-your-product-by-suhail-doshi-245495565d92?source=rss-2ed015ac9f39------2</link>
            <guid isPermaLink="false">https://medium.com/p/245495565d92</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ignacio Alonso]]></dc:creator>
            <pubDate>Sun, 19 May 2019 20:29:24 GMT</pubDate>
            <atom:updated>2019-05-19T20:44:15.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*At-dWvVIN-i0W6uHgbnIxw.png" /></figure><h4>my notes on <a href="https://www.youtube.com/watch?v=MABmQhOlmJA">this video</a> by mixpanel.com Founder</h4><h3>Questions you’ll likely need to answer in the first 24 months of your startup</h3><h4>1. Is my product easy to understand?</h4><h4>2. Is it easy to get started with my product (For customers)?</h4><h4>3. Are people coming back to my product?</h4><p>—</p><p>Those 3 are the most important questions you could ask yourself when building your startup.</p><p>Then you’ll need to understand how to make a successful startup for that.</p><p>So we can break making a successful startup into a formula.</p><h3>The formula for a successful startup</h3><p>These nexts factors are the levers for your successful startup. The more you have down the funnel, the better you do.</p><h4>Visits</h4><p>People hitting your landing page or mobile app screen.</p><h4>Sign ups</h4><p>The number of people who then sign up.</p><h4>People who found value</h4><p>The number of people who do the thing the product was made for.</p><h4>Retention</h4><p>The number of people who then subsequently come back and do that valuable thing again.</p><h4>Spread the product</h4><p>The number of people who want other people to know about your product (sharing, word of mouth, sales, etc).</p><h4>= Growth</h4><blockquote><strong>The basics are really important.</strong></blockquote><p>All of the levers mentioned before are the basics. Most startup founders in Silicon Valley and outside never get the basics right.</p><p>They overcomplicate their metrics with thousands of fancy trackers that are just vanity metrics and ignore the really important stuff.</p><p><strong>If you focus on the basics and get them right. You’ll grow.</strong></p><ol><li>Pick 3–5 metrics.</li><li>These are things that guide the team.</li></ol><p>You should be able to assess why you’re not growing with this simple formula</p><p>This is how the funnel looks like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*XQQsX2IiMMIaTkYknkx56w.png" /></figure><p>Once you know why you’re not growing then you should be able to take action on a lever &amp; fix it.</p><h3>How to answer the 3 most important questions</h3><h4><strong>Ways to measure your product being easy to understand:</strong></h4><ol><li>Do people bother to sign up?</li><li>Ratio of single page visits to multi-page engagement</li><li>B2B: Do they visit your pricing page?</li><li>Consumer: Performing A/B tests of your copywriting</li></ol><h4><strong>Ways to measure your product being easy to get started</strong></h4><ol><li>People who do one valuable thing (ie: watch a video)</li><li>Measure a funnel of your initial user experience</li><li>Speed to doing that valuable</li></ol><p><strong>Tips and tricks to make it easy to get started:</strong></p><ol><li>Email/text confirmations will have significant drop-off</li><li>Constantly iterate on your initial user experience</li><li>Let users in the product before asking them to sign up</li></ol><p><strong>Ways to measure people coming back:</strong></p><p>Poor retention is often the <strong>most ignored</strong> metric by early founders. It’s often the reason even products with millions of users die.</p><ol><li>New users who came back 1 week + 30 days later to do a valuable thing again.</li><li>Number of people who use the product every day (DAU instead of MAU)</li><li>B2B: Revenue churn — monthly $ lost in a given month</li></ol><h3><strong>Q: What if I have &lt; 50 users/customers?</strong></h3><h4>A: Talk to your customers. Write everything down.</h4><p>You will always get more information from talking to customers than checking it on a graph.</p><p>Pick one north star &amp; choose 3–5 metrics.</p><blockquote>Less is more.</blockquote><p>A frequent mistake is having too many metrics that you monitor.</p><h3>Advanced resources</h3><p>•16 startup metrics:<a href="https://a16z.com/2015/08/21/16-metrics/">https://a16z.com/2015/08/21/16-metrics/</a></p><p>•After the Techcrunch bump:<a href="http://redeye.firstround.com/2008/01/after-the-techc.html">http://redeye.firstround.com/2008/01/after-the-techc.html</a></p><p>•On Negative Churn:<a href="http://tomtunguz.com/negative-churn/">http://tomtunguz.com/negative-churn/</a></p><p>•A/B testing by Eric Ries:<a href="http://www.startuplessonslearned.com/2008/09/one-line-split-test-or-how-to-ab-all.html">http://www.startuplessonslearned.com/2008/09/one-line-split-test-or-how-to-ab-all.html</a></p><p>•The next feature fallacy:<a href="https://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product/">https://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=245495565d92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Product by Michael Seibel]]></title>
            <link>https://medium.com/@ignacio-al/building-product-by-michael-seibel-8dc6c1a3e68?source=rss-2ed015ac9f39------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dc6c1a3e68</guid>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Ignacio Alonso]]></dc:creator>
            <pubDate>Sat, 18 May 2019 19:14:29 GMT</pubDate>
            <atom:updated>2019-05-18T19:14:29.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*HDJ01mIdq4sbGOQh83bR6g.jpeg" /></figure><h4>my notes on a<a href="http://youtu.be/C27RVio2rOs"> great video by the current Y Combinator CEO</a></h4><h3>What’s the problem you are solving?</h3><p>Figure out what you are doing what’s your expected result.</p><h4>1. Can you state the problem clearly?</h4><p>If you need to write an essay to explain the problem you are doing it wrong. You should be able to explain it in 1 or 2 sentences.</p><h4>2. Have you experienced the problem yourself?</h4><p>Do you have experienced the problem? Is it something you actually know? How close are you to the pain?</p><h4>3. Can you define the problem narrowly?</h4><p>Niche down your solution from all of the customers that you want to help to the people that you can address first. In other words, ask:</p><blockquote>“How do we get the first indication that this thing is working?”</blockquote><h4>4. Is the problem solvable?</h4><h3>Who is your customer/user? (Who is your ideal first customer?)</h3><h4>1. It is <strong>not</strong> EVERYONE.</h4><h4>2. How often does your user has that problem?</h4><h4>3. How intense is the problem?</h4><p>The more intense the problem the higher you can charge for it.</p><p>You can test this by making it harder to use your product. If customers are still using it that means that the problem is intense.</p><h4>4. Are they willing to pay?</h4><h4>5. How easy it is to find them?</h4><p>How do you talk to the customers that are using your product for real, not the hobbyists?</p><p>It’s really important that <strong>you talk to the right customers. </strong>The ones that are using your product correctly and not taking advantage of you.</p><h3>Does your MVP actually solves the problem you are trying to solve?</h3><p>Test it by giving the product to customers!</p><h4>1. Which customers should you go after first? (the easy ones!)</h4><p>Who’s business is going out of business without using your product?</p><p>How do you find the people who are screaming for something like your MVP?</p><h4>2. Which customers should you run away from? (the bad/hard ones!)</h4><p>You identify them because they will be blasting support constantly, complaining stupidly, being rude.</p><h4>3. Should you discount or start with a super low price (no!)</h4><p>There are structured ways where you can offer third party discounts.</p><p>He gives an example where the Zenefits founder offered discounts because AWS gave some credits and he went and talked to his customers and said “Ok I have this discount and I can give you this for 3 months if you buy now, I don’t want you to miss on this”</p><p>That kind of discount is really great and works better than what’s usually done.</p><h3>How to setup metrics</h3><p>If you are only using Google analytics to get data <strong>you are doing it wrong.</strong></p><h4>Google analytics + <strong>something else (event based analytics like Mixpanel, etc)</strong></h4><p>It is really important to setup an event based analytics tool to get actionable data about how are your customers using your app.</p><p>It will be the #1 source of product ideas an inspiration.</p><h4>Pick 5–10 important tasks to measure at first</h4><p>Don’t go overboard trying to measure every single thing imaginable.</p><p><strong>Everyone in your company must understand how to use Mixpanel and read it. </strong>This is not a tool that only the CTO uses and runs but one that <strong>EVERYONE on the team must use.</strong></p><p>e.g. Instagram 5 important tasks at the beginning for customer actions:</p><ol><li>Open the App.</li><li>Create an account.</li><li>Took a photo</li><li>Applied any effects</li><li>Shared the photo</li></ol><p>Naming conventions are really important when starting out since you probably are going to end up with 1000’s of tasks when growing.</p><h4>Make measurement a part of your product spec</h4><p>Spec the stats to track.<br>Spec the stats to improve when you build the product.</p><h3>Product development cycle (v 1.0)</h3><p>write down specs!</p><p>You should have short dev cycles (1–2 weeks the most for web products).</p><h4>KPI Goal</h4><p>Track how good you are doing.</p><p>For revenue generating products you should Almost ALWAYS track <strong>revenue.</strong></p><p>For free products, track should be <strong>usage based.</strong></p><p>99% of times you should use those KPI’s.</p><p>When investors ask you should be able to say what’s the metric being tracked, what’s the current number, what it was 3 months ago, what it was at the beginning.</p><h4>Brainstorm</h4><p>Any idea that’s stated is written on the board. No idea is dumb enough to not be written down.</p><p>Everyone computer should be opened to see Mixpanel metrics and check statistics on the spot.</p><p>You should have a board with ideas for new features | bug fixes | tests.</p><p>Then separate every idea into <strong>EASY, MEDIUM HARD.</strong></p><p>Easy ideas can be implemented in less than 1 day.</p><p>Medium ideas take 1–2 days.</p><p>Hard ideas take 1 developer the whole cycle.</p><p>If you have a hard idea think about which parts are useless and hard. Almost always most hard ideas are both, remove.</p><h4>Decide which idea impacts KPI the most</h4><p>Go for hard first.</p><h4>Write specs</h4><p>After brainstorming actually write the specs on how the idea will look like code wise, delegate.</p><p>Cadence of release should be 1–2 weeks at most.</p><h3>Pivot vs iterate</h3><p>This is hard. Building is hard. If it was easy then somebody would have done it by now.</p><p>It’s going to take at least 2 years of constant iteration and shipping to reach product-market fit.</p><h4>Pivot = Changing customers or changing the problem (rare)</h4><h4>Iterate = Changing the solution (common)</h4><p><strong>Identifying the problem is the genius part. </strong>Google wasn’t a search engine at first, Facebook wasn’t a social network at first, Justin TV wasn’t a streaming service at first.</p><p>Don’t try to find customers for your solution but change the solution to a good problem.</p><h3>Fake Steve Jobs vs Steve Jobs</h3><p>Real Steve Jobs iterates and talks to customers.</p><p>Fake Steve Jobs just dreams and creates art.</p><h4>Don’t be fake Steve Jobs.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dc6c1a3e68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should stop fearing shipping your products]]></title>
            <link>https://medium.com/@ignacio-al/why-you-should-stop-fearing-shipping-your-products-8b6cc2c4b7e5?source=rss-2ed015ac9f39------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b6cc2c4b7e5</guid>
            <category><![CDATA[freecodecamp]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[indiehackers]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ignacio Alonso]]></dc:creator>
            <pubDate>Wed, 15 May 2019 18:12:44 GMT</pubDate>
            <atom:updated>2019-05-15T18:12:44.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7j69jLMyDHg_ZMlI" /><figcaption>Photo by <a href="https://unsplash.com/@ffstop?utm_source=medium&amp;utm_medium=referral">Fotis Fotopoulos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a novice indie hacker my biggest fear to overcome is shipping. I spent way too much time developing my idea into a product and then I suddenly fell anxious when it’s time to show it to the world.</p><p>What if they laugh? What if it’s not good enough? What if nobody cares?</p><p>These are some of the questions that I start to think about and the hard truth is that even if those things where to happen…</p><h4>…None of it really matters for your success!</h4><p>If you really want to be successful as an indie hacker you must care about the right things:</p><ol><li>Solving a really painful problem so that customers are willing to pay you for solving it.</li><li>Shipping so that you know if your solution is actually a solution that people care about enough to pay (redundant but must be understood).</li><li>Caring only about the actual process on finding and latching on to the right solution, not the idea that you have.</li></ol><p>As <a href="https://medium.com/u/67f5049293c7">Naval Ravikant</a> said on twitter:</p><h3>Naval on Twitter</h3><p>My number one predictor of whether or not a company will find product-market fit: High shipping cadence.</p><p>And also Paul Graham:</p><h3>Paul Graham on Twitter</h3><p>@naval @__tosh I would not disagree with that. It might sound like you could spoof this heuristic by constantly shipping random crap. But no one can stand doing that for long. So in practice shipping regularly means you&#39;re on the track.</p><blockquote>“So in practice, shipping regularly means you’re on the track”</blockquote><p>To be successful then you should start caring more about finding the right thing to solve and pursuing it with relentless focus.</p><p>While also caring about the solution enough to be motivated to pursuit it and find the right angle for it to work with the market that wants it.</p><p>Two months ago I stopped being fearful about shipping my ideas and <a href="https://www.producthunt.com/posts/quote-genius">launched my first paid product on product hunt</a>. And it was awesome really.</p><p>It was not one of the top products of the day and it didn’t make me rich overnight (I only earned like $90).</p><p>But the truth is that it was an amazing learning experience where I got people visiting my application and actually buying it! A guy from Australia bought it even thought I’m in Mexico, how cool is that?</p><p>Now I’m a little ahead, I know a little more about selling online and I validated that I can make it work!</p><p>So, what’s stopping you from getting closer to your goals?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b6cc2c4b7e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to learn anything in 20 hours (and start MAKING)]]></title>
            <link>https://medium.com/swlh/how-to-learn-anything-in-20-hours-and-start-making-463e90559e3?source=rss-2ed015ac9f39------2</link>
            <guid isPermaLink="false">https://medium.com/p/463e90559e3</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Ignacio Alonso]]></dc:creator>
            <pubDate>Thu, 14 Jan 2016 22:30:00 GMT</pubDate>
            <atom:updated>2016-04-27T00:59:55.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MdIFO-nmYEegIdkBM6g_Sg.jpeg" /></figure><p>Here are some tips for you to learn how to code straight from the <a href="http://amzn.to/1SQMQRV">best</a> <a href="http://amzn.to/1JNdauc">books</a> on learning ( you can use this list to learn whatever you want):</p><p>First we must make a distinction between <strong>skill acquisition </strong>and <strong>learning</strong>:</p><ul><li><strong>Learning: </strong>The theory of everything, the rules of the game, e.g. When you learn spanish in school.</li><li><strong>Skill acquisition: </strong>When you go and talk and practice spanish with native speakers.</li></ul><h4><em>When you learn you plan, edit and correct as you practice.<br>Learning is NOT skill acquisition.</em></h4><p>If you want to acquire a new skill you must:</p><ul><li><strong>Train: </strong>Improve a skill you already acquired through repetition. What happens after you acquired a basic skill if you want to keep improving.</li></ul><p>So now that we are clear about the difference between skill acquisition and learning how can we go about improving our way of doing both?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tku66LQaRW0w7_MtG-TMyQ.png" /><figcaption>@sivers on learning</figcaption></figure><p>According to Josh Kaufman in <a href="https://www.youtube.com/watch?v=5MgBikgcWnY">How to learn anything in 2o hours</a> we have a checklist:</p><h3>Checklist for effective learning:</h3><ol><li><strong>Research the skill and related topics</strong></li><li><strong>Jump in over your head (don’t fear confusion)</strong></li><li><strong>Identify mental models and mental hooks:</strong><br> Mental models are the most basic unit of learning: a way of understanding and labeling an object or relationship that exists in the world while mental hooks are metaphors and analogies you can use to remember new concepts.</li><li><strong>Imagine the opposite of what you want:</strong><br>By knowing the least desirable outcome you can notice important steps that must be learnt.</li><li><strong>Talk to practitioners to set expectations</strong></li><li><strong>Eliminate distractions in your environment</strong></li><li><strong>Use spaced repetition and reinforcement for memorization</strong></li><li><strong>Create scaffolds and checklists</strong></li><li><strong>Make and test predictions</strong></li><li><strong>Honor your biology (90 minutes is the optimal time for learning)</strong></li></ol><p>Now if you follow the checklist you will be ready for the next step. Skill acquisition:</p><h3>Checklist for rapid skill acquisition</h3><ol><li><strong>Choose a lovable project</strong> (e.g. Making a website, learning to draw, dance, play your favorite song on the guitar)</li><li><strong>Focus your energy on one skill at a time</strong></li><li><strong>Define your target level of performance: </strong>What kind of website would you like to create? How well would you like the song to sound?</li><li><strong>Deconstruct the skills into subskills </strong>( CSS: broken down is just different codes in order of importance and specificity that style a website. Guitar chords are just combinations of different notes, etc.)</li><li><strong>Obtain critical tools </strong>(Computer, Guitar, etc)</li><li><strong>Eliminate barriers to practice:</strong> Turn off your cellphone and mail client</li><li><strong>Make dedicated time for practice</strong></li><li><strong>Create fast feedback loops</strong> ( For programming you can use an IDE to quickly know if you are correct or not, and adjust accordingly)</li><li><strong>Practice by the clock in short bursts</strong> ( Use things like pomodoro to make intense focused blocks of time)</li><li><strong>EMPHASIZE QUANTITY AND SPEED</strong></li></ol><p>These are the basics of learning and skill acquisition, you can use these framework to learn anything you want.</p><h4>Stop losing time consuming content and start optimizing your outflow of creations!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*DBLBZnyM6Qw5u5sGbxd3jA.gif" /></figure><h4>If the article was helpful to you, please press Recommend and share the article with someone who might need this.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=463e90559e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-learn-anything-in-20-hours-and-start-making-463e90559e3">How to learn anything in 20 hours (and start MAKING)</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>