<?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[Teach &amp; Code - Medium]]></title>
        <description><![CDATA[Thoughts, stories, and ideas. - Medium]]></description>
        <link>https://medium.com/teach-code?source=rss----f7f2fabebba7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Teach &amp;amp; Code - Medium</title>
            <link>https://medium.com/teach-code?source=rss----f7f2fabebba7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:18:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/teach-code" 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 Small Business Needs A Mobile App to Survive — Here’s Why]]></title>
            <link>https://medium.com/teach-code/your-small-business-needs-a-mobile-app-to-survive-heres-why-1e3e4066c042?source=rss----f7f2fabebba7---4</link>
            <guid isPermaLink="false">https://medium.com/p/1e3e4066c042</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Keith Elliott (keithelliott.co)]]></dc:creator>
            <pubDate>Wed, 28 Dec 2016 22:17:00 GMT</pubDate>
            <atom:updated>2016-12-28T22:16:59.634Z</atom:updated>
            <content:encoded><![CDATA[<p>Just a few years back, we were all talking about mobile being the future. That’s no longer the case.. mobile is the present. It’s the here and now of business. Mobile apps serve as the tipping point that will increase sales and customer satisfaction. Mobile is too big to ignore, and you’re missing out.</p><p>Frankly, there are many reasons that a small business needs a mobile app. Today, I’ll focus on three standout areas that make having an app essential. If you’re a small business owner, you need an app to engage socially with your customers, to sell more to them, and to differentiate your business from competitors.</p><h4>Engage Your Customers</h4><p>The biggest reason you need a mobile app is to expand your social presence, engaging with them on their terms. Whether you personally use social media or buy into the hype, your customers do, and they use their mobile phones. Let that sink in for moment. Your customers carry their phones everywhere they go, accessing apps on their phone all of the time. If you build a mobile app for your customers, you go along for the ride and get exclusive access to the customer.</p><p>Your customers love sharing! In fact, they share all the time. When they are waiting in line, they pull out their phones to see and share what their friends and family are up to. What’s so cool about a mobile app is that it gives you the ability to provide content that your users will want to see and share. By adding share and like buttons to the content in your mobile app, your customers can help you spread the word about your brand anytime and anywhere.</p><p>The value proposition outlined above is a major selling factor alone. However, here is the real killer that is even more important to your engagement strategy: push notifications.</p><p>Push notifications give you the super human abilities to reach out the customer to wow and awe them with relevant content that reaches them at the right time and place. A well built mobile app can help you determine your customer’s current location, which allows you to send targeted information at the time that it’s most relevant to them and to your business. For example, adding a geo-fence (location based perimeter) around your brick and mortar storefront could let you know when your customers are close to your store. If you knew that a good customer was 1 mile away from your store, you could send that customer a special offer or other incentive to stop by your store while they are close.</p><p>Push notifications are extremely valuable because you get the power to reach out to your customers directly with offers, discounts, and rewards customized to each customer, group, or all users of your app in broadcast form.</p><h4>Increase Sales</h4><p>A mobile app can be an important part of your sales and marketing strategy. The name of the game is competition: show current and potential customers the reasons they should choose your product or service over a competitor. Your mobile app gives you the platform to position your product in its best light. In addition, when you add payment capabilities, you can sell your products through your app, capitalizing on the immediacy of impulse. Your app could be a sales igniter to help you sell more to users right when they are ready to buy. Even if you don’t have a product that makes sense to sell online or via mobile, you can give your potential customers all the insights and information they need to walk into your stores ready and informed enough to buy!</p><h4>Uniqueness</h4><p>Your mobile app is your “always on” channel to highlight your brand’s uniqueness. A mobile app gives you a canvas to paint a masterpiece that appeals to your most loyal following. You can reward them with loyalty programs stored and accessible from their apps. You can use your creativity to show what’s special about your business to current and potential customers that were interested and intrigued enough to download your app. When you showcase your products and brand, you will be rewarded with more traffic from referrals, shares, and likes.</p><h4>Wrapping Up</h4><p>I want to leave you with a simple message. If you own a small business, you could be missing out on a big opportunity to strengthen your company. A mobile app can help you increase sales, expand your social presence, and add sparkle to your brand.</p><p>If you’re interested in having a mobile app for your business, visit us at <a href="http://www.gittie.com/">GittieLabs</a>. We’re a small business just like you — passionate about making a difference where we can. We build awesome apps. We won’t break the bank. We can help you get the app you need today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e3e4066c042" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teach-code/your-small-business-needs-a-mobile-app-to-survive-heres-why-1e3e4066c042">Your Small Business Needs A Mobile App to Survive — Here’s Why</a> was originally published in <a href="https://medium.com/teach-code">Teach &amp; Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5 Top Traits of RockStar Developers]]></title>
            <link>https://medium.com/teach-code/the-5-top-traits-of-rockstar-developers-68d1dc5070eb?source=rss----f7f2fabebba7---4</link>
            <guid isPermaLink="false">https://medium.com/p/68d1dc5070eb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Keith Elliott (keithelliott.co)]]></dc:creator>
            <pubDate>Sun, 13 Mar 2016 03:04:30 GMT</pubDate>
            <atom:updated>2016-03-13T03:04:29.935Z</atom:updated>
            <content:encoded><![CDATA[<p>I have spent over 15 years in software development. I have been an individual contributor, a technical lead, and have overseen building teams. I have played each of the key roles of a software team, and I have loved every minute of the journey. Make no mistake though, I’m not done. Instead, I’m at the reflecting part of my career, and I want to share what I see as the top traits of elite software developers. No one is born knowing how to code. Choosing to become a developer is easy. Persevering and battling long enough and hard enough to master your craft puts you into a very small and elite class of developers: I call rockstars.</p><blockquote>Choosing to become a developer is easy. Persevering and battling long enough and hard enough to master your craft puts you into a very small and elite class of developers I call rockstars.</blockquote><p>As software developer, the goal is to become elite — to be at the top of your game. A subject matter expert (SME), the one that everyone knows can and will get the job done — the Rockstar.</p><p>No matter how much raw talent you have, you can’t get to the summit without hard work. Many will try; few will get there. It’s more likely that after several years in the game, you will opt for management. Or worse yet, you could be content with never stressing your limits and pushing beyond. However, I think the journey is worth it. And if you’re curious about what it takes to get to the top, read on!</p><h4>#1 Rockstars actively seek to learn and apply new things</h4><p>The number one trait that Rockstar developers share is an active learning mindset. They never stop learning and are searching for ways to improve their skills. For example, as a mobile developer specializing in the Apple ecosystem, I spend at least 1.5 hours a day (on average) learning Apple APIs, watching WWDC videos, and applying what I’ve learned to work and side projects. I’ve watched over 90% of WWDC videos that focus on development. In fact, I’ve watched a good portion of those videos multiple times. I find reasons and ways to apply my learnings in my day job as well. Sometimes it means that create side projects to experiment with technologies that I don’t need today but might need tomorrow. The moment you stop learning, you’re done in technology. The sooner you accept it, the better.</p><p>How many developers do you know who spend their free time watching WWDC (Apple’s World Wide Developer Conference) and getting excited about the next developer conference? I’m guessing the number is small and limited to the truly dedicated. But that’s the rub! A passion for learning is what separates the truly good ones from the rest.</p><p>I’m not saying that you have to possess rocket scientist intellect to become a Rockstar. You don’t… instead you need to have more drive than the developers satisfied with relying only on their intellect and degrees. After all, it’s been my experience that high grades in school alone aren’t the best measure of future success in software development. It definitely helps, but I would hire the passionate and driven developer over the big school degree candidate any day of the week.</p><p>Rockstars commit themselves to their craft. They want to be the best in their fields. And while you may not aspire to be an MacOS/iOS developer, I believe that the same process and dedication applies to all developers and across all domains and disciplines. You don’t have to tell a rockstar to go learn. Chances are they are already ahead of you learning something new at this very moment.</p><blockquote>You don’t have to tell a rockstar to go learn. Chances are they are already ahead of you learning something new at this very moment.</blockquote><h4>#2 Rockstars stay up to date on new innovations</h4><p>Rockstar developers aren’t satisfied with yesterday’s knowledge and approved solutions. They are intellectually curious and are constantly proposing new ways to accomplish tasks. They evaluate new and promising ideas and adopt them quicker than most. If you’re a team lead or project manager, don’t be alarmed. You might be thinking that these developers are going to kill your project. Rest assured, this won’t happen. A true Rockstar wouldn’t risk your project simply to implement an unproven framework or new idea. Instead, a Rockstar would benchmark the new idea or framework in a separate project (probably one of their many side projects) before risking it in your production code. Searching for new innovations and contributing to novel new approaches are so ingrained in a Rockstar’s DNA that they are more than happy to do this work on their own time. However, no matter how it happens, a Rockstar will find a way to bring vetted best practices back their code bases and make the team and project better for it.</p><h4>#3 Rockstars live to share, help, and teach others</h4><p>A Rockstar lives for sharing sharing and demonstrating what he/she knows to help others improve. They volunteer for opportunities to share their knowledge with their peers. Think “lunch and learn” or “brown bag” lectures where a Rockstar will lead a discussion on new trends. They go to meetups, conferences, and are apart of development groups. Knowledge is like air; it’s that fundamental to a Rockstar. Once these folks obtain knowledge, they have to share it with others. A Rockstar will peer review another developer’s code and offer pointers to make the code better. A Rockstar can always be interrupted and is approachable for other developers to bounce ideas, peer program an issue, brainstorm to ideas to bypass obstacles, and will sacrifice their entire workday to help someone else get their work done. It’s just what they do.</p><h4>#4 Rockstars take pride in every line of code they produce</h4><p>If you really want to incite rage in a Rockstar, check in code that doesn’t compile and go home before the build finishes (or rather fails). This is so enraging to Rockstars because they don’t just sling code. Each line of code they produce is personal, and there is no room for shortcuts. Checking in code that doesn’t compile and then leaving it to the build server to find errors is a huge pet peeve of Rockstars. It screams that the guilty developer is not focused on code quality and is lazily trying to check off the task. It also states that the developer doesn’t care whether the code works and is leaving the task of testing to someone else.</p><p>A Rockstar treats every line of code as if it is their personal signature being introduced into the code base. From a Rockstar’s vantage, every line of code is judgement of their skills as a developer, and a Rockstar won’t settle for anything short of excellence.</p><blockquote>A Rockstar treats every line of code as if it is their personal signature being introduced into the code base.</blockquote><h4>#5 Rockstars lead with their code over boasting about skills</h4><p>Rockstars don’t have to tell you how good they are. In fact, they are the first to downplay their skills and probably have a hard time promoting themselves. Instead, they lead with their code. Their code speaks volumes, and every other developer on the team knows who to go to when they need help.</p><h4>Wrapping Up</h4><p>If you consider yourself a serious software developer, you should aspire to emulate this list. I won’t promise you that the path is easy or without bumps, but I will say that it’s worth the pursuit. We can all improve our skills; much of the requirement stems from our attitude and outlook. I’ve shown you the list. It’s up to you to make the change.</p><p>On a lighter note, I also wrote an article on why creating native apps is probably the best way to go in most of your mobile development endeavors. Please read that one and weigh in the discussion!</p><p><a href="https://medium.com/p/416041d27eac">Your Hybrid App is Going to Kill You</a></p><p>If you find this post helpful, please recommend it for others to read. You can visit me at <a href="http://www.gittielabs.com/">www.gittielabs.com</a> and subscribe to my RSS feed so that you won’t miss a post. I’m also putting together a video course to teach Swift development and could use your input on topics you feel would be helpful. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68d1dc5070eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teach-code/the-5-top-traits-of-rockstar-developers-68d1dc5070eb">The 5 Top Traits of RockStar Developers</a> was originally published in <a href="https://medium.com/teach-code">Teach &amp; Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Hybrid App is Going to Kill You]]></title>
            <link>https://medium.com/teach-code/your-hybrid-app-is-going-to-kill-you-416041d27eac?source=rss----f7f2fabebba7---4</link>
            <guid isPermaLink="false">https://medium.com/p/416041d27eac</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Keith Elliott (keithelliott.co)]]></dc:creator>
            <pubDate>Fri, 04 Mar 2016 00:16:35 GMT</pubDate>
            <atom:updated>2016-03-13T13:19:53.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqtBS70McfTjydY5ls_96w.jpeg" /><figcaption>Courtsey of <a href="https://unsplash.com/photos/U5rMrSI7Pn4">Matthew Wiebe</a></figcaption></figure><p>If your company only makes hybrid apps, you are going to lose in the end; it’s just a matter of time. Hybrid mobile apps do have their place, but most companies either ignore their limitations or don’t care enough to listen to warnings that are presented every day by native mobile developers.</p><p>Before we dive into things, let’s set some parameters on what I mean when I say that hybrid apps will suck the life out of you. I’m a mobile developer who has a lot of experience (more years than I care to admit) developing mostly native apps but a fair share of hybrid apps too. My first mobile app was for a Palm V written in C++. Does anyone remember those days? I’m not going to quote you statistics on how every mobile project fails. I really dislike the stats that float around the web from executives that have never coded an app stating how beneficial hybrid apps can be. It’s a real shame that these executives are the ones empowered with the decision making power to choose between hybrid and native apps; they doom their company’s mobile efforts with their unwise decisions.</p><h4>So How Did We Get Here?</h4><p>Why are hybrid apps chosen over native apps? <strong>Shortcuts!</strong> Hybrid apps are usually chosen because executives are looking for shortcuts. Some marketing genius (sarcasm) planted the seed that hybrid apps are developed quicker and are less expensive by hiring web developers instead of native mobile developers, investing less time, and targeting every mobile device without having to create multiple versions of the code. Guess what? <strong>Those claims are lies!</strong> (This is the case unless the project is so basic that it could have been a responsive web application from the onset, which doesn’t apply to what I’m referring to.) So sad, so pathetic, and yet it’s the current state of the mobile developer world. Hybrid apps appear to be here to stay. I’m willing to bet that when you ask the business gurus in charge why they chose hybrid for the direction of your company’s app, you will hear some variation of the reasons above. You’ve been warned!</p><h4>The Lies Non-Technical Managers Tell You</h4><p>As I mentioned above, I’m not going to allow the statistics of non-coders to to trump the experience of real developers. I will tell you that when one of these manager types tells you that your next project is going to be done in half the time, with a small team, and will support iOS and Android… you should run! These managers don’t know that they are signing your death certificate — or, at the very least, you will hate your life while on the project. How in the world did these individuals get put in charge any way? Ah, that is a question for another day. The key takeaway is that you need to be vary suspicious about the supposed sources of the claims that your next hybrid project is the right decision because the stats floating around the internet claim hybrid is winning the mobile race. If you’re a native girl or guy, I would say it’s time to look for a better job.</p><h4>The Good Truth About Hybrid Apps</h4><p>The truth about hybrid apps is that they are useful in some cases. Hybrid apps are good in cases where the application just needs to do basic display work in support of your main web application. When all you’re really doing is trying to get a bigger audience using the app stores (Google and Apple), then a hybrid app might work… especially when the app doesn’t really do anything useful.</p><p>Hybrid apps could also be advantageous when they are just components of a native app. However, in other words, you have a native app and want to add a web component from your web application. In this case, you can’t even really say you have a hybrid app.</p><h4>Why Do Hybrid Apps Spiral into Death Cycles</h4><p>Every hybrid app starts off with the best intentions. Armed with all of the success stats on hybrid apps your manager dumped on you (which you know to be complete crap), you launch you editor and code away. In the beginning, things are good. Your first set of features seem to be coming along nicely. And then it happens; you get your first request to do something that isn’t supported on Android but is supported on iOS. What do you do? Naturally, you add your first (of a long list to come) conditional statement to do feature A for iOS and do feature B for Android. A week later you realize that your code now contains so many of these conditional statements that you’re beginning to wonder if you should split your code into iOS and Android codebases so that you don’t have to keep adding conditionals! But wait, you can’t do that because your manager told you that hybrid apps are meant to be written once and run everywhere. But that doesn’t seem to be the case here, does it? Besides, if you split your code base, you would have to support two separate sets of code. Ugh! Two sets of code? One for iOS and one for Android? Forget that! Especially since your manager has also already informed you that you should be able to do this in less time than if you had written a native app. Two code bases would break a cardinal rule of having a hybrid app.</p><p>Let’s skip over the dual code base problem for a moment. You have bigger problems to address. After a while, you are beginning to see performance issues on Android. You want to ask the Android expert on your team why things don’t look right, but you can’t. Your manager didn’t let you add one to the team. Instead, you only have mobile web developers that don’t understand Java or the Android SDK. In order to do the next best thing, you search aimlessly through StackOverflow for an open source plugin that will hide the details of the OS. Your goal is to allow your web developers to make Javascript calls to their hearts’ desires without understanding the underlying operating system or how to fix the problems that are coming up. Congratulations; you just created your first cover up! You don’t really know how the problem was fixed or why this plugin fixed things, but who cares — you’re building a hybrid app and, according to your boss, you should be halfway done. You explain away the side effects of the plugin you introduced as issues you just have to live with. After all, you can’t be expected to fix Android OS issues or any issues introduced by phone manufacturers! Wow, that sounds good, and some of it might even be true. Too bad you don’t have an Android developer on the team to verify if it’s really true. Instead of a proper consultation, you add 20 more plugins to your app to handle additional problems that seem to be rapidly showing up.</p><p>Then you discover your more problems. According to your manager, you are weeks behind schedule. You just can’t seem to add enough conditional statements to handle all of the OS specific use cases or find enough plugins to address the issues that you don’t understand because you chose not to add any native mobile developers to the team. At this rate, you need to add a bunch more developers or sacrifice the release schedule to make the deadline — and who in the world set such a ridiculous deadline anyway? Given the opportunity to hire more developers, you grab a few additional web developers. Your manager is now telling you that this project is getting expensive and that there really isn’t room to hire native developers. You can have more bodies, but they need to be web developers. After all, the new developers could work on either iOS or Android issues and will be cheaper than highering expensive talent that can only work on iOS or Android. At this point your project is officially screwed, and you are powerless to stop it.</p><h4>What Do We Do Now</h4><p>The entire tragedy of hybrid apps hasn’t been fully represented above. The real saga is even more somber. When you take into account the sacrifices you make in terms of performance and features that users expect, the impact of choosing hybrid is even more costly. What user really wants to use an app that is slow and unresponsive? If you’re an iOS user, do you want to use an app that looks like an Android app? If you’re an Android user, do you want to use an app that feels like an iOS app? The answer is no! But the write-once mantra, would say, “It’s really not that important to please users; writing once will save you money!”</p><p>If you haven’t started that hybrid app, I suggest you really think long and hard before starting one! There is probably a real reason that companies like Facebook have abandoned their reliance on a hybrid strategy. Check out React Native if you have doubts on that claim. Chances are you aren’t going to finish your project quicker using a hybrid strategy. You aren’t going to save money, and you definitely aren’t going to delight your users by taking shortcuts. But hey, that’s you manager’s call, right?</p><p>If you are in the middle of a hybrid app, I so hope that you chose this route for one of the (two) good reasons I mentioned earlier. If not, get your resume in order and find a better job. You’re in for a lot of headaches with that project — ones that could have been avoided by going native from the start.</p><p>On a related note, check out my article on the common traits Rockstar developers possess.</p><p><a href="https://medium.com/p/68d1dc5070eb"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=416041d27eac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teach-code/your-hybrid-app-is-going-to-kill-you-416041d27eac">Your Hybrid App is Going to Kill You</a> was originally published in <a href="https://medium.com/teach-code">Teach &amp; Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Why do I code?] I code to change the world.]]></title>
            <link>https://medium.com/teach-code/why-do-i-code-i-code-to-change-the-world-241183274a0a?source=rss----f7f2fabebba7---4</link>
            <guid isPermaLink="false">https://medium.com/p/241183274a0a</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Keith Elliott (keithelliott.co)]]></dc:creator>
            <pubDate>Thu, 25 Feb 2016 12:15:47 GMT</pubDate>
            <atom:updated>2016-02-25T12:15:47.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xUrSmIidxUN0g04hAa_mvg.png" /></figure><p>Sure, that is a bold statement. But what does it really mean to change the world? In my mind, it means <em>to add value to others in the precise quality and quantity that allows freedom from a set of problems in order to focus on a more important or essential task</em>. To change the world, you need to provide a solution that is greater than the collective previous alternatives. In examining truly ground breaking discoveries, I imagine we would agree that a great deal of hard work goes into such efforts — many that could attest to how great the impact is for mankind.</p><p>Can we change the world, as individuals, without being vaulted to the world stage? Can small inputs into the improvement engine be the impetus of major feats? I say yes. They do count; they do contribute<em>. </em>Every exhaustive effort that leads toward progress counts, no matter the size. Efficiency gained from the tiniest of innovations fuels the flames, inching us closer to even larger breakthroughs. Perceived minor improvements in some areas can spark of new thought in another area or permit us to redeploy resources in new promising arenas. We all benefit when people step up the plate to share skills and knowledge.</p><p>My goal is to take existing problems, break them into smaller ones, and then into even smaller bits, until I get to the essence of logic statements that I can craft into code, which will be compiled into products that solve real problems. And while my software applications won’t always generate earth shattering outputs — the basis of which unicorn companies are made to rule the day on Wall Street — they are innovations just same. I know that my work helps to make e<em>veryday life more efficient, more enjoyable, more productive</em>. Isn’t that a worthy purpose to which we should aspire?</p><p>I love my craft. I’ve spent my entire career working with technology and developing software to solve problems. I am excited each day to work on new and novel ideas. I live for the moments when my work product offers a viable solution to any of life’s challenges and inefficiencies. I am at awe and humbled by users interacting with my creations that, while not perfect, are helping to satisfy real needs and desires.</p><p>Software is my passion and I am a master craftsman capable of tackling all manner of problems presented. I dream of creating amazing solutions and then carefully pursue building the foundation to reach my lofty aspirations.</p><blockquote>If you have built castles in the air, your work need not be lost; that is where they should be. Now put the foundations under them. — Henry David Thoreau</blockquote><p>My humanity is evident, however. My creations don’t solve the world’s largest problems. I haven’t developed code to solve cancer or to feed a starving population. Still, I’m not discouraged. In fact, I am motivated to solve the problems that might enable someone else to solve those larger problems. Every minute I can save you from repeating a mundane task that I could automate or eliminate entirely matters greatly and prompts us to seek new challenges to address. The <em>ripple</em> is what I’m after — that’s when the increase in productivity to which I contributed allows someone else to build upon that and create their own productivity gains and so on, until we all benefit from a large breakthrough.</p><p>I solve problems. I know that I am helping others, and that makes me happy. I’m doing my part to make the world a better place, one line of code at a time. I am a coder. I am helping to change the world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=241183274a0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teach-code/why-do-i-code-i-code-to-change-the-world-241183274a0a">[Why do I code?] I code to change the world.</a> was originally published in <a href="https://medium.com/teach-code">Teach &amp; Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>