<?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 Lee Song on Medium]]></title>
        <description><![CDATA[Stories by Lee Song on Medium]]></description>
        <link>https://medium.com/@leesong?source=rss-32a36883a912------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fjuZSz8KrEh4ljnb.</url>
            <title>Stories by Lee Song on Medium</title>
            <link>https://medium.com/@leesong?source=rss-32a36883a912------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:52:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leesong/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[Are good grades useless? A short and simple analogy.]]></title>
            <link>https://medium.com/@leesong/are-good-grades-useless-a-short-and-simple-analogy-b3aa73e8d458?source=rss-32a36883a912------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3aa73e8d458</guid>
            <category><![CDATA[university]]></category>
            <category><![CDATA[grades]]></category>
            <category><![CDATA[high-school]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[good-grades]]></category>
            <dc:creator><![CDATA[Lee Song]]></dc:creator>
            <pubDate>Thu, 25 Jul 2019 02:19:07 GMT</pubDate>
            <atom:updated>2019-07-25T02:24:02.393Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve seen many good grades students graduated, confused when they cannot find any jobs, or got lower pay than average. I want to use a simple analogy to describe a situation.</p><p>Assuming you are attending a lecturer class, which kind of lecturer do you want?</p><ol><li>Not so knowledgeable but delivers the knowledge very well.</li><li>Very knowledgeable but you cannot understand at all.</li><li>Not knowledgeable and you cannot understand at all.</li></ol><p>I would assume their capabilities as follows,</p><ol><li>CGPA 3.6, delivers knowledge well.</li><li>CGPA 4.0, cannot deliver knowledge.</li><li>Did not attend university, cannot deliver knowledge.</li></ol><p>Thus, it is normal for (1) to have higher salary than (2). Grades are not everything, but you cannot say it is useless, that will become (3).</p><p>Of course, a lecturer that had CGPA 4.0 and delivers knowledge well would be very powerful, but I believe you would not read this topic if you already understand the strength here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3aa73e8d458" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is programming just about coding: 10 analogy with MMORPG]]></title>
            <link>https://medium.com/@leesong/is-programming-just-about-coding-10-analogy-with-mmorpg-603e41eff3e8?source=rss-32a36883a912------2</link>
            <guid isPermaLink="false">https://medium.com/p/603e41eff3e8</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-engineer]]></category>
            <dc:creator><![CDATA[Lee Song]]></dc:creator>
            <pubDate>Sat, 08 Jun 2019 15:47:33 GMT</pubDate>
            <atom:updated>2019-06-08T16:38:34.095Z</atom:updated>
            <content:encoded><![CDATA[<p>This article brings a MMORPG as analogy to helps you to understand better to the previous topic, <a href="https://medium.com/@leesong/is-programming-just-about-coding-5945e161cb95">Is programming just about coding?</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*190yf2U4vCvUj0n8eMpqMg.png" /><figcaption>Image taken from MapleWiki</figcaption></figure><p>The diagram below is captured from the previous topic. The career basically works like how you evolve in a MMORPG game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*TQn4n4ePxeDchtmnJ8X7_g.png" /><figcaption>The hierarchical chart for a software engineer</figcaption></figure><ol><li>You starts from a coder, then you earn experience and get into higher job advancement.</li><li>You earn passive skills from school and active skills during your work. If your passive skill is strong, you can advance quicker. Else, they will be the barrier stops you from advancing to higher job advancement.</li><li>You may consider Coder is Lv. 10, Programmer is Lv. 30, Software engineer is Lv.70, Architect is Lv. 120 and so on.</li><li>Ten coder (Lv. 10) will not able to defeat a boss (challenging problem), but one architect (Lv. 100) will. Similarly, a legendary (Lv. 200) can defeat world boss (state-of-art problem), while it might take a team of architects (Lv. 150) to defeat it.</li><li>If you played with buying boss services in game before, single strong player is usually cheaper than a team of professionals. In real life, it is because you are feeding one family, one living costs versus a team of them.</li><li>If you believe it is just about coding, you stuck on first job advancement (coder) for entire career.</li><li>If you got a degree and believe it is just about coding, you forgot all passive skills you earn from school and stuck in first job advancement career.</li><li>If you claim to be a software engineer without academic knowledge, it will be like a magician without passive skills. Your mana drains quickly and fail to cast spells with high mastery. Most importantly, your entire party will die in a boss fight.</li><li>If you want to become software engineer just to earn money, without passion, I would say it is very hard for you to obtain experience and level up. You may get bored at Lv. 13 and quit the game.</li><li>If you decide not to go software engineering, interesting enough, you can start with coder then job advance into other path such as security expert or mathematician. One code file that works is good enough for their domain. It works similarly like how you start with magician then advance into mages or clerics.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=603e41eff3e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is programming just about coding?]]></title>
            <link>https://medium.com/@leesong/is-programming-just-about-coding-5945e161cb95?source=rss-32a36883a912------2</link>
            <guid isPermaLink="false">https://medium.com/p/5945e161cb95</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Lee Song]]></dc:creator>
            <pubDate>Sat, 08 Jun 2019 15:35:45 GMT</pubDate>
            <atom:updated>2019-06-08T16:36:19.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKRHC9_s9CKR6kxP0p_vhg.jpeg" /><figcaption>Photo credits to IIya Pavlov from unsplash.com</figcaption></figure><p>I been playing around with programming since twelve years old. Like most people asking question on online platforms, we got no clue what is happening next, such as</p><ol><li>Is programming just about coding?</li><li>Do we need a degree?</li><li>Is coding bootcamp sufficient?</li></ol><p>Recently, I found my path clear and I would like to share with the new comers. I would like to introduce the following diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*TQn4n4ePxeDchtmnJ8X7_g.png" /><figcaption>The hierarchical chart for a software engineer</figcaption></figure><p>The bottom part of the diagram describes the academic knowledge required for the titles above. I will explain one by one from coder to legendaries in the sections below.</p><p>Before I start, I would like to mention in software engineering, <em>passion</em> is a very important factor for you to grow. If you just looking for working opportunity, it is very recommended for you to consider the alternative route.</p><h3>Coder</h3><p>Someone types on the keyboard all day.</p><ol><li>A coder only care about gluing syntax to make it compile as work as expected. It may lead the software become hard to maintain and abandoned.</li><li>A coder got no clues on whats happening behind the scene. When a coder sees an error, the coder stackoverflow and copy paste the answers. It may lead to serious bugs and loss in money.</li><li>It’s about working on the code on a very surface area. One code file for whole project is totally fine.</li><li>If you know games for kids like Scratch or Minecraft Coding, yes, they fall into coder category. If you look at the diagram, it actually requires high school knowledge, so its awesome for kids to play around with them.</li></ol><p>I consider peoples who joined bootcamp falls into this category. As you can see, the knowledge is very surface. Interestingly, most undergrad students stuck at this level. They consider what they learnt is useless and gluing the syntax all day.</p><p>Recommended actions: Get into a university. Apply knowledge if you already did.</p><h3>Programmer</h3><p>A programmer is not just writing codes anymore. A programmer is able to compose a program together.</p><ol><li>Have understanding of how basic OO works. It is a very fundamental concept, describing real life object, and the <em>modularization</em> to compose smaller parts into bigger ones.</li><li>A programmer should start to obey practices such as using clearer variable names to explain logic.</li><li>Able to think critically, write queries and data processing.</li><li>A programmer should try to understand the code from stackoverflow instead of blindly copy and paste.</li></ol><p>Based on the diagram, a diploma is what you will learn to become a programmer. However, there are much interesting things ahead.</p><p>Recommended action: Earn a degree or get in touch with design patterns, clean code and refactoring.</p><h3>Software engineer</h3><p>An engineer truly emphasizes on <em>principles</em>.</p><ol><li>An engineer should have the knowledge such as SOLID principles and design patterns. They may not used them practically, but they should know them.</li><li>Should be able to execute statements like if-then-else in the brain quickly.</li><li>Working in a team with principles such as refactoring into understandable format. Do not write /* This is magic. Do not touch */</li><li>Have most knowledge in degree such as operating systems, computer architecture, networking and security.</li><li>Improve themselves and not restricted to simple CRUD software. Get in touch with different programming languages and databases.</li></ol><p>I personally believes the fun part comes in as software engineer. We learn the practices from geniuses around the world, then build something with it.</p><p>Recommended actions: Get in touch with TDD (Test-driven design), DDD (Domain-driven design), design patterns and automation.</p><h3>Architect</h3><p>An architect is able to take decisions based on their experience as software engineer.</p><ol><li>Apply design patterns, principles and <em>consider their consequences</em>. One should not refactor two constructor parameter into builder pattern because it is loosely coupled. <em>They introduce complexity.</em></li><li>Similarly, one should not trying hard, spending five hours to extract method from two functions, because of DRY principles. An architect should be clear on the consequences.</li><li>An architect should treat languages and platforms as tools, consider their consequences and not overly biased towards one of them.</li><li>An architect should able to select software architecture wisely. Not to blindly follow the hype when the expertise is not there. <em>Some introduces complexity, </em>and able bring whole project to death when the skill set is not there.</li><li>An architect tries out new things and gains experience throughout the career.</li></ol><p>As shown in the diagram, you can see an architect starts to touch the postgraduate knowledge. There are cases where an architect collaborate with research scholar to produce papers, then publish them to journals. They contribute cutting-edge knowledge to the humanity.</p><h3>The Legendaries</h3><p>The legendaries refers to peoples like Uncle Bob or GoF (Gang of four). They had many years of experience. Some of them do not have PhD, but a lot of PhDs cites their work. Their insights are very well respected and most importantly, works in the industry.</p><h3>Conclusion</h3><p>I started as a coder back in twelve years old, a programmer on 15, then I lost help from the seniors on how to evolve myself. A degree is what brings me to look into design patterns, principles and methodologies, of course with awesome lecturers with rich industrial experience. A lot of architect from the industry guided me so I consider myself evolved a lot in the recent years.</p><p><em>This article clearly states that programming is not just about coding</em>. If you are still unclear, I got <a href="https://medium.com/@leesong/is-programming-just-about-coding-10-analogy-with-mmorpg-603e41eff3e8">10 analogy based on MMORPG games</a> to help you to understand clearer, if you just graduate from high school ;).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5945e161cb95" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>