<?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 Abner Coimbre on Medium]]></title>
        <description><![CDATA[Stories by Abner Coimbre on Medium]]></description>
        <link>https://medium.com/@abnercoimbre?source=rss-4d9ecbcfc373------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lBcgJcbGfvoptCL6gsC59w.png</url>
            <title>Stories by Abner Coimbre on Medium</title>
            <link>https://medium.com/@abnercoimbre?source=rss-4d9ecbcfc373------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:05:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abnercoimbre/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[Abandon Twitter, Dev Some More]]></title>
            <link>https://medium.com/hackernoon/abandon-twitter-dev-some-more-489fb34d2a2b?source=rss-4d9ecbcfc373------2</link>
            <guid isPermaLink="false">https://medium.com/p/489fb34d2a2b</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming-tips]]></category>
            <dc:creator><![CDATA[Abner Coimbre]]></dc:creator>
            <pubDate>Fri, 15 Sep 2017 07:09:58 GMT</pubDate>
            <atom:updated>2019-05-24T05:27:51.897Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I used Twitter as a developer (and why I left it)</h4><p>UPDATE #2: <a href="https://medium.com/@IsaacSimpson/how-leaving-social-media-affects-your-mind-c9e22df2c354">Here</a> is an amazing article describing the effects of leaving social media.</p><p><em>UPDATE: It’s been a few months since my last tweet, and I returned to Twitter on a healthier schedule. This article is still relevant, because without abandoning Twitter for a good while, I would not have seen how productive I can be without it.</em></p><p>It’s not clear when, but I’ve become addicted to a certain way of living online, and I’ve also realized this particular approach of leveraging the web may have stunted my growth as a developer. I dubbed it the Twitter way, since Twitter is the central platform around which most (but not all!) of my troubles came about. If you’re reading this article, you may be wondering what this silly “Twitter way” is, and why at the end of my epiphany I deleted my account with alacrity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*yQWmOWtfiKSjcaGWamq04w.jpeg" /><figcaption>It’s crazy I think of social media as an arresting addiction. I never wanted to be that guy.</figcaption></figure><p>Before I go on, let me emphasize I’m describing a personal problem, and I’m not claiming most developers face it. I also regard Twitter as an incredible networking platform in general (ignoring how it might employ Ad Tech, though it seems <a href="https://hackernoon.com/tagged/facebook">Facebook</a> is more perverse.) <strong>My decision to abandon the Twitter way doesn’t mean we should all delete our accounts — even though I did.</strong> You may very well be someone who doesn’t identify with any of the symptoms I’m about to discuss, and you should stick to Twitter to keep track of all your strong, meaningful connections there...</p><p>At the very least, the reader may appreciate the other steps I’ve taken to be more productive online.</p><h3>The Twitter Way</h3><p>There were three specific patterns of behavior I saw myself acting out, and it eventually became something I did routinely and on a daily basis.</p><h4>1. Lose myself in debate threads between two or more developers</h4><p>The reason this was bad has to do with losing an unjustifiably large amount of time <em>seeking thrills from debates</em>.</p><p>If I’m honest with myself, the topic at hand wasn’t relevant to me. As long as it involved spicy language, and some of my favorite programmers were involved, all the better! In addition, I always felt remorse for not taking the time to instead read the programmer’s blog posts on my own time to actually <em>learn from them. </em>Why did I come to admire these developers in the first place? Why do I feel a need to look at their rants so often, when that’s not what motivated me to want to be like them? Over time, I had exactly zero hours to do any research online and learn new things about <a href="https://hackernoon.com/tagged/programming">programming</a>… because by the time I closed the Twitter app, it was time for bed.</p><h4>2. Confuse @ mentions with a sense of duty</h4><p>Whenever your name is mentioned somewhere on the Internet, and you get notified by it, there’s a rush to it that makes you believe you are loved and respected. Even if the comments are negative, who cares! They’re <em>paying attention</em>! And when a large enough number of people are following you, and the rate of notifications increase, you tell yourself people admire you.You start to believe it as a hard fact, and you justify spending time on birdsite because you have a duty to your fans.</p><p>I call bull.</p><p>First, the rate of @ mentions say nothing meaningful about what people actually think. There are forces beyond your control that may determine why people react to your online persona: hype; a trending topic; your reddit comment becoming a meme, and so on. However, let’s pretend we somehow became hugely influential — that doesn’t mean we have <em>any</em> responsibility to regularly keep people informed on our lives. You may believe you need to tweet all the time, but if you’re a programmer who’s not in charge of some official marketing campaign (i.e. you’re not a company and you’re not a full-time indie), there isn’t any meaningful need. In fact, I claim if you’re a good enough programmer, people will find the means to keep up-to-date with you. I can count with just one hand the programmers that’ll seriously make me go out of my way to find out what they’re up to. This revelation gave me pause about my own inflated ego.</p><h4>3. Dropping the ball on e-mail</h4><p>What started off as putting off e-mails for tomorrow (in favor of Twitter thread replies) became putting off dozens of important and delayed mail responses<em> </em><strong>per week</strong><em>. That is insane. </em>Let’s think about this for a second: I gave priority to answering simple tweets from randos instead of sitting down and having long-form conversations with programmers who cared enough to compose an e-mail for me. If that’s not a serious lapse in judgement I don’t know what is. This was the third and final pattern of behavior that made me realize I have a problem.</p><h3>What’s your new way?</h3><p>Let’s recap on the essentials:</p><ol><li>I fooled myself into thinking that being with other devs on Twitter meant I was productive.</li><li>The above behaviors I described are not<strong> </strong>representative of developers who <em>actually</em> want to have real personal growth outside of their job.</li><li>I called it the Twitter way because I have other close friends who had had similar patterns of behavior until they came to similar conclusions.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*3nAhs_mZTIAKh8u04MWFEw.png" /><figcaption>This is the only royalty-free bird I found. Yikes.</figcaption></figure><p>Now that I saw the error of my ways, how do I plan to spend my free time online, network with programmers, and actually improve myself?</p><h4>Fight for a Cause: Online Privacy</h4><p>I think we should all actively engage in some online cause. Mine is privacy, and developers are in a great position to understand morally iffy trackings of user data. Here are a few links to recent discussions which reflect my views on the matter:</p><p><a href="https://www.lrb.co.uk/v39/n16/john-lanchester/you-are-the-product">You Are the Product </a>— The most interesting critical analysis I’ve read on Facebook’s business model. It’s a long essay but enlightening and potentially worth your time.</p><p><a href="https://www.youtube.com/watch?v=KwzJlvx4ndk">It’s time to break up Google</a> — A poignant but accurate video by privacy advocate Bryan Lunduke.</p><p><a href="https://spreadprivacy.com/how-to-remove-google/">How to Live Without Google</a> — This article came out at the time of writing! In this post, DuckDuckGo (DDG) recommends ways an individual can reclaim their privacy.</p><p>Of course, taking back your privacy involves some annoying effort. As much as I love DDG, and although their search results have improved significantly, they’re still not Google. It’s a hit I decided to take, though, and the developers are open to examples of where to improve. I’ve deleted Facebook; I’m slowly phasing out Gmail in favor of <a href="https://protonmail.com/">ProtonMail</a>; I’ve installed the EFF’s <a href="https://www.eff.org/privacybadger">Privacy Badger</a> and I’m getting my news through <a href="https://feedly.com/i/welcome">Feedly</a>. That last one is an extra measure to avoid my temptation in being a spectator to outrage and flame wars.</p><h4>Engaging in a valuable Networking Platform</h4><p>I deleted a ton of online accounts and I’m letting my personal domain expire—many devs don’t need a website — in favor of focusing on platforms that actually encourage me to have long useful discussions. So far, Medium and <a href="https://twitch.tv/abnercoimbre">Twitch</a> (and of course, <a href="https://handmade.network/">Handmade Network</a>!) are my top choices. I’m at a new apartment and I still need to buy furniture and proper equipment before I stream again, but it’s definitely a worthwhile investment for serious programmers looking for real-time moderated feedback.</p><h4>Reading Source Code</h4><p>I’ll reveal two programmers that I would go out of my way to see what they’re up to: <a href="http://fabiensanglard.net/">Fabien</a> and <a href="https://fgiesen.wordpress.com/">Fabian</a>. From what we know about them, what do they owe a lot of their success to? Reading. Metric Tons. Of Source Sauce.</p><p>This has not been easy for me to do, but I’m slowly getting used to it, and there are indeed treasure troves to be found even in the most obscure of codebases. If you’re interested in this kind of hobby, I highly recommend you start your journey with <a href="https://github.com/fabiensanglard/Chocolate-Wolfenstein-3D">Wolfenstein 3D</a>. Fabien’s <a href="http://fabiensanglard.net/Game_Engine_Black_Book_Release/index.php">latest book</a> may make your foray into this code much easier to muddle through— and you’ll develop your skills measurably faster than any Tweet thread ever will.</p><h3>Signing Off</h3><p>I’ll miss the bird, but I’m excited about my commitments. Send me an <a href="http://abner@handmadedev.org/">e-mail</a>, maybe this time I’ll reply!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*-cbZeTUN3TZyCOP0FWdIkg.png" /></figure><p><em>Abner Coimbre (left) was Kennedy Space Center’s Intern of the Year in 2015 and was named to Kennedy’s 2016 Top 10 Innovators . He currently lives in Seattle working for Thekla, Inc.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=489fb34d2a2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/abandon-twitter-dev-some-more-489fb34d2a2b">Abandon Twitter, Dev Some More</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Look into NASA’s Coding Philosophy]]></title>
            <link>https://medium.com/student-voices/a-look-into-nasas-coding-philosophy-b747957c7f8a?source=rss-4d9ecbcfc373------2</link>
            <guid isPermaLink="false">https://medium.com/p/b747957c7f8a</guid>
            <category><![CDATA[nasa-coding-philosophy]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nasa]]></category>
            <dc:creator><![CDATA[Abner Coimbre]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 14:45:03 GMT</pubDate>
            <atom:updated>2018-06-19T08:01:33.875Z</atom:updated>
            <content:encoded><![CDATA[<p>A Look into NASA’s Coding Philosophy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7R3chd2n8ia5Xxoca2IKtw.jpeg" /><figcaption>Kennedy Space Center</figcaption></figure><p><em>Having done work for Kennedy does not imply I’m NASA’s mouthpiece. This write-up was made at a personal capacity, and came from a </em><a href="https://www.twitch.tv/videos/159126334"><em>live talk</em></a><em> I gave on Twitch.</em></p><h3>Who, out of all of us, speaks the truth?</h3><h4>The World of Modern Software</h4><p>There’s a recurring theme in the programming community that’s tied to finding “better ways” to write “modern software.” Whether or not the term “modern” is actually any useful — computer programming hasn’t been around for very long — I’m definitely left with the impression folks always have something “new” or “better” to say on the subject. And so if we pay attention to the conversations surrounding software development today, we’ll quickly realize how important it is to separate the wheat from the chaff: what’s useful and what isn’t.</p><p><strong>NASA has to Cut through the Bullshit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T5c8A2vpxtqDN2pODpP0Ug.jpeg" /><figcaption>Stakes are high when writing safety-related software (Photo: David McNew/Getty Images)</figcaption></figure><p>Given all of this modern software talk, I have seen beginner programmers asking what I think is the most important question of their careers: “Which things should we pay attention to?”, and honestly, it’s generally quite cruel to encourage them to follow that up with:</p><ul><li>Should OOP be the future of programming?</li><li>Let’s join the Rust Evangelism Strikeforce LUL</li><li>Is Go like totally better than&lt;language_with_other_design_goals&gt;?</li></ul><p>At least, that’s not how NASA set out to answer it when it had asked that question too. The story of the agency is well-known, which is that the space program may suffer irreversible consequences if any of its software is incorrect, among them death. The shock of that reality has allowed them to develop a certain attitude towards programming. It could be instructive to take a look at what they value.</p><p>With some years of work there, I wish to provide a first-hand account on the philosophy that’s allowed the space agency to produce some of the world’s most reliable software, and I’ll frame their attitude towards programming with a set of four assumptions I think they make for programmers in the workforce (and which I have experienced directly.)</p><h3>NASA’s Four Assumptions</h3><h4>You will have Access to a Mentor</h4><p>“Who’s your mentor?” is a common ice-breaker with any pair of sweaty NASA programmers avoiding eye contact, and it’s thanks to the agency’s commitment to making sure each programmer can have a mentor. It could be at the level of business, with the OSBP’s Mentor-Protégé program, the internal NEXT project, or with the Pathways Agency Cross-Center Connection (PAXC). Interestingly, you don’t need to go out of your way to get access to one, because we’re all assigned personal mentors from the very beginning. The idea that a programmer can’t have someone capable and with senior experience to overlook their individual progress is close to horrifying for the space program.</p><h4>We Trust Each Other’s Potential</h4><p>There’s a reasonable degree of trust when entering the workforce due to the federal background investigations you’re subjected to. It is also assumed, however, that everyone has something valuable to offer, and we trust the potential of the individual. Show that you’re good and the title becomes almost meaningless. It’s not uncommon for an intern to contribute to high-profile NASA software projects.</p><h4>You’ll Say “I Don’t Understand”</h4><p>This statement is thrown around left-and-right. You will have knowledgeable senior developers asking interns “I don’t understand this part of the codebase. Is that a language feature I don’t know about yet?” or management asking engineers “I’m not sure what the implications of your work today are. Could we go over it a few times until I have a good grasp of it?” These questions are at the core of their daily work routine.</p><h4>We Value Insights into how Computer Systems Operate</h4><p>NASA hungrily searches for insights into how computers work, and they find value in discovering fundamental system limitations to prevent backing into bad software development decisions.</p><p>Consider Gene Amdahl. He was an early computer pioneer with an interesting inquiry: what’s the effectiveness of improving one component of a system? Say that fifty percent of your program’s running time was improved by a factor of four (wow!) and now we want to know how fast the application is. In other words, something took time <strong>T1</strong> to run to completion, and now a part of that something (which takes some fraction <strong>f</strong> from <strong>T1</strong>) is <strong>k </strong>times faster. I’ll spare you any math, although it’s very simple — define the new time <strong>T2</strong> using<strong> T1</strong>, <strong>f</strong>, <strong>k</strong>, and express the relative performance increase as a ratio of <strong>T1 </strong>and <strong>T2</strong>. You’ll end up with the following equation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/184/1*BTCwVOTQUNxflHLLK08-ZA.png" /><figcaption>Fig. 1 — Amdahl’s Law</figcaption></figure><p>Let Amdahl’s Law sink in... Going with the earlier example, to know how fast your application is now simply apply the formula:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*zof7UQmQzhe4-xet5Secng.png" /><figcaption>Fig. 2 — Applying Amdahl’s Law</figcaption></figure><p>This gives <strong>1.6</strong>. Though you took half of your entire program, and optimized it to be four times faster, the overall system is only 1.6x faster. Let’s shock ourselves further. Say you take some other component and the time it takes to run it is now zero (<strong>k</strong> tends to infinity). You get a special case of Amdahl’s Law:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*stNysYOVHfmnqGxkpxADBQ.png" /><figcaption>FIg. 3 — Special Case of Amdahl’s Law</figcaption></figure><p>Assume that component comprises 60% of your program’s running time, and it now takes effectively no time to run it. The theoretical maximum speedup is <strong>2.5</strong>… Amdahl’s Law is telling us that to significantly improve the speed of a system, we’ll have to improve a very large fraction of it. Simple truth, but easily forgotten. The <a href="https://en.wikipedia.org/wiki/Amdahl%27s_law">law</a> is used often in parallel computing to predict speedups using multicore processors, and <a href="http://www.julianbrowne.com/article/viewer/about">Julian Browne</a> reformulates it in that context: “Essentially the law states that whilst a process can be decomposed into steps which may then be run in parallel, the time taken for the <em>whole</em> process will be significantly limited by the steps that remain serialised.” (<a href="http://www.julianbrowne.com/article/viewer/amdahls-law">source</a>)</p><p>With these assumptions in mind, the rest of the article gives a more personal view on what lessons could be gleaned from them.</p><h3>Avoid Unreliable Sources of Knowledge</h3><p>Some of my friends agree the programming profession hasn’t matured yet because it’s at a pre-scientific stage of its existence. I claim many of us are subconsciously subscribing to traditional sources of knowledge that have proven to be unreliable, and as far as I can tell NASA has done well to guard themselves against them:</p><h4>Faith</h4><p>I don’t mean faith in the sense of <em>hope</em>. Faith is also used when we want to believe in something with no good reason to believe in it:</p><p><strong>Lead</strong>: <em>“I like our app’s new features for our customers, and you said you downloaded a library to write them?”</em></p><p><strong>Junior</strong>: <em>“Yeah. It’s worked fine so far.”</em></p><p><strong>Lead</strong>: <em>“Is it open source? Otherwise who is the vendor and how good are they on support? Have you proven it to be robust and tested it across our parameter space?”</em></p><p><strong>Junior</strong>: <em>“No but I’ve been using it for a while and it hasn’t caused any issues.”</em></p><p><strong>Lead: *</strong>PLONK*</p><p>This happens not just for random downloads, but when your code wasn’t working but then it magically did and you decide to call it a day. It may be difficult to notice when someone is relying on faith to decide how good their software is, but if it drags on long enough it will lead to slow and buggy software.</p><h4>Revelation</h4><p>I mean revelation when a figure of authority reveals something as incontrovertibly true, or some fact has been passed down from earlier times, and you believe it to be true because it has been believed to be true. If you tie it with the need for people to identify with some random subset of the programming community, it’s the root cause of heated arguments about which text editor reigns supreme, and how much your use of one language makes you a real programmer.</p><h4>Charisma</h4><p>The conference is packed with an atmosphere of euphoria; excitement for what’s to come as the next framework is announced. A passionate author comes to the stage with a singing voice. The talk and powerpoint slides discuss the newest principles that promise bullet-proof programming practices — of the kind that’ll make you the 10x programmer (for real this time!). With a natural ability to work the crowd, and the official setting in which the author talks, it can be hard to realize we’ve come to believe the author’s claims. And most importantly buying their book.</p><h4>Glow</h4><p>I realize it’s a weird word to use, but when an idea is compelling and exciting enough it just seems to give off a certain “glow.” It is shiny and it must therefore be true.</p><p>We could go on, but moving away from this kind of list is what it means to be scientific about our technological progress.</p><h3>Expand Your Computer Literacy</h3><p>A conversation about the nature of the universe is generally more useful when those talking are scientifically literate. Similarly, a discussion on programming benefits from everyone reaching a certain threshold in computer literacy. Indeed, there are enduring ideas giving life to computer systems, and programmers ought to value them. If we call ourselves professionals, we have a real responsibility to learn the underlying concepts behind computers. It protects us from unreliable sources of knowledge, and it shows us the things we should pay attention to. NASA realized this, and has made sure the organization’s culture allows for everyone’s literacy to skyrocket.</p><h3>Recommendations</h3><p>Did any of this resonate? Are you a programmer looking to improve your computer literacy? If so I have a couple of personal suggestions.</p><h4>Computer Systems: A Programmer’s Perspective</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/1*lsuov5xNUZKaJg5nOrCWWQ.jpeg" /><figcaption>Codenamed CS:APP</figcaption></figure><p><a href="http://csapp.cs.cmu.edu/">Computer System’s: A Programmer’s Perspective</a> was very formative in my career, and if it matters, it is my favorite programming book. The topics covered here are the kind of foundations I think everyone should have. At the very least, a thorough study of Chapters 1–3, the memory hierarchy, and System I/O are eye-opening. If you are working on anything web-related, of course the chapter on Network Programming is relevant.</p><h4>Finding Like-Minded People</h4><p>There’s a small community called <a href="https://handmade.network/">Handmade Network</a>, with an <a href="https://handmade.network/about">incredible team</a> (spoiler: I’m part of the team) as we try to build a place where we can step away from the modern software conversation, and instead talk about the things I have laid out here. We are as vulnerable as other communities to fall into dogma (and we have in the past), but we try to be cognizant of it.</p><p>The community also has interviews with well-known programmers discussing the state of affairs, whether or not they agree with our conclusions. Previous ones are available<a href="https://handmadedev.show/"> here</a>.</p><p><strong>Related Press</strong></p><ul><li><a href="https://www.reddit.com/r/programming/comments/66vdor/handmade_software_manifesto/">Reddit</a> (2017)</li><li><a href="https://killscreen.com/articles/people-trying-save-programming/">KillScreen Op-ed </a>(2016)</li><li><a href="https://news.ycombinator.com/item?id=10095104">Hacker News</a> (2015)</li><li><a href="https://www.reddit.com/r/programming/comments/3hufkw/the_handmade_manifesto/">Reddit</a> (2015)</li><li><a href="https://twitter.com/JAXenter/status/635755784916234241">JAXenter</a> (German) (2015)</li></ul><h3>About the Author</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*Il1lce23H6nn0PMEO1NFmQ.png" /><figcaption>Abner Coimbre,25</figcaption></figure><p>2017 marked three years of work at Kennedy Space Center, writing and maintaining launch control system software. I was awarded Kennedy’s Intern of the Year by 2015 which lead me to NASA’s Pathways program, where I got tasked to research ways to simplify the debugging of (wait for it) flying space robots. The fruit of that work landed me on Kennedy’s 2016 Top 10 <a href="https://blogs.nasa.gov/kennedy/2016/07/26/kickstart-showcase-celebrates-innovators-technologies/">list</a> of Innovators — though just barely!</p><p>Most of my work is unfortunately SBU so it may not be disclosed online. I technically <em>could</em>, but I’ve been told federal prison does not have chocolate wine. So no dice. You can find me over at <a href="https://twitter.com/abnercoimbre">Twitter</a>, <a href="https://twitch.tv/abnercoimbre">Twitch</a>, or <a href="/service/mailto:abner@handmadedev.show">e-mail</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b747957c7f8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/student-voices/a-look-into-nasas-coding-philosophy-b747957c7f8a">A Look into NASA’s Coding Philosophy</a> was originally published in <a href="https://medium.com/student-voices">Student Voices</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>