<?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 Mickey Dang on Medium]]></title>
        <description><![CDATA[Stories by Mickey Dang on Medium]]></description>
        <link>https://medium.com/@mickeymdang?source=rss-84e935c829bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*biCFNPtK2kMKtEVImZTlng.jpeg</url>
            <title>Stories by Mickey Dang on Medium</title>
            <link>https://medium.com/@mickeymdang?source=rss-84e935c829bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:41:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mickeymdang/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[Your Todo List is Bottomless]]></title>
            <link>https://medium.com/the-ascent/your-todo-list-is-bottomless-10cc8f3c0693?source=rss-84e935c829bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/10cc8f3c0693</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Mickey Dang]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 13:11:01 GMT</pubDate>
            <atom:updated>2020-01-07T13:11:01.126Z</atom:updated>
            <content:encoded><![CDATA[<h3>Face it, Your Todo List is Endless</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kQq6-DsiShVgqUE5M2nhcA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@esteejanssens?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Estée Janssens</a> on <a href="https://unsplash.com/s/photos/schedule?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPtTProfIhjnOy0IRdlw0g.jpeg" /><figcaption>A photo from my morning breakfast ~Oct 2017</figcaption></figure><h4>When I was in first year,</h4><p>I remember waking up in my dorm almost every morning, well before the start of class (usually at 8:30). I would go down to the cafeteria, pour some coffee, and head back up to eat breakfast, looking out from the student lounge on the tenth floor of my residence. People would trickle by on their way to campus which made for a quiet half an hour, apart from the occasional hello. As the autumn went on, I would be able to catch the sunrise as it covered the campus buildings in a warm fuzzy glow.</p><p>Of course, time is a scarce resource when you’re studying engineering. The elevators moved agonizingly slow and they would stop at multiple levels. It would take at least 10 minutes to make the full trip. I could have eaten my breakfast in class or on the walk to school. Shouldn’t I have used that half an hour to get some well needed sleep? Why not spend the extra time catching up on emails, reviewing some notes, or going to the gym? Surely, there are better times in life to sit down, and do nothing but distract yourself with the same old view. For someone who takes pride in good time management, this morning routine seemed inexplicably non optimal.</p><p><strong>But first, a thought.</strong></p><p>Inevitably, there’s a time of year (school, work, or otherwise) that feels as hectic as this:</p><blockquote>There’s a block of lectures in the morning, a three hour lab in the afternoon, a club meeting in the evening, and a group project to finish at night. Your planner reminds you to follow up with that recruiter you emailed a few days ago. Maybe you can multi-task at lunch to handle that a bit quicker. Your fitness app reminds you to keep up with your weekly step goal. There’s a convenient gap in the evening, so maybe you can squeeze in a run. You notice on your GCal that classes start later the next day. Maybe you can study for the upcoming midterm after that project at night. Perfect!</blockquote><p>It feels satisfying when you figure out how to fit those tasks into your schedule, and squeeze more time out of your day. We inevitably deal with it as we assume more responsibility and independence.</p><p><strong>Here’s the thing,</strong></p><blockquote>Why does it feel like those extra tasks we’ve finished never give us more free time?</blockquote><blockquote>If we’re becoming more efficient, why does it feel like we can never get ahead of those extra errands?</blockquote><p>We put our heads down to get through this week, only for the next week to magically fill up again. We don’t catch a break, because we don’t give ourselves one when we’re presented with free time. There’s always another hurdle to jump over, another checkpoint we can put our efforts towards.</p><p>And how do we try to fix this never-ending problem? By throwing more efficiency and more technology at the problem. It’s counter-intuitive; we think that working smarter and faster will give us an edge, but we don’t realize that our goal posts simply move farther away the instant they seem attainable.</p><p>Of course, there’s a positive word for that called <em>growth</em>. It’s why the ambitious side of our nature likes to be a small fish in a big pond. And it’s often a phenomenally rewarding feeling! There’s no doubt, all that planning and optimization comes in handy when you’re faced with a challenging week. But when everything gets planned to squeeze one more task out of the day, is there such thing as <em>too much</em> efficiency?</p><blockquote>What happens when this hunger for faster growth and more productivity becomes a perpetual state of mind?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2jmbYRYsAY7XWW1FWJ7V8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@martinirc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">José Martín Ramírez C</a> on <a href="https://unsplash.com/s/photos/busy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>“Millennial burnout” is a recent <a href="https://www.nbcnews.com/think/opinion/millennial-burnout-real-it-touches-serious-nerve-critics-here-s-ncna974506">term</a> to specifically describe the constant anxiety and inability to relax among students and young professionals. I don’t know enough to support or refute the <a href="https://www.bbc.co.uk/bbcthree/article/c384d54a-0116-437f-83e8-ddbca65b6c06">many</a> <a href="https://www.buzzfeednews.com/article/annehelenpetersen/millennials-burnout-generation-debt-work">many</a> articles and <a href="https://www.goodreads.com/book/show/34523218-kids-these-days">books</a> that attribute it to a litany of factors. Regardless of the cause, when I look around at my peers in the competitive university I attend — when people skip lectures not because they are delinquent, but because they’d rather learn the content “faster” on their own, and prepare for an upcoming job interview in the meantime — when people build their portfolios, resumes, and online presence in an ever escalating arms race with each other to get that “fulfilling career” immediately after graduation — when this culture proliferates beyond university, and kids seek competitive internships before they even enter their first year. I can’t help but wonder whether this positive feedback loop of insatiable hunger will lead anywhere but to an eventual burnout if left unchecked.</p><p>I don’t claim to have a perfect answer for myself, let alone anyone else. And it’s also true that broad trends don’t reflect individual idiosyncrasies. It’s possible you can’t relate to the tragically brief feeling of mental relief after getting through a hard week, only for it to disappear once you realize next week isn’t looking much better. If so, congratulations, you’re doing really well! But assuming you’re with the rest of us, I do think there are some ways to view this problem that can better help you reach your own sense of balance.</p><p><strong>How about I just take a break when I’m done?</strong></p><p>Vacations help, but even if you’re fantastic at compartmentalizing your thoughts while away from work, breaks just loosen a pressure valve on your problems until you return. Very soon, the pressure builds right back up.</p><blockquote>Eventually, that default state needs to shift into something more sustainable.</blockquote><p>Fighting burnout is a mentality shift. It’s being willing to take some of that free time you created, and deliberately “do nothing” with it, despite the storm of work that may be swirling around you.</p><p>Not just doing it after you “get through this week”, but doing it as consistently as possible, even when it feels like you’re in the thick of it. It’s internalizing that the list is truly infinite. And although those tasks won’t solve themselves just by sitting around, they also won’t end the world if they were handled just a little bit slower. You’ll work them out eventually whether you saved that half an hour or not, and you might just save yourself from chronic burnout in the process.</p><p><strong>So what was I doing in the morning?</strong></p><p>Those quiet half an hour mornings gave me some time to clear my mind and mentally prepare for the day ahead. It wasn’t “doing nothing” per say. I would notice the steady stream of cars passing by on the street below, and admire the way different buildings on campus looked based on when they were built. More important was what I didn’t think about. I wasn’t thinking about my plans for the day or worrying about an upcoming deliverable. These mornings were my flashes of zen, spread throughout the week to just reflect on the moment, and temporarily detach myself from day to day worries. It was a deliberately non-optimal habit to remind myself that in the broader perspective, not everything has to be done as soon as humanly possible.</p><p><strong>Of course, an obligatory disclaimer,</strong></p><p>Finding what habits work for you is a constantly evolving process in and of itself. I find that the best way to discover them starts with thinking about what simple hobbies can take your mind off of work.</p><p>Success isn’t to maintain a perfect state of calm and balance forever. Pragmatically, there will be moments in a career when you need to throw all your effort into your work. The trick is to have the awareness to recognize when that critical moment is over, and to have reliable strategies which can flip that mental off-switch.</p><p>Now a days, I know that reading a book for a couple of hours helps me slow down the pace of a busy week. But of course, that doesn’t help when I can’t find a good book to read. I know that walks or runs offer some time away from endless notifications and distractions. But that only works when it’s warm outside. There’s no silver bullet that works forever and in all cases if only it could be discovered. This will always remain a work in progress.</p><p>Maybe one day, we’ll all reach that point of satisfaction where we can retire on the proverbial beach, away from all the noise; honestly, it could be quite literal as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lqfrmnaHnnVmB4sFGLOZMA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lukemichael?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Luke Michael</a> on <a href="https://unsplash.com/s/photos/busy-day?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>But after all, our end destinations are fickle. We love to change them as they get closer within our reach. So perhaps it’s better to just try and enjoy the journey in the meantime 🙂 .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10cc8f3c0693" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-ascent/your-todo-list-is-bottomless-10cc8f3c0693">Your Todo List is Bottomless</a> was originally published in <a href="https://medium.com/the-ascent">Ascent Publication</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does it Mean to be a Good Developer?]]></title>
            <link>https://medium.com/@mickeymdang/what-does-it-mean-to-be-a-good-developer-cc435dad6052?source=rss-84e935c829bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc435dad6052</guid>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-internship]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mickey Dang]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 23:37:50 GMT</pubDate>
            <atom:updated>2019-11-07T05:35:46.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcjI9ASxo9cvQ6HgEOtZYA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marvelous?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marvin Meyer</a> on <a href="https://unsplash.com/s/photos/development?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve had the good fortune to work in a bunch of different software positions over the past 2 years. And along the way, I met a bunch of amazing people who have taught me basically everything I know.</p><p>Some of them had an incredible ability to describe their architecture in excruciating detail. Some of them were curve busters that could fix the most obscure bug I stumbled across. But also, they would all take the time to walk me through the code, component by component, glossing over the irrelevant parts, and focusing on details that mattered. They would patiently pair with me on bugs that I spent all morning banging my head against. And I’m sure they were suppressing their laughter when they politely answered all of my trivial questions (<a href="https://stackoverflow.com/questions/11828270/how-do-i-exit-the-vim-editor?__hstc=188987252.eb3a5e33f4ba71d97c1208d786f2828d.1571107618556.1571107618556.1571107618556.1&amp;__hssc=188987252.1.1571107618557&amp;__hsfp=4198582531">here’s how to exit vim</a> if you were wondering btw).</p><p>As someone who had very little programming experience going into university, I never really thought about software engineering apart from the usual stereotypes. So perhaps it’s not surprising that back when I first started out, if you asked me what skills I thought were needed to do well, I would only be half right at best. Here’s what I’ve learned since then.</p><h4>But first, a question.</h4><blockquote>When someone asks you what are the common attributes of a software developer, what comes into your mind?</blockquote><ul><li>Logical?</li><li>Analytical?</li><li>Structured?</li><li>A quick thinker?</li></ul><p>Sure, all that. They’re useful skills in solving complex problems and implementing elegant solutions.</p><blockquote>Here’s the thing, does this also mean that being a <strong>better</strong> developer requires being <strong>more</strong> logical, <strong>more</strong> analytical, and <strong>more</strong> structured?</blockquote><p>The answer seems intuitive. You need to write structured code for a computer to compile. But if the only objective was to write code that a computer can understand, what’s stopping us from writing it like this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PIrXG7XzvHAg1B8Ti2qi1w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/s/photos/programming?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The answer is simple, we’re also writing code for the next person to understand and maintain. That’s why we organize code into classes. That’s why we name our variables and functions descriptively. That’s why we establish software patterns to build a shared mental model of thought. Of course, the compiler couldn’t care less.</p><p>So, how do we decide what patterns to enforce, what variations we’ll make to fit our needs, and how we’ll organize and communicate it so that our code stays maintainable and avoids becoming spaghetti?</p><p>Well, we need to consider how other developers use our system. We need to imagine how they’ll approach our codebase when they need to make changes. We need to leverage our own experiences and understand the common mistakes that people make when facing code they’ve never touched before. We need to think about what kind of cues can be used to ensure that people keep our code clean moving forward.</p><p>From a different perspective, when you get a code review, what percentage of that review is focused on making your code correct? What percentage of that review is focused on making your code more readable, maintainable, and adherent to everything around it? If you’re not in the habit of pushing code that literally doesn’t work (I would hope not), it’s almost always the latter.</p><blockquote>So what skills do developers use when they’re trying to decide?</blockquote><p>A little bit of logic, structure, and technical background sure, but not a particularly abundant amount if you’re willing to dedicate some time to read up and hone your skills. What’s most important is thinking about your fellow developers who are working alongside you — in other words, it’s about having <strong>empathy</strong>.</p><h4>Empathy? Sounds like design.</h4><p>Yes and no. It’s great if developers have that same level of empathy for their users and can relate the impact of their work to building a better end experience. It’s also (understandably) not something that is front of mind when you’re automating testing pipelines or defining new schemas.</p><p>It <strong>is</strong> <strong>important</strong> however, that developers are thinking about their fellow contributors, and it’s something that good developers practise on a day to day basis. It comes up when your coworker walks you through a tricky part of the codebase, and explains exactly what you’re looking for because they too have been confused by the same little hack. It comes up when you’re deciding whether to add a comment to that slightly ambiguous line, or maybe just drop a little note in the pull request. Being empathetic helps developers communicate their code to the rest of the team, and since software is such a team sport, building and fostering that collective understanding makes all the difference.</p><h4>So why does it matter if we’re (sort of) doing it already?</h4><p>I can’t count the number of times I’ve heard phrases like</p><blockquote>“I don’t think I’m qualified [for this position] because I’m not very technical”</blockquote><blockquote>“It’s exciting, but I’m just nervous because I’m not very logical or smart”</blockquote><blockquote>“It’s hard because I’m not a very good coder”</blockquote><p>It’s great for people who are already in software to implicitly understand that empathy and communication are as vitally important as good problem solving skills. It’s not great when people are discouraged from exploring a potentially rewarding opportunity, simply because they equate being a good developer to solving a LeetCode hard in a breeze.</p><p>Again, it does take an <em>average</em> level of logical thinking (a level that most STEM majors ought to have by simply studying in their field). It does take a persistence to learn and a determination to overcome challenges. But what we tend to miss in our conventional way of thinking is that beyond a certain level, you don’t need to have exceptional reasoning and analytical thinking to excel in most roles; there are other less visibly portrayed skills that are just as important. You won’t win any <a href="https://ioinformatics.org/?r=301">IOI medals</a>, but fortunately, that’s not what it means to be a good developer.</p><p>Good luck to everyone who is hard on the internship grind this season and trying to find their interests 💯.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc435dad6052" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>