<?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 Jonas Bauer on Medium]]></title>
        <description><![CDATA[Stories by Jonas Bauer on Medium]]></description>
        <link>https://medium.com/@jonasbauer?source=rss-3d6f9a9fb24b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*r36ht-yx25Ve6v6T.</url>
            <title>Stories by Jonas Bauer on Medium</title>
            <link>https://medium.com/@jonasbauer?source=rss-3d6f9a9fb24b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:11:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonasbauer/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[Lessons learned as the youngest of 200]]></title>
            <link>https://medium.com/the-cabin-kids/lessons-learned-as-the-youngest-of-200-2bf7ff9d73fe?source=rss-3d6f9a9fb24b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bf7ff9d73fe</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Jonas Bauer]]></dc:creator>
            <pubDate>Sat, 27 Apr 2019 05:41:46 GMT</pubDate>
            <atom:updated>2019-04-27T16:58:38.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uw7vF6nzyX9thEdfX6LdUQ.jpeg" /></figure><p>A quick self-introduction:</p><p>I’m a software engineer by profession working at a mid-size tech startup, where I have been the youngest employee for the past ~3 years. I started, at high school age, with no diploma, as a glorified tech support intern answering emails from customers with technical problems. I had little-to-no knowledge of programming in a professional environment. Today I work as an engineer making contributions to multiple developing products at the company. What follows is an attempt to document two guiding principles I believe have helped contribute to getting me to where I am today; take them with a grain of salt.</p><h3>Know what you don’t know</h3><p>When you are in a position of lesser education than just about everyone else in a building, one of the most important skills to have is being able to identify your weakness. There is no shame in not knowing something, and a good group of peers will not blame you for not being able to solve a problem or answer a question off the top of your head. A healthy work environment will focus on the results you produce, and so a college graduate and a high school dropout providing the same value will be viewed equally (yes, there are plenty of places where status is given by more arbitrary measures, but that’s a discussion for another day). If you are dedicated enough, effective execution alone will allow you to work on almost anything you want, provided you can get a foot in the door. If you understand both your abilities and your ability to learn and use that to inform whether you can commit to the project, you will find a wealth of new opportunities within your capabilities.</p><p>Essential to this gradual progress is the understanding of your own limits because ignorance of your own ignorance is no excuse. To be able to accurately estimate your ability to accomplish a task you must know both the entire scope, the intersection of that scope with your own skillset, and the amount of effort required to learn anything outside your existing mastery. This is an idealistic view since it is never possible to fully conceptualize your own knowledge or every detail of a task in advance of starting. The important thing is becoming good at estimating, creating <strong>accurate </strong>margins of error for yourself, and correctly sizing buffers to account for what you don’t know. This is only possible over many iterations of success and failure, but will never happen if you don’t actively pay attention to it every time you approach a new problem.</p><p>Even when you are the only stakeholder in a project, you need to know what you can reasonably accomplish, and what things either can’t be done or need further self-investment (think more education) for you to complete. Without this self-evaluation, you will find yourself committing to tasks beyond your ability to complete, leading to inevitable disappointment at the lack of meaningful progress.</p><h3>Never stop learning</h3><p>Learning is a continual process, and anyone that forgets that will quickly become dated, relegated to slowly becoming irrelevant in a world that never stops moving forward. There is a large segment of even well-educated people that expect there to be a termination point in their education, which once reached will allow them to kick back and coast on what they already know. For some individuals, this target is the completion of high school, while for others it’s the attainment of a Bachelor’s, Master’s, or another university-level degree. Unless you are focusing on an area where everything to know is already known, a debatable point itself, there is no singular point at which it is possible to claim to have ‘complete’ knowledge. Understanding this, and its implications of an endless cycle of learning new things, returning to review existing knowledge in light of new information, and the improvement of skills is critical to growth.</p><p>When projects in life come up that require the completion of work in “unfamiliar territory” do not shy away from them on principle. Evaluate whether you have the abilities to complete the task and whether you have the ability to learn the necessary parts to complete the task. When you aren’t sure if you have the capability to learn what you need to, take a step back and evaluate that as its own problem: What do I need to learn now, to be able to understand how to approach learning the original thing in the future?</p><p>Consider that you decide to try baking your favorite dessert for the first time. If you immediately go to the kitchen to get started, you may find vital cooking utensils missing from the kitchen, unusable ingredients, and simply missing skills to produce that final tasty treat. Instead of blindly diving in, most people would take the time to look at a recipe, ensuring they have all the ingredients and necessary cookware in advance. If you don’t have a cookbook, then you don’t just give up, you go find one. If you aren’t confident in your skills, you might try making something fundamentally similar, but simpler. If you’re not sure where to get what you need, use a search engine, a trusted friend, or trial and error until you have it.</p><p>The point is, there is always an easier step to begin with if where you’re starting seems infeasible. The more you do this, the more tools are generally readily available for you to use, allowing you to skip a few more pre-cursor steps. You start to gain the knowledge of how to substitute tools and skills, from experience that they can produce equivalent results, allowing you to approach more complex problems with creative solutions.</p><h3>Afterward</h3><p>If you take anything away from this post, I would say that it should be that people (myself included) are less capable than they think, but that doesn’t mean they shouldn’t try new things. Pick something you aspire to have completed a week, a month, or a year from now. Understand why you can’t do that right now, and then go figure out what you need to improve about yourself to get there. Do this over and over again, breaking it down into smaller and smaller chunks until you have a single thing you can go do right now that helps you get there, something you can have done by the end of the day, and go do it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bf7ff9d73fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cabin-kids/lessons-learned-as-the-youngest-of-200-2bf7ff9d73fe">Lessons learned as the youngest of 200</a> was originally published in <a href="https://medium.com/the-cabin-kids">The Cabin Kids</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>