<?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 Luna Lunapiena on Medium]]></title>
        <description><![CDATA[Stories by Luna Lunapiena on Medium]]></description>
        <link>https://medium.com/@lunacodes?source=rss-76b4c666105a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zjM3ztXxJqTxy-P8Qw37Gg.jpeg</url>
            <title>Stories by Luna Lunapiena on Medium</title>
            <link>https://medium.com/@lunacodes?source=rss-76b4c666105a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:31:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lunacodes/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[Teaching Git Internals Better: Use Your GUI]]></title>
            <link>https://medium.com/making-programming-more-accessible/teaching-git-internals-better-use-your-gui-8eee9e7ce87b?source=rss-76b4c666105a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8eee9e7ce87b</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Luna Lunapiena]]></dc:creator>
            <pubDate>Fri, 17 Jun 2016 17:27:26 GMT</pubDate>
            <atom:updated>2016-06-18T19:06:41.231Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Programming is unnecessarily unfriendly to newer programmers. We can make it better through simple optimizations. This is the </em><a href="https://medium.com/making-programming-more-accessible"><em>Third of a Series</em></a><em> of blog posts where I’ll be exploring that!</em></p><p>A lot of people teach <a href="https://codewords.recurse.com/issues/two/git-from-the-inside-out">Git Internals</a>. It’s a great thing! It helps people understand Git and just how it works, and what all those commands do. However, there’s one frequent problem with their approach: They don’t use their Operating System’s GUI*.</p><blockquote>The problem with this is that <strong>the command line is implicit</strong>. You have to trust that it’s just doing its thing.</blockquote><p>Yes, at some point, every programmer needs to be proficient and comfortable with the command line, but it’s inaccessible and confusing to most newer programmers. This makes your presentation harder to absorb and learn from.</p><p>On the other hand, there’s something we all already know how to do: Double click our folder in our Window System and <em>see</em> what’s actually going on. There’s another thing we all know how to do: Open up a file with a text editor, and see what’s actually inside!</p><p>Can you learn Git Internals from a command line using nano, vim, emacs, etc? Sure. But if you’re new and Git’s already confusing, chances are that command line text editors are not your strength. They usually lack syntax highlighting, and have a steep learning curve. So they’re overwhelming for newer programmers.</p><p>On the other hand, open up the Git Directory in Finder, Explorer, etc, and open up the files in a text editor, and suddenly everything makes sense. This hits a really important aspect of Human-Driven or <a href="https://en.wikipedia.org/wiki/User-centered_design#User-centered_design.2C_needs_and_emotions">User-Centered-Design</a>:</p><blockquote><strong>Combine your new product or information with something your user or audience already knows how to do!</strong> It will feel familiar and welcoming, it will be positive, and it will help them reinforce the new techniques</blockquote><p><strong>When you open those files in a text editor, they’re concrete</strong>. I can see them, and I can figuratively hold and touch them. You’ve shown me they exist!</p><p>Key Principle:</p><blockquote><strong>Explicit is better than Implicit</strong>.</blockquote><p>Carry this with you, and your lessons will go further than you thought possible.</p><blockquote><strong>tl;dr: Show, Don’t Tell. Use your Operating System’s GUI. It’s much easier to understand than the command line. Connect with something your users already know.</strong></blockquote><p>*I’m not talking about Git GUIs — those are their own thing. I’m referring to the Operating System’s GUI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8eee9e7ce87b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/making-programming-more-accessible/teaching-git-internals-better-use-your-gui-8eee9e7ce87b">Teaching Git Internals Better: Use Your GUI</a> was originally published in <a href="https://medium.com/making-programming-more-accessible">Making Programming More Accessible</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Your Open Source Project More Accessible To New And First-Time Contributors]]></title>
            <link>https://medium.com/making-programming-more-accessible/making-your-open-source-project-more-accessible-to-new-and-first-time-contributors-f2e5f14b7f16?source=rss-76b4c666105a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e5f14b7f16</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Luna Lunapiena]]></dc:creator>
            <pubDate>Sat, 02 Apr 2016 20:21:28 GMT</pubDate>
            <atom:updated>2016-06-17T16:36:34.312Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Programming is unnecessarily unfriendly to newer programmers. We can make it better through simple optimizations. This is the</em><a href="https://medium.com/making-programming-more-accessible"><em> Second of a Series</em></a><em> of blog posts where I’ll be exploring that!</em></p><blockquote>One of the most challenging and popular topics amongst newer (and especially self-taught programmers) is contributing to open source.</blockquote><p>The scope of making your first open source contribution can be extremely overwhelming — especially when so many open-source projects don’t make any significant efforts to be inclusive of new or first-time contributors.</p><blockquote>Here’s a list of light-weight suggestions for your Readme.md and Contributing.md files that will make your open-source project accessible to beginners, and build a stronger community around your project*.</blockquote><p><strong>Contributing.md:</strong></p><ol><li><strong>Always have a Contributing.md</strong></li><li><strong>Git &amp; GitHub hyperlinks:</strong> Include Hyperlinks to how to <a href="https://help.github.com/articles/fork-a-repo/">Fork A Repo</a> and<a href="http://rogerdudler.github.io/git-guide/">If You’re New To Git</a>**</li><li><strong>New Contributors Section:</strong> Have a “New Contributor Tasks” section (<a href="https://www.drupal.org/contributor-tasks">Drupal</a> is a great example!!)</li><li><strong>Break Tasks into levels:</strong> (Easy, Intermediate, Advanced). <strong>Tag Easy Issues</strong> as “first-timers” or “first-timers-only”</li><li><strong>Is your “Easy” actually Easy:</strong> Realistically Check that your concept of “Easy” is <em>actually</em> easy for newer programmers. If necessary, find outside, newer programmers and get their feedback***.</li><li><strong>Write </strong><a href="http://medium.com/"><strong>Medium.com</strong></a><strong> articles</strong> like this one from <a href="https://medium.freecodecamp.com/how-to-land-your-first-open-source-contribution-from-your-browser-in-15-minutes-756d9bbf81ad#.ej25auoce">FreeCodeCamp</a></li><li><strong>Make “Squashing Commits” a hyperlink</strong>****</li><li><strong>IRC is a nightmare for newcomers:</strong> The visual interface is highly inaccessible, and it’s very confusing to learn at first. I suggest <a href="http://slack.com/">Slack</a> instead. <a href="https://gitter.im/">Gitter</a> is another option, though its lack of a Search Field, and unintuitive notification options are barriers to accessibility an enjoyable use.</li><li><strong>Link to your Docs:</strong> If you have multiple sets of documentation, link explicitly to the docs you want contributors to use</li><li><strong>Explicitly state dependencies:</strong> If you have dependencies, special libraries or a specific style guide you use, link to them in a “Before Contributing, Read This” Section</li><li><strong>Open Issues? Or Just Pull Requests:</strong> Specify whether you want people to open Issues for a contribution first, or to just make the pull requests. If the answer is mixed, give examples for tasks that would fall under both sections</li><li><strong>Who are the project maintainers anyway:</strong> Explicitly mention who and where contributors can contact project maintainers or mentors they can ask for help. Explicitly mention who the project maintainers are (or link to a page with their names)</li></ol><p><strong>Readme.md:</strong></p><ol><li><strong>Always Have a Readme.md</strong></li><li><strong>Have one for every top-level folder:</strong> For each major folder in your repo, have a Readme.md file. Explicitly describe the purpose of that section (ie, running scripts to build, or this is the module that does translation, etc.) Break down important sections of the code.</li></ol><p>If you have other suggestions to add, or feedback on this list, feel free to leave them in the comments.</p><p><strong>tl;dr: Make your contributing.md and readme.md files explicit. Include links to Git/Github Tutorials. Label issues/bugs as “Easy” or “first-timers” or “first-timers-only”. Check </strong><a href="https://www.drupal.org/contributor-tasks"><strong>Drupal’s guide</strong></a><strong> for reference.</strong></p><p><strong>Footnotes:</strong></p><p>*Note: This list is just as useful for onboarding new employees at your company or organization.</p><p>**I didn’t mention BitBucket or Mercurial, etc. because I haven’t used these, and don’t have the appropriate knowledge for this. The same general guidelines apply.</p><p>***I am happy to provide feedback on this. I have been programming for a year, am self-taught and at an early-intermediate skill level</p><p>****Sorry — I don’t have a good reference link for this.</p><h3>Related:</h3><p><a href="https://medium.com/making-programming-more-accessible/how-to-make-programming-suck-less-accessibility-in-programming-tutorials-guides-documentation-82f1199a4cce#.u7d9lo3fk">Accessibility In Programming Tutorials, Guides &amp; Documentation</a></p><p><em>Originally published at </em><a href="https://lunacodes.wordpress.com/2016/04/02/how-to-make-programming-more-accessible-making-your-open-source-project-more-accessible-to-new-and-first-time-contributors/"><em>lunacodes.wordpress.com </em></a><em>on April 2, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2e5f14b7f16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/making-programming-more-accessible/making-your-open-source-project-more-accessible-to-new-and-first-time-contributors-f2e5f14b7f16">Making Your Open Source Project More Accessible To New And First-Time Contributors</a> was originally published in <a href="https://medium.com/making-programming-more-accessible">Making Programming More Accessible</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility In Programming Tutorials, Guides & Documentation]]></title>
            <link>https://medium.com/making-programming-more-accessible/how-to-make-programming-suck-less-accessibility-in-programming-tutorials-guides-documentation-82f1199a4cce?source=rss-76b4c666105a------2</link>
            <guid isPermaLink="false">https://medium.com/p/82f1199a4cce</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Luna Lunapiena]]></dc:creator>
            <pubDate>Sat, 27 Feb 2016 22:50:55 GMT</pubDate>
            <atom:updated>2016-06-17T16:37:19.157Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Programming is unnecessarily unfriendly to beginners. We can make it better through simple optimizations. This is the </em><a href="https://medium.com/making-programming-more-accessible"><em>First of a Series</em></a><em> of blog posts where I’ll be exploring that!</em></p><p>I’ve been learning programming very steadily for the last year, and there’s something that bothers me a lot: There is an unnecessarily steep learning curve for beginners — especially people who are self-taught! A learning curve makes sense — programming is a very technical, complex &amp; intricate craft. It’s a very big skillset to develop, and it takes a long time. But we’re making it unnecessarily hard for our new people — and on top of that, it’s an accessibility issue*.</p><blockquote><strong>Two common problems</strong> that tend to come up for new developers: <strong><em>many tutorials don’t define their terms; and almost everything seems to have lots of unstated dependencies</em></strong>.</blockquote><p>As a beginner, this means I have to go through a never-ending rabbit hole of googling and looking things up just to try to learn or start this one basic new thing**.</p><blockquote>One of my favorite pieces of programming wisdom is The <a href="https://www.python.org/dev/peps/pep-0020/">Zen of Python</a>. This line in particular: <strong>“Explicit is Better than Implicit”</strong>. There are a couple of easy ways that we can apply the “Explicit is Better than Implicit” guideline.</blockquote><ol><li><strong>Hyperlinks</strong>: It’s so easy to make a Hyperlink (like I just did for <a href="https://www.python.org/dev/peps/pep-0020/">The Zen of Python</a>) — that reduces the amount of hunting your readers have to do.</li><li><strong>Footnotes</strong>: A great example of using Footnotes is this <a href="https://codewords.recurse.com/issues/one/an-introduction-to-functional-programming">Intro to Functional Programming</a>. Every other (functional programming) tutorial I’ve attempted to read just gives me all these strange terms, out of context. Additionally, when I google them, there’s a lack of consensus about what they do &amp; don’t mean. Most of that information is irrelevant to me as a beginner who’s new to functional programming. I would need to be a more experienced developer before I could take advantage of most Functional Programming Tutorials. It’s counter-productive!</li><li><strong>Guide to Contributing for Newcomers</strong>: Contributing to many OSS (Open Source Software) projects is a Nightmare. <a href="http://www.videolan.org/vlc/index.html">VLC</a> does a <a href="https://wiki.videolan.org/Outreachy_May_2016/">Pretty Good Job of this</a>, so does <a href="https://wiki.gnome.org/Newcomers/ChooseProject">Gnome</a>. As a beginner, you’re often looking at code that’s beyond the level you’ve worked at, and you have to go through a very Large Code Base to understand what’s what. Wouldn’t it be much better for all of us if there was some magical document showing people where to go? — It’s like having Street Signs (or GPS)!</li><li><strong>Too Long, Didn’t Read</strong>: tl;dr statements first appeared in the early 2000’s, as a snarky response to overly long posts! They can be a great way to succinctly present the most important points of a tutorial or section. A more elegant approach would be <strong>Concept </strong>(at the Top of a tutorial/section); <strong>Summary </strong>(at the Bottom of a tutorial/section)</li></ol><blockquote>There’s lots of other options to explore too! I don’t have all the answers, but I think with some experimenting, we can make the programming world better for everyone — newcomers especially!!</blockquote><p><strong>tl;dr: Put in some Hyperlinks &amp; Footnotes. Make guides for contributing to Open Source Software. Use tldr statements.</strong></p><p>Explicit Is Better Than Implicit! :)</p><p><strong><em>Footnotes:</em></strong></p><p>*What do I mean by that? A lot of programmers are <a href="http://www.urbandictionary.com/define.php?term=Neuroatypical">neuroatypical</a>. Many of us have learning disabilities or other disorders that make programming uniquely challenging.</p><p>(Tangentially: Some people prefer to use <a href="http://shitborderlinesdo.tumblr.com/post/121319446214/psa-from-the-actual-coiner-of-neurodivergent">neurodivergent</a>. There’s debate about whether they are synonymous or dichotomous — well outside the context of this post!)</p><ul><li>*This is called <a href="http://www.hanselman.com/blog/YakShavingDefinedIllGetThatDoneAsSoonAsIShaveThisYak.aspx">Yak shaving</a>. A definition: “Yak Shaving is what you are doing when you’re doing some stupid, fiddly little task that bears no obvious relationship to what you’re supposed to be working on, but yet a chain of twelve causal relations links what you’re doing to the original meta-task.”</li></ul><p>Cross-Posted from: <a href="https://lunacodes.wordpress.com/2016/02/01/how-to-make-programming-suck-less-accessibility-in-programming-tutorials-guides-documentation/">Luna Codes — Reflections on Coding &amp; IT</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82f1199a4cce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/making-programming-more-accessible/how-to-make-programming-suck-less-accessibility-in-programming-tutorials-guides-documentation-82f1199a4cce">Accessibility In Programming Tutorials, Guides &amp; Documentation</a> was originally published in <a href="https://medium.com/making-programming-more-accessible">Making Programming More Accessible</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>