<?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 Listiarso Wastuargo on Medium]]></title>
        <description><![CDATA[Stories by Listiarso Wastuargo on Medium]]></description>
        <link>https://medium.com/@lwastuargo?source=rss-ca1629ce933a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9PnT5ObRv9yKb_k9soFnOQ.jpeg</url>
            <title>Stories by Listiarso Wastuargo on Medium</title>
            <link>https://medium.com/@lwastuargo?source=rss-ca1629ce933a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:19:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lwastuargo/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[How to Market Yourself]]></title>
            <link>https://levelup.gitconnected.com/how-to-market-yourself-e4eef2c860ad?source=rss-ca1629ce933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4eef2c860ad</guid>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[tech-interview]]></category>
            <dc:creator><![CDATA[Listiarso Wastuargo]]></dc:creator>
            <pubDate>Thu, 11 May 2023 04:25:25 GMT</pubDate>
            <atom:updated>2023-05-11T04:25:25.790Z</atom:updated>
            <content:encoded><![CDATA[<p>In the fierce battleground of today’s job market, many competent individuals are left stranded, unable to secure work due to the overwhelming number of applicants. So, how do you outshine your rivals? The key lies in effective self-promotion.</p><p>Drawing from my personal experience that bagged me <strong>multiple offers over</strong> <strong>$800k</strong>, this guide will walk you through optimizing your resume, LinkedIn, and online presence to win more interviews and ultimately secure that dream job.</p><h3>📝 Sculpt Your Resume</h3><p>The first impression is the last, and your resume is your first impression. Use LinkedIn’s features to craft a comprehensive resume that complements your traditional one. Emphasize displaying your skills, experience, and cultural compatibility, which are top priorities for recruiters. Highlight your most notable achievements, relevant skills, work experience, and academic qualifications. Prune out outdated or irrelevant data and avoid lengthy paragraphs or text blocks. Keep your resume concise and restricted to a maximum of two pages. For additional pointers, check out <a href="https://stackoverflow.blog/2020/11/25/how-to-write-an-effective-developer-resume-advice-from-a-hiring-manager/">this article</a> on how to write an impressive developer resume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_zzx_aNVZgG7Z2HZ.png" /></figure><h3>🔗 Build Your LinkedIn</h3><p>LinkedIn is your professional digital identity, a platform that makes you visible and accessible to potential employers and recruiters. Even though I believe that job titles are overrated, recruiters still use them as a preliminary filter to evaluate your suitability for the job.</p><p>Make it a point to underscore the skills you’ve applied in your experience. Not only does it enhance your profile visually, but it also enables hiring managers to spot your profile when they’re in search of a candidate with specific skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZCA7c02oM4CBkUf3.png" /></figure><h3>🔍 Operating LinkedIn</h3><p>LinkedIn’s search feature can be your ally in discovering job opportunities and connecting with professionals in your field. Pro tips: following companies can increase your profile’s visibility and inform you about job vacancies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CTbXxwywQfao8QrK.png" /></figure><p>Set your profile to indicate that you’re open to new opportunities without tipping off your current employer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gBwbvsaDPHRnYwFr.png" /></figure><p>Personalize your messages to your connections, expressing your interest in particular roles or companies. Regularly posting relevant content helps exhibit your expertise and engage with your network.</p><h3>📧 Approach the Head of Engineering</h3><p>Skip recruiters and directly contact the head of engineering, engineering directors or VPs, who are more likely to engage with you. Engineering managers might lack the authority to make hiring decisions; hence it’s wiser to target higher-level decision-makers. Check out <a href="https://www.linkedin.com/posts/eugenesegalheadofproduct_how-i-landed-10-big-tech-interviews-without-ugcPost-7052257422932881408-YkH7/?utm_source=share&amp;utm_medium=member_desktop">this thread</a> for more insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/0*Q4rVpQ1BJUKDHcpY.png" /></figure><p>Leverage online tools and resources to locate the email addresses of the head of engineering. Use ChatGPT-4 to draft personalized and engaging emails.</p><h3>🕵️ Work with Headhunters</h3><p>With their vast networks and expertise, headhunters can help you secure interviews at premium companies. Always respond to headhunters professionally and politely. Collaborating with headhunters costs you nothing but time, as the hiring company pays their fees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/0*t3oeIzHDR9ZT8whx.png" /></figure><h3>📥 Manage Recruiter Reachouts</h3><p>Treat each interaction with a recruiter professionally and respectfully, as they can be your gateway to new opportunities. Create a separate folder in your inbox to keep track of recruiter emails, ensuring easy access for future reference. Stay connected with recruiters, even if they’ve moved to a different company, as they might still provide valuable leads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jzO8g56xPfAEbNOf.png" /></figure><h3>🌐 Job Portal Applications</h3><p>Make use of diverse job portals to boost your job search efforts. Some well-known platforms include <a href="http://remoteok.com/">remoteok.com</a>, <a href="http://angel.co/">angel.co</a>, <a href="http://workatastartup.com/">workatastartup.com</a>, <a href="http://weworkremotely.com/">weworkremotely.com</a>, and <a href="http://jobboardsearch.com/">jobboardsearch.com</a>.</p><h3>🌟 Build Your Online Presence</h3><p>Maintain an active online presence to build credibility and authority in your field. Keep your <a href="https://www.linkedin.com/in/lwastuargo/">LinkedIn profile</a> current and actively interact with your network. Share industry updates and insights, and engage with professionals on <a href="https://twitter.com/lwastuargo">Twitter</a>. Publish articles on Medium to showcase your expertise and experiences. Start a Substack newsletter to share your thoughts and insights with subscribers. You can also start a <a href="https://www.youtube.com/@lwastuargo">YouTube channel</a> to share tutorials or industry insights. And remember, a little bit of light-hearted content or “shitposting” is okay too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zoLHT9VtIsh4NYPr.png" /></figure><h3>💻 Contribute to Open Source Software (OSS)</h3><p>Although contributing to OSS can be demanding in terms of time, the benefits are undeniable. Make substantial contributions that enhance the project and exhibit your skills. Despite the commitment involved, OSS contributors often find themselves with a higher success rate in securing job interviews.</p><h3>🎲 It’s All a Numbers Game</h3><p>At the end of the day, be prepared for a fair share of rejections. Always bear in mind that it’s a numbers game. Rejections are not a reflection of your worth; they simply suggest that the role wasn’t the perfect fit for you. Devote time and effort to refining your resume, expanding your network, and differentiating yourself from other candidates. Your funnel of interview might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yAKKsmGscTxBPSwP.png" /></figure><p>How do you market yourself?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4eef2c860ad" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/how-to-market-yourself-e4eef2c860ad">How to Market Yourself</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Be a 10% Engineer: Be a 10x Engineer First]]></title>
            <link>https://levelup.gitconnected.com/how-to-be-a-10-engineer-be-a-10x-engineer-first-f670a9bca968?source=rss-ca1629ce933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f670a9bca968</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[10x-engineer]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Listiarso Wastuargo]]></dc:creator>
            <pubDate>Tue, 01 Nov 2022 03:04:03 GMT</pubDate>
            <atom:updated>2022-11-01T03:04:03.602Z</atom:updated>
            <content:encoded><![CDATA[<p>We probably will never know who first coined the term 10x engineers. But we sure know there are many definitions and memes around them. For example, one of the most popular discussions about 10x engineers was started by Shekhar Kirani back in July 2019.</p><h3>Shekhar Kirani on Twitter: &quot;10x engineersFounders if you ever come across this rare breed of engineers, grab them. If you have a 10x engineer as part of your first few engineers, you increase the odds of your startup success significantly.OK, here is a tough question.How do you spot a 10x engineer? / Twitter&quot;</h3><p>10x engineersFounders if you ever come across this rare breed of engineers, grab them. If you have a 10x engineer as part of your first few engineers, you increase the odds of your startup success significantly.OK, here is a tough question.How do you spot a 10x engineer?</p><p>You’d see few points which I <strong>agree</strong> with…</p><ol><li>10x engineers can convert “thought” into “code” in their minds and write it in an iterative fashion.</li></ol><p>…and I <strong>disagree</strong> with…</p><ol><li>10x engineers hate meetings.</li><li>10x engineers know every line of the code that has gone into production.</li><li>Most of the 10x engineers are full-stack engineers.</li><li>10x engineers rarely look at help documentation of classes or methods.</li><li>10x engineers are poor mentors as they can’t teach others what to do OR parcel the work.</li><li>10x engineers don’t hack things.</li></ol><p>…which signifies how many permutations of 10x engineer qualities, activities, and characteristics according to different professionals in the industry. This blog is focused on 10% engineers, so I am only going to discuss the 10x engineer definition that’s related to being a 10% engineer (and the best kind of 10x engineer you should consider to be a 10% engineer).</p><p>Rather than explaining what constitutes a 10x engineer, let me give an example of what a team <strong>without</strong> a 10x engineer looks like, and what happens <strong>with</strong> one.</p><h3>A Team Without 10x Engineer</h3><p>A team of 3 engineers (2 frontends and 1 backend engineer), 1 product manager, and 1 designer working on a car rental marketplace. The business premise is for an individual to be able to list their car(s) for rent while other people can search, browse, discover, rent, and pay for the car.</p><p>The PM started the requirement by asking the engineering team to build a listing website with their map and live location of the cars in 2 months. The engineers said making their map is unreasonable and pushed back the requirement, and asked for 6 months. The PM begrudgingly agreed to use Google Map instead but pushed back that everything needs to be done in 4 months. The team then invested all the 3 engineers in building this.</p><p>Two months in, and it seemed like the engineers thought we’d not get this done in time. The PM asked for more resources from leadership without asking the engineers. The original team somehow got another 1 backend and 1 frontend engineer to help but also wondered who will have the time to get these 2 new engineers on board. But at least now they had more people to drink with during happy hour.</p><p>Four months in, the project was “almost ready,” according to the most outspoken engineer. After user acceptance testing, seems like the map integration was flaky, the UI had some flickering issues, and the backend team insisted they want to add 100% test coverage to their code. The team agreed to add additional 2 months to get this project up and running.</p><p>Seven months in, after a minor delay here and there, the project is finally ready to launch. The marketing team was ready to start sending promotions, and the management team was super excited about the launch. “July 4th, that’s the best timing,” everyone agreed.</p><p>July 4th. The website is public. Marketing was massive. The website was down for a while due to traffic. The team doesn’t know how many people come to the website, but it was massive. The backend engineer increased their EC2 instance from small to large to help with the load. The team ended up with 100 signups and 0 transactions closed.</p><p>July 7th. The website is not crashing anymore. But the PM kept wondering why there were still 0 transactions. The PM asked the team to debug. Apparently, their payment integration was not working well, which was never tested before because none of the engineers want to test against their credit card. The team quickly fix this with PM’s credit card and they receive 2 transactions (where 1 of them was a test transaction).</p><p>July 20th. Seems like now the website is working well. But there were only 10 transactions closed so far. It seemed like people are using the website, and the demand was there, but they can’t close the transaction. The hypothesis was the website was too complex to navigate (one of the frontend engineers mumbled, “the customer is just too dumb”). Sadly, the team didn’t know where the customer got stuck. One of the engineers suggested that we put some tracking and logging into the website. He proposed the use of <a href="https://firebase.google.com/">Firebase</a> and <a href="https://www.metabase.com/">Metabase</a> to log and store the events (he heard that it’s the industry standard and it’s highly scalable). Since the team needed to research these new tools, they would need another 2 months and scaled down the team to just 1 backend and 1 frontend engineer (from 5 engineers).</p><p>September 1st. Somehow the team implemented the logging faster than expected (great job, team!). Now the team understood that there was an issue with the checkout page due to the number of drops off based on the logging. It was a simple 3-liner fix. The team pushed the code and eagerly looked at the transaction number. Though right now, the marketing team ran out of budget for this project, so they didn’t have enough traffic to test the transaction. They had to wait for 1 month to see if their fix actually improved business metrics.</p><p>October 1st. The website started closing consistently 10 transactions/day. But the management team thought this product was not worth the investment due to the amount of time (10 months) and people (7 people) wasted on this. They want the company to focus on upcoming Thanksgiving and Christmas-related products. The PM begged the management team and promised that the team will include Thanksgiving-related work in the project. Finally, he’s given 2 months and 2 engineers to prove that this can grow to 30 transactions/day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Eec5TORdxFVgNX-.png" /><figcaption>Probably not how Turo was created</figcaption></figure><h3>A Team With 10x Engineer</h3><p>The 10x engineer got the same requirement as above. She wondered why the live location is important since the car would be parked in the same place for a long time, emphasizing that they were on different business than Uber/Lyft. She also got on the same page with the PM that they’re building a marketplace product — which means there’s a supply and demand problem that needed to be solved, possibly separately. The PM and the 10x engineer agreed that solving the demand side was a more important problem to solve than the supply side. They needed to design a website that was as frictionless as possible and tested the demand.</p><p>The PM then went to ask all the team members for whoever wanted to rent their car since they agreed that they didn’t want to solve the supply side of the marketplace yet and thus would need some inventory to break the chicken-and-egg problem (no car inventory means no customer. No customer means no one wants to rent their car). Meanwhile, the 10x engineer consulted with the legal team about whether they can use a 3rd party tool to build the website. Upon approval, she gathered a team of 1 engineer and started building the website using a no-code tool like <a href="https://bubble.io/">Bubble.io</a>. After designing the database, her team went on to spend 2 hours manually inserting the car-to-be-rented into the database</p><p>Ten days into the project, the website was done. The 10x engineered prep the website to be able to handle 1,000 traffic based on marketing team estimation by upgrading the subscription plan from $25/month to $100/month. She also integrated Google Analytics into the website even though she didn’t know what they would use the tracking for (she only had a hunch the team would need it based on her experience). While the management team was disappointed that the website only contains a listing of cars (and no way to systematically supply new cars through the website), they’re excited to launch this to the public.</p><p>On the first day of launch, everything was good. Marketing was successful, and it was apparent that the website had more demand than the currently available supply. They received 80 signups and closed 40 transactions on the first day and 20 transactions on the 2nd day, and 30 transactions on the 3rd day. The 10x engineer and the PM immediately planned for the next iteration: how to solve the supply side by allowing people to upload and list their cars for rent.</p><h3>Software Engineers are NOT Coders/Programmers</h3><p>Something critical for us to be on the same page before we discuss about 10x engineers: software engineers are not coders/programmers.</p><p>The closest analogy for software engineers vs programmers I can think of is comparing doctors vs nurses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*6bOjpCkPuIEwn93-.jpeg" /><figcaption>Photo by <a href="https://www.istockphoto.com/id/portfolio/NanoStockk?mediatype=photography">NanoStockk</a> on <a href="https://www.istockphoto.com/">iStock</a></figcaption></figure><p>Can doctors measure blood pressure? Sure they can!</p><p>Can doctors do an infusion? Sure they can!</p><p>Can doctors do daily follow up to make sure the patients are drinking their medicines on time? Sure they can!</p><p>But why do you rarely see doctors do anything mentioned above? Because of the following reasons:</p><ol><li>Some things <strong>can only be done by them</strong> and can’t be done by nurses. For example: attaching your thumb back together, LASIK operation.</li><li>There are <strong>more important</strong>/high-level things to do to ensure the patient is well. For example: figuring out which part of the brain artery needs to be unclogged, how to do it while preventing future side impacts, and figuring out the right medication.</li><li>There is quite a bit of thing that needs to be done, and the doctor has to <strong>delegate</strong> some of the work to someone else as efficiently as possible. Theoretically, a doctor can delegate the work to another doctor, but it won’t be an efficient use of both of their time.</li></ol><p>Similarly, not all software engineers need to code every day (or at all) to accomplish what’s expected of them and to deliver value to the company. You might’ve heard that some engineers on the principal level stop coding altogether and mainly contribute to software architecture and their tradeoffs.</p><p>Most software engineers started their career writing code. But sufficiently tenured engineers know that a successful project requires more than just code. To name a few, you’ll need monitoring, project management, cross-functional alignment, a design that works, project momentum, and prioritization. And later in their careers, software engineers are expected to deliver a good product, not just deliver a functional code that works according to the product manager’s specification.</p><p>Due to the non-trivial amount of things (and people involved) that need to happen for a (big) project to run smoothly, 10x engineers will fill a role within the project that fits their strengths and help drive the project to be successful as effectively and efficiently as possible. These roles vary across 10x engineers thus, it might be interesting to talk about the archetypes of 10x engineers.</p><h3>The Archetypes of 10x Engineer</h3><p>Describing a 10x engineer is tough because there are no one-fits-all activities they do day-to-day. And their qualities shine differently between individuals and teams they are in (or spotted in a team without them, as illustrated above). Here’re the archetypes of 10x engineers per my observation over the years:</p><p><strong>Generalist</strong> is a 10x engineer who breaks down complex and ambiguous problems into digestible ones by their coworkers. Then they usually will work either on the hardest or the riskiest one (but not always the most impactful one). They are well-versed in multiple technologies, thus allowing them to apply themselves in the right place as needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_SARUYjNFlLRX1Cn.png" /><figcaption>Generalist</figcaption></figure><p><strong>Specialist</strong> is a 10x engineer who specializes in one platform or one technology that created an outsized impact. They are usually a renowned player in the industry, be they a creator/big contributors to widely used open-source projects (e.g. React Native) or creators of a platform (e.g. Android, Git). People join a company to be able to work with them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vxWMi-SKlQ2Di0x_.png" /><figcaption>Specialist</figcaption></figure><p><strong>Fixer</strong> is a 10x engineer with the special power to spot a problem (not necessarily complex) and make a sizable impact. They usually know (or know how to quickly know) a domain (source code, business vertical, platform) really well, thus knowing how things should work and what’s the delta between the current situation vs its most optimal version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O4pN0z0uod__krO4.png" /><figcaption>Fixer</figcaption></figure><p><strong>PM Hybrid</strong> is a 10x engineer who has great product sense and worked very closely with the product leader/PM to build a product strategy together. A PM Hybrid can often play a temporary product manager role in their absence. Their skillset is also wider (but more shallow) than Generalist, being savvier on data analysis and designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0JA6gniKUqKtXv1B.png" /><figcaption>PM Hybrid</figcaption></figure><p><strong>Coding Machine</strong> is a self-explanatory archetype. They output more code than any other engineers. A typical engineer would output 100 to 200 pull requests every 6 months (or an average of 1–2 PR/day). This person will output 1500–3000 pull requests every 6 months (or an average of 10–20 PR/day). Sadly, recurrently I’ve seen that they’re not the best teacher so the skill doesn’t seem to be replicable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u6xE6-iZZgS4hLvN.png" /><figcaption>Coding Machine</figcaption></figure><h3>The Logistics to Become 10x Engineer</h3><p>Then how to actually become a 10x engineer? Sure there are “keep coding”, “keep hustling”, and “go beyond your comfort zone” tips that I can give you. But let me give you some practical ones:</p><p><strong>Choose a company</strong>. Do NOT jump between too many jobs if you really want to become a 10x engineer. The goal is to learn and then to earn (ideally both at the same time). Unless the company doesn’t have a good path to <strong>learn</strong> (performance review, mentorship, challenging projects, exposure) nor <strong>earn</strong> (promotion, credibility, bonuses), STAY.</p><p><strong>Become a senior engineer</strong>. This is usually pretty straightforward. Most decent companies will have a path to becoming senior engineers (if they don’t, see points above). If you’re the founder of the company, then this is automatically achieved. The importance of becoming a senior engineer is not only about accumulating the skill, but also about social capital within the company, and reputation and opening you up to more staff-level project opportunities (yes, title matters here).</p><p><strong>Spot and execute staff-level projects</strong>. According to <a href="https://staffeng.com/guides/staff-projects">staffeng.com</a>, not all staff engineers need to execute staff-level projects. But to become a 10x engineer, you need to execute staff-level projects. There’s really no good way to spot a staff-level project (and a lot of time, you might need to spot the potential, not just how the project is right now). But usually, it has the 3 ingredients: complex and ambiguous, multiple divided stakeholders, and critical to company strategy/metrics.</p><p><strong>Pick an archetype</strong>. It’s tempting to try every archetype. But usually, you’ll start out being good at one (due to there being only a limited amount of time a person can work in a day). Not only it’s going to be more efficient, but you’ll also get good at “how do I get good” at another archetype as well. It’s totally possible to exercise multiple archetypes in your day-to-day work (in fact, a 100x engineer will know what archetype he needs to play in a given project he’s in right now), so be flexible as well and spot the opportunities.</p><h3>Recommended Reading</h3><p>Here are several recommended reading if you want to learn more in-depth/case studies on how to become a better engineer/professional which will get you closer to becoming a 10x engineer:</p><ol><li><a href="https://amzn.to/2Q27F56">The Effective Engineer</a></li><li><a href="https://amzn.to/3urln05">Problem Solving 101</a></li><li><a href="https://amzn.to/2SsPLJn">How to Win Friends and Influence People</a></li><li><a href="https://staffeng.com/">Staff Eng Blog</a></li><li><a href="https://10percentengineer.substack.com/">How to Become a 10% Engineer</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f670a9bca968" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/how-to-be-a-10-engineer-be-a-10x-engineer-first-f670a9bca968">How to Be a 10% Engineer: Be a 10x Engineer First</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Be a 10% Engineer: Be Insanely Efficient]]></title>
            <link>https://medium.com/@lwastuargo/how-to-be-10-engineering-be-insanely-efficient-bbd13939854b?source=rss-ca1629ce933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbd13939854b</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[life-hacking]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Listiarso Wastuargo]]></dc:creator>
            <pubDate>Sun, 23 Oct 2022 05:38:36 GMT</pubDate>
            <atom:updated>2022-10-23T05:42:11.781Z</atom:updated>
            <content:encoded><![CDATA[<p>Going from a <a href="https://medium.com/@lwastuargo/10-engineer-ingredient-be-a-10x-engineer-first-f40a7b62c200">10x engineer</a> to a 10% engineer is primarily about efficiency. But at the same time, you’ll find out that when you become a better 10% engineer (by having more time), you also become a better 10x engineer (by becoming more effective).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/0*q0vKfM6m3_InwTXG.png" /><figcaption>The 10% engineer flywheel.</figcaption></figure><p>But how can I become a more efficient engineer? I follow a simple RADC framework: Reduce, Automate, Delegate, Compound (inspired by the RAD framework from <a href="https://www.youtube.com/watch?v=gcGquCZxsJc">Ali Abdaal’s recent video</a>).</p><h3>Reduce, Reuse, Recycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*HD-C7BqJIyzx-7TA.jpeg" /><figcaption>Let’s save the earth by becoming a 10% engineer.</figcaption></figure><p><strong>Reduce</strong>, means removing unneeded work. This is where you apply the famous <a href="https://en.wikipedia.org/wiki/Pareto_principle">Pareto principle or the 80/20 rule</a>. In the software engineering domain, you can apply this rule in the following lists:</p><ol><li>80% of the information you need to do the work is held by 20% of the team member. This means you only need to regularly meet a subset of your team to understand most information you need to do your job.</li><li>80% of the system can be observed and monitored by putting it in the core 20% spot. This means you can put logging only in a few call sites in your system to catch and prevent top issues.</li><li>80% of the error/crashes in the system can be fixed by fixing the top 20% of the most-reported bug.</li><li>You can achieve 80% sub-optimal decision-making only by understanding 20% of the domain knowledge. This means you only need to learn the high-level or first principle of a domain. Then you can make a decent decision on 80% of problems occurring in that domain.</li><li>80% of the knowledge can be shared just by sharing the top 20% condensed information. This means your weekly report doesn’t have to be lengthy to be informative.</li><li>80% of code review issues can be fixed with linter or choosing the right paradigm/language. Focus on the 20% that actually matters.</li></ol><p><strong>Reuse</strong> means making use of your previous work. In software engineering, it’s generally a sub-optimal practice if you can reuse your work. It means your work could’ve been written such that you only need to build it once and configure it for multiple use cases. That’s why the DRY principle (Don’t Repeat Yourself) is very popular among software engineers. Whether you’re a hardcore DRY believer or not, there are few examples where it’s good to reuse your existing work:</p><ol><li>Project management template (weekly meeting template, project updates, retrospective).</li><li>Building UIKit and Design Language System for the whole app, or the whole product sets.</li></ol><p><strong>Recycle</strong> means breaking down items into their raw material and reuse them. In product development, I consider this as breaking down a product requirement into smaller pieces where you might observe some tasks are repeated. In software engineering, I consider this as breaking down your system into modular ones so it can be reused for other projects. A few examples:</p><ol><li>Building a shared networking library by decoupling it from your main application to be used in your internal tools.</li><li>Building a podcast API by decoupling it from your search engine. This is how <a href="https://www.listennotes.com/blog/how-i-accidentally-built-a-podcast-api-business-46/">Listen Notes built its API business</a>.</li><li>Facebook recycled React declarative pattern and reused it for their native app application UI library, <a href="https://github.com/facebook/litho">Litho</a> and <a href="https://github.com/facebook/componentkit">ComponentKit</a>.</li></ol><h3>Automate</h3><p>Discussion about efficiency is incomplete without automation and productivity tools. In this post, I want to lightly touch on productivity tools from the angle of <strong>why</strong> we need them vs <strong>what</strong> they offer — so you don’t have to get attached to these tools when something better appears.</p><p><strong>Build your life operating system</strong>. Have you ever been in a situation where you forget about things you need to do for a given day? Say no more. You need a life operating system, a system that allows you to take in work, evaluate prioritization, evaluate the time of execution, and feed the system back about things you might additionally need to do.</p><p>Building a life operating system will allow you not to have to constantly worry about “what do I have to do today? Am I missing something?” The moment you know you need to do something in the future, the task will be captured in your system. Then it will be placed at the exact date when it should be done. This allows you to save not only time but also mental space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RQ1Y0XoNNTq0VuuO.png" /><figcaption>My Life OS using Notion.</figcaption></figure><p>There are many frameworks that are subsequently powered by different tools you can use to build your life operating system. I personally use a loosely-adopted-overly-simplified <a href="https://gettingthingsdone.com/">GTD framework</a> with Notion and Google Calendar.</p><p><strong>Schedule your message</strong>. Many leaders (especially boomers) often love to send non-urgent requests or questions during off-hour (be it on weekends or at night). This is not only inappropriate but also inefficient. Looking from an efficiency standpoint, those messages will not arrive during the productive hour of the recipient, thus they will not get the response that they expect (either timeliness or quality of response). The correct way to approach this is by sending your message to your recipient during their productive times so you get a timely and good response. This also helps build a better work culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hjTvs7qV6ZHVFFsM.png" /></figure><p>Schedule your email as well since people don’t read email at night and your email will be buried with other emails in the morning. I usually schedule my emails at 9:41 am on their timezone for the following reason:</p><ol><li>Between 9.30 am and 10:00 am because that’s when people start preparing for work. This is also the time when all the other spammy emails are sent already so your email will stay on top of the inbox.</li><li>At minutes 37, 41, and 53 (or any non-round number) so it doesn’t look like an automated message.</li><li>Send it in their timezone because the goal is to ensure they read it at their best convenience, not ours.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kYhLQiNzOuPl9pCF.png" /></figure><p>The option to schedule an email. Also, I invest in real estate. Hit me up if you’re interested to discuss this!</p><p><strong>Zero inbox</strong> is very underrated and not talked about nearly enough. Emptying your inbox is an important tool to free up your mental space to allow you to be more creative and kickstart the flywheel of 10% engineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gV6YWq0AilKR__XK.png" /><figcaption>0 inbox cures cancer.</figcaption></figure><p>There are top 2 things you can do to empty your inbox. The first one is by unsubscribing to unnecessary emails if you don’t need them. The 2nd one is by adding email rules to move the emails to respective folders or labels if you think you might need them in the future. The goal is to ensure only important and urgent emails go into your inbox, thus into your attention. When you don’t see values from an email list or subscription, add a rule to filter it out, move it to a separate folder, and enjoy less clutter. Don’t worry about false-negative (important emails that get filtered out of your inbox). If they’re <em>that</em> important, they will get to you somehow through other means (possibly Slack, WhatsApp messages, or maybe legal letters).</p><h3>Delegate Work</h3><p>People are one of the oldest known multipliers to your time and effort. The <em>right</em> people arguably are your greatest asset. But dealing with people is a complex problem because everyone is unique. Doing it incorrectly and you’ll have liabilities instead of assets. I follow these 4 principles:</p><p><strong>Understand their motivation</strong>. Everyone has different things that make them tick. Some people simply want the job for the money. Some people want to learn and get challenged. Some people want a bigger title.</p><p>Mapping the right work against people’s motivation can put the company, team leader, and team members in a win-win-win solution. For example, people who’re motivated by learning will be a good fit for explorative and research-y problems. People who just want to chill might be happy with normal business-as-usual problems (let’s face it, not all urgent and important problems will be novel and challenging).</p><p>Understanding people’s motivation also allows you to delegate work to others without requiring you to be a team leader or manager. This is called leading by influence vs leading by authority.</p><p><strong>Invest in onboarding framework and help with onboarding effort</strong>. <a href="https://amzn.to/3hMjfwD">In his book</a>, Edmond Lau mentioned that investing in an onboarding framework is the highest leverage activity you can do as an engineer (a leader or not). Investing 6 months in building an onboarding framework and 6 weeks for each new team member will give you a massive recurring return of investment by generating effective engineers who will use the knowledge they get from onboarding for years to come.</p><p><strong>Give the right bite-size problem to your team member</strong>. Giving easy problems to your team member, and your team member will not feel challenged enough and incur opportunity costs. Giving hard problems to your team member and you risk failed projects and frustrated team members. You might need to break down projects into tasks, products into projects, and problem statements into products.</p><p><strong>Invest in mentorship</strong>. Giving context for an ambiguous problem is relatively easier than breaking it down into projects and tasks. Thus it’s in your best interest to make your team member capable of doing harder, more ambiguous, more complex problems. To allow your team to digest more ambiguous problems you need to mentor them.</p><p>There are several mentoring styles. My personal favorite is giving them a harder problem than what they’re comfortable with, giving them enough space (this is the time efficiency kicks in), staying around for their sense of security, and intercepting when needed.</p><h3>Delegate Knowledge Gathering</h3><blockquote><em>Good artists copy, great artists steal.</em></blockquote><p>Within the domain of software engineering and product building, everyone is “forced” to keep learning to stay relevant. There are new JavaScript frameworks every day. New Kubernetes tool every other week. New machine learning algorithm variations every month. New programming paradigm every year. This can get overwhelming real fast, especially as Generalists whose superpower is their ability to connect the dots of multiple domain knowledge to build successful products. It suffices to say that continuous learning is part of the job.</p><p>So how do you optimize this learning requirement? There are a few principles that I use to help optimize my time for learning new technology:</p><p><strong>Do not reinvent the wheel</strong>. In my limited time in the industry, I’ve never seen a problem that has not been solved by someone else. A lot of my failed projects happened because I tried to reinvent the wheel. It’s either the same problem with different flavors of industry, different scales, different companies, or different user types. Sometimes you have to drop your maker’s hat and put your problem solver’s hat instead. Learn from other’s experiences.</p><p><strong>Be reactive in your problem-finding, be proactive in your problem-solving</strong>. Technology is created to solve a problem and make life easier. But at the same time problem evolves (based on the current market situation, company size, problem complexity change). In response to this, I usually try to learn new technology only when I see a problem. Then I do extensive research: understand the currently available frameworks and first principles, come up with multiple solutions, lining up their pros and cons, and future problems based on other people’s experience. Finally, I choose the best solution that will work for the next 2 years.</p><p><strong>Get a mentor</strong>. You need someone with who you can exchange ideas on specific scenarios of your ongoing issues. You also need someone who is a subject matter expert in an area regardless of your expertise in that area. This doesn’t have to be a formal paid mentorship either. This can be your accountability partner, your housemate, your direct reports, your manager, your skip manager, someone you follow on Twitter, someone you meet in a meetup, or a stranger you found in a bar.</p><h3>Stay to Compound</h3><p>If you’re lucky enough to find a company where you don’t burn out, get fairly compensated, compensations are adjusted frequently, are merit-based, and are constantly learning, then consider staying. Staying in one company compounds. Here’re three reasons why:</p><p>It’s not a surprise that the longer you work in one domain the better your <strong>familiarity with the tech stack</strong> used in the domain is. The more familiar you are with a tech stack, the more effective and efficient you will be in using them in your day-to-day work and planning.</p><p>The more senior you’re as a software engineer the more you realize that a lot of software engineer problems are actually people problems. Thus you need to generate <strong>social capital</strong> to allow you to work seamlessly and effectively with the people around you. Social capital consists of trust among team members, reputation among leaders, and established relationships between the cross-organization cross-functional team. Building social capital requires time and commitment. Thus more reason why you need to stay in one company.</p><p>As a 10x engineer, it’s important to operate based on the result, not action. And thus understanding <strong>business knowledge</strong> is paramount. The longer you stay in one company, the more familiar you’re with the funnel within the business. This translates to correct products to build, correct metrics to pursue, optimal prioritization, and correct team composition you need to gather to do a successful project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lRNOBDfzfZ9ceWWN.jpeg" /></figure><p>I doubt Einstein actually said this. Putting this here for the meme.</p><p>That’s the high-level optimization that I do to make my life and work more efficient. Let me know about yours!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbd13939854b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is 10% Engineer]]></title>
            <link>https://medium.com/@lwastuargo/what-is-10-engineer-97c1710b74bb?source=rss-ca1629ce933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/97c1710b74bb</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Listiarso Wastuargo]]></dc:creator>
            <pubDate>Fri, 14 Oct 2022 03:09:37 GMT</pubDate>
            <atom:updated>2022-10-14T03:09:37.830Z</atom:updated>
            <content:encoded><![CDATA[<p>Everybody who has spent a long time in software engineering probably would have heard about the (myth) of 10x engineer. The first Google search result of 10x engineer will give you the following definition:</p><blockquote><em>The concept of a </em><strong><em>10X engineer</em></strong><em> is actually very simple: It’s an </em><strong><em>engineer</em></strong><em> who’s 10 times better at their job than their peers.</em></blockquote><p>In practice, you’ll wonder what 10x engineers would look like in real life (if they’re not a myth). Some folks will say that 10x engineers are engineers who output 10x as much code compared to their peers. Others will say that 10x engineers are engineers who debug and fix issues 10x faster than their peers. Some will even say that 10x engineers are engineers who drive alignment with 10x less drama than their peers. I think that there are <strong>archetypes of 10x engineer</strong>, in which one can be within one or more archetypes, and I’d even add the more experienced 10x engineer (100x engineer?) would know which archetypes they should be playing right now.</p><p>Then, what is 10% engineer, and how is it related to 10x engineer? This is my definition of 10% engineer</p><blockquote><em>10% engineer is a </em><strong><em>10x engineer</em></strong><em> who has </em><strong><em>high degree of efficiency</em></strong><em> thus only requiring to work 10% of the time to accomplish similar result </em><strong><em>expected</em></strong><em> out of them.</em></blockquote><p>In short, you require three ingredients to become 10% engineer:</p><ol><li>Become a 10x engineer.</li><li>Crystal clear expectation (even if you’re the one who’s making expectations yourself).</li><li>Be insanely efficient.</li></ol><p>So that seems like a lot of work, right? So why bother? Here’s an example of a week in the life of 10% engineer named Vincent working at Facebook:</p><ol><li><strong>Monday</strong>: 1:1 with core team members (Vincent “manages” &gt; 20 engineers but only do regular 1:1 with 3 of them), cross-team and cross-functional sync. Then walk his dog in the afternoon. Work hours: <strong>3 hours</strong>.</li><li><strong>Tuesday</strong>: Walk his dog. Work hours: <strong>0 hours</strong>.</li><li><strong>Wednesday</strong>: Play League of Legends. Then walk his dog. Work hours: <strong>0 hours</strong>.</li><li><strong>Thursday</strong>: weekly sync. Then walk his dog. Work hours: <strong>1 hour</strong>.</li><li><strong>Friday</strong>: Walk his dog. Then happy hour with team. Work hours: <strong>0 hours</strong>.</li><li><strong>Saturday</strong> and <strong>Sunday</strong>: not so obvious but Vincent doesn’t work on weekends. Work hours: <strong>0 hours</strong>.</li><li>Total work hours: <strong>4 hours/week</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*GAxp-5zloDmr36Z9.jpeg" /><figcaption>Walking a dog is not only a fun activity but also a healthy one</figcaption></figure><p>I can personally say that I’ve seen multiple 7-figure-income engineers who’re working on the most interesting/challenging area in the company have accomplished this. And it’s not as mythical nor impossible as it sounds. Also, becoming a 10% engineer is not for everyone for multiple reasons. For example, not everyone knows what to do with all the remaining free time they have, and people can get depressed because of this.</p><p>If you’re interested to hear more about how to become a 10% engineer, what are the different tools you have to leverage, or how to use the remaining time you have as 10% engineer <strong>please consider following me in Medium</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97c1710b74bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>