<?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 Abhishek Pillai on Medium]]></title>
        <description><![CDATA[Stories by Abhishek Pillai on Medium]]></description>
        <link>https://medium.com/@abhishekpillai?source=rss-f9a3596b30d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NO5rkINYFUBIOkM2HZsZog.jpeg</url>
            <title>Stories by Abhishek Pillai on Medium</title>
            <link>https://medium.com/@abhishekpillai?source=rss-f9a3596b30d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:27:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhishekpillai/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[Transparent Leadership]]></title>
            <link>https://medium.com/teacherspayteachers/transparent-leadership-b285ef363ac5?source=rss-f9a3596b30d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b285ef363ac5</guid>
            <category><![CDATA[new-york-city]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Abhishek Pillai]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 18:16:12 GMT</pubDate>
            <atom:updated>2018-08-06T19:09:07.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*XiZqdzJkyenopk37.jpg" /><figcaption>Our CEO, Adam Freed, sharing company updates at an annual conference with teachers on our platform!</figcaption></figure><p>Have you ever had the experience where you are listening to a presentation by a leader at your company and you (and everyone else) is wondering,</p><blockquote>“I hear what they’re saying but what are they REALLY thinking?”</blockquote><p>I have even heard of a leadership team that told their whole company that “things are great” during one week and then laid off a number of people on the team the very next week!</p><p>In my last year and a half as a Tech Lead at Teachers Pay Teachers, I’ve seen our Senior Leadership Team (SLT) do things that have demonstrated a level of transparency that I have never heard of anywhere else and is something that I have come to value incredibly highly.</p><p>In this post, I want to share a few examples of that.</p><h3>Company Level OKRs</h3><p>The first example is not unique but I do want to call it out as it is my first experience with it.</p><p>Every year and every quarter, we define our company level objectives and key results (OKRs). OKRs are tools that get the company to focus on outcomes, gain alignment, measure progress, and enable autonomy. Essentially, they are goals and they help us all rally around the same things. There’s a lot that goes in to writing them well and you can <a href="https://felipecastro.com/en/okr/what-is-okr/">learn more about them here</a>.</p><p>Every week, we take 5 minutes as a company to review a few of them on a slide that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pUGe7sDxdD5I6b6T" /><figcaption>Template of a Google Slide that we use to show progress towards our key metrics</figcaption></figure><p>In terms of transparency, this tool provides me clarity around what the SLT is aiming to do for the quarter and for the year. I know that these are the goals that they are reviewing on a weekly basis and I have a link to the document they use to track the company’s progress.</p><h3>The Data Package</h3><p>Every week at Teachers Pay Teachers, we have a 30 minute, company-wide all-hands. In this all-hands, we spend 5 minutes reviewing key business metrics. Those metrics, in addition to a link to an in-depth look into our numbers, are auto-published daily in the #general slack channel and accessible to everyone!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfG0i78SSzxf8Hcc9XhUgA.png" /><figcaption>Screenshot of the daily, auto-published report in our #general slack channel</figcaption></figure><h3>Development Plans</h3><p>This was the best example of transparency that I have seen from a leadership team.</p><p>At the beginning of the year, our SLT collected feedback about their performance from people in the company. They did this by having a consultant solicit feedback through interviews with tens of people from all levels and across the organization. That feedback was shared, in both synthesized and raw form, with each member of the SLT. The team then shared the feedback they received with each other and put together development plans for themselves.</p><p><strong>Here’s the part where that transparency is taken to another level</strong>: The SLT presented their development plans in a presentation to the company! :shocked_face: During and at the end of the presentation, they all talked about how it was tough to digest all that feedback, present it openly, and ask everyone to hold them accountable.</p><p>At Teachers Pay Teachers, one of our company’s core values is that we learn and grow together. This is just one way our Senior Leadership Team practices it.</p><h3>The Value of Transparent Leadership</h3><p>It’s clear that being a transparent leadership team takes a lot of effort, especially in a fast-moving, fast-growing company. Among other things, it requires a lot of communication that needs to be repeated because there are always new people in the company who haven’t heard it before. But, that effort is worth it.</p><p>Having a leadership team that is transparent about the company, about their process, and about themselves is <strong>incredibly empowering to the teams that they lead</strong>. It empowers teams to make the best decisions quickly because they don’t have to worry about whether they have all the context they need to make the best decisions. If they feel that they are missing some context, there isn’t hesitation in asking for that context because transparency is the default.</p><p>If you’re part of a leadership team or a leader on a team, I hope you consider creating channels and processes through which you can be more transparent with your team(s).</p><p>If you’re not part of a leadership team, push your leaders to create channels through which you and your whole company can regularly get context.</p><p>It’s going to help you, your team, and your whole company level up.</p><p><em>Thanks for reading! We’re hiring! So, if you want to be part of a company with a transparent leadership team and a product loved by millions of educators around the world, then check us out at </em><a href="https://www.themuse.com/profiles/teacherspayteachers"><em>https://www.themuse.com/profiles/teacherspayteachers</em></a></p><p><em>Originally published at </em><a href="http://engineering.teacherspayteachers.com/2018/08/06/transparent-leadership.html"><em>engineering.teacherspayteachers.com</em></a><em> on August 6, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b285ef363ac5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teacherspayteachers/transparent-leadership-b285ef363ac5">Transparent Leadership</a> was originally published in <a href="https://medium.com/teacherspayteachers">teacherspayteachers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned from Coursera’s “Learning How to Learn”]]></title>
            <link>https://medium.com/learn-love-code/learnings-from-learning-how-to-learn-19d149920dc4?source=rss-f9a3596b30d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d149920dc4</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Abhishek Pillai]]></dc:creator>
            <pubDate>Fri, 26 Aug 2016 15:11:20 GMT</pubDate>
            <atom:updated>2016-08-28T00:17:45.759Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I’m using learning techniques from a Coursera course to be a better developer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkoIio7Ke2Yt4THOt_Ndpg.jpeg" /></figure><p>I’ve been a Software Developer for more than 4 years now and if there’s one thing that never changes about this job it’s that it is always changing. There are always new things to learn. I love that part of it. <em>Learning is the destination.</em></p><p>So, when I saw a course called <a href="https://www.coursera.org/learn/learning-how-to-learn"><strong>Learning How to Learn</strong></a> on Coursera, I jumped on the chance to learn about learning from academic experts — <a href="https://www.coursera.org/instructor/barboakley">Dr. Barbara Oakley</a> and <a href="https://www.coursera.org/instructor/terry">Dr. Terrence Sejnowski</a> from University of California, San Diego.</p><p>Here are the key takeaways from the course that help me be a better developer and, in general, a better learner.</p><h4><strong>“Focused” and “Diffused” Modes</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*b9268pO3ROlJ8lVFIRrOdg.gif" /></figure><p>When learning, there are times in which you are <em>focused </em>and times in which you allow your mind to wander. This unfocused, <em>or diffused</em>, mode is just as valuable as the focused mode in allowing your brain to LEARN something. So — <strong>take breaks, meditate, think about other things, and give yourself plenty of time in both modes</strong>.</p><p>One way of making sure you’re taking regular breaks is to follow the <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">Pomodoro technique</a>. This is where you program for 25 minutes, then take a break for 5 minutes. The work and break time lengths can vary based on what works best for you. The important part is that you have a regular break. There are several applications out there that help you setup a Pomodoro timer. I use <a href="https://itunes.apple.com/us/app/pomodoro-time-focus-timer/id973134470?mt=12">Pomodoro Time</a>.</p><h4><strong>Chunking</strong></h4><p>This is the idea of breaking what you want to learn into concepts. The goal is to learn each concept in a way that they each become like a well-known puzzle piece. In order to <em>master</em> a concept, you not only need to know <em>it</em> but also to know how <em>it</em> fits into the bigger picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*eHZ0OxiAUjYMNlSyY5K6Dg.png" /><figcaption>Mastered chunks form a whole puzzle (left) vs. learned but not mastered chunks don’t fit into a larger puzzle (right)</figcaption></figure><p>Dr. Oakley suggested a great step-by-step process to approach learning something. First, <strong>survey and priming</strong> — this involves scanning a book or the syllabus of a course, for example, to get a general idea of the bigger picture. Second, <strong>observe an example</strong>. Then, <strong>do it yourself.</strong> And, finally, <strong>do it again and again in different contexts</strong>.</p><p>So — let’s say I was trying to learn React and I was lucky enough to find <a href="https://medium.com/u/c52389e3ee63">Tyler McGinnis</a>’s awesome <a href="http://courses.reactjsprogram.com/courses/reactjsfundamentals">React.js Program course</a>. To apply this suggested process, I would first look over all the units in the course to try to get a general gist of the topics covered. Then, I would follow along closely as Tyler builds an example application. After that, I would build my own application. And finally, I’d apply those learnings into the new features we are developing in React at my job.</p><h4><strong>Beware of Illusions of Competence</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*YbNb1pYWQhd9Zz0Dh2cbAQ.jpeg" /></figure><p>There are many ways in which we can make ourselves <em>feel </em>like we have “learned<em>”</em> a concept. For example, looking at a solution and thinking that you know how to arrive at that solution is one of the most common illusions of competence in learning. Highlighting or underlining are also techniques that often lead to this illusion of learning. On the other hand, <strong>brief notes that summarize keys concepts are much more effective</strong>.</p><p>Recently, I found this great application called <a href="https://medium.com/u/f23e05cfe0ec">Highly</a> (<a href="https://www.highly.co/">you should use this!</a>). They make it really simple to highlight any article that I’m reading on the web using a Chrome extension. When I’m done reading and highlighting an article, it provides a beautiful summary of everything I highlighted. This is immensely useful to me.</p><p>I try to be sparing in what I highlight. The fewer takeaways, the more likely that I’ll actually take it away. This ties well into the next point…</p><h4><strong>Recall</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Qwv_V6ljhXZCGEubesLCLw.jpeg" /></figure><p>Dr. Oakley points to <a href="http://science.sciencemag.org/content/331/6018/772">Dr. Jeff Karpicke’s research about retrieval practice</a> to provide scientific support behind <strong>taking a couple minutes to summarize or recall material you are trying to learn</strong>. It goes a long way to taking something from short-term memory to long-term learning. Even recalling material in different physical environments can help you grasp the material independent of any physical cues that your brain may have.</p><p>So — after you finish reading this article (or any article), take a moment and try to state what you remember from the article. It’ll go a long away.</p><h4><strong>Bite-Sized Testing</strong></h4><p>In order to avoid or break through illusions of competence, you should <strong>test yourself as you’re encountering new material</strong>. Recall is a simple example of this mini-testing.</p><p>It’s not important that you pass these tests without making any mistakes. Mistakes (and correcting those mistakes) are an important step towards solidifying your learning.</p><h4><strong>Over-Learning</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*dXJcIXKipBETJ7zUI4V5hw.gif" /><figcaption>After a long learning session…</figcaption></figure><p>The main takeaway on this point is not to spend too much time in one sitting going over the same material over and over again. The law of diminishing returns certainly applies. <strong>Spread it out over many sessions and over many different modes of learning</strong>.</p><p>I have been trying to set aside 30–60 minutes every day for each new thing I am trying to learn or learn in more depth. Not only has this been better in resulting in lasting learning, but I also find it way more achievable to say that I am going to work on X for 30 minutes.</p><h4><strong>Interleaving</strong></h4><p>Once you have a basic understanding of what you are trying to learn, interleaving can be used to help you master the concepts. By practicing jumping back and forth between problems that require different techniques, you can solidify your understanding of the concepts by learning how to choose to apply them in various situations. <strong>Know <em>when</em> to apply a particular concept is as important as knowing <em>how.</em></strong></p><p>I haven’t deliberately applied this technique yet but, going back to the earlier example of learning React, I can apply the interleaving technique by having 2 different projects in which I am applying React and Flux architecture.</p><h4><strong>Process over Product</strong></h4><p>When facing procrastination, think of process over product. I often procrastinate when I’m overwhelmed by the thought, “Ok, I have to get X done”. Instead, <strong>it can be beneficial to think, “Ok, I will spend an hour on X” </strong>— which isn’t overwhelming, doesn’t require a long breakdown of tasks, and gets me started (90% of the battle).</p><h4><strong>Metaphors and Analogies</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hSpFmuFTtf5Hc_347Rtdhg.gif" /></figure><p>Metaphors and analogies are often talked about as helpful study techniques. Personally, I never made much use of them. But, as I’ve met more people and more teachers/mentors, I’ve found that the best ones always use these as they communicate. And being able to communicate what you’ve learned is one of the main skills that differentiates a good developer from a great one (IMHO).</p><p>So, <strong>try to make a deliberate effort to teach what you learn to someone else</strong> and, in doing so, you will likely be forced to explain concepts with relatable metaphors and analogies.</p><p>There are several opportunities in the daily practice of software development to teach and learn from others. You can pair program, comment on pull requests, sign up to give a code talk about a particular topic, and blog! <em>Do all of these things.</em> I know I’m trying to.</p><h4><strong>Study Groups / Teamwork</strong></h4><p>This one isn’t new to me and has proven to be most beneficial to maintain continued progress and hold each other accountable. But, it is important to include in this list and note that finding the right group is key.</p><p>At work, I’m lucky to have plenty of internal groups: tech book club (currently reading <a href="http://pragprog.com/the-pragmatic-programmer/">Pragmatic Programmer</a>), open source club, culture club, elixir group, and likely others too. But there are several awesome communities that meet and learn together in NYC and online!</p><p>No matter what or where you are learning, <strong>you don’t have to learn alone</strong>. In fact, it is the uniqueness of the people with which you learn and the discussions you have together that make what you learn unforgettable.</p><p><em>Click the ❤ below so other people will see this here on Medium.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*emxDrmtEiMy6h5JXecj-Og.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d149920dc4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-love-code/learnings-from-learning-how-to-learn-19d149920dc4">What I learned from Coursera’s “Learning How to Learn”</a> was originally published in <a href="https://medium.com/learn-love-code">Learn. Love. Code.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers: How to Overcome Imposter Syndrome]]></title>
            <link>https://medium.com/learn-love-code/developers-how-to-overcome-imposter-syndrome-48edee803cf4?source=rss-f9a3596b30d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/48edee803cf4</guid>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Abhishek Pillai]]></dc:creator>
            <pubDate>Thu, 28 Jul 2016 15:00:33 GMT</pubDate>
            <atom:updated>2016-07-28T19:21:22.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*725DsgO5CKgztSCce3whxw.jpeg" /><figcaption><a href="http://pre11.deviantart.net/a182/th/pre/i/2010/120/b/c/the_imposter_by_yastach.jpg">http://pre11.deviantart.net/a182/th/pre/i/2010/120/b/c/the_imposter_by_yastach.jpg</a></figcaption></figure><blockquote>“Impostor syndrome can be defined as a collection of feelings of inadequacy that persist even in face of information that indicates that the opposite is true. It is experienced internally as chronic self-doubt, and feelings of intellectual fraudulence.”</blockquote><blockquote>— <a href="https://counseling.caltech.edu/general/InfoandResources/Impostor">Caltech Counseling Center</a></blockquote><p>Whether you’ve just begun your journey to learn how to code or you’ve been paid to code for many years, you can and (likely) will face imposter syndrome. I’ve been working as a Developer for four years now and I still face imposter syndrome every day!</p><p>The nature of software development is fast-paced, fluid, and always in flux. It’s what makes building software so challenging, interesting, and fun. But that also means that you’re constantly faced with things you don’t know. And even the things that you don’t know (and everyone says you “need to know ASAP”) are changing before you can even <em>start</em> to know them.</p><p>So, you’ll need some ways to overcome that feeling of being an imposter. Here are a few ways that help me:</p><h4><strong>Get a Mentor</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*Ig_jiMRz2SbfUqZnFFZqAA.gif" /></figure><p>This one ain’t easy but it’s one of the things that most helped me get through my early days as a Developer. Preferably, your mentor is someone who is more experienced than you in software development or has worked on software teams, i.e. in QA, Product, Design, etc. <strong>A mentor can really help you get over the many humps you face early on</strong>. They don’t necessarily have to help you get over those humps by coding with you, but they can help give you perspective and guidance on your progress.</p><p><a href="http://blog.flatironschool.com/your-ultimate-guide-to-finding-and-keeping-a-tech-mentor">Here’s an awesome post by Flatiron School on <em>how</em> to find a mentor.</a></p><h4><strong>Get a Peer Pair</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*M817N_pT5cqK4Jw4qt-9rA.gif" /></figure><p>Form a “peer pair” with someone who is going through what you’re going through. It can be immensely helpful to be able to communicate your frustrations, failures, victories, or even just the day-to-day. With a peer, I have found that you can be more open without worrying about how they may view you. And more importantly, you can listen and learn from what they’re going through.</p><p>There’s a lot of fellow “newbies” out there in the developer community (check out the appropriately-titled <a href="http://www.codenewbie.org/">CodeNewbies</a> community) and everyone is a newbie in something. There’s a lot to learn about the different ways we all approach learning. So, <strong>find someone with whom you can share your learnings</strong>.</p><h4><strong>Surround yourself with smarter people and take advantage of it</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*Bug495w0zshJ9Rs3LRSbJQ.gif" /></figure><p>My first job in software development was as a Test Engineer at Groupon. I realize that not everyone is as fortunate to join a company with hundreds of experienced engineers. But, as you search for meet-ups, online communities, or prospective employers, <strong>put yourself in an environment where you’re the dumbest person in the room</strong>. Because that’s the way you’re going to learn the most.</p><h4><strong>Be curious</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*b1PWhxZJwL1XZXMSVyVYBA.gif" /></figure><p>Once you’re surrounded by smart people and challenging problems, be curious. <a href="http://shop.oreilly.com/product/9780596518387.do"><em>Apprenticeship Patterns</em></a><em> </em>by <a href="https://twitter.com/davehoover">Dave Hoover</a> and <a href="https://twitter.com/ade_oshineye">Adewale Oshineye</a> is a great book and a must-read for all developers. It treats software development like the craft that it is and paves your long journey from an apprentice to master with practical patterns. One of these patterns is “Exposing Your Ignorance”:</p><blockquote>“The <strong>most obvious way to expose your ignorance is to ask questions</strong>. This is easier said than done, particularly when the person you’re asking has assumed that you already know the answer. Press on! Sure, you could protect your pride and take less direct routes to obtain the required knowledge, but remember that your road to journeyman will be shortened by taking the most direct route available.</blockquote><blockquote>With practice and time, you will find that asking direct questions to the most knowledgeable people on your team will become second nature. While you are exposing your ignorance, you are also exposing your team to your learning ability. And sometimes they will gain a new clarity about their own knowledge in the process of answering your question.”</blockquote><blockquote>— Chapter 2: Emptying the Cup, Apprenticeship Patterns</blockquote><h4><strong>Pick something and practice it, regularly</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ms7N7zCf-c5GJ-nl1YGG0A.gif" /></figure><p>Earlier this year, a fellow coworker of mine declared his next month the “month of React.” So, he spent that month focused on learning React. From an outside perspective, I could see his conversations around React evolve over the course of the month. By the end of the month, he had created a #react-js slack channel within the company, was sharing links to libraries and concepts that others hadn’t encountered, had written a great <a href="http://snags88.github.io/tips-for-starting-out-on-react">blog post about learning ReactJS</a>, and is now building a big feature in React.</p><p>I’m not exactly sure how he picked ReactJS to be his focus, but it doesn’t matter. He <strong>picked it, stuck with it, and </strong><a href="http://expertenough.com/1423/deliberate-practice"><strong>deliberately practiced</strong></a><strong> it</strong>.</p><h4><strong>Make decisions consciously</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*5HFGZhpos6t_ugQtOBar-Q.gif" /></figure><p>Oftentimes, when faced with an overwhelming codebase, it can be easy to fall into the trap of programming by copy-pasting code, following existing patterns, and “making it work” without thinking through your choices. Try not to fall into this trap.</p><p>When you’re writing code, make sure you understand how your code works and why it’s structured in the way that it is. Remember, I’m not saying that you shouldn’t ever copy-paste code. I’m saying that, <strong>if you are copying code, it’s important to understand the code that you’re copying because you are implicitly making all the decisions that were made by the original author(s) of that code</strong>. And you are also making an explicit decision not to refactor the code so that you don’t have to copy it.</p><p>Basically, when someone asks you, “Why did you build it this way?” — try not to respond with, “Well, this other code was written that way.” This may mean that you won’t write a solution as elegant or reusable as a more experienced colleague but, if it meets the requirements of the task, that’s okay! Over time, each decision you consciously make, articulate, and learn from will help you make better decisions in the future.</p><h4><strong>Be aware when you’re experiencing imposter syndrome</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*3MRTxsvw5Bl5fHab6b4oWQ.gif" /></figure><p>Awareness is a big step in actively combating imposter syndrome. For me, self-doubt creeps in as I’m implementing a feature and it starts to take longer than it “should.” As this happens, I start to stress about how I’m being viewed by my co-workers and managers and this usually further delays the feature. It’s a vicious cycle and the only way to get out of it is to realize that I am stuck in this circle. I remind myself:</p><ol><li>The feature will take as long as it takes me.</li><li>I work hard and care about the quality of the code I produce.</li><li>I have asked for help when I’m stuck. If not, I can and should.</li><li>I have communicated my current status to the stakeholders of my feature.</li><li><strong>F**k everything else.</strong></li></ol><h4><strong>Read Chapter 1 of the </strong><a href="https://pragprog.com/book/tpp/the-pragmatic-programmer"><strong>Pragmatic Programmer</strong></a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*gj_dQ4-xGnbREofRSgjIcA.jpeg" /></figure><p>I recommend the whole book, but if you’re only going to read only one chapter, this first chapter articulates the philosophy of a pragmatic programmer. Some of the great advice include reading a technical book every quarter, participating in local meet-ups, and so much more. Don’t worry about your current skill-set or experience or how you’re perceived. <strong>If you’re practicing the lifestyle laid out in this chapter, then you’re doing it right</strong>.</p><h4>That’s it</h4><p>Now go forth and fight those battles against self-doubt, insecurity, and imposter syndrome. Remember, there’s a big difference in how you perceive yourself and what is reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*e4p0w6DEB5gQofwCwE4zxQ.png" /><figcaption>Perception versus Reality</figcaption></figure><h4>Other great posts on Imposter Syndrome</h4><ul><li><a href="http://startupbros.com/21-ways-overcome-impostor-syndrome/">http://startupbros.com/21-ways-overcome-impostor-syndrome/</a></li><li><a href="https://open.buffer.com/impostor-syndrome-8-tips-i-wish-i-had-known/">https://open.buffer.com/impostor-syndrome-8-tips-i-wish-i-had-known/</a></li><li><a href="https://42floors.com/blog/startups/imposter-syndrome">https://42floors.com/blog/startups/imposter-syndrome</a></li></ul><p>If you want to talk more about overcoming that feeling of being an imposter or how you can help others overcome that feeling, find me on <a href="https://twitter.com/abhiondemand">Twitter</a>!</p><p>Also, if you’re looking to learn or are currently learning how to code, check out what we’re building over at <a href="http://flatironschool.com/">Flatiron School</a></p><p><em>Click the ❤ below so other people will see this here on Medium.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*emxDrmtEiMy6h5JXecj-Og.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48edee803cf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-love-code/developers-how-to-overcome-imposter-syndrome-48edee803cf4">Developers: How to Overcome Imposter Syndrome</a> was originally published in <a href="https://medium.com/learn-love-code">Learn. Love. Code.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>