<?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[The StudentRND Blog (Archived) - Medium]]></title>
        <description><![CDATA[Increasing Computer Science enrollment nationwide. - Medium]]></description>
        <link>https://medium.com/the-studentrnd-blog?source=rss----f2bac48f2a58---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The StudentRND Blog (Archived) - Medium</title>
            <link>https://medium.com/the-studentrnd-blog?source=rss----f2bac48f2a58---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:10:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-studentrnd-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Electronics Lab at CodeDay]]></title>
            <link>https://medium.com/the-studentrnd-blog/electronics-lab-at-codeday-879e7244cb6d?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/879e7244cb6d</guid>
            <category><![CDATA[hardware]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Fri, 08 Feb 2019 22:08:21 GMT</pubDate>
            <atom:updated>2019-02-15T22:16:51.289Z</atom:updated>
            <content:encoded><![CDATA[<p>SRND and Digikey are excited to present a workshop to help you learn the basics of designing your own circuits at CodeDay! Here are some of the basics to try out in the workshop.</p><p><strong>This lab is going to go through making your first circuit on a breadboard, which will light up an LED.</strong></p><p>(If you’re more experienced, try overcomplicating things by using an MSP430 microcontroller. This is a cool chip, but a little more complicated than an Arduino. Check out our note at the very end of the article for a few tips.)</p><h3>Electronics Basics</h3><h4>Why It’s Called a Circuit</h4><p>We call things circuits because, to work, they need to be a closed loop. You can imagine the electricity running around in circles. (This is not very technically accurate, but it’s good enough for our purpose.)</p><p>So, this will not work, because it’s nota closed loop:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*mJN_tWAWc_teOaWhZOvRDA.png" /></figure><p>But if we close the loop, our LED will light up!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*jTXhfRZUU3ZW0LKchyN84g.png" /></figure><p>Some components need to be connected in certain ways to work properly. For example, you’ll notice in the diagram above, the LED is an arrow. It needs to “point” from the positive side of the battery, to the negative side.</p><h4>Making a Schematic</h4><p>The diagram we drew above is called a “schematic.” If we imagine a your IRL circuit is like a compiled program, a schematic is the sourcecode. (Not the perfect analogy but you get the idea.)</p><p>Like source code, schematics need to be converted into the real-world. Each symbol on a schematic correlates with a real-world part. For example, this is an LED in schematic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/187/1*YoHeH2h6N0E6jsxdAP-w7A.png" /></figure><p>And these are the LEDs you have in your kit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/0*5CDFWkm9IC-nb2Re" /></figure><p>Remember how the LED symbol had an arrow that “points” in a specific direction? Well, the real-life LED has one leg that’s longer than the other!</p><p>(Is it the longer or shorter one that gets connected to positive? Even people with real-world electrical experience forget. Try Googling “LED long lead positive/negative”)</p><p>Also like code, your schematic might have a bug. In this case, we need to add a “resistor.” (Want to know why? Read “The math you need to know*” below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/1*PTSzfh3JgSChrQVT9gvNpw.png" /></figure><p>Want to make your own schematic? An easy place to start is <a href="https://easyeda.com/editor">https://easyeda.com/editor</a> (There are more complicated bits of software that can do all the same things and more, like KiCad and DipTrace, but they’re hard to get the hang of. If you enjoy this, consider giving them a try.)</p><h4>Putting It All Together: PCBs and Breadboards</h4><p>When you think of a circuit, you probably think of what we’d call a “Printed Circuit Board,” or PCB. The problem with PCBs is that they’re hard to make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*KXyzGQQDHQ4BDDxdvL-7QA.jpeg" /></figure><p>When you want to know if your code works, you just click “build.”</p><p>To test a circuit with a PCB, on the other hand, you can order it and wait 1–3 weeks, or DIY it with printed transparencies, UV light, copper-clad fiberglass, ferric chloride acid, and more. Not ideal for debugging.</p><p>To make things easier, electrical engineers have “breadboards”, which are the sandbox videogames of electronics. On each side of a breadboard, each row is electrically connected, as are the columns on the side:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*GvOsnamgHpZ-FxUigj0m4A.jpeg" /><figcaption>The sharpie lines represent sections which are electrically connected on the breadboard.</figcaption></figure><p>(Wait, why are the columns c-c-c-combo breakers? Well, almost every component of a circuit is going to need a connection to power or ground —power and ground columns make that simple.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DJNw3cN9SBlNG7jRcgMNhw.jpeg" /></figure><p>So what happens when you want to connect one component to another? Sometimes, if the component has long <em>leads</em> (legs), you can directly connect one lead onto another row. But most of the time, you’ll end out using <em>jumpers</em> (pre-made wires with pins on the end).</p><p>How do we get power in? We could use a battery, but for this workshop we provided you with a component that fits into your breadboard and provides power! Just press it into the two columns, and connect it to a computer or phone charger over USB:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*jeqOJhkowA5zsB5VKeQ_Nw.png" /></figure><p>Two notes: make sure you connect it as shown above, so the pins labeled “+” on the power supply slot into the columns labeled red, and not the other way around. Also, this power supply puts out both 5V (on the left) and 3.3V (on the right). We recommend you use the 3.3V option.</p><p>Ok, let’s convert our earlier schematic to a breadboard. Using what we learned above, see if you can connect the LED and resistor to the + and - columns in the correct way. If you’ve got it right, it should turn on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*nuHbLFRKe0gPNAx8P9CJJg.gif" /></figure><p>If it’s not turning on, make sure the power supply is powered on,“+” on the power supply is connected to the “+” column, and everything is pressed in firmly. If you’re still having problems, try reversing the LED.</p><p>You can also ask for help on chat.srnd.org!</p><h4>The Only Math You Need to Know*</h4><p><em>(*unless you get really into electronics)</em></p><p>Want to know why we need a resistor?</p><p>You can do a lot of basic electronics knowing only one equation, called “Ohm’s Law”: <em>Voltage = Current × Resistance</em></p><p>You can move the terms around with algebra:</p><ul><li>Voltage = Current × Resistance</li><li>Current = Voltage ÷ Resistance</li><li>Resistance = Voltage ÷ Current</li></ul><p>We can use Ohm’s Law to figure out why we added the resistor to the LED circuit earlier. LEDs run at about 2.2V, and if we didn’t add the resistor, its resistance would be close to zero, so its current draw would be:</p><p>Current = Voltage ÷ Resistance<br>Current = 2.2V ÷ (almost zero)</p><p>As “almost zero” gets smaller, 2 ÷ (almost zero) gets <em>really really</em> big. In theory, infinitely big! In practice, the LED will just burn itself out.</p><h3>Advanced students: using the MSP430</h3><p>This section isn’t as detailed, because we have no idea what you’ll want to do with your MSP430. Instead, here are a few getting-started tips. More questions? Ask in ~Helpdesk on <a href="https://chat.srnd.org/">https://chat.srnd.org</a> :)</p><ul><li>You’ll need to use the TI Launchpad to program your MSP430. We provided each city with a single one, so when it comes time to write the code to the chip you may need to share.</li><li>You can write code using the free software here: <a href="http://www.ti.com/microcontrollers/msp430-ultra-low-power-mcus/tools-software.html">http://www.ti.com/microcontrollers/msp430-ultra-low-power-mcus/tools-software.html</a></li><li>Slot the chip in the breadboard so it straddles the gap in the middle — each side will then be electrically isolated. One side of the chip has a little half-moon dimple depression. That side should go “up”. We’ll assume that orientation for the following.</li><li>The top-left pin needs to be connected to 3.3V.</li><li>The top-right pin needs to be connected to ground.</li><li>The fifth pin from the top on the right side needs to be connected <em>through a resistor</em> to 3.3V (“pulled up”) each time you reconnect power, or the chip won’t start up.</li><li>There’s no code on most of the MSPs by default, but the one that comes with the launchpad comes with code which blinks an LED connected to the second pin from the bottom on the right-hand side.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*0jNUMrjJ1RcEsmHuRIy7Ig.png" /><figcaption>Sample connections for the demo program, preloaded on the MSP430 which comes plugged into the Launchpad.</figcaption></figure><p>Again: more questions? There are lots of technical details online, especially in the “MSP430 Datasheet” (google it). Or ask us in ~Helpdesk on chat.srnd.org.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=879e7244cb6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/electronics-lab-at-codeday-879e7244cb6d">Electronics Lab at CodeDay</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Ready for CodeCup]]></title>
            <link>https://medium.com/the-studentrnd-blog/getting-ready-for-codecup-f4bb32a080a3?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/f4bb32a080a3</guid>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Thu, 15 Feb 2018 23:28:36 GMT</pubDate>
            <atom:updated>2018-02-15T23:28:35.880Z</atom:updated>
            <content:encoded><![CDATA[<p>Not sure what to expect from 7–8PT during CodeDay?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*T09kk6wvG8hQWaJryRx8vA.png" /><figcaption>(Staff members: Go to Day Of and then CodeCup Login on Clear to get this info)</figcaption></figure><p>To get started, you’ll need to go to <a href="https://codecup.sh/">https://codecup.sh/</a> and log-in with your city’s username and password.</p><p>Yes, that’s right: there’s one login for everyone in your city. Staff will tell you your city’s login shortly before the start.</p><p>Once you’re logged in, you’ll see a map, with individual states/provinces highlighted. (You’ll also see some tool windows around the edges: you might find it helpful to expand the leaderboard, announcements, and clock to start.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I3GyWUikVuygDZ27zZJHEw.png" /><figcaption>Once your city starts capturing things, you’ll see states get marked with a yellow triangle.</figcaption></figure><p>Each state has a challenge, and multiple teams can capture the same state. (No freebies: you’ll even need to capture your own state!) To see challenge details, just hover over the state. It’s a good idea to briefly check out the options before you commit to one.</p><p>To see the full challenge, just click on the state. Once you think you know the answer, type it in the box and hit submit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*8YRnLIM1dOP2CF6uZkkGqA.png" /></figure><h3>Questions</h3><p>Questions range from total beginner to very experienced, so everyone will have something to work on. Here are some general types of questions:</p><ul><li>Quiz</li><li>Coding</li><li>Non-Techincal</li><li>Website Security</li><li>Reverse Engineering</li><li>Cryptography</li><li>Stenography</li><li>Forensics</li></ul><p><a href="https://gist.github.com/tylermenezes/30ae1f5f218c31334bec2bbce0539b02">Here are some examples from past CodeCups</a></p><h3>Strategy</h3><h4>Challenges for all Skill Levels</h4><p>Solving a challenge earns your city points. The harder the challenge, the more points you win.</p><p>In general, 1–25 points are beginner, 26–50 are intermediate, and 51+ are advanced. (There are some exceptions for simple tasks that take a while.)</p><p>If you’re the first city to solve a challenge, you often earn bonus points.</p><p><em>To maximize the number of bonus points you earn, more experienced programmers should start on difficult challenges, and let less experienced programmers do the easier ones.</em></p><h4>Work Together</h4><p>CodeCup is city-vs-city, which means you‘re working with everyone else at your event.</p><ul><li>Get everyone participating in CodeCup together so you can talk.</li><li>Before you start working on a new problem, ask if anyone else is already working on it. If so, ask what’s already been done so you don’t duplicate work.</li><li>If you solve a difficult problem, announce it to the group. Others might have tabbed out of the CodeCup site, and not notice it’s done.</li></ul><h4>Have Fun!</h4><p>Like everything else at CodeDay, it doesn’t really matter if you win or lose at CodeCup.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4bb32a080a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/getting-ready-for-codecup-f4bb32a080a3">Getting Ready for CodeCup</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to Node.js: Making a Telegram Bot]]></title>
            <link>https://medium.com/the-studentrnd-blog/intro-to-node-js-making-a-telegram-bot-964b8cfe1129?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/964b8cfe1129</guid>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[codeday]]></category>
            <dc:creator><![CDATA[TJ Horner]]></dc:creator>
            <pubDate>Wed, 15 Mar 2017 01:33:40 GMT</pubDate>
            <atom:updated>2017-03-15T01:33:40.225Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<p>In this workshop, we will create a simple Telegram bot that tells us how long until CodeDay ends using Node.js, the Telegram API, and the Clear API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*CRRHRuWtdYGl-UdSJkrvQQ.jpeg" /><figcaption>The almighty Botfather.</figcaption></figure><p><em>This post is intended to serve as a guide for my </em><a href="https://codeday.org/"><em>CodeDay</em></a><em> workshop, but if you’d like to use this to make your own Telegram bot with Node.js, go right ahead :)</em></p><h3>Part I: Chat bot</h3><p>Telegram has two types of bots: chat bots and inline bots. Chat bots use commands (such as <strong>/start</strong>, <strong>/help</strong>, etc.) to interact with users. Inline bots can instead be called from anywhere and help users find and send content from your bot to any chat they wish. This section covers chat bots.</p><h4>Step 0.1: Acquire Node.js and npm</h4><p>You should have already done this before the event, but it’s a pretty small download if you still need to get it. Here are links to the version of Node.js we will be using for this workshop:</p><ul><li><strong>Windows</strong>: <a href="https://nodejs.org/dist/v6.6.0/node-v6.6.0-x64.msi">https://nodejs.org/dist/v6.6.0/node-v6.6.0-x64.msi</a></li><li><strong>macOS</strong>: <a href="https://nodejs.org/dist/v6.6.0/node-v6.6.0.pkg">https://nodejs.org/dist/v6.6.0/node-v6.6.0.pkg</a></li><li><strong>Linux</strong>: You should already know how to get Node.js.</li></ul><h4>Step 0.2: Get Telegram</h4><p>Since we’re making a Telegram bot, you’ll need a Telegram account. Head over to <a href="https://telegram.org/dl">telegram.org/dl</a> and create your account.</p><h4>Step 1: Set up your project directory</h4><p>Now that we have Node.js and npm installed and our Telegram account is ready, we can start with the project. Open up your preferred terminal and run these commands:</p><pre>mkdir codeday-telegram-bot<br>cd codeday-telegram-bot</pre><p>Now we have a directory for our Telegram bot, but we need a package.json, this tells npm information about our project. To do this, (in the same terminal window) we need to run this:</p><pre>npm init</pre><p>This command will tell npm to initialize a pre-made package.json in our project directory. Just hit enter at all of the prompts, we can worry about those later.</p><h4>Step 2: Install necessary packages</h4><p>For this project, we will only need one npm package. An npm package is essentially a piece of code (“package”) in the npm registry that we can download with a simple command, `npm install`.</p><p>We’re going to use a package called `node-telegram-bot-api`, we can install it like so:</p><pre>npm install --save node-telegram-bot-api</pre><p>The ` — save` part signals npm to save this package to our package.json so it is easily installed later, along with any other dependencies that our package may need.</p><h4>Step 3: Get a Telegram bot token</h4><p>Using Telegram, contact <a href="https://telegram.me/botfather">@botfather</a> and use the /newbot command to create a new bot. Name it whatever you’d like with any username, it doesn’t matter.</p><h4>Step 4: Write some code!</h4><p>Now that we have our bot token, we can use it to interface with the Telegram Bot API.</p><p>Create an index.js file in your project directory, then open it in your favorite text editor. Here’s some simple “Hello world” boilerplate code I’ve written to assist with this step:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/80de0f445b5ba945ccc09e6af6c9baaf/href">https://medium.com/media/80de0f445b5ba945ccc09e6af6c9baaf/href</a></iframe><p>Essentially, what this code does is include the library we downloaded from npm earlier, then instantiated a new `TelegramBot` object with our token and told it to poll for updates from Telegram. Then it will listen for the “text” event (which, in this library, is a simple text message) and then send a message to the chat the original message was saved saying “Hello world”.</p><p>Now, run the index.js file with this command:</p><pre>node index</pre><p>Send your bot a message. It should reply with “Hello world”. If it does, awesome! If it doesn’t, ask me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/284/1*tYyl6aP0zMspA60G3mp25A.png" /><figcaption>It works!</figcaption></figure><h4>Step 5: Implement a simple command</h4><p>In its current state, this bot is not very useful. Let’s make it useful, how about by adding a <strong>/codeday</strong> command that tells us when CodeDay ends! We will be utilizing two more libraries here, <strong>codeday-clear</strong> and <strong>moment</strong>. <strong>codeday-clear</strong> is the official Node.js library for interacting with the Clear API. Clear is our internal CodeDay management system and has a very nice API. We will be using this API to get the ending date of CodeDay and then use <strong>moment</strong> to convert it into a human-readable format.</p><p>To install these libraries:</p><pre>npm install --save codeday-clear moment</pre><p>In our code, we then need to include these two libraries and instantiate a `Clear` instance. Since the Clear API requires access to Clear and an API token/secret pair, I have created a sample app with limited permissions for the purpose of this workshop:</p><ul><li><strong>Token</strong>: 1YZiGaj3baaLU8IKVsASRIWaNF2oJNg0</li><li><strong>Secret</strong>: 1COMnWyGnGBsNqkhaZ6WMBWB9UWZw6QZ</li></ul><p>Here’s what it should look like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/216f9202886724cf679d0ae9d1a8a611/href">https://medium.com/media/216f9202886724cf679d0ae9d1a8a611/href</a></iframe><p>This code should go right after where we declare the `telegram` instance (this should be line 3 if you are following along). Now that we have our Clear and moment instances declared, we can use them in a simple command. Let’s replace the code inside of the “text” event with something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6dfb6c6795a472e9e839acf8931baad2/href">https://medium.com/media/6dfb6c6795a472e9e839acf8931baad2/href</a></iframe><p>Here’s a breakdown of what’s happening here:</p><ul><li>We check with the JavaScript `indexOf` function if the message starts with <strong>/codeday</strong></li><li>If it does, we tell the Clear library to grab the event with ID <strong>oo4QIuKQQTYA</strong> (that’s San Diego Fall 2016’s ID)</li><li>We use a callback function once it gets the event, and then parse the `ends_at` date with <strong>moment</strong>. (We multiply it by 1000 to convert it to milliseconds (which moment understands), since Clear sends this date in a UNIX timestamp format.)</li><li>We then use <strong>moment</strong>’s `fromNow` function to get the relative time (e.g. “in 10 hours”) of the `endsAt` date and then send that all through the Telegram API.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*o5g4U7bYKUPAq6I6D8Gj_w.png" /><figcaption>Since I wrote this post two months before CodeDay, this happened…</figcaption></figure><h4>Step 6: Getting fancy with Markdown</h4><p>Telegram supports messages sent with <strong>Markdown</strong>, a simple way to format text. Let’s make the end date bold as an example.</p><p>In Telegram’s version of Markdown, we will surround the text we want to bold with asterisks, so the raw message we send to Telegram should look something like this:</p><blockquote>CodeDay ends *in 2 months*!</blockquote><p>To implement this, it’s rather simple; all we need to do is surround the end date in asterisks and then pass the `parse_mode` parameter to the Telegram API and set it to “Markdown”, this will tell the Telegram API that we want the text to render as Markdown.</p><p>The modified code could look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c9114ba69b68d1eb1dc4eee71c5c7f5/href">https://medium.com/media/3c9114ba69b68d1eb1dc4eee71c5c7f5/href</a></iframe><p>Now when we run the <strong>/codeday</strong> command, it will look like this instead:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*LT5DM_fkl1_vw6TuVLaZEw.png" /><figcaption>Fancy bold text!</figcaption></figure><p>Telegram also supports italics, inline code, code blocks, and inline URLs along with the bold option we just used.</p><h3>Part II: Inline bot</h3><p>This section will cover how to turn this bot into an inline bot, which can be called from anywhere and help users find and send content from your bot.</p><h4>Step 0: Enable inline mode in Botfather</h4><p>Bots don’t have inline mode enabled by default, so you need to send the <strong>/setinline</strong> command to Botfather to enable it. You can use anything as your placeholder text, but I used “Search CodeDays…” as mine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*PcwCVjKJ-TCUkeJHXk6paQ.png" /><figcaption>Here’s what your conversation with Botfather should look like.</figcaption></figure><p>After you enable inline mode, you may need to restart whatever Telegram client you’re using for the changes to take effect (since they’re cached). Once you restart, type your bot’s username then a space. If you see the placeholder text you set, you’re ready for the next step.</p><h4>Step 1: Implement inline queries</h4><p>Now we need to tell our script how to react to inline queries. To do this, here’s some boilerplate “Hello world” code I’ve written to simplify the process:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8cc3a9c56ec40b8430f71a1efd6e8cae/href">https://medium.com/media/8cc3a9c56ec40b8430f71a1efd6e8cae/href</a></iframe><p>Here’s how it works:</p><ul><li>Upon an inline query…</li><li>Respond with an array with 1 “article” result…</li><li>Which has a title of “Hello world” and sends the message “Hello, world! This was sent from my super cool inline bot.”</li></ul><h4>Step 2: Implement Clear API</h4><p>Now let’s actually make it show the CodeDay events. We need to iterate over every event and turn them into an object the Telegram API understands, so you could have something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/264e6fb21815a82f1afc5943c0df55e2/href">https://medium.com/media/264e6fb21815a82f1afc5943c0df55e2/href</a></iframe><p>So what we’re doing here is…</p><ul><li>Upon an inline query…</li><li>Ask Clear for a list of events…</li><li>Then turn those events into objects the Telegram API can understand…</li><li>And make the message content the venue the CodeDay is at.</li></ul><h3>Part III: Conclusion</h3><p>Now that you know the basics of bot creation, I encourage you to play around with Telegram’s bot API and make something awesome with it! You can make games, tools, calculators(?)… anything, really. Go check out the docs and see what you can build! <a href="https://core.telegram.org/bots/api">https://core.telegram.org/bots/api</a></p><p><strong>And remember, have fun!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=964b8cfe1129" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/intro-to-node-js-making-a-telegram-bot-964b8cfe1129">Intro to Node.js: Making a Telegram Bot</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CodeDay Philly Winter 2016 Wrap-Up]]></title>
            <link>https://medium.com/the-studentrnd-blog/codeday-philly-winter-2016-wrap-up-9c28c9ff1fb6?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c28c9ff1fb6</guid>
            <category><![CDATA[philadelphia]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[codeday]]></category>
            <dc:creator><![CDATA[StudentRND]]></dc:creator>
            <pubDate>Tue, 14 Mar 2017 23:38:59 GMT</pubDate>
            <atom:updated>2016-02-29T21:41:24.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xD5xhywXFZ11urP2PEGFDA.gif" /><figcaption>The Philadelphia Skyline at sunset, as seen from CodeDay Philly. Raw video here: <a href="https://youtu.be/9dichqQU-tc">https://youtu.be/9dichqQU-tc</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tq3j92x4KU8Xb22QsJpt8Q.png" /></figure><h4>It’s always amazing to see what students can create when they come together and share their passion for technology. This past CodeDay Philly was no exception.</h4><p><strong>42 middle school, high school, and college students from across the Philadelphia area came together to build cool apps and games.</strong></p><p>A special thanks to our media partners <a href="http://technical.ly/philly/">Technical.ly Philly</a>, <a href="https://phillycam.org/">PhillyCAM</a>, and <a href="http://codeforphilly.org/">Code for Philly</a> for helping us reach out to the community, Chris Cook from <a href="http://tonicdesign.com/">Tonic Design</a> for being an such an amazing host, our wonderful volunteers judges, mentors, and most importantly our amazing partners that make this event possible: <a href="http://splunk.com/">Splunk</a>, <a href="http://www.lexisnexis.com/risk/">LexisNexis Risk Solutions</a>, <a href="http://www.kinesis-ergo.com/">Kinesis Keyboards</a>, <a href="http://leangap.org/">Leangap</a>, <a href="http://makeschool.com/">Make School</a>, <a href="http://techgirlz.org/">TechGirlz</a>, <a href="http://girlswhocode.com/">Girls Who Code</a>, and <a href="http://codeforphilly.org/">Code for Philly</a>.</p><p>We hope you enjoyed CodeDay Philly as much we’ve spent the time and effort into organizing it. Below is a recap written by our lead organizer Victor. 😀</p><p>- Your fellow organizers, <br><em> </em><a href="http://twitter.com/lablayers"><em>Victor Lourng</em></a><em>, </em><a href="http://twitter.com/varninja"><em>Kyle Permuy</em></a><em>, </em><a href="http://twitter.com/bogdanvitoc"><em>Bogdan Vitoc</em></a><em>, </em><a href="http://twitter.com/cydrobolt"><em>Chaoyi Zha</em></a><em>, and Eric Wang</em></p><p><a href="https://technical.ly/philly/2016/02/12/student-programmers-will-codeday-philadelphia-weekend/">Student programmers will be at CodeDay Philadelphia this weekend - Technical.ly Philly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLqFrZ5bGq7hrXHMsKne1Q.png" /></figure><p>This year, CodeDay Philly was hosted at Tonic Design in Old City. Our attendees were in for a pleasant surprise, because every desk in the office was hooked up to a fancy Thunderbolt Display! 💻</p><p>We started the event with a classic rock-paper-scissors tournament as a fun way for our attendees to get to know each other. Congrats to Tyler, Josiah, and Dan who made it to the final rounds! 🐚📄✂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EyXO-P3Fd_OPsTL-yxUSZg.jpeg" /></figure><p>As CodeDay kicked off, everyone came together for a group brainstorming session. Everyone had a chance to pitch a few ideas for what they want to created, here were some of the more notable ideas that never got built:</p><ul><li>CodeDay simulator where you write a CodeDay simulator <em>recursively! </em>👍</li><li>Cat/Pepe/Dank meme generator 🐸</li><li>Panera bread button for smartwatches 🍞</li><li>Realtime bus app 🚌</li><li>Pest infestation reporting app 🐞</li><li>Game that blasts Donald Trump to the moon 🌝</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*F-u88kIu1-QtRdu2MmAcHA.jpeg" /></figure><p>Attendees then proceeded to teams around the ideas that thought were the coolest, and these teams spent the next 24 hours building that idea! 🔨</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gU_Pt0hh_hSHOFg-eblCfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CCMHVZMITJgrUtxteo-Kvw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*saj9I02RS1_yOdgRJKOLQQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHx-kpC35pD24VYu36ZdCQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IKgMLt214Ue9gA2o-RdUkg.jpeg" /></figure><p>Later that day, lunch from Subway arrived. Combined with Tonic’s unique assortment of hot sauces and barbecue sauces, attendees came up with some rather unique flavor combinations, like putting Siracha on ham (which is surprisingly delicious.) 🍔🔥🔥🔥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NDYMYj6BdiGP1PtcBWQv4g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nenISRKGwlq4cythb_33jA.jpeg" /></figure><p>Throughout the afternoon, we hosted a number <strong>workshops</strong> geared towards beginners and students who want to sharpen their skills, and and in the process we learned a lot from each other. ❤</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQ-AaluWohpoUeIulHuw0g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ydFJYn65M-2VvfxsIodFdA.jpeg" /></figure><p>If you missed a workshop or interested in diving in a little deeper into a topic, these are all available online! Click the workshop title for a link:</p><ul><li>Beginner: <a href="https://www.scirra.com/tutorials/37/beginners-guide-to-construct-2">Make a Game (Game Development with Construct 2)</a></li><li>Intermediate: <a href="https://studentrnd.org/build/making-better-games-with-splunk">Making Games Better Using Data (Splunk)</a></li><li>Beginner: <a href="https://github.com/hackclub/hackclub/blob/master/workshops/cloud9/README.md">Make Cool Websites Part 1 (Setting up Cloud9)</a></li><li>Beginner: <a href="https://github.com/hackclub/hackclub/blob/master/workshops/personal_website/README.md">Make Cool Websites Part 2 (Intro to Web Development)</a></li><li>Intermediate: Cross-Platform Apps (Web Development using Ionic)</li><li>Beginner: Intro to iPhone Apps (App Development)</li></ul><p>Our mentors were floating around to assist with workshops and show students how to bring their ideas to life. ⚡️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NLtm8hRYPlQHGdqVp7eEVw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLVigGqipbbGuJ38FMgFvA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KViAMRhMgeil10u6o9LM8A.jpeg" /></figure><p>We also had a few young visitors stop accompanied by their parents! Here is our youngest visitor who stopped by to write her first line of javascript and showed her eternal gratitude by doodling the CodeDay logo on the glass wall.🎈</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hqp7rLkTLw7BXWCRzT9inA.jpeg" /></figure><p>By the time the evening rolled around, we had teams design their own pizzas (with up to 5 toppings.) Here is what they came up with: 🍕</p><ul><li><strong>Cheezy</strong>: cheese pizza (x3)</li><li><strong>Pepe</strong>: pepperoni pizza (x3)</li><li><strong>Buffy</strong>: buffalo chicken + ranch pizza</li><li><strong>Meaty</strong>: pepperoni + sausage + basil pizza</li><li><strong>Meaty-o-Deggon</strong>: pepperoni + sausage + canadian bacon + chicken + lite bbq sauce + flat crust pizza</li><li><strong>Piña</strong>: pineapple + ham + old bay + crust pizza</li><li><strong>Veggie</strong>: mild pepper + onion + olives + mushroom + basil + parmesean + flat curst + well done pizza</li><li><strong>Drizzle n’ Shizzle</strong>: chicken + pepper + old bay + bbq sauce pizza</li><li><strong>Pie</strong>: gluten-free tomato pie pizza (no cheese)</li></ul><p>A lot of them came up with some pretty unique combinations. I personally liked the barbecue meaty-o-deggon. 🍗</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K37KvI_bYQekkfn_MklK6w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Ib6Hm5i6NchTbwHrjtFGg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ri1wJL6NELdoYwCkD9NZmA.jpeg" /></figure><p>We had a room streaming the Republican debate, because a good number of us wanted to watch Donald Trump (and other presidential candidates) yell at each other. We broke out the popcorn just for that! 🎥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNs3RZK9jIY8YnO-zUg1Mw.jpeg" /></figure><p>Later that night, we hosted a <strong>ping pong tournament</strong>, a tradition unique to CodeDay Philly, because every venue happened to have a ping pong table for whatever reason. We rallied back and forth for nearly an hour, before declaring Dan K (yes his name truly is DanK) as the winner in a very close &amp; intense final round. 🎾</p><figure><a href="http://challonge.com/codeday2"><img alt="" src="https://cdn-images-1.medium.com/max/994/1*-GDk0BNYB4sL84s76-g9VA.png" /></a></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgDHBuYAwnAqISbhGu9Mig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gERClA7cP9UO4fZ_BHdzMg.jpeg" /></figure><p>Most of us were hard work throughout the evening building out their games, apps, and websites. 🔧</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lb6KBwATE8iJmaFLLRK6gQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*koxwQrZpjvlaf6QIu35riQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1pZ59NUsnaQzE1BQXNfeg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uz6fEp74Sf95wAmmLYWYBg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sy_IZ3wA8jl3Xzf-9JM1mQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvfXxYNfJeUmTc0DUlf1VQ.jpeg" /></figure><p>Some of us even got a chance to hang out with attendees from other CodeDays across the world — including New Jersey, San Diego, Seattle, and Silicon Valley. 👾</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3QiudVuiP-NwutGJiGBhg.jpeg" /></figure><p>Later in the night, we went outside to take some photos of CodeDay Philly. Some of our fellow night owls even saw us out the window and waved at us! 👋</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thj0-jDkkWHhZvXOsyF9dA.jpeg" /></figure><p>As at temperatures fell to single digits (which turned out to be coldest night of the winter), the building heat did a great job of keeping us warm and comfortable. Mentors were still floating around to help out. We had random activities and impromtu workshops throughout the night to keep our attendees motivated. ✌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ltzlcYHcaJ1E1qRM_fzUgQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ELsmS0yotrJPCz0pEOYiFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jFeH8AkvKFT3ZasBTotkQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7HN4J6UruQeHk2svHv1ZA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2MZlDjRTxO9HdjTN0lvgAg.jpeg" /></figure><p>My favorite experience (and photo) of the night was serving root beer floats. It was fun playing with cans of whipped cream: 🍰</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q18aVR1S7ROQK84faNL19w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUDLOfZhPgd9QzkaJYqxMQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TfZsZUzKgeLnjXVugfQRvA.jpeg" /></figure><p>Beyond midnight, some of us were still awake <em>clearly</em> focusing on getting their projects done. (Well, mostly haha.) 🌙</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AEhPYBhfOHlyJI0rfuBf4w.jpeg" /></figure><p>By the time morning rolled around, we had coffee and donuts for everyone. Federal Donuts makes the best donuts ever! ☕️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2iXCjeghDCr7z5d3Tow_g.jpeg" /><figcaption>Federal donuts granted us a behind-the-scenes look into their magical hot fresh machine!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPMWPAfpvFcFSnWokCWgrA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_x0TYGhPGvTi-6CsrFZTQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kXIoAMZUoG4Kn_DkutZUQ.jpeg" /></figure><p>As breakfast was served, everyone was putting together some final touches to their projects. 🐎</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfpZFUIjIT2AAN3Lpl7ynA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXa44ES6FpUAS9HjOSCzsA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jp7YpimXEPFaH3cXc2s1mg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZJg2qiKJITMJtYqiTUdJA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8ymrpih76tRNor-1jeT7Q.jpeg" /></figure><p>At 9am judges and mentors rolled around to talk with attendees and see what they’ve built in 24 hours. 🎺🎺🎺</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_TSkHP6jWh9eDaQgprse3Q.jpeg" /></figure><p>At 10am everyone presented their ideas and projects in front of everyone (see below for a list.) Parents and members of the community came together to witness what their scholars have created. 📢</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AeA5fFl7vptSOLA4KGbeWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5dns59t5TU-p-ZztTFThw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*651c0Vj-UFY0DF0Tm0bo2A.jpeg" /></figure><p>At the end of the day, our CodeDay attendees have said that they had a lot of fun sharing and exploring their passion for technology. 💜</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZkOl9yOdfbnBRPpN9-6jQ.png" /></figure><h4>We want to recognize not only the efforts of the winners but also the efforts of everyone. A complete list of projects can be found below.</h4><p>A special thanks to our panel of judges who came out to see what these students have created in 24 hours:</p><ul><li><a href="https://twitter.com/Yuriy_P"><strong>Yuriy Porytko</strong>, Venture Capitalist at FundingPost</a></li><li><a href="http://tonicdesign.com/"><strong>Christopher Cook</strong>, Tech Director at Tonic Design</a></li><li><a href="https://twitter.com/johnsons531"><strong>Sarah Johnson</strong>, Outreach Director at TechGirlz</a></li></ul><p>(Our prizes were lazer-cut wood trophies, but it is important to note that they are not main emphasis of the event.)</p><h3>Trading Waitlists (Best Overall)</h3><h4>by Heman Gandhi and Divesh Otwani</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nOc14bCPbqpLlZwc3HXj3w.jpeg" /></figure><blockquote>In college you get wait listed for your favorite classes sometimes. This is a website that allows you to connect with several other people and make trading circles (person A gives up one of his classes with B, B with C, …, Z gives up a class that A wants) so that everyone can get the classes they want. It’s just an extended version of trading classes with another person.</blockquote><p>Here is a judge’s note on how they won Best Overall:</p><blockquote>Taught us about what their app did, as well as handcrafting the full architecture for the app.</blockquote><h3>Ter0: The Awakening (Best Game)</h3><h4>by Micheal Ryan, Arnav Misra, Tyler Swartz, Seth Treiman</h4><p>Play the game here: <a href="https://xenonmolecule.github.io/codeDayGame/">https://xenonmolecule.github.io/codeDayGame/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*gfcLBqG5oPHKDRZOHiNNjA.png" /></figure><blockquote>This is a basic RPG Video Game that portrays a robot going to different rooms to discover and explore for different treasures!</blockquote><p>Here is a judge’s note on how they won Best Game:</p><blockquote>Built from scratch, build all graphics new, great user experience.</blockquote><h3>Tappy War (Best App)</h3><h4>by Trevor Antram and Josiah Somani</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkn8ZAf8HQg-Svo53F-ieA.jpeg" /></figure><blockquote>A simple game in which you must tap both sides of your phone. Whichever side taps the most, wins!</blockquote><p>Here is a judge’s note on how they won Best App:</p><blockquote>Great example of a simply-addictive, fun app.</blockquote><h3>PhysicsDay (Most Innovative)</h3><h4>by Nick DeFilippis and Daniel Swartz</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zV2TwsFkDzgtJNLssrG5Kg.jpeg" /></figure><blockquote>Simulates physics problems involving collisions and gravity.</blockquote><p>Here is a judge’s note on how they won Most Innovative:</p><blockquote>Students chose to create physics-based simulations instead of just a game or app.</blockquote><h3>Steam Game Analysis Website (0–60 Award)</h3><h4>by Jonathan Halter</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1E8CdrFDObckElGe31018Q.jpeg" /></figure><blockquote>The main page of a website that would contain reviews of Steam games and would suggest new games or games on sale based on review you favorite or create.</blockquote><p>Here is a judge’s note on how they won 0–60 Award, given to beginners:</p><blockquote>Jonathan knew nothing about even making a website before coming to CodeDay, and made a full, nice-looking website by the end of the event.</blockquote><h3>Space Attack</h3><h4>by Josiah Somani and Trevor Antram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zg_dwLO6w6pffvFGnjj6eA.jpeg" /></figure><blockquote>A turn-based RPG battling game in which your star-base is attacked by Komavrizi aliens, who are destroying your base! Stop them, and meet an old king to help you along the way.</blockquote><h3>Sewer Sluggers III: This Time it’s Personal</h3><h4>by Ranwei Hu, Alexander Serebriiskii, Jonathan Sherwood, Arie Dash</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFbLTR_SzP3-y_Xk4rnZiw.jpeg" /></figure><blockquote>A classic side-scrolling fighting game featuring the creators as characters.</blockquote><h3>KwikScore</h3><h4>by Nasir Kasumu and Jared Massa</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k60TiqF8kcBb82sniErRQA.jpeg" /></figure><blockquote>Converts Audio Wave Files into the Tone/Pitch/Frequency and the equivalent concert pitch and octave. Base of project is completed, future steps would be getting microphone input and converting it through the same process. End goal: Have live audio input from microphone become transformed into readable sheet music in Concert Pitch.</blockquote><h3>Ultimate Frisbee organizer</h3><h4>by Eric Kim and Salman Fakhri</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I5Fnq6vJh1QSWdRxb2gfYA.jpeg" /></figure><blockquote>Makes organizing ultimate games easier</blockquote><h3>Space Kitties</h3><h4>by Janice Noh, David Kwon, Elizabeth Qian</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3Na7nZtNvo2roIpTdmGfw.jpeg" /></figure><blockquote>Changing the world with cats, one arduino at a time!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yr_TN0ugPnzlCEwIZK3f4A.png" /></figure><h4>Despite the fact that this was our smallest CodeDay Philly ever in terms of the numbers of attendees, our #1 focus is providing welcoming and inclusive learning environment.</h4><p>That means making our event as beginner friendly as possible, as well as providing opportunities for more advanced students. Here are our statistics from this winter’s CodeDay Philly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*WkP807EYiv0je2suXRzb7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*PbnXDdhfhCvjTKFfCn8UWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*dE0vY21VVELWmauRHqO_Ww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*Vcb3b7vGnjnR_tnmXhQ0fA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*v7SpjKA5yvYhLeFVQUMiQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*PSDmo22P1H-Uficj321zpQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*sg_e0FZw608YSgDDoxqYUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*-xkQrj-ftXZKtIOYnJtMXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*T_ABQS9M-EE-6mr3zqb7Mw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_h73tHdFt8ddY77fIAZLw.png" /></figure><h4>It’s important to recognize, when looking at the demographic numbers, that CodeDay isn’t defined solely by the numbers; the numbers represent actual people, many learning about coding for the first time in their lives!</h4><p>This CodeDay was more inclusive towards beginners than ever. Over 50% of our attendees were first time programming marathon attendees, and at least 30% have also never written a line of code before.</p><p>In past events, we have maintained a 20–30% female attendees ratio but this season was particularly unacceptable when it came to gender ratio. We had only 3 females check into event — it’s the worst number for a CodeDay event ever across the United States.</p><p><strong>For our next event this May, we are partnering with </strong><a href="http://techgirlz.org/"><strong>TechGirlz</strong></a><strong>, </strong><a href="http://girlswhocode.com/"><strong>Girls Who Code</strong></a><strong>, and </strong><a href="http://hopeworks.org/"><strong>Hopeworks</strong></a><strong> to bring our programs to even more minority in tech groups across the area.</strong></p><p>Diversity has always been an important part of CodeDay and our goal is to host an event that represents the diversity of the greater Philadelphia area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKnb_9QMXgSe5Zkb33w-_g.png" /></figure><h4>We took a whole bunch of photos from CodeDay Philly, from both the organizer and attendee perspectives.</h4><p>Attendees, judges, sponsors, and StudentRND volunteers can find a Google Photos link in your emails. If you happen to lose the link or want to access these photos a parent or press, shoot me an email to victor (at) studentrnd.org and I am happy to set you up with access.</p><p><strong>License information: You may freely reuse, distribute, and modify these photos in an appropriate manner. You must also attribute “<em>Victor Lourng from StudentRND</em>” when you share these photos.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4EghXK5rCUFDxF2tb3wEA.png" /></figure><h3>From Our Attendees</h3><p>Here are some words from our fellow attendees highlighting their CodeDay experiences: ✏️</p><p><a href="https://medium.com/p/fb3339e97214"></a></p><p>If you wrote something for CodeDay Philly Winter 2016, send an email to victor (at) studentrnd.org and I’m happy to add it to this section!</p><h3>Stay Connected</h3><p>Check out this Facebook group for fellow CodeDay attendees to connect with each other:</p><figure><a href="https://www.facebook.com/groups/studentrnd"><img alt="" src="https://cdn-images-1.medium.com/max/657/1*XW7YKKP8m7B6P2dyh2pVNw.png" /></a></figure><p>If you’re a high school student, join this amazing community of makers and creators:</p><figure><a href="http://facebook.com/groups/pennappshs"><img alt="" src="https://cdn-images-1.medium.com/max/659/1*o-iz2o4uLfftYfwfQW5JnA.png" /></a></figure><p>If you want to get in touch with a specific attendee, mentor, or judge, please send me an email to victor (at) studentrnd.org and I am happy to get you connected! If you have feedback for CodeDay or interested in helping out, please let me know as well!</p><h3>Summer Programs</h3><p>If you’re looking for some things to do this summer, check out our sponsors <a href="https://leangap.org/">Leangap</a> and <a href="http://makeschool.com/">Make School</a> (need-based scholarships are available!)</p><p><a href="http://leangap.org/"><strong>Leapgap</strong></a> is designed to help high school students start real companies in one summer. While the vast majority of entrepreneurship programs for high school students only talk about ideas and validation, we take it one step further. We believe that only by building and selling can students truly learn the core fundamentals of entrepreneurship.</p><p><strong>The deadline to apply for Leangap is Feburary 29 so APPLY ASAP: </strong><a href="http://leangap.org/">http://leangap.org/</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuokVO9FRaX0%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuokVO9FRaX0%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuokVO9FRaX0%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f8f1f2274836b75bc6845ac77cb1caad/href">https://medium.com/media/f8f1f2274836b75bc6845ac77cb1caad/href</a></iframe><p><a href="http://makeschool.com/"><strong>Make School</strong></a> is the college replacement for founders and developers. Apply to their Summer Academy to build and ship your own iPhone app!</p><p>Applications are open and decisions are being made on a rolling basis. Apply using this link, <a href="http://make.sc/codeday">http://make.sc/codeday</a>, for priority application review.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0aNOvs3foXE%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0aNOvs3foXE%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0aNOvs3foXE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/30ccc242440be51e660aa1485c9561c2/href">https://medium.com/media/30ccc242440be51e660aa1485c9561c2/href</a></iframe><h3>Upcoming Events</h3><p>If you liked CodeDay Philly, here are some upcoming events you may be interested in attending. Be sure to check them out:</p><p><a href="http://hackumbc.org/"><strong>HackUMBC</strong></a>, March 5–6 in Baltimore MD</p><p><a href="http://profhacks.com/"><strong>ProfHacks</strong></a>, March 12–13 in Glassboro NJ</p><p><a href="http://hackbca.com/"><strong>hackBCA</strong></a>, April 2–3 in Hackensack NJ (with a free bus from Cherry Hill NJ)</p><p><a href="http://hackehs.com/"><strong>HackEHS</strong></a>, April 23–24 in Edison NJ</p><p><a href="http://2016.phillytechweek.com/"><strong>Philly Tech Week 2016</strong></a>, April 29–May 7 across Philadelphia</p><p><a href="http://hackgfs.io/"><strong>hackGFS</strong></a>, May 14–15 in Germantown Philadelphia</p><p><a href="http://hacksj.org/"><strong>HackSJ</strong></a>, May 21 in South Jersey NJ</p><p><a href="http://twitter.com/pennapps"><strong>PennApps</strong></a> is happenning this fall in University City Philadelphia. Follow the <a href="https://medium.com/u/c702efc4ee40">@PennApps</a> Twitter for updates. (You should probably mention CodeDay Philly when you apply!) 😉</p><h3>CodeDay Spring 2016 is returning May 21–22.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8xOTVthlbFmNUmRlRedrA.png" /></figure><p>Visit <a href="http://codeday.org/">CodeDay.org</a> or click out these cities below to sign up for updates:</p><figure><a href="http://codeday.org/philly"><img alt="" src="https://cdn-images-1.medium.com/max/524/1*h_s_yksQCj3aSMAOy44g7A.png" /></a></figure><figure><a href="http://codeday.org/jersey"><img alt="" src="https://cdn-images-1.medium.com/max/524/1*twdchmUUIFWPAlwlYywrgg.png" /></a></figure><figure><a href="http://codeday.org/ny"><img alt="" src="https://cdn-images-1.medium.com/max/523/1*3fchv7628bg-3noYynpJlA.png" /></a></figure><figure><a href="http://codeday.org/baltimore"><img alt="" src="https://cdn-images-1.medium.com/max/523/1*QNbndk7sskYTBJPcBxUksw.png" /></a></figure><figure><a href="http://codeday.org/dc"><img alt="" src="https://cdn-images-1.medium.com/max/524/1*w4RJzYnTF85-3v53m6VDvA.png" /></a></figure><figure><a href="http://codeday.org/boston"><img alt="" src="https://cdn-images-1.medium.com/max/524/1*OPPWvuyIPsAOqGP_8xLV_Q.png" /></a><figcaption>So many cities, so little time!</figcaption></figure><h4><strong>Thanks for reading! If you liked this recap, please recommend this post and spread the word about CodeDay by sharing this on social media!</strong></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c28c9ff1fb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/codeday-philly-winter-2016-wrap-up-9c28c9ff1fb6">CodeDay Philly Winter 2016 Wrap-Up</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Education]]></title>
            <link>https://medium.com/the-studentrnd-blog/education-12e0499b332f?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/12e0499b332f</guid>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Tue, 14 Mar 2017 23:21:13 GMT</pubDate>
            <atom:updated>2013-08-16T09:39:31.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*40zrGy3Q-_ceEEuC.png" /></figure><blockquote><em>“Millennials are entitled narcissists,” claim the journalists. “They have no purpose and they don’t care.” </em><strong><em>Stupid kids.</em></strong></blockquote><p>Being a student starts at age five. For 180 days a year, you sit in a room for six hours a day and memorize facts and skills. You have no input on which skills you’ll be memorizing, of course, except that most quickly decide the question, “will this be on the test?” is very worthy of memorization.</p><p>This goes on for six or seven years, before you’re allowed some <em>electives.</em> These, it seems to you, are used as a filter: the students which want to get into college <em>elect</em> to take AP classes. (You also <em>elect</em> some extra-curriculars: mostly community service and academic clubs. Colleges like to see those.)</p><p>Repeat for another eight years. Some of your teachers will be better than the rest: they explain why some of these facts are important and exciting. Occasionally you get <em>really </em>lucky with some hands-on, real-world examples.</p><p><em>What would our world look like if students, instead of needing to worry about getting into selective schools and majors, could worry about actually learning instead?</em></p><p>Eventually, you make it to college, where you spend another year or two taking required classes. Finally, by the time you’re twenty, you declare your major, and take a year or so of classes which are interesting to you.</p><p>With all those math and humanities courses you took, you did find something which interests you, right? Oh, and your major better not be a humanity. You’ll end up as just another jobless Millennial. The journalists told you so.</p><blockquote><em>“Teachers don’t teach,” claim the parents. “Our education system is failing our kids.” </em><strong><em>Stupid teachers.</em></strong></blockquote><p>Perhaps you’re a very idealistic Millennial. You believe you can make a difference in the next generation; help them discover what they’re passionate about. When you graduate, you become a teacher.</p><p>This is to the strong disapproval of your parents. “Teachers don’t make much.”</p><p>Being a teacher is actually more difficult than it seemed. For one, most students don’t actually want to learn, it’s just a requirement to get into college. Given that condition, many choose to do as little work as necessary.</p><p>So you start spending your nights grading homework and tests, and harassing students who are starting to fall behind.</p><p><em>What would our world look like if society thought of learning, not just as a path to a good career, but as something fun and exciting and worthwhile?</em></p><p>Oh, by the way, how are you doing? No, really, the government wants to know exactly how you’re doing. You’re directly shaping the futures of these students, so you better be good. The government, in the 2001 <em>No Child Left Behind Act</em>, decided testing would answer this question.</p><p>So, from the public perspective, your entire job boils down to how well the kids you teach do on a standardized test.</p><p><strong>Standardized. </strong>It turns out that teaching really isn’t about helping students find their passions, because passions are individualized. We can’t measure individualized traits in a standardized test.</p><blockquote><em>“</em>NCLB<em> killed education,” claim the education pundits. “We’re encouraging teaching to the test.” </em><strong><em>Stupid politicians.</em></strong></blockquote><p>But, as it turns out, there are very few Standardized Testing lobbyists, if any. <em>No Child Left Behind</em> isn’t a result of corruption. The politicians really do represent us.</p><p>Education reform isn’t possible until we change our priorities.</p><p>Society is responsible, because we know each of our own children is better than the rest, and we need to make sure the school system is doing a good job of educating them. So we measure it. To measure it, we assume everyone needs the same skills.</p><p>Society is responsible, because we don’t value learning, we value money and careers. Good careers: maybe a scientist, or a CEO. No one wants their child to be a waiter, or a hairdresser, even though we rely on these people hundreds of times each day.</p><p>Whether you blame the students, the teachers, or the government, you are encouraging the system, because you are a member of society.</p><p><strong>You</strong> are responsible for education reform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e0499b332f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/education-12e0499b332f">Education</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CodeBreak]]></title>
            <link>https://medium.com/the-studentrnd-blog/codebreak-138a19eb8ea3?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/138a19eb8ea3</guid>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Tue, 13 Dec 2016 22:36:02 GMT</pubDate>
            <atom:updated>2016-12-13T22:36:02.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhbM8caB65QyMKKTyLbubQ.png" /></figure><p>When I was in high school, I finished many of my favorite coding projects over winter break. Winter break is the perfect balance of external factors for people who love coding:</p><ul><li>It’s roughly the coldest time of the year, so there’s not much to do outside.</li><li>It’s long enough that you can finish an actual project..</li><li>It’s short enough that there’s pressure to finish it.</li></ul><p>Because it’s such a great time to make something,<strong> we’re hosting CodeBreak, a fun way to stay motivated and complete a project over your winter break. </strong>You can get a limited edition t-shirt for participating!</p><h3>How To Participate</h3><h4>1. Sign Up</h4><p><a href="https://srnd.wufoo.com/forms/studentrnd-codebreak-winter-2016/">To sign up for CodeBreak, just fill out this form.</a> You can pick any project, even an existing one. You also don’t need to finish the project during CodeBreak; it’s about the process of making.</p><p>We recommend choosing individual projects, but teamwork is allowed; each person should sign up individually.</p><h4>2. Join The Chat</h4><p>After signing up, you’ll get instructions to join the StudentRND Slack — a sort of chatroom where you can talk with other cool students who love coding, and where you’ll post your CodeBreak updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QIDOVGCHsb-WV86TssIsQ.png" /></figure><h4>3. Update Each Day</h4><p>Each day starting December 18th and ending on the 31st, post an update on your project in the #waywo (“What Are You Working On”) room in Slack.</p><p>Your update can be a brief description, a picture, a live development stream, a download, or anything else that shows your progress.</p><h4>4. Get Help</h4><p>StudentRND staff, volunteers, and mentors, as well as other smart students, will be on Slack throughout the break to help with coding questions. Post any questions in the #helpdesk room.</p><h4>5. Finish It (And Get Rewarded!)</h4><p>There are 14 days in CodeBreak, and each student who posts an update for at least 10 of those days will get a limited edition CodeBreak 2016 t-shirt.</p><p>(You’ll also get an awesome project to list on your resume!)</p><p><a href="https://srnd.wufoo.com/forms/studentrnd-codebreak-winter-2016/">Sign Up for CodeBreak by December 18!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=138a19eb8ea3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/codebreak-138a19eb8ea3">CodeBreak</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strong Codes of Conduct]]></title>
            <link>https://medium.com/the-studentrnd-blog/strong-codes-of-conduct-2abd51b1da75?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/2abd51b1da75</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[code-of-conduct]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Mon, 07 Nov 2016 17:38:49 GMT</pubDate>
            <atom:updated>2016-11-07T18:58:15.120Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*Y4RpE96IcOA7Z-jMMxSvNQ.png" /></figure><p>I believe strongly in the technology industry’s ability to make the world a better place. As anyone who’s seen HBO’s <em>Silicon Valley</em> knows, however, that sentiment doesn’t often translate into practice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJ-GVd_HLlps%3Fstart%3D32&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJ-GVd_HLlps&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FJ-GVd_HLlps%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5c1042d5b79467d2f393708d237243cd/href">https://medium.com/media/5c1042d5b79467d2f393708d237243cd/href</a></iframe><p>Right now, one of our biggest barriers is a lack of diversity in background. You’ve likely heard plenty about how white and male the top technology companies are. It’s bad for equality, but it’s also preventing us from seeing important problems and unusual solutions. StudentRND is working to improve it.</p><p>Many people don’t get involved in technology because they’re made to feel unwelcome by people already in technology. Many organizations try to address this with a Code of Conduct.</p><p>Our Code of Conduct has stuck with us as we’ve grown to 40 cities with tens of thousands of participants. <a href="https://srnd.org/code-of-conduct">Today, we’re making changes which we believe will make our community more welcoming.</a></p><p>By sharing our changes, and the rationale behind them, we’re hoping other groups and projects might be able to improve their communities, too.</p><h3>Be Positive. Start With Why. Ask For Help.</h3><p>Many Codes of Conduct simply explain what people aren’t allowed to do. This makes them rules. No one wants to read the rules. (Seriously, we’ve had 20 visits to our rules page in the last month.)</p><p>We’ve always taken a slightly positive approach, which has received broad compliments from attendees, and our latest policy takes this further by leading with our vision for the community, and how attendees can help:</p><blockquote>StudentRND strives to make students feel welcome so they can meet new friends, have fun, and build cool things. To create this atmosphere, we need the help of the whole community.</blockquote><blockquote><strong>At StudentRND events, please be friendly and welcoming.</strong></blockquote><blockquote>Be humble, even when you’re successful.</blockquote><blockquote>Respect, encourage, and support others.</blockquote><p>Because the Code of Conduct is one of the first signs our community members see when attending an event, leading with a vision not only increases the reading rate, it also helps create the StudentRND culture.</p><p>Having people on-board and excited about the Code of Conduct also helps with enforcement. In talking about the updates, our community has already turned the core principle into a meme, which gets brought up every time someone says something vaguely mean:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*jwuOwg3b8GT1yZvdWPh_Hw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*XPMYeo9LECDypn7YICJA2w.png" /><figcaption>The most recent Slack quote is from an attendee who hadn’t even heard about the new code of conduct.</figcaption></figure><h3>No Harassment. Anywhere.</h3><p>Many behaviors are dangerous, illegal, or make others feel unwelcome, and while we don’t encourage them, we respect the right to disagree. Diversity of opinion is important, so most of our code of conduct applies only when attending CodeDay. This is true of most Codes of Conduct.</p><p>Unusually, one provision from our Code of Conduct, however, applies even when participants aren’t acting as our community members:</p><blockquote><strong><em>StudentRND members may never harass others.</em></strong></blockquote><blockquote>Harassment includes words or behavior which are intended to disparage, demean, mock, or intimidate a person or group. People who participate in harassment are not welcome at StudentRND events, even when this behavior takes place outside the event.</blockquote><p>Attendees who participate in harassment make their targets, actual and potential, unwelcome at our events, even when it doesn’t happen here. By silently ignoring this behavior, organizers are making a choice about which group they’d like to attend their events.</p><p>We’ve made our choice explicit.</p><p>We don’t plan to proactively police this policy. A number of times, someone who’s been the past target of harassment by an attendee has brought it to our attention, but without a clear policy, we’ve done nothing. With this change, we’re empowering our staff to do the right thing.</p><h3>We’re Not a Dating Event</h3><p>Most Codes of Conduct contain language which prohibits “unwelcome sexual advances.” This has been one of our most common problems at CodeDay, but dealing with it has been a big problem:</p><ul><li>When considering whether an advance was “unwelcome”, do we consider only the opinion of the recipient, or what the advancer could have been reasonably expected to believe?</li><li>If we consider the beliefs of the advancer, how do we get the facts of the situation? Body language is a major cue which can’t easily be repeated.</li><li>If our staff sees it happening, do we intervene?</li><li>How do we reduce the pressures against reporting an unwanted advance? It’s common for attendees to feel the person making the advance didn’t realize it was unwanted, even if it seems clear to us.</li></ul><p>There’s actually a simple solution to this problem: <em>stop being a matchmaking service.</em> Industry events and technical communities are not the place for getting dates.</p><h3>Carol Mertz on Twitter</h3><p>I&#39;m thinking about starting a spreadsheet to log the frequency of rando dudes asking me out after public speaking engagements.</p><p>Our latest Code of Conduct prohibits anyone from hitting on others at StudentRND events. If you like someone, and they like you, I have no doubt you’ll keep in touch after our event.</p><p>Two of our earliest attendees have been engaged for the last year. This policy wouldn’t have stopped that. It will, however, empower us to stop most of the behavior making us all uncomfortable.</p><h3>Encourage Third-Party Reporting</h3><p>This is untested so far, but I hope that it works.</p><p>A big problem we had with our last Code of Conduct was community members experiencing a clear violation, brushing it off, and going on with the event, only to never show up again and mention the incident in passing months later.</p><p>Reporting another attendee is an obvious way to make that attendee dislike you. If that attendee is being an awful human, one might be tempted to ignore it, but there’s also a real fear that it will alienate other attendees as well. And really, that’s a totally valid fear.</p><p>That’s why our latest Code of Conduct encourages third-parties to report behavior by offering free admission to future events for all good-faith reports, and making it easy to do so quickly and anonymously: providing both an email, and a phone number.</p><p>(Quick note: Because we work with high school students, we aren’t as draconian about punishing violations as an industry event or group might be. Depending on the nature of the violation, we might discuss why the behavior isn’t ok, or ban the offender for only a season or a year. We’ve had success with people changing their behavior this way, although we keep a close eye on past offenders. This isn’t a great strategy for adults, who are far less likely to change behaviors.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2abd51b1da75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/strong-codes-of-conduct-2abd51b1da75">Strong Codes of Conduct</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A History of StudentRND, As Told By Files I Found On My Old Hard Drive]]></title>
            <link>https://medium.com/the-studentrnd-blog/a-history-of-studentrnd-as-told-by-files-i-found-on-my-old-hard-drive-946f175eddaa?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/946f175eddaa</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[stem]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 20:52:10 GMT</pubDate>
            <atom:updated>2016-11-04T15:04:16.355Z</atom:updated>
            <content:encoded><![CDATA[<p>With CodeDay coming up in a week, I thought I’d share my history with StudentRND/CodeDay. You can respond to posts on Medium, so it would be great to hear your stories, as well!</p><h3>2009</h3><p>Fun fact for people who refer to me as StudentRND’s original founder: I’m totally not! I was barely even involved with StudentRND for the first several years!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/20/1*3Hm6U4NbaAzxuJ_hVssulA.png" /><figcaption>StudentRND’s actual founder, as told by emojis I found on Twitch.</figcaption></figure><p>I got involved when our actual founder, <a href="http://edjiang.com/">Edward “EdwardStarcraft” Jiang</a> — who used to be legitimately famous enough for Starcraft II that he got a Twitch emoji — contacted me in 2009 asking if I’d be interested in designing the logo:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*Qw7Cv2ep1CmbJhs-bPBn0g.png" /><figcaption>The logo I actually came up with is on an even older hard drive, but here’s a recreation from the best of my memory.</figcaption></figure><p>It turns out <a href="https://web.archive.org/web/20090723162945/http://www.collegeboard.com/">I’m not the only one </a>who liked Adobe Illustrator’s built-in “Scientific” color palette and slab serif fonts, so he got another volunteer, Claire Lin, to make this logo instead:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*shOaoFYcK0MrN0aXPki6FA.gif" /></figure><p>The other thing about 2009-era StudentRND is that there was no CodeDay — the idea was to open a space where students could get access to tools to work on projects. In 2009 this space was Edward’s basement, a 30 minute drive into the suburbs. Edward spent the rest of the summer trying to convince me to visit the space, and I was not interested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*lVGH9zoLjkXO84NHqQXZbQ.png" /></figure><p>End of 2009, according to my hard drive.</p><h3>2010</h3><p>In 2010, Washington Mutual, a bank you probably haven’t heard of, was bought by Chase, a bank you have probably heard of. Unlike Chase, people really liked Washington Mutual, so Chase decided to give away a bunch of money to Washington-based nonprofits to make people like them.</p><p>They did this by means of a Facebook voting contest, which wasn’t hard to win in 2010. So we, and many other nonprofits, got a $25,000 check!</p><p>(Ironically, Chase wouldn’t actually give us a bank account because Edward was under 18. We had to go with US Bank, a bank so bad they literally lost our money three times.)</p><p>Having a bunch of money, we bought one of the first 3D printers! Aside from looking worse, it worked roughly as well as modern ones.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F12197786&amp;url=https%3A%2F%2Fvimeo.com%2F12197786&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F68031534_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="436" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7ddf37cbd20aa34c4e00357f890dab7/href">https://medium.com/media/e7ddf37cbd20aa34c4e00357f890dab7/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*GNDwILtTqQnvT7oWJv6UPw.jpeg" /></figure><p>We also found a great space for the summer: in industrial Bellevue, right across from a giant pile of dirt. It also didn’t really have “floors” by most definitions — it had hardened flooring glue.</p><p>But it was cheap, and available for a short-term summer lease, so we took it, and held the grand opening!</p><p>I either made the flyer, or printed it, because I found it in a folder called “Older stuff”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*d8zuPcWUsbZnWOi4tkGX-w.png" /></figure><p>We worked on a bunch of projects over the summer, including a Microsoft Surface. No, not that one. <a href="https://www.youtube.com/watch?v=t2ty_QIWspE">This one.</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F47071357&amp;url=https%3A%2F%2Fvimeo.com%2F47071357&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F327888987_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/65177a14d08ed89964b5930395cd674a/href">https://medium.com/media/65177a14d08ed89964b5930395cd674a/href</a></iframe><p>And a Trebuchet.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F14330810&amp;url=https%3A%2F%2Fvimeo.com%2F14330810&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F83921269_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd6f380b44f49c56901c8788f69829b9/href">https://medium.com/media/cd6f380b44f49c56901c8788f69829b9/href</a></iframe><p>Then at the end of the summer, we packed everything up, and went back to school. End of 2010, according to my hard drive.</p><h3>2011</h3><p>In the Summer of 2011, we got a space with real floors! I went to do an internship in Canada, so I was only there for the tail end, but at some point <a href="https://www.facebook.com/studentrnd/photos/a.10150236357341332.323798.106352456331/10150236358576332/?type=3&amp;theater">a world-famous DJ stopped by to play a show</a> and no one believed us.</p><p>Edward used that show as a launching point for a new initiative: year-round StudentRND workspace! (Remember, until now, it was only over the summer.)</p><p>I got back from Canada, and made this video to tell people the good news:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F28753400&amp;url=https%3A%2F%2Fvimeo.com%2F28753400&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F192051891_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/04139f18365a54c32785f4ff6f3d7e08/href">https://medium.com/media/04139f18365a54c32785f4ff6f3d7e08/href</a></iframe><p>We worked on a few projects, including two kickstarters: a robotic pipe organ, and a plasma speaker!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ev0bNMrORWuPe1MhZsVvLg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*-mtiFDbNFcIn1YBoWRix9Q.png" /><figcaption>(The little rainbow guy is Commander Video from the bit.trip games, which I was really into at the time. Later on, I dropped my Nintendo DS bit.trip cartridge and it bounced into a small hole in the wall and was lost forever, so I call that even.)</figcaption></figure><p>We also <a href="http://arhsinflight.com/feature/2012/01/11/students-compete-at-local-24-hour-game-creation-contest/">hosted our first CodeDay,</a> based on the fact that some friends and I worked on a game in high school, but actually did all the work in the 24-hours before we presented it.</p><p>We called the first CodeDay “HACK” because I went to the grand-opening of Facebook’s Seattle office, and they had a sign that said “HACK” on the wall, and I thought it sounded cool.</p><h3>2012</h3><p>Right after HACK, we started using the name CodeDay, and in early 2012 we held the first event under that name!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F48183508&amp;url=https%3A%2F%2Fvimeo.com%2F48183508&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F333958889_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="424" frameborder="0" scrolling="no"><a href="https://medium.com/media/b3d47ae6433a058955ca936922e9175f/href">https://medium.com/media/b3d47ae6433a058955ca936922e9175f/href</a></iframe><p>While all the CodeDay stuff was going on, I was still not actually working at StudentRND, and I came up with a cool idea for a startup with my <a href="https://www.linkedin.com/in/jenniferschumaker">at-the-time-girlfriend</a> <a href="http://adamryman.com/">and</a> <a href="https://www.linkedin.com/in/paulcretu">some</a> <a href="https://twitter.com/david_d_tyler">other</a> <a href="https://medium.com/@vu0tran">friends</a>. This eventually became a real startup, and some of us moved to San Francisco, so I missed out on most of this year in StudentRND. To the left is a video of our pitch to 400+ investors.</p><p>In September-ish 2012, Edward came to San Francisco to ask companies for money. I still didn’t work for StudentRND, but he stayed at our house, and we ran through the pitch-deck together — <a href="http://assets.srnd.org/history/2012pitch.pdf">which I apparently saved!</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*LBytnQJKAfL59iHWBocL6A.png" /><figcaption><a href="http://assets.srnd.org/history/2012pitch.pdf">http://assets.srnd.org/history/2012pitch.pdf</a></figcaption></figure><p>From what I understand, after seeing this pitch, Splunk signed on for $10,000 to help us get to five cities.</p><h3>2013</h3><p>We hosted our first CodeDay San Francisco, and it was a big success! I found the kick-off deck we used:</p><p>Remember that map from the pitch deck earlier? We didn’t quite make it to all the cities, but by mid 2013 we were in quite a few:</p><ul><li>Seattle (where we started, obviously)</li><li>Portland (first outside of Seattle)</li><li>San Francisco (second outside of Seattle)</li><li>New York (third)</li><li>LA (fourth; not on the map above)</li></ul><p>In June, I quit my startup job, and moved back to Seattle.</p><p>Until September, I kept telling Edward I wouldn’t work for him, but I would do some volunteer work, because once he paid me, I had to do what he wanted. Eventually, I gave in and became StudentRND’s first Programs Director.</p><p>Edward and I put together a list of all the cities we wanted to experience CodeDay. Which really meant Edward and I searched “largest US cities” on Google, and went down the list. Here was our schedule for year zero of truly nation-wide CodeDay:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*KmZGlxUr5lpxMILQAKjkjg.png" /><figcaption>(Does email count as “found on my hard drive?”)</figcaption></figure><p>We needed some additional funding to make that happen, so we went back to our friends at Splunk with this new, much larger proposal.</p><p>Splunk signed on, as well as a few other sponsors, and we set to work expanding CodeDay. First, to Chicago and Des Moines (major thanks to Fisher Adelakin and Brett Neese for making that happen), then to, well, everywhere else.</p><p>We also closed the physical workspace, focusing full-time on CodeDay. No pictures of this; I didn’t take any because it was too sad.</p><h3>2014 and Beyond</h3><p>And, well, the rest is history. The history you probably already know, anyway. We continued to make plenty of scaling mistakes over the next several months, but eventually made it to 24 cities by the Spring of 2014, hitting Edward’s goal of a nation-wide non-profit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*z_SwGHoAb1PzzarxXZ9H2A.png" /><figcaption>(via <a href="https://srnd.org/open/minutes/2014-06-25">https://srnd.org/open/minutes/2014-06-25</a>)</figcaption></figure><p>Having achieved his goal, Edward left StudentRND in June of 2014, and I took over as Executive Director from there.</p><p>The best thing about this story is that it shows how quickly a great idea can take off. StudentRND existed from 2009–2012 with some small successes. In the two years after we came up with CodeDay, however, we grew from working with dozens of students in one city, to thousands in 25. Two years!</p><p>Also: Edward had a dream of bringing StudentRND to this many people — he even dropped out of university to make it happen. If you’re a fan of CodeDay, make sure to thank @EdwardStarcraft on Twitter.</p><p>I’ll leave you with this presentation. I don’t know what it was for, but apparently I made it in 2013.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*pMgYWxQo1IvcZRojQyjdRg.png" /><figcaption><a href="http://assets.srnd.org/history/juststart.ppt">http://assets.srnd.org/history/juststart.ppt</a></figcaption></figure><p>(Here’s what our website looked like from 2009 through today:)</p><ul><li><a href="https://web.archive.org/web/20091210055815/http://studentrnd.org/">2009</a></li><li><a href="https://web.archive.org/web/20100814030058/http://studentrnd.org/">2010</a></li><li><a href="https://web.archive.org/web/20111226231733/http://studentrnd.org/">2011</a></li><li><a href="https://web.archive.org/web/20121115051212/http://studentrnd.org/">2012</a></li><li><a href="https://web.archive.org/web/20131205065130/http://studentrnd.org/">2013</a></li><li><a href="https://web.archive.org/web/20150101063832/http://studentrnd.org/?">2014</a></li><li><a href="https://web.archive.org/web/20160228224523/https://studentrnd.org/">2015</a></li><li><a href="https://web.archive.org/web/20161001000000/https://srnd.org/">2016</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=946f175eddaa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/a-history-of-studentrnd-as-told-by-files-i-found-on-my-old-hard-drive-946f175eddaa">A History of StudentRND, As Told By Files I Found On My Old Hard Drive</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To Get an Internship in High School, Ignore Your School’s Résumé Advice]]></title>
            <link>https://medium.com/the-studentrnd-blog/to-get-an-internship-in-high-school-ignore-your-schools-advice-d48d6707baa?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/d48d6707baa</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[high-school]]></category>
            <category><![CDATA[resume]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Thu, 26 May 2016 23:29:04 GMT</pubDate>
            <atom:updated>2016-05-27T05:35:34.719Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dn18605bNW-j0eNQZjmXLw.jpeg" /><figcaption>Press photo: team I worked with to create a game for Microsoft’s Hunt the Wumpus competition in high school. My school insisted I not discuss this on my résumé except as one of my many “activities”. (Photo: Mary Decker/Redmond Reporter)</figcaption></figure><p>By my senior year of high school, I had created several successful open-source projects, won a few awards for coding, been featured in some local press, done some contract work, and even gotten an internship working on a platform for those “customers who bought this item also like…” sections.</p><p>Here’s the résumé my high school insisted I use:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*7SiUQ7R2POVZHkK2sRzmsg.png" /></figure><p>“Insisted” is putting it lightly. I turned in my actual résumé, which had already landed me an internship, and I was called to the administration office where a teacher threatened to hold me back from graduation unless I turned in a “real” one — the one you see above.</p><p>If you’re in high school, maybe you’re looking at this and thinking, “what’s wrong with this?” As someone who works with recruiters, as well as an employer of several interns over the years,<strong> let me be clear: this résumé is <em>awful.</em></strong></p><h3>What’s Wrong with School Résumés?</h3><p>A résumé is not a magical incantation. Employers do not hire you because your resume is formatted correctly. No hiring manager for a tech company has ever turned anyone down for failing to list their objective.</p><p>Résumés have one goal: summarize relevant information to convince someone you’re worth further investigation.</p><p>Employers receive stacks of résumé. When I listed a position for an intern at my last company, I received over 300 applications. A page requires 3–5 minutes to read, so to read all 300 would take 20 hours!</p><p>What employers do is skim first, then read promising ones in full. It’s not unusual to reject 90% of résumés within a few seconds of seeing them. Burying the relevant information is a great way to make sure you don’t make the cut.</p><p>Below, I’ve highlighted the relevant information in my school’s ideal résumé:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*QEPC2jB99jiH2suW2pcw-w.png" /></figure><h3>The Real Preferred Résumé Format</h3><p><strong>There is no real preferred résumé format! </strong>The reason the school-mandated format falls flat is because a standard format cannot summarize everyone’s relevant experience!</p><p>The ideal résumé depends on you and the job for which you’re applying!</p><p>What sets you apart from your peers? What would make an employer excited to meet you? What shows people, “this candidate knows his/her stuff?”</p><p>There’s no right answer here, but here are some things to consider:</p><ul><li><strong>Your Github link, if you have open source work.</strong></li><li><strong>Spotlight a particularly cool project or two.</strong> For example, I know someone who wrote a hobby operating system. That should be on there.</li><li><strong>Your blog,</strong> if you write about technical topics. (Or just spotlight a particularly relevant/interesting post.)</li><li><strong>Any projects you’ve done</strong> as a class/club/group/etc.</li><li><strong>Internships, unpaid work, contract work, etc.</strong> Make sure your most impressive work contains the most detail. Summarize less-impressive work.</li><li><strong>Awards you’ve won, </strong>if they’re relevant and recent. (e.g. do not list awards you won in middle school!)</li><li><strong>Press mentions.</strong></li><li><strong>CodeDays, game jams, and hackathons you’ve attended.</strong></li><li><strong>Publications and talks you’ve given.</strong></li><li><strong>Leadership experience,</strong> if you have it, particularly technical leadership (e.g. “lead a robotics team”). Don’t go into great detail here, just the role name will probably be fine.</li><li><strong>Relevant classes</strong> you’ve taken.</li><li><strong>Your GPA</strong> if it really sets you apart.</li></ul><p>Again, do not include that entire list! Your goal is both to highlight what sets you apart, and to avoid hiding it in a long list of unexceptional details.</p><p>There are also some things you do <em>have </em>to include. Luckily, it’s a short list: your name and contact info, at least the name of your current school, and at least the name and dates of prior employers.</p><h4>An Example</h4><p>Here’s a to-the-point resume I put together a few years ago:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*fR7nnb5F6PjVJ421YzLRcQ.png" /><figcaption>(Information is outdated.)</figcaption></figure><p>A few more closing notes:</p><ul><li>Your résumé should be one page. I have significant work experience, and I can still keep it to one page, because I remove older, less exciting information.</li><li>I recommend using a little color, a font other than Times New Roman, and a layout which makes sense for your content. If you stick to purely stock Word designs, you’re not going to stand out in a pile.</li><li>(Don’t get too carried away with the unique layouts. The end result should look enough like a résumé that employers will know how to skim it.)</li><li>Make sure your name is pretty big on the page!</li><li>If you’re turning in your résumé in-person, go to FedEx Office and have it printed on some nice paper!</li><li>Even with a nice résumé, as a high-schooler, you should expect to be rejected from 95% of companies to which you apply. As much as possible, reach out to small startups, try to talk directly with engineers (not HR or recruiters, who don’t actually know how to code), and reach out to lots of companies.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d48d6707baa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/to-get-an-internship-in-high-school-ignore-your-schools-advice-d48d6707baa">To Get an Internship in High School, Ignore Your School’s Résumé Advice</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mentorship at CodeDay]]></title>
            <link>https://medium.com/the-studentrnd-blog/mentorship-at-codeday-7c26b807a2f7?source=rss----f2bac48f2a58---4</link>
            <guid isPermaLink="false">https://medium.com/p/7c26b807a2f7</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Tyler Menezes]]></dc:creator>
            <pubDate>Thu, 05 May 2016 21:05:30 GMT</pubDate>
            <atom:updated>2017-05-08T20:20:40.915Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0m5WzuZKJNuV6UVja6spw.jpeg" /></figure><p>CodeDay happens six days a year, which means we spend the other 359 (366 this year!) thinking about how to improve the attendee experience. I have exciting news to share today on that front!</p><p>Mentors at CodeDay have been an afterthought since the very first event. CodeDay is an event about pushing yourself and learning something new, neither of which <em>require</em> external help. So we haven’t started a formal mentor program.</p><p>The last year has convinced us that mentors can really help attendees shine, however. Mentors in LA, Boca Raton, and San Francisco have shown that increasing the number of people available to help student can cut down on students waiting, and help unblock them faster.</p><p>This season, we made mentorship a priority, and have several exciting announcements to make.</p><h4>In-Person Mentorship</h4><p>Mentors will now be available through all events to support attendees as needed. As an attendee, you’ll be able to login to mentor.codeday.org to request help, and all appropriate mentors on duty will get a text message to dispatch them.</p><p>Mentors will also wear a nametag to identify what help they can provide:</p><ul><li>UX</li><li>Android/iOS Development</li><li>Web Development (HTML/CSS/Javascript)</li><li>Hardware/Electronics</li><li>Project Management</li><li>Unity</li><li>Misc. Code</li><li>Sponsor-Specific Technologies (e.g. Amazon Echo)</li></ul><h4>Slack</h4><p>Additionally, all attendees will have access to the StudentRND Slack. Slack, if you don’t know, is an easy-to-use group chat with the ability to create different sections for different topics.</p><p>We’ve been beta-testing ways to bring our community together for the last several months, including an attendee community forum, and a limited Slack test at certain events.</p><p>Now, for the first time, we’re inviting all attendees to come together in a single place. Mentors will be available in Slack throughout the event to provide support.</p><h3>Partners</h3><p>These programs are only possible thanks to the support of several partners.</p><h4>LexisNexis Risk Solutions, Splunk, and Oracle</h4><p>Our largest partners, LexisNexis Risk Solutions and Splunk, have continued to show their support for CodeDay by promoting mentoring opportunities to their employees. (Make sure to look out for these mentors — many past attendees have gotten jobs or internships out of connections they’ve made to volunteers from our partner companies!)</p><p>Oracle has also joined to support additional San Francisco Bay Area operations, including mentors.</p><h4>Hacker Fund</h4><p>In addition to mentors from our existing sponsors, we will have additional mentor support from Hacker Fund, a non-profit which works to build mentor communities for CS education.</p><p>Hacker Fund is providing 5–10 mentors in almost every CodeDay city, many of whom have much prior experience at summer camps, hackathons, hack hours, and community centers.</p><p>Mentors from Hacker Fund come from big companies, startups, and universities from around the US. The Hacker Fund team themselves were previously responsible for a large part of several large hackathons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c26b807a2f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-studentrnd-blog/mentorship-at-codeday-7c26b807a2f7">Mentorship at CodeDay</a> was originally published in <a href="https://medium.com/the-studentrnd-blog">The StudentRND Blog (Archived)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>