<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lauren Abrams on Medium]]></title>
        <description><![CDATA[Stories by Lauren Abrams on Medium]]></description>
        <link>https://medium.com/@labrams10?source=rss-c280d111dc12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0ccGxY2RCMPObKij</url>
            <title>Stories by Lauren Abrams on Medium</title>
            <link>https://medium.com/@labrams10?source=rss-c280d111dc12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:36:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@labrams10/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Temperamental World of Javascript Nomenclature]]></title>
            <link>https://medium.com/tech-at-power/the-temperamental-world-of-javascript-nomenclature-var-let-const-c6df9ba60379?source=rss-c280d111dc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6df9ba60379</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[declarative-programming]]></category>
            <category><![CDATA[variables]]></category>
            <dc:creator><![CDATA[Lauren Abrams]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 15:25:50 GMT</pubDate>
            <atom:updated>2018-08-23T13:51:29.476Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post is written by a Nitro Developer Bootcamp Student Developer. To learn more about this program, follow the </em><a href="https://blog.techatpower.com/benefits-of-training-your-own-entry-level-developers-3d23103df7af"><strong><em>Training Your Own Entry Level Developers</em></strong></a><strong><em> </em></strong><em>blog series on </em><strong><em>Tech at Power</em></strong><em>.</em></p><h3>The Temperamental World of Javascript Nomenclature: var, let, const</h3><p>There are several unspoken rules in the world of programming, but one particular goal that supersedes all others — keep your code comprehensible and straight forward; integrating a simplistic nature will ensure longevity and functionality. Writing code that constantly requires edits and refactoring isn’t something to strive for, and certainly won’t go very far.</p><p>It should come as no surprise to anyone even semi-fluent in any programming language that there are countless ways to achieve a singular goal. Through trial and error — and years of experience — specific techniques that lead to more functional code emerge; luckily, there are a few hints to beginners that will get you on the right track.</p><h4>The Ecclectic World of Variables</h4><p>Variables are one of the foundational pillars of JavaScript, and anyone who is embarking on conquering this language should quickly befriend them.</p><p>Variables act as a sort of storage container that can be accessed after they’re defined. They can contain essentially any data type, from numbers, to strings, to true/false boolean values. The bittersweet fact about variables, however, is that their values can change depending on how they’re initially defined: enter var, let, and const.</p><h4>var</h4><p>Although varallows for a lot of versatility, it really should be avoided most of the time if good-practices are a priority.</p><p>For all-intensive purposes, here is an example of varin action:</p><pre><strong>var</strong> country = &quot;France&quot;;<br>//=&gt; <em>undefined</em> </pre><pre>country = &quot;Italy&quot;;<br>//=&gt; <em>&quot;Italy&quot;;</em></pre><pre>country = &quot;Greece&quot;;<br>//=&gt; <em>&quot;Greece&quot;;</em></pre><pre>country;<br>//=&gt; <em>&quot;Greece&quot;;</em></pre><p>A few things to note here. Although varoffers a lot of user-friendly freedom, you can see that the value of “country” — initially defined as “France” — can be redefined over and over again. This makes it impossible to keep track of where and when these variables are redefined, especially when working with large amounts of data. Luckily, there are variations in the JavaScript world of variable declarations that offer a little more stability.</p><p><strong>let</strong></p><p>JavaScript ES2015 introduced new ways to declare variables in the language. Although still not bulletproof, letoffered developers a more reliable way to establish their variables:</p><pre><strong>let</strong> elevation = 5280;<br>//=&gt; <em>undefined</em></pre><pre><strong>let</strong> elevation = &quot;My name is Ada.&quot;;<br>//=&gt; <em>Uncaught SyntaxError: Identifier &#39;elevation&#39; has already been declared</em></pre><p>As you can see, on the occasion that an attempt is made to declare one particular variable twice, an error will be thrown(unlike var).</p><p>Let does share some similarities with varthough:</p><pre><strong>let</strong> elevation = 5280;<br>//=&gt; <em>undefined</em></pre><pre>elevation = &quot;My name is Ada.&quot;;<br>//=&gt; <em>&quot;My name is Ada.&quot;</em></pre><pre><strong>typeof </strong>elevation<br>//=&gt; <em>&quot;string&quot;</em></pre><p>Through proper syntax, variables do have the ability to be redefined when using let, which can be beneficial (and necessary) under certain circumstances. However, ES2015 introduced an additional variable declaration tool, one that’s even more impenetrable than it’s predecessors.</p><p><strong>The One to Rule Them All: const</strong></p><p>With ES2015 came const<em>— </em>the preferred defining instrument for variables that prevents them from not only being redefined, but also from being reassigned. When fresh eyes are scanning your code and they see const, it’s reassuring to know that every time that variable appears, it contains the same value or points to the same object throughout the program.</p><pre><strong>const</strong> elevation = 5280<br>//=&gt; <em>undefined</em></pre><pre>elevation = 2018<br>//=&gt; <em>Uncaught TypeError: Assignment to constant variable.</em></pre><p>Another defining characteristic to constlies in the fact that it requires an assignment value the moment it is implemented, due to the fact that once defined, the variable cannot be reassigned.</p><p><strong>Eeny, Meeny, Miny, Moe</strong></p><p>In general, it’s a safe assumption that varshould be avoided. It allows for too much fluidity and is hard to keep track.</p><p>The usage of letdepends entirely on the intended functionality of the variable at hand; if your code is going to require a variable’s value to change, letis the preferred declaration tool that allows some versatility while also maintaining some safe guards.</p><p>In most cases, however — it’s constthat should be the go-to. The inherent security is priceless, and will keep your code concise and reliable even after it leaves your hands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6df9ba60379" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/the-temperamental-world-of-javascript-nomenclature-var-let-const-c6df9ba60379">The Temperamental World of Javascript Nomenclature</a> was originally published in <a href="https://medium.com/tech-at-power">Tech at Power</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This post was written jointly by Benjamin Krigel and Lauren Abrams, two Nitro Developer Bootcamp…]]></title>
            <link>https://medium.com/tech-at-power/the-road-to-revolutionary-why-women-belong-in-tech-e902a25491da?source=rss-c280d111dc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/e902a25491da</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[equality]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Lauren Abrams]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 02:46:31 GMT</pubDate>
            <atom:updated>2018-07-25T08:51:38.967Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post was written jointly by Benjamin Krigel and Lauren Abrams, two Nitro Developer Bootcamp Student Developers. To learn more about this program, follow the </em><a href="https://blog.techatpower.com/benefits-of-training-your-own-entry-level-developers-3d23103df7af"><strong><em>Training Your Own Entry Level Developers</em></strong></a><strong><em> </em></strong><em>blog series on </em><strong><em>Tech at Power</em></strong><em>.</em></p><h3>The Road to Revolutionary: Why Women Belong in Tech</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ryYoghrXkMT0SRVKgWDiQQ.jpeg" /></figure><p>Determining how certain stereotypes come into existence can be a tricky game to play; everyone can agree that our society is riddled with them, but cementing when — and <em>how — </em>they came to be, is a whole different animal. The million dollar question remains: when it comes to tech, where are all the women?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMvODwVovmnwcpdjeNoUhg.jpeg" /></figure><p><strong>An Insidious Gender Disparity</strong></p><p>So why aren’t more women interested in tech? Is there an influence (intentional or not) that from an early age manages to convince young girls that a field in science — computer science, specifically — is not the path for them? There are several undeniable factors that have been proven to affect women diverging from the tech world once they enter the work force (and even prior to that) — which allows us to at least work on identifying part of the problem.</p><p>Assuming <em>at least</em> half of all college applicants are women, the lack of female presence within computer science majors highlights a key moment when women tend to diverge from tech. Was it even an option on the table to begin? This question uncovers yet another problem to confront on the topic: are women being encouraged to pursue such a degree? At what point are they introduced to the field, if at all? PNAS offered some insight into the problem in a <a href="http://www.pnas.org/content/early/2012/09/14/1211286109">study</a> they conducted that revealed subtle gender biases do in fact exist — this one illuminating how male students in science faculties are actually favored.</p><p>However, determining the root of the problem most likely traces back long before college, with signs emerging even during high school. <a href="https://www.usnews.com/news/blogs/data-mine/2014/01/14/ap-test-shows-wide-gender-gap-in-computer-science-physics">US News</a> reported that a large gender disparity amongst young girls in computer science and physics arose from their AP Test Scores; it wasn’t that they were lower than their male counterparts, the scores just simply weren’t there — indicating that high school girls weren’t even taking the exams.</p><p>So, the glaring question remains: why are women so deterred from this field? Further, when it comes to the workforce, men typically <a href="http://www.randalolson.com/2014/06/14/percentage-of-bachelors-degrees-conferred-to-women-by-major-1970-2012/">outnumber women 8 to 2</a> in tech. Sure, it has its stereotypes — i.e. the nerdy, introverted man being its only constituents. Also, science fields are very logic-oriented, which is where another very common misconception lies; if you don’t have a particular affinity towards the more logic-based ways of thinking and learning, then failure within the field is imminent (so better to go with the Plan B liberal arts major). These considerations offer a glimpse into the societal erosion that causes the majority of women to stray away from even <em>considering</em> the option of a science-heavy career path.</p><p>One additional misconception is that careers within tech ultimately limit one’s ability to express their own innate creativity. Women are drawn to careers in care-taker roles and those that allow for a more prominent level of creative expression. A <a href="https://www.independent.co.uk/life-style/inspired-debate-are-women-better-able-to-express-their-creativity-in-the-modern-age-5346680.html">heavy debate</a> resides around this topic — whether women find it easier to access an inherent creativity than men in the modern age. Regardless, it is a common wives tale that has long been due for a healthy de-bunking; almost every stage of software development — a common career path within computer science — requires an enormous amount of creativity. Although it requires a more off-the-beaten-path medium of expressing creativity, it makes for a more holistic, well-rounded developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c333d_YNEHG4q3UDb1wTA.jpeg" /></figure><p><strong>Tackling The Dilemma</strong></p><p>The solution to integrating more women in the tech world is a tricky one. After all, if it were simple, there would be an even split between men and women, and the exponential advancement of the tech world would be at the hands of an incredibly balanced team.</p><p>It’s hard to identify the moment in time when girls fall into the trap of believing computers and the tech world only belong to men. At the very least, a drastic effort should be made to introduce girls to technology at a young age, whether that be through summer camps or interactive lessons in an academic setting — it’s time for barbies to take a hike.</p><p>The Harvard Business Review wrote an <a href="https://hbr.org/2017/04/women-dominate-college-majors-that-lead-to-lower-paying-work">article</a> about how women continue to dominate the majors in college that ultimately lead to lower-paying jobs (nursing, teaching, etc). Oftentimes, women aren’t even aware of the earning potential that exists amongst careers in tech. It argues that “by showing young women the facts about what they could potentially earn, more of them might choose a physics or engineering major.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zxqXoiRyIEeXhWSU5zFnnQ.jpeg" /></figure><p><strong>It’s Good For Business</strong></p><p>When the topic of gender imbalance in the workplace is discussed, the rhetoric in favor of greater diversity often rests on moral or emotional arguments. Those who strive to foster an atmosphere of equality generally do so, at least in part, by claiming it is “the right thing to do.” And while there will always be some people who contend that diversity in the workplace is not inherently a good thing or even the right thing outright, many people who do sympathize with the moral arguments in favor of gender equality also don’t believe that “diversity for diversity’s sake” alone is a compelling reason to enact meaningful change. Many people in both the tech world and also the business world at large only care to dedicate their time and resources to address factors that directly affect their bottom line. There is a common belief that, while diversity is perhaps a good thing in an ethical sense, it is not determinatively a good thing in a business sense. This misconception is reinforced by the fact that there is admittedly no conclusive statistical evidence that directly links greater diversity to better business performance. Despite the lack of definitive proof, there is a profusion of empirical evidence to support the argument that a more diverse staff will produce better results than its homogenous counterpart.</p><p>Before we dive into the numbers, let’s examine some of the abstract benefits that gender diversity can have on business. There exists a widely accepted idea that products are best designed by employees who accurately reflect users. In most cases in the tech world, heavily male staffs are designing applications whose users are 50% female. It is a biological fact that men and women think and act differently from each other, and so it is easy to see how a program designed primarily by men could either intentionally or accidentally overlook features that would enhance the user experience for its female audience. An overt example of this could be found in voice recognition software; because it was designed and tested mostly by men, there were countless reports that upon first release, the <a href="https://techcrunch.com/2016/11/16/when-bias-in-product-design-means-life-or-death/">technology struggled to recognize higher-pitched female voices</a>. If the development team in this example were to have included more females, this major flaw in the software ostensibly could have been avoided before it reached production, and ultimately saved the company time and money spent redeveloping the technology.</p><p>Another abstract benefit to diversity is that it produces a much wider range of perspectives. Having as many varying opinions and points of view as possible increases any team’s problem-solving capacity and accuracy. Homogenous groups tend to think more similarly than heterogenous groups, meaning innovation is less likely to emerge.</p><p>Furthermore, companies that have greater gender-balance on average <a href="http://www.ncwit.org/sites/default/files/resources/impactgenderdiversitytechbusinessperformance_print.pdf">report better scores of employee happiness and workplace culture</a>. Many tech companies have famously invested in workplace culture as a means to attract applicants, increase employee retention rates, and, most importantly, keep their employees happy. If happier employees are more productive, and inclusive cultures produce happier employees, it is logical to surmise that companies prioritizing gender equality will in-turn see overall productivity increase.</p><p>These abstract arguments in favor of gender-equality are reinforced by tangible and measurable benefits, as well. According to <a href="http://www.ncwit.org/sites/default/files/resources/impactgenderdiversitytechbusinessperformance_print.pdf">research</a> conducted by the National Center for Women &amp; Information Technology (NCWIT), tech companies that boast greater gender diversity demonstrate superior team dynamics and productivity, are more likely to stay on schedule and under budget, and are more likely to have higher employee performance ratings and pay bonuses. Additionally, gender-diverse teams show evidence of better financial performance, especially when there are women in upper-management. Tech companies led by women <a href="https://www.weforum.org/agenda/2017/11/the-tech-industry-needs-more-women-heres-how-to-make-it-happen-d1eec473-48cc-4801-bd40-dfba040b0e4a/">achieve a 35% higher return on investment </a>than those run by men and, despite receiving 50% less venture capital funding, produce 20% higher revenues. Despite the evidence, there remains a dearth of women in leadership roles in the tech industry.</p><p>Looking at these issues through an even wider lens, there is an argument to support inclusivity that goes beyond what is right or what is good for business but rather what is good for the national economy. In the United States, there is a massive disparity between tech jobs available and qualified American applicants, which explains why the industry has such a large reliance on outsourced labor. <a href="https://techcrunch.com/2016/05/10/the-lack-of-women-in-tech-is-more-than-a-pipeline-problem/">Trends</a> suggest that by 2020, qualified Americans will only be able to fill 29% of domestic tech openings. That void can be filled in large part by encouraging American women to pursue technical careers (<a href="https://www.nextgeneration.ie/blog/why-arent-there-more-women-in-tech/">currently only 5% of American women study science, technology, or math-related fields</a>) rather than continuing to rely on foreign labor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y-djx_fBY4GWJoNR6pVAw.jpeg" /></figure><p><strong>Men In Tech Need To Be Allies</strong></p><p>It’s common for women to be advocates for their female peers, but for a true shift in the industry to take place, it is much more critical that men in tech support women too. This is particularly true when upper-management in the industry has the most power to enact change and is<a href="https://www.weforum.org/agenda/2017/11/the-tech-industry-needs-more-women-heres-how-to-make-it-happen-d1eec473-48cc-4801-bd40-dfba040b0e4a/"> currently over 95% male.</a> One of the largest hurdles in the quest for gender equality is a pipeline issue, as the applicant pool on average is only 20% female. But, before we can see a rise in female applicants, we must foster a culture of inclusivity — a culture that nurtures and encourages female excellence — in order to attract those applicants. According to <a href="https://www.forbes.com/sites/quora/2017/02/28/why-women-leave-the-tech-industry-at-a-45-higher-rate-than-men/#5f10bc354216">NCWIT research</a>, women are 45% more likely to leave a tech job within a year of hire than men and cite lack of support as the main cause for departure. It is crucial that men in the tech world actively encourage and support diversity, rather than hiring women for the sake of filling quotas and expecting them to assimilate into the dominant male culture. Corporate involvement in supporting female employees is another area for improvement. An easy way to address the issue of corporate apathy is to promote more women. Moreover, men in tech must facilitate open and honest dialogue and assume that people are coming from a positive place when they share their opinions and experiences. They must give both women and men a chance to voice their struggles and speak out about unique issues they face in the workplace. It is through civil discourse, celebration of diversity, and equal opportunity for advancement that men can best support women in tech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqlvrNZCGwVcXL444rvRqg.jpeg" /></figure><p><strong>What Can We Do?</strong></p><p>The continuing integration of technology into every avenue of society highlights the importance of introducing all children at a young age to the world of computer science, but especially girls. Small exercises that encourage them to create an idea for a health science app, or a visually engaging game for young children, are all great ideas to slowly introduce the creation of technology to children, in the hopes that it will plant seeds that ultimately lead to a heavier influx of women interested in becoming a part of the tech world.</p><p><em>This post was written jointly by Benjamin Krigel and Lauren Abrams.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e902a25491da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/the-road-to-revolutionary-why-women-belong-in-tech-e902a25491da">This post was written jointly by Benjamin Krigel and Lauren Abrams, two Nitro Developer Bootcamp…</a> was originally published in <a href="https://medium.com/tech-at-power">Tech at Power</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This post is written by a Nitro Developer Bootcamp Student Developer.]]></title>
            <link>https://medium.com/tech-at-power/ruby-case-statements-2ad7691bd90d?source=rss-c280d111dc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ad7691bd90d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[student-life]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Lauren Abrams]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 12:36:32 GMT</pubDate>
            <atom:updated>2018-06-13T20:18:40.532Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post is written by a Nitro Developer Bootcamp Student Developer. To learn more about this program, follow the </em><a href="https://blog.techatpower.com/benefits-of-training-your-own-entry-level-developers-3d23103df7af"><strong><em>Training Your Own Entry Level Developers</em></strong></a><strong><em> </em></strong><em>blog series on </em><strong><em>Tech at Power</em></strong><em>.</em></p><h3>Ruby Case Statements</h3><p>Melding versatility and functionality is one of the many things Ruby case statements allow its users to embrace. As our curriculum frequently reminds us, programmers are “lazy” — so, executing code with the most “value” or “bang” for our buck — with as little headache as possible — is the ultimate goal. How do we continue this trend in order to efficiently — and effectively — implement the highest functioning code into our programs? Case statements offer a great starting point.</p><p><strong>The Case Equality Operator ( === )</strong></p><p>This method is very context-specific; with anything in Ruby, it deals with objects; so when it comes to the case equality operator, the comparison being executed is completely contingent on <em>what</em> exactly the objects that are being compared are:</p><pre>(1..5) === 3              # =&gt; true<br>(1..5) === 6              # =&gt; false</pre><pre>Integer === 42            # =&gt; true<br>Integer === &#39;forty-two&#39;   # =&gt; false</pre><pre>/ell/ === &#39;Hello&#39;         # =&gt; true<br>/ell/ === &#39;Knox&#39;          # =&gt; false</pre><p>Case statements can also function using <strong>case/when</strong>:</p><pre>case <strong>capacity</strong><br>when 0<br>  &quot;You ran out of gas.&quot;<br>when 1..20<br>  &quot;The tank is almost empty. Quickly, find a gas station!&quot;<br>when 21..70<br>  &quot;You should be ok for now.&quot;<br>when 70..100<br>  &quot;The tank is almost full.&quot;<br>else<br>  &quot;Error: capacity has an invalid value (#{capacity})&quot;<br>end</pre><p>(<em>Examples pulled from </em><a href="https://stackoverflow.com/questions/4467538/what-does-the-operator-do-in-ruby"><em>StackOverflow</em></a><em> and </em><a href="https://www.skorks.com/2009/08/how-a-ruby-case-statement-works-and-what-you-can-do-with-it/"><em>Skorks</em></a><em>)</em></p><p>One thing to note is that this operator has absolutely <em>nothing</em> to do with equality.</p><p>That’s why referring to this operator as having anything to do with “equality” can get a little sticky (and difficult to understand). A good starting point is to define the case’s parameters in plain english. You are setting conditions for a specific instance that is adjusted on a <em>case by case</em> basis. In the example with gas tank capacity, a different message is output depending on where the value of capacity currently resides.</p><p>0 is not equal to the phrase You ran out of gas. That’s nonsensical. However, in the <em>case</em> of “capacity”, when the value of that variable is equal to 0, the condition set forth by the operator has been met. Thus, the appropriate value will be output, which in this case is a predetermined string.</p><h3>So what?</h3><p>Is there any benefit to using case statements over other Ruby methods? There are many ways to accomplish any one method in Ruby, and case statements offer another versatile option.</p><p>For example, when confronted with an instance where an <strong>if/elsif/else</strong> statement is required, a case statement could replace that code while maintaining the same functionality. Following this pattern also provides the code with a more “syntactic sugar” feel.</p><p>For more information on Ruby case statements, <a href="https://www.skorks.com/2009/08/how-a-ruby-case-statement-works-and-what-you-can-do-with-it/">Skorks</a> has a great article that offers additional examples of the variety of ways this method can be implemented into your code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ad7691bd90d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/ruby-case-statements-2ad7691bd90d">This post is written by a Nitro Developer Bootcamp Student Developer.</a> was originally published in <a href="https://medium.com/tech-at-power">Tech at Power</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>