<?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 Katie Weber on Medium]]></title>
        <description><![CDATA[Stories by Katie Weber on Medium]]></description>
        <link>https://medium.com/@katieweber_93912?source=rss-34d2063fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d_S0nMNDe1XYyiRqkTovcw.jpeg</url>
            <title>Stories by Katie Weber on Medium</title>
            <link>https://medium.com/@katieweber_93912?source=rss-34d2063fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:11:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katieweber_93912/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[Alan Kay]]></title>
            <link>https://medium.com/tech-at-power/alan-kay-certified-badass-godfather-of-modern-programming-languages-4f9dac64b5bc?source=rss-34d2063fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f9dac64b5bc</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[alan-kay]]></category>
            <category><![CDATA[object-oriented]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[smalltalk]]></category>
            <dc:creator><![CDATA[Katie Weber]]></dc:creator>
            <pubDate>Thu, 23 Aug 2018 12:33:54 GMT</pubDate>
            <atom:updated>2018-08-24T15:15:48.349Z</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>Alan Kay: Certified Badass &amp; Godfather of Modern Programming Languages</h3><p>Let’s turn back the clocks to a time when personal computers were not a household staple — a time when the computer’s primary intended use was for defense logistics and educational purposes, not for consuming endless amounts of social media and videos of puppies and babies. In this time, the way the computer works was a bit difficult for the average human to understand.</p><p>The computer was shrouded in mystery. Functional programming languages were the staple of the industry. These languages were written by humans for computers to understand. With functional programming’s roots in lambda calculus, they depend heavily on calculations and recursion, or the repeated application of a procedure or definition.</p><p>Fast forward to the present day, now we have at least one computer, tablet, or smartphone in just about every household across the country. If computers had remained in this mathematical state, how did we get here? Not too long ago, there were a group of people who argued for and understood that people all have different learning styles and dedicated their life’s work to making computers accessible to all types of people.</p><p>Alan Kay is generally known as one of the godfathers of modern computer engineering and computer programming. He has a laundry list of awards, including a Turing Award, and is decorated in degrees and honorary professorships. However, he has an interesting past that brought him to where he is today.</p><p>Kay was born May 17, 1940 in Springfield, Mass., but spent most of his childhood in the New York metropolitan area. Here he attended the prestigious Brooklyn Technical High School. However, before he could finish he was kicked out (primarily) for insubordination. Having enough credits to graduate, Kay continued on to Bethany College in West Virginia where he studied Biology with a minor in Mathematics. Once again, Kay was asked to leave by administration before he could complete his degree. This time it was for protesting the school’s Jewish quota, rather than insubordination.</p><p>After leaving Bethany, Kay moved to Denver, Colo. where he taught guitar for about a year before the local draft board inquired about his non-student status. At this point Kay swiftly enlisted in the Air Force, where he was billeted as a computer programmer. This was a bit unusual because this was primarily a woman’s role in the military at this time, due to the secretarial nature of the position. However, Kay exceeded in this role, developing an early predecessor of a cross-platform file transfer system.</p><p>After being discharged, Kay enrolled at the University of Colorado Boulder, where he earned his B.S. in Mathematics and Molecular Biology in 1966. He immediately enrolled in graduate school at the University of Utah College of Engineering where he received his M.S. in Electrical Engineering in 1968 and then a Ph.D. in Computer Science in 1969. Kay’s doctoral dissertation was on a computer language he invented called <em>FLEX: A Flexible Extendable Language. FLEX </em>would later evolve into something much bigger.</p><p>After college, Kay joined forces with MIT fellow, Seymour Papert. He learned the logo programming language and studied the research of Jean Piaget and constructionist learning: a concept where learners construct models to resemble the outside world, advocating student based and discovery oriented learning.</p><p>Taking this newfound knowledge with him to his position at Xerox PARC, Kay led the way as a visionary for modern computing. He is credited for the inventions of the modern graphical user interface (GUI) and the ancestor of the laptop and tablet, the Dynabook. At Parc he also built upon his <em>FLEX</em> language to create a language that would be known as <em>Smalltalk</em>. <em>Smalltalk</em> is one of the first known object-oriented programming languages, making use of the terms “class” and “object” and making use of “message passing” as a means of communication. The language came complete with a debugger and a developer environment.</p><p>Kay’s work with Smalltalk at PARC would go on to spark a revolution in computer programming. While Smalltalk was one of the first object-oriented languages, Objective C++ is credited with making object-orientation widely accepted in the marketplace. Up until 2017, a variation of Smalltalk was still in the list of Top 26 Favorite Programming Languages. It would go on to inspire the creation of common languages we still use today like Ruby, Python, and Java. Modern object-oriented languages expanded a bit and now include features like classes, polymorphism, association, inheritance, and encapsulation.</p><p>The name Alan Kay is now engrained in just about every facet of modern computing, from the display to the way it’s programmed. With a badass and nontraditional past, he blazed the trail of computer programming, going where many people had been afraid to go and is responsible of object-oriented programming making it to the mainstream. Kay’s work is best summed up when he said, “the best way to predict the future is to invent it.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f9dac64b5bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/alan-kay-certified-badass-godfather-of-modern-programming-languages-4f9dac64b5bc">Alan Kay</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/what-about-crud-8f87b3240dd4?source=rss-34d2063fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f87b3240dd4</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[crud]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Katie Weber]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 13:02:03 GMT</pubDate>
            <atom:updated>2018-07-18T12:19:09.250Z</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>What About CRUD</h3><p>Nearly every modern dynamic website shares a few of the same features: a database to store data, a querying language, such as SQL, to communicate with the database, a framework to build your application, such as Rails or Sinatra, and HTML and CSS to wrap data from the database to present in the browser. The acronym CRUD refers to the basic data interactions one would experience in a web application — Create, Read, Update, and Delete. These four actions are typically what a user and/or administrator will interact with. Because of this, it becomes important to decide what CRUD actions you have readily available to your users and administrators. Imagine an e-commerce site that requires users to sign up and after signing up, they can buy or sell items. You will find some really great examples of CRUD in the processes of these interactions.</p><p>I bet you’ve used CRUD many times without even knowing it. When registering as a new user on a site — Congrats! — you’ve just performed your very first CRUD action. The registration form rendered on a website submits the data you’ve entered back to the server and <em>creates</em> a new user. From there your information is typically encrypted and stored until the next time you access the website. As a SQL request this would look something like this: INSERT INTO USERS (ID, NAME, EMAIL, USERNAME, PASSWORD) VALUES (1, &quot;Bob Smith&quot;, &quot;bsmith007@aol.com&quot; &quot;bsmith007&quot;, &quot;MyPassword&quot;);. However, this is not what the user would see. This would likely render an HTML form with input fields for name, email, username, and password. The ID assigns itself autonomously based on the order the user was created in.</p><p>Here’s another CRUD action I’ve bet you’ve used and never even realized: the <em>read</em> action. After you’ve registered yourself as a user on a shopping website (let’s call it Clamazon), you will likely want to search for products you would like to buy. In a search field, you may type in a search for items that have “exercise bands” in their name, the website would then display a list of all items containing “exercise bands” somewhere in their name field. As a SQL request you would see SELECT * FROM ITEMS WHERE NAME=&quot;exercise bands&quot;;. This * operator selects all the information associated to an item that has the name of “exercise bands.” As the site owner, we may not want a user to be able to see all of the data we’ve just queried. For example, the user doesn’t necessarily need to know the unique ID the item has, but it’s pretty essential to us as the administrator. The end user would probably be more interested in seeing a description for the item and its price, so the administrator would choose to only display these pieces and to keep the others hidden.</p><p>A user could then add these items into their shopping cart. To the user, it just looks like the item is in their cart. However, there are some more complex relationships happening under the hood here. We know that we have tables for items and for users, but how do we tell an item that it belongs to the user? There is likely a join table called something like USER_CART, which serves as the relationship between items and users. The user has_one :user_cart, the cart belongs_to :user and has_many :items. Now every time you click an “add to cart” button, you can visualize the process of an item being added to a user’s cart.</p><p>After we register ourselves as a Clamazon user, and we purchase some items, we may need to <em>update</em> the information associated with our account. For example, maybe the email address you created in college doesn’t exist anymore and you’d like to change it to your new professional email address. We’ll update our very first user Bob as an example. Bob would like to change his email from “bsmith007@aol.com” to his new Gmail account “b.smith_007@gmail.com.” To do so, he would navigate to his user profile, click on the “edit settings” button, and then choose to edit his email. Under the hood this is rendering a form that takes Bob’s existing information and submits a SQL request to update it with his newly input information. The SQL request would subsequently look like this: UPDATE USERS SET EMAIL=&quot;b.smith_007@gmail.com&quot; WHERE ID=1;. Because Bob has a unique ID with a value of 1 this query ensures we are not accidentally updating the email address for every Bob Smith who has an account on our site. Look at how many CRUD actions you’ve performed without even knowing!</p><p>Now that we’ve created, read, and updated items in our database, we are left with our final CRUD operation: <em>delete. </em>Imagine you are an administrator for Clamazon and — oh no! — one of your retailers tells you they are discontinuing their exercise bands. How will you remove the exercise bands from your site?! If you guessed CRUD, you are correct! The administrator likely has access to a “delete” button available on all items. Under the hood, this button submits a delete request to the database to remove this specific item and would look like this DELETE FROM ITEMS WHERE NAME=&quot;exercise bands&quot;;. This example assumes that there is only one item named “exercise bands” listed on Clamazon, otherwise you would need to include the unique ID in this query.</p><p>CRUD operations exist in just about every dynamic website you will access. Everyday we create, post, edit, etc. These are essential functions in just about every site. Going forward, you should now have a better understanding of what is happening behind the scenes when you are using forms or submitting requests on a website!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f87b3240dd4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/what-about-crud-8f87b3240dd4">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>
        <item>
            <title><![CDATA[This post is written by a Nitro Developer Bootcamp Student Developer.]]></title>
            <link>https://medium.com/tech-at-power/this-post-is-written-by-a-nitro-developer-bootcamp-student-developer-1313e8bdc4ae?source=rss-34d2063fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1313e8bdc4ae</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Katie Weber]]></dc:creator>
            <pubDate>Wed, 13 Jun 2018 20:20:19 GMT</pubDate>
            <atom:updated>2018-06-14T13:25:13.988Z</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’s Versatility: Using “If” and “Unless”</h3><p>One of my favorite parts of learning how to write in the Ruby language is the versatility you have. Two people coding to solve the same problem can have totally separate solutions. Neither one of these two solutions is more right or wrong than the other.</p><p>To illustrate Ruby’s versatility, let’s take a look at a pair of my favorite statements: ‘if’ and ‘unless.’ These two modifiers are the inverse of each other, meaning they will yield opposite results. For example, let’s say we want to write a simple method that checks to see whether or not a homeowner has the most energy efficient window on the market. We can use an if statement to achieve this, which would look like this:</p><pre>sl2700 = true<br>if sl2700<br>  return &quot;Congrats! You have the most energy efficient window on<br>  the market!&quot;<br>else<br>  return &quot;I stopped by because I noticed you have the original<br>  windows!&quot;<br>end</pre><p>Alternatively, we could write the opposite using a bang (!) operator. The bang operator negates whatever is stated after it, so for example != would read as “does not equal” and !true would read as “not true.” The opposite method above would look like this with a bang operator:</p><pre>sl2700 = true<br>if !sl2700<br>  return &quot;I stopped by because I noticed you have the original<br>  windows!&quot;<br>else<br>  return &quot;Congrats! You have the most energy efficient window on<br>  the market!&quot;<br>end</pre><p>Now doesn’t the above statement look a little confusing? “If not sl2700” doesn’t necessarily roll off the tongue. As a lazy Ruby programmer, we understand that we want to make our code as easy to read as possible. What if we could achieve the same results but not use that pesky bang operator? Why not try writing the same with a more readable unless statement? Let’s see how this would look:</p><pre>sl2700 = true<br>unless sl2700<br>  return &quot;I stopped by because I noticed you have the original<br>  windows!&quot;<br>else<br>  return &quot;Congrats! You have the most energy efficient window on<br>  the market!&quot;<br>end</pre><p>This piece of code is much easier to read and still accomplishes the same desired effect.</p><p>Now, there are cases when unless simply will not work. For example, when using multiple conditionals (elsif statements) using unless will raise a syntax error. For best practice, unless should be used primarily for evaluating true/false statements or in cases where there are only two conditionals.</p><p>Again, this is not to say one way is better than the other. This just goes to show how versatile Ruby can be. If you are still feeling confused about when you should use if or unless the blog RailsTips offers some <a href="http://www.railstips.org/blog/archives/2008/12/01/unless-the-abused-ruby-conditional/">friendly advice</a> on which might work best on a case by case basis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1313e8bdc4ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-power/this-post-is-written-by-a-nitro-developer-bootcamp-student-developer-1313e8bdc4ae">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>