<?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 Salil Navgire on Medium]]></title>
        <description><![CDATA[Stories by Salil Navgire on Medium]]></description>
        <link>https://medium.com/@salilnavgire?source=rss-a8bc40fdd561------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s3RSTJ1SCTqV7G_9HmWTkQ.jpeg</url>
            <title>Stories by Salil Navgire on Medium</title>
            <link>https://medium.com/@salilnavgire?source=rss-a8bc40fdd561------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:21:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@salilnavgire/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[Book Summary: 14 Habits of Highly Productive Developers by Zeno Rocha]]></title>
            <link>https://medium.com/@salilnavgire/book-summary-14-habits-of-highly-productive-developers-by-zeno-rocha-8494d7c6b04a?source=rss-a8bc40fdd561------2</link>
            <guid isPermaLink="false">https://medium.com/p/8494d7c6b04a</guid>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[jomo]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Salil Navgire]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 21:20:02 GMT</pubDate>
            <atom:updated>2021-12-09T07:09:17.719Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IyBmcBuu5wck4exQ" /><figcaption>Photo by <a href="https://unsplash.com/@punttim?utm_source=medium&amp;utm_medium=referral">Tim Gouw</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Yesterday, I was going through my usual quarantine routine of sipping fresh coffee and scrolling through blogs and social media searching for a dopamine fix. I came across a Show HN article with a very clichéd title <em>14 Habits of Highly Productive Developers </em>that was released the same day<em>, </em>I normally click on a title that’s catchy but my FOMO has reached so extreme that ill read about anything. The website gave a free preview of chapter 1 of the book, and I ended up reading it in a couple of minutes. The substance of the book was really interesting, but I stumbled across that sentence.</p><blockquote>“We are constantly faced with FOMO….Instead, we should practice <strong>JOMO</strong> (the joy of missing out), which is mostly about being happy and content with what you already know. ” — Zeno Rocha</blockquote><p>This was the first time I came across that term and I am like WTF’s JOMO? So, I ended up reading more online and turns out it is a legit word and there are even books published on that subject. By essence, JOMO embraces the idea that it is humanly impossible to keep up with everything and to be content with what you might miss out on. Seems like a very interesting concept but difficult to implement in real life. Anyway, I ended up buying the book!</p><h3></h3><p>Play iterated games. All the returns in life, whether in wealth, relationships, or knowledge, come from compound interest.</p><blockquote>“Habits are the compound interest of self-improvement…. It is only when looking back two, five, or perhaps ten years later that the value of good habits and the cost of bad ones becomes strikingly apparent.” — James Clear</blockquote><p>Zeno seeks to encapsulate all of his experience from 10 + years of work, contributing to open-source software and giving various talks around the world in slim, succinct 125-page books with tips from the best developers working in top tech companies. This is my feeble attempt to summarize the book into a blog post.</p><h3>Habit 1: Look For The Signals</h3><p>Practice JOMO, try to strike a good balance between putting your existing skills into action and learning new. You should not waste time checking some shiny new tool posted on HackerNews or ProductHunt as there is no best tool available. Instead seek to concentrate on saying more noes than yes. Sparingly using Yes!</p><blockquote>“Accept the fact that you simply can’t learn everything. Remember, desires are endless; needs are limited” — Zeno Rocha</blockquote><h3>Habit 2: Focus On The Fundamentals</h3><blockquote>“You can practice shooting eight hours a day, but if your technique is wrong, then all you become is very good at shooting the wrong way. Get the fundamentals down and the level of everything you do will rise.” — Michael Jordan”</blockquote><p>Stress getting your basics right and they’ll help you out in the future. If you want to become a great developer, it’s best to spend more time learning Algorithms, Data Structures, Networking, System Design, etc. because even if it doesn’t benefit you in the short term, in 10 years it’s going to be of immense help.</p><h3>Habit 3: Teaching Equals Learning</h3><h3></h3><p>If you want to master something, teach it. A great way to learn is to teach. pic.twitter.com/6FDrVMf5yy</p><p>The process of teaching something through a talk, blog, or video helps you reconsider and digest the material easier. You are especially careful to learn and understand everything, so that you can explain it to others convincingly and answer their questions better.</p><blockquote>“If you can’t explain it to a six year old, you don’t understand it yourself.” — Albert Einstein</blockquote><h3><strong>Habit 4: Be Boring</strong></h3><h3></h3><p>Being very boring will make you very rich #algebraofhappinessvia @BettyWLiu https://t.co/9X5OmbHAo3</p><p>Intensity is unsustainable, leading to burnout and frequent breaks. When you’re more persistent you ‘re putting in more hours or doing better in the long run than hitting limits every day.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_fbCcWyYthQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_fbCcWyYthQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_fbCcWyYthQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/964be7dcfc78c08b70692481af2f6fe1/href">https://medium.com/media/964be7dcfc78c08b70692481af2f6fe1/href</a></iframe><p>James Carse introduced in his <a href="https://www.amazon.com/Finite-Infinite-Games-James-Carse/dp/1476731713">book</a> the idea of finite games (known players / goal to win) and infinite games (known and unknown player / target to keep playing) Programming is an infinite game, even if most people believe it’s a finite game and they keep working from sprint to sprint, hoping for a bonus, and completing it for the sake of it, you are not going to get very good at it.</p><blockquote>“Deep down we all want to be rebels. Discipline. Consistency. Persistency. Those concepts are not sexy at all, but they are the key to playing infinite games.” — Zeno Rocha</blockquote><h3>Habit 5: Do It For Your Future Self</h3><h3></h3><p>Tag yourself, I&#39;m me. pic.twitter.com/x0oGXa60f7</p><p>How many times have you started a side project, have all been excited about it for a couple of days and then you see another shiny object a new platform, tool, or project which you want to play with. You are abandoning your current project but when you come back to it next year, you have no context whatsoever and you don’t understand what you’ve written. Always code as if you’re writing it for your future self and not for the current self; using meaningful names, writing comments, or keeping documentation will make it easy for you to get started where you left off, or even better not to switch frequently because it has <a href="https://fs.blog/2011/08/switching-costs/">negative cost</a>.</p><h3>Habit 6: Your 9–5 Is Not Enough</h3><blockquote>“Don’t expect to be motivated every day to get out there and make things happen. You won’t be. Don’t count on motivation. Count on discipline.” ― Jocko Willink</blockquote><p>Putting 9–5 work is perfectly fine but developers are valued for their skills and if not updated they can get stale very quickly. You need to get out of your comfort zone because your job isn’t reflecting your full potential.</p><h3></h3><p>There is no progress in the comfort zone. pic.twitter.com/LU3t1Se6n4</p><h3>Habit 7: Master The Dark Side</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/0*wC_qQ27occmMRhOD.jpg" /></figure><p>The author states that he assumed programming was the light side and business was avoided because it was the dark side. And he discovered that it was a valuable skill that could help everyone connect, plan better than save time in the end. It’s rare for developers to know the business side of things and to be able to connect with those people that could help them in their careers.</p><h3>Naval on Twitter: &quot;Learn to sell. Learn to build. If you can do both, you will be unstoppable. / Twitter&quot;</h3><p>Learn to sell. Learn to build. If you can do both, you will be unstoppable.</p><h3>Habit 8: Side Projects</h3><h3></h3><p>One reason there are so few really big startups founded by MBAs is that MBAs don&#39;t do side projects.</p><p>Many of today’s popular major tech companies have been launched as a lame side project concept. You should pick a side-project that overlaps your personal interest with the skills you want to learn. The author lists the questions you should ask before you start,</p><ul><li>Do I really enjoy this work?</li><li>Are you willing to spend at least 5 years on this idea?</li><li>Can you execute this idea fully by yourself or would need some external help?</li></ul><h3>Habit 9: Mario Or Sonic?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2OdjQV6kmfHyUuIB.jpg" /></figure><p>The author uses these 2 fictional characters — Mario(jumping one place to another representing courage) and Sonic(facing challenges and representing resilience). He further says that its okay to switch jobs frequently at the beginning of your career but it can lead you to be superficial than making a long term impact. Both have equal potential but if you have a choice then be more like Sonic.</p><h3></h3><p>GRIT: talent x effort = skill skill x effort = achievement. EFFORT counts twice! Angela Duckworth @angeladuckw speaking to neurosurgeons about GRIT pic.twitter.com/IS1oF2uOSA</p><h3>Habit 10: Active Listening</h3><blockquote>“Everyone you meet is fighting a battle you know nothing about. Be kind. Always.” — Robin Williams</blockquote><p>A company is just a collection of individuals with diverse skills set and roles like engineer, sales, HR, designers, product managers, etc. Conversations go both directions, not only talking all the time, but mastering the art of active listening, not responding back, but actually knowing it.</p><h3>Habit 11: Don’t Underestimate</h3><p>Developers solve problems but most times they are really bad at estimating the time it will take to solve something. How many times have you been in a situation where you thought it would take 1 hour to fix some problem but end up spending the whole day? Here are some reasons which contribute to it,</p><ul><li>we want to impress others</li><li>we forget that its not all about coding</li><li>we don&#39;t focus on one thing</li><li>we think everyone is the same</li><li>we cant handle the pressure</li></ul><p>Without being able to say “no” and lack of estimation skills, we end missing deadlines and lose faith, in these circumstances it is safer to be <strong>under promise and overdeliver</strong>.</p><h3>Habit 12: Specialist vs Generalist</h3><blockquote>if you want something extraordinary, you have two paths:<br>1. Become the best at one specific thing.<br>2. Become very good (top 25%) at two or more things. — Scott Adams</blockquote><p>Every developer will be in a situation where they have to decide to be a Specialist or a Generalist, both approaches work but it depends on what you identify with</p><p>Specialist<br>Pros — Good compensation, technical authority, only need to be updated on one platform/language<br>Cons — roles are few, risk of becoming obsolete</p><p>Generalist<br>Pros — learning new technologies fast, more opportunities, flexible and easy to transition in new company<br>Cons — hard time to solve technology specific problem, difficult to reach leadership position if you keep switching fields constantly</p><h3>Habit 13: Control your variables</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*tVn4RG57bWbOXa2I4m5mPw.png" /></figure><p>With the current COVID 19 quarantine, we keep worrying about many things, and spending time on social media doesn’t help. There are some variables you can control — washing your hands, avoiding public gatherings, wearing masks, and staying healthy, but you cant control how bitcoin prices fluctuates, politics or layoffs. You can control how to react to this situation and make the best of it, your response will determine your character.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/0*cSJYyuyBml_5JVU8.png" /></figure><h3>Habit 14: Stop Waiting</h3><blockquote><em>“We suffer more often in imagination than in reality.” — Seneca”</em></blockquote><p>Most humans are keep wishing for better future, but we are still waiting for that moment when you feel strongly about doing it, but it rarely happens and we end up feeling a lack of motivation. The only thing that doesn’t let you do it is yourself!</p><blockquote><em>We bought in to this complete falsehood that at some point you are going to have the courage…at some point your going to have the confidence….and it’s total bullshit frankly! — Mel Robbins</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX54GQFS_ouM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX54GQFS_ouM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX54GQFS_ouM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6dd0ae84a0fac36bb927770373d9a850/href">https://medium.com/media/6dd0ae84a0fac36bb927770373d9a850/href</a></iframe><h3>Final Thoughts</h3><p>I really liked the book, some people might think it’s too shallow, or the author doesn’t go too deep into the subjects. I think the book is mainly for beginners who are starting as developers and need to help them manage their careers. There are several books you can read to get deeper into those subjects. The author has done a brilliant job of encapsulating all of his teachings in this book and please go buy the book if you can and support the author here — <a href="https://14habits.com/">https://14habits.com/</a> or buy on amazon -<a href="https://www.amazon.com/dp/B08BF74RRG">https://www.amazon.com/dp/B08BF74RRG</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8494d7c6b04a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>