<?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 Briana Marie on Medium]]></title>
        <description><![CDATA[Stories by Briana Marie on Medium]]></description>
        <link>https://medium.com/@brianamarie132?source=rss-37a977c0f404------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UK7jJ1vfHFuFbPH7.jpeg</url>
            <title>Stories by Briana Marie on Medium</title>
            <link>https://medium.com/@brianamarie132?source=rss-37a977c0f404------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:28:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brianamarie132/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[Things People Learning to Code will Understand: Part 2]]></title>
            <link>https://medium.com/free-code-camp/things-people-learning-to-code-will-understand-part-2-6685cbed8c6?source=rss-37a977c0f404------2</link>
            <guid isPermaLink="false">https://medium.com/p/6685cbed8c6</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[gif]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Briana Marie]]></dc:creator>
            <pubDate>Sun, 07 Feb 2016 07:55:24 GMT</pubDate>
            <atom:updated>2016-06-10T18:15:54.938Z</atom:updated>
            <content:encoded><![CDATA[<p>When you write code you can be proud of:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*51sjsyXx5sdvpSY1xuZQnQ.gif" /></figure><p>When you run your code for the first time, and it works as expected:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*AdMNtj1pZ2aoSZFpNUCnug.gif" /></figure><p>When someone mentions white board algorithms:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*j8_AmX6lbwHXQGnQgxgmkQ.gif" /></figure><p>When you see brilliantly written code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/273/1*YFMGslBNPjScoNIbVMY4FQ.gif" /></figure><p>When you realize you pushed to production too soon, and it’s too late to fix:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*Xcal3Yt7gLgposwM31Xqlw.gif" /></figure><p>When somebody actually spends their time trying to convince you that JavaScript isn’t worth learning:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/216/1*jfQ-Q5gShv429IQutvj7Xg.gif" /></figure><p>When you get to sit down and code after busting through red tape of chores and other work:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*DEF7jJXaS1Gufp2VkgSTDQ.gif" /></figure><p>When you get an error you’ve ever seen before:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*sWgdITAiofQMHm0M_oFjbQ.gif" /></figure><p>When someone says “Oh, I can make websites too, I use (insert template building site here)”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*0mV8pafFISGEzX89grkYsw.gif" /></figure><p>When you FINALLY fix that bug:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*mAk6aEhO5tDXb05ZOL1P1g.gif" /></figure><p>When you FINALLY fix that bug, and then somehow, you didn’t actually:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Sd0aEHTyAXRcz53iH8PmAQ.gif" /></figure><p>Everything you hear about work/life balance in tech:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*eCMd5KdvO-pMg8cMomuWjA.gif" /></figure><p>When — after hours of troubleshooting — all you to do was update a CDN link:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*tgck1Ok2ADxkCCgA3wk4bw.gif" /></figure><p>When everyone on your team disagrees about React vs Angular 2:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*nZ2Yc54SXxtjE4NxbUiz-w.gif" /></figure><p>Why would you <em>not</em> use JSX?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0oD41e9rRNstxSCu4OsCwQ.gif" /></figure><p>When you hear “Women just make better designers than developers”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*CzXthrAp3R0ysS1nzn8P7w.gif" /></figure><p>When you force yourself to read documentation with a tired brain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*kIl0NZsTU6jq-eUBaXRbGA.gif" /></figure><p>When you start talking about all the reasons you are learning to code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*gSBk2D8D72sTfv1THIz-Qw.gif" /></figure><p>When someone says, “Learning to code is easy!”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*On_N7eQ16PmOq_Bg59u1lQ.gif" /></figure><p>When someone says “learning to code is hard, but worth it”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*UF4k6lygsp54aK3nrND-AQ.gif" /></figure><p>Can’t get enough? <a href="https://medium.freecodecamp.com/things-everyone-who-s-learning-to-code-will-understand-d289658ad263">Read part 1.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6685cbed8c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/things-people-learning-to-code-will-understand-part-2-6685cbed8c6">Things People Learning to Code will Understand: Part 2</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things Everyone Who’s Learning to Code Will Understand]]></title>
            <link>https://medium.com/free-code-camp/things-everyone-who-s-learning-to-code-will-understand-d289658ad263?source=rss-37a977c0f404------2</link>
            <guid isPermaLink="false">https://medium.com/p/d289658ad263</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Briana Marie]]></dc:creator>
            <pubDate>Fri, 15 Jan 2016 04:44:57 GMT</pubDate>
            <atom:updated>2016-06-10T18:25:01.085Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been there. You’ve been there. We’ve all been there.</p><p>When you discover a perfect library for something you just spent a ton of time coding from scratch:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*we25kHInIaJmN-vUQlbCwg.gif" /></figure><p>When you’re writing a semi-complex algorithm:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*MINb-ejYCab5RKkhqAplDA.gif" /></figure><p>When your code isn’t working and you don’t know why:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*V2n6hr4cF2soBaCQIM-n3w.gif" /></figure><p>When you’re in the zone and someone tries to talk to you:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Unv-QRH3ObAewf43S-1Vfw.gif" /></figure><p>When you have no idea what other coders are talking about, but want to still seem cool:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/346/1*1bGeVE0kc4hn4-grNFbzxw.gif" /></figure><p>The next day at work after you stayed up way too late working on a project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*rtx08QtAc0a6CauBZ3g19Q.gif" /></figure><p>When someone asks about something you know nothing about:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*4c-A4QnkiN6FuSLmxs0ZsQ.gif" /></figure><p>When someone you don’t know that well asks if you can fix their computer problem:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*3L1vY-h0o7WHuNAgBJDQAw.gif" /></figure><p>Trying to maintain spaghetti code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*lEUbmBlhpuZem-4dLnG85A.gif" /></figure><p>When someone says “You don’t<em> look</em> like a programmer!”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*v4jyaugHQXBSf2O4D66Onw.gif" /></figure><p>When your code is functioning as expected:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*jYPX0QSLeBfYUAu3rLIr9g.gif" /></figure><p>When your code is successfully deployed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*iDzOfFf6buf7V6XgmDnW1A.gif" /></figure><p>When you fulfilled all of the client’s user stories…and then they change the user stories:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*7xQXvaGgRXlm7IejxVo7vA.gif" /></figure><p>When you try out a new IDE:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*lsaJL7KMw6GMQnF0n7MZmQ.gif" /></figure><p>When your CSS works exactly how you want it to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2ulHV9esHFWoZOOi5yU9AQ.gif" /></figure><p>When new Free Code Camp challenges come out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*x-o1lSNhJqSmZx6WCPaS4Q.gif" /></figure><p>When you were sure you’d pushed to your fav VCS before your computer died, but you were wrong:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*4OgB3GoGY0AW3mc2Wbp5jQ.gif" /></figure><p>When you forgot to eat while you were coding for all those hours:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*L7G3kMYgAO70kdt20yFEkw.gif" /></figure><p>When someone says their preferred browser is internet explorer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*f-2m0CZp80PcQwWLaK-2hQ.gif" /></figure><p>When you don’t understand the errors your code is getting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*uPT_A2Oy6KD8cZzy-FK-tQ.gif" /></figure><p>When you’re coding in public and you want the world to understand your frustration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*m_9D2VxZtM47c_PK9b9x1w.gif" /></figure><p>When you look back at your own code from long ago that you’re not super proud of:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*TThDWv4cDLu46m-yUwESTA.gif" /></figure><p>When you know how to solve your team’s problem:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*KFzrVRw4atiMWT3SGlvsrQ.gif" /></figure><p>When you’re trying to use business lingo to make a meeting go faster:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wxGfGUNZj78wlJWcR3FPcA.gif" /></figure><p>When you aren’t sure how, but you know that last bit of code just broke everything. EVERYTHING.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Vq2rMVz1nLIMqlyFu7LNyw.gif" /></figure><p>When people ask how you like ES6:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*u6hPRc_sdanPkQjFTGHgFQ.gif" /></figure><p>When you spend hours fixing something that turned out to be super simple:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*4uRquOvuMLF7m9zBj5lEeA.gif" /></figure><p>When you realize that you’ll never run out of problems to solve with code…and you love it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*7iVruK393XI2ybnY1sRO1g.gif" /></figure><p>Want more? <a href="https://medium.freecodecamp.com/things-people-learning-to-code-will-understand-part-2-6685cbed8c6#.5dxeynij8">Read part 2.</a></p><p>Want to talk with some people going through the same thing? Join <a href="http://www.freecodecamp.com/">FreeCodeCamp.com</a> and head over to their <a href="https://gitter.im/FreeCodeCamp/FreeCodeCamp">chat room</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d289658ad263" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/things-everyone-who-s-learning-to-code-will-understand-d289658ad263">Things Everyone Who’s Learning to Code Will Understand</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</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 Contribute to Free Code Camp’s Video Challenges]]></title>
            <link>https://medium.com/free-code-camp/let-s-go-for-a-hike-here-s-your-map-4301df6e3801?source=rss-37a977c0f404------2</link>
            <guid isPermaLink="false">https://medium.com/p/4301df6e3801</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Briana Marie]]></dc:creator>
            <pubDate>Tue, 12 Jan 2016 08:30:58 GMT</pubDate>
            <atom:updated>2016-06-10T18:27:08.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LM9MyL3PP0lqm2-zMR2-LQ.jpeg" /></figure><p>Free Code Camp is launching short instructional videos, called Video Challenges, aimed at teaching useful software engineering concepts to beginners. Each video is about 2 minutes long, and is followed by 2 or 3 true/false questions. You can learn from them on a computer in a library or your phone on the subway.</p><p>For examples, check out <a href="https://www.youtube.com/playlist?list=PLWKjhJtqVAbmfoj2Th9fvxhHIeqFO7wOy">this YouTube playlist</a>. These videos will be live on <a href="http://www.freecodecamp.com/">Free Code Camp</a> in the near future (but you could sneak a peek on our <a href="http://beta.freecodecamp.com/hikes">beta</a>).</p><p>Unlike Free Code Camp’s hands-on coding curriculum, Video Challenges emphasize theory over practice. Video Challenges explain concepts in easy-to-understand terms. They give you just enough of an understanding that you can recognize these concepts when you encounter them in the real world. And when you do, you’ll have the theoretical understanding you need to ask informed questions and google accordingly.</p><p>Like the rest of Free Code Camp’s open source curriculum, Video Challenges are created by our community. I started scripting and recording videos a few months ago, and now other campers are joining me. And you should consider contributing, too!</p><h3>Video Challenges are a form of teaching. And teaching is hard. But these pointers will help.</h3><p>Structuring, scripting, and recording a video can seem daunting, but it’s rewarding work. Whether you have experience as a teacher or not, you probably already know that it’s not just about the facts on the page.</p><p>Some things matter a lot when you’re teaching. Some of those thing have to do with your content, but most of them don’t.</p><h4>The obvious — what you’re saying has to be accurate and contextually appropriate.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*WrN42jrij_sRZGNDluTRkw.gif" /></figure><p>Okay, but what else?</p><h4>Don’t make a Video Challenge unless you’re sure the content will make sense.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*EsmE-cacVTO7GzeARvTIzg.gif" /></figure><p>There are hundreds of topics that are important to know as a software engineer.</p><p>The reality is, some topics are simply too big to fit into the shoebox that is a two-minute video. Maybe a written tutorial would be a better way to acquaint someone with that particular subject.</p><p>The key distinction of a Video Challenge is that you should be able to watch it and store that high-level knowledge away fully — without needing practice.</p><h4>Hack user energy with lighting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*M9Bw_We98e04-7aBu17xNA.gif" /></figure><p>Lighting. Lighting is really important! It should be bright in the room, with your face and whiteboard/blackboard in full view.</p><p>Studies show that blue tones alert us, and orange tones make us feel tired and relaxed. Use this trick to your advantage to keep your viewers energetic.</p><h4>Write stuff on the board before you film</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*D1N8HW4bw6ReSJBwN_WMuw.gif" /></figure><p>Have examples, the title, or other text written on the board at the beginning of the video.</p><p>These short videos need to be jam-packed with information. Writing a simple explanation, definition, or example that you can refer to later will solidify knowledge and give the user an anchor.</p><h4>Stand up with good posture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*yZMMde_qF_UnT6Mj-wAAjQ.gif" /></figure><p>Stand up, don’t sit. Your posture should exude energy.</p><h4>Dress to impress</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*jbMYdYA2wNFy3_FW9IkayA.gif" /></figure><p>Dress professionally, like you’re going to be presenting in front of thousands of people of diverse cultural backgrounds. Because you are.</p><h4>Entertain your audience by moving your face and arms</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6RSTI3hryyJLyzT6yr-0Sw.gif" /></figure><p>Be visually expressive. If you mute a video, there should still be lots of nonverbal cues. Your face and arms should be moving and expressing contrast. Let your personality show through.</p><p>The more contrast you can pull off, the more entertaining your video is likely to be. This will prevent viewers from getting bored and spacing out.</p><p>Contrast also helps gives cues about the content. There is a lot of context to be shown nonverbally, and when the videos are so short, we need to take advantage of that.</p><h4>Sound less like a robot and more like a stage actor</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*hzA6XbDznCNb74SvM1NamA.gif" /></figure><p>Vocal expressions matter.</p><p>Just as nonverbal cues are important for expressing context and engaging the user, tone, pitch, volume, and speed of voice are also important. Speak loudly and clearly, and not too quickly.</p><p>Move your voice around up and down when it’s appropriate. Most humans normally do this, but in videos like this, it’s imperative to exaggerate.</p><p>Changes in vocal tone catch people’s attention, and we want their attention when we’re trying to teach them something!</p><h4>If you can’t say it in 7 words or less, find a better way to say it.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*c4pSX94gciBWT08ijVg2GQ.gif" /></figure><p>One of my most influential education professors, Dr. Charles Robinson, insists teachers deliver important content in “7 words or less”. If you can’t say it in 7 words or less, you aren’t saying it concisely enough.</p><p>If you need a script to do this, that’s totally fine. Personally, I give myself two to four short points to cover in the video, because that’s all I can really keep track of during filming.</p><p>Whatever your process, the outcome needs to be the same — get out the content in as few words as possible. Sound scripted, even if you’re not.</p><h4>Tell them what you want to tell them. Then tell them again. Then tell them what you wanted to tell them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*UlBjscGm6qeLMk0tuhpH6w.gif" /></figure><p>Bookend every video with the “it”.</p><p>Tell the user at the beginning what they’re going to know by the end. Then in the middle, tell them that thing in as few words as possible. At the end, remind them what they just learned.</p><p>It may sound simple, but breaking complex concepts down into something a beginner can grasp is something even experienced teachers struggle with from time to time.</p><h4>Try not to make cuts in the filming.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*9vBUihNzU5K_8zrunc7rUw.gif" /></figure><p>Ideally in editing, there are no cuts. Too many cuts will make the video seem less like one lesson and more like an edited compilation. If you have to make some, do so between main points and at natural breaks.</p><p>Try to make the visual transition as smooth and seamless as possible so users don’t even notice.</p><h4>Record (and rerecord) to perfection.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*DXgOv01JEKwL_N7oWiqKMw.gif" /></figure><p>When the outcome is a few minute video, it needs to be the highest quality content you can produce.</p><p>Watch out for any repetitive or unnecessary motions or sounds you may unconsciously be making. Keep an eye out as you review your videos. By the time you notice, ten students in a real classroom already would have.</p><p>For each two minute video you see, I probably recorded about twenty minutes of material. That’s me practicing saying the “it” of the video as concisely as possible.</p><p>I probably rambled a bunch, got facts just entirely wrong, my dog barked or cat meowed in the background, the AC kicked on too loud, there was a siren pass by, heck — who knows, maybe I burped or got the hiccups.</p><p>The point is, you need to keep rolling until you get it right.</p><h3>Let’s get started!</h3><p>Think you want to do this? Check out the current progress and help contribute to new Video Challenges on <a href="https://github.com/FreeCodeCamp/hikes">GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4301df6e3801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/let-s-go-for-a-hike-here-s-your-map-4301df6e3801">How to Contribute to Free Code Camp’s Video Challenges</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>