<?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 Adrienne Alyzee on Medium]]></title>
        <description><![CDATA[Stories by Adrienne Alyzee on Medium]]></description>
        <link>https://medium.com/@adriennera?source=rss-3a9f137fb4e2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pcgtUWO1pTsVXmcnu-Aqng.jpeg</url>
            <title>Stories by Adrienne Alyzee on Medium</title>
            <link>https://medium.com/@adriennera?source=rss-3a9f137fb4e2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:42:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adriennera/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[Breaking through the design process — lessons in prototyping a mobile app]]></title>
            <link>https://medium.com/@adriennera/breaking-through-the-design-process-lessons-in-prototyping-a-mobile-app-32c5f98555e8?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/32c5f98555e8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 03:59:44 GMT</pubDate>
            <atom:updated>2018-11-18T04:05:07.228Z</atom:updated>
            <content:encoded><![CDATA[<h3>Breaking through the design process — lessons from prototyping a mobile app</h3><p>The common cultural narrative would tell you that people are either born with a knack for design or they’re not. The less sexy truth is, anyone who has the right design process can also design elegant and intuitive products. So what is the right design process? Ideally, you want a design process where you can learn a lot and iterate quickly. This tends to be easy if you are methodical — being methodical makes it possible to articulate your process in a way on which you can evaluate and iterate. This is the best way to ensure that your process is always improving. When you take a methodical approach to design, you gain insights about the inner workings of human needs and desires, and how those might generalize to a broader global audience— which is different from adopting Airbnb’s sign-up flow to your own web app. While adopting works for scenarios that are similar to yours, making design decisions by example will result in clunky products that may not actually solve user needs. And it’s hard to come up with truly novel and innovative solutions when you outsource your thinking. Using first principles, on the other hand, allows you to to form deep intuitions about the principles involved in great design, so you can design truly groundbreaking products.</p><p>While there are many blogposts and books on design, most talk about design principles, rather than the process necessary to get to those principles. This case study describes my first principles approach to design, through the lens of building Spindle, an iOS app for quickly building webpages on your mobile phone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pDhgxHlxM-olxzDcnzizqg.png" /></figure><h4>Use cases</h4><ul><li>You’re hosting a party and want a personalized page to share your event</li><li>You just went on a camping trip and want a page of pictures</li><li>It’s Mother’s Day and you want to create a page celebrating your Mom</li></ul><p>Watch a video of Spindle in action.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F53j8531eTm4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D53j8531eTm4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F53j8531eTm4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6427be9c8b36b6a9d9fa398c1052d29/href">https://medium.com/media/f6427be9c8b36b6a9d9fa398c1052d29/href</a></iframe><p>Building webpages takes a long time. If a user doesn’t know how to code webpages, she can use a website builder like Squarespace or Wix — but even then, Squarespace overwhelms users with dozens of options. I built Spindle to help provide a simple way for someone to create a website on the go.</p><h3>The design process behind Spindle</h3><p>When you first start designing an app, sometimes it can get overwhelming to think about all the screens you have to design for, and where to start. I find that it’s easy to start by designing with what I know. In this case, I know that I’ll need a way to express preferences about how I want my website to look, and I’ll also need a way to edit the final site. I also thought of a few more features, but bolded the most important ones. Good design is about separating the important from the unimportant, constantly prioritizing.</p><h4>Feature ideas</h4><ul><li><strong>Choose look and feel</strong></li><li><strong>See examples based on my choices</strong></li><li><strong>Choose a design</strong></li><li><strong>Edit the design</strong></li><li>Add photos from Facebook, Instagram</li><li>See website’s user metrics, hits</li></ul><p>Then I thought about some goals I wanted the app to exhibit.</p><h4>Principles</h4><ul><li>Feels like a conversation</li><li>Offer a simple way to create a website</li><li>Fast</li></ul><p>Then we sketch. While it’s tempting to start with one idea and then go on to fully flesh it out, the first design may not be the right design. We can’t know our design is right if we only try one idea, we also need to look at the problem from other angles to find new insights and approaches that we might be missing, otherwise we might end up at a local maxima.</p><p>Going back to my app goals, I want this to be speedy way to build a website, so I decided on an interface where you swipe left or right on designs that you see. Now we can narrow the design decision to whether we want to the user to select between finished websites, or whether we want to show the user only website layouts (single column vs. two column), and go from there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*noIkamSyUsOJTrAVIOP19w.png" /></figure><p>Now I could go ahead and build these two apps, but that would involve a lot of resources. So why not just use a prototyping tool?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0KHTqXcIyN8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0KHTqXcIyN8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0KHTqXcIyN8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/20ba45d1429517b2868620040dd56e81/href">https://medium.com/media/20ba45d1429517b2868620040dd56e81/href</a></iframe><p>This took me 2 minutes in keynote. And now I can immediately see what’s working about the first design.</p><h4>What’s working?</h4><p>I let friends play-test the prototype, and learned several things. First, this interface is a quick way to create a website. One user commented she recently spent an entire weekend trying to create a website with SquareSpace because she was confused by all the options. The minimal amount of steps to a final website on Spindle made it easy to get started. Second, this app is useful for quick, one-off webpages than permanent pages like blogs or corporate landing pages. A common use case users wanted to use it for were event invitations. One user commented, “I would use this for a birthday party invitation. I’d like something more special than a generic Facebook event.”</p><h4>What’s not working?</h4><p>This works for users who are not yet sure what kind of website they want to build. If I already know what I want, I don’t want to swipe through all of these webpages. I want to tell you that I want a two-column layout with a menu.</p><p>Then we prototype the second sketch.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fzod-OGfh_e8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dzod-OGfh_e8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fzod-OGfh_e8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7103f1cb6bf42e1406166d679eb54926/href">https://medium.com/media/7103f1cb6bf42e1406166d679eb54926/href</a></iframe><h4>What’s working?</h4><p>This works great if I know exactly what I want. A user who had spent the a weekend creating a page for his dad’s cleaning service company said he preferred this second version more because he already knew he wanted a two-column layout and the website components he had wanted already.</p><h4>What’s not working?</h4><p>On the other hand, if I don’t know what I want, this version can force me to make decisions too early. This flow would be akin to building a house and having an architect ask you whether you want marble tiles or glass tiles vs. seeing pictures of those tiles in the context of pictures of kitchens.</p><p>Doing this iteration forced me to consider who my customer really was. I asked myself questions such as, does my customer:</p><ul><li>Want to create a website for <strong>temporary use</strong> or permanent use?</li><li>Want a website for business purposes or <strong>consumer purposes</strong>?</li><li>Prefer a pre-made template or a <strong>custom-generated one</strong>?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4AMrgHf2rwx7iIXkEQMsw.png" /></figure><p>I eventually decided that because we are designing this for mobile, people are probably on the go and not ready to design a finished product. Thus, the medium would lend itself better to temporary use cases for consumer purposes.</p><h3>Create the template</h3><p>Now that we’ve finished designing the way users express how they want the website to look, I wanted to validate that deeper and see if it was even easy for users to pick websites they like based on pictures. And from that, could I tell what they liked about that site. e.g. if they chose an image of Instacart.com, Could I even decipher what they liked about Instacart? The header vs footer vs the font styling.</p><p>Now I could have gone ahead and started writing a machine learning algorithm that would learn from user preferences to auto-magically generate custom website templates on demand, and test it to see how accurately it actually matched someone’s preferences. But this would distract me from the task at hand. My responsibility as a product designer is to validate ideas as quickly as possible — so that we don’t pour hours of engineering labor into something that might not be possible or solve anyone’s problem.</p><p>So I decided to run a cheap test. I printed out pages of websites and asked people to choose their top three.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lelt2aZRWIxqRvpH1r9ruQ.png" /></figure><h4>What’s working?</h4><p>&lt;easy to choose&gt;</p><h4>What’s not working?</h4><p>&lt;struggle between similar looking sites&gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e_5CNxbGl7_3CYheATEY6A.png" /><figcaption><em>(1) Less distinct</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCAACAQf1LCQZzZAmr6ktw.png" /><figcaption><em>(2) More distinct</em></figcaption></figure><p>Now that the user is done choosing the way she wants the site to look, she can move on to editing a web template.</p><h3>Edit the website components</h3><p>I sketched out two ideas for editing text components on a website. The first is in-line and the second is a pop-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vi6IhX5MA66O7VJW5ZNfBA.png" /></figure><p>Here’s the first idea:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-lTLzTNZboI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-lTLzTNZboI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-lTLzTNZboI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/585b36bbb61d969c3317ceef9f6eb9a9/href">https://medium.com/media/585b36bbb61d969c3317ceef9f6eb9a9/href</a></iframe><h4>What’s working?</h4><p>The direct manipulation of touching text and having it immediately go into editing mode is intuitive.</p><p>Contrast this with SquareSpace. All the editing happens in a left sidebar that is removed from the page you are editing. When it’s easy for the user to manipulate, the app establishes a feedback loop for creation. When it’s difficult, there is more latency in this loop and barriers are present to creative activity. (<a href="http://worrydream.com/MagicInk/">Bret Victor</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*IQM8vHgK24RJqgqQV1T0BA.png" /><figcaption>Snapshot of Squarespace</figcaption></figure><h4>What’s not working?</h4><p>The inline editing feels a little clunky. Let’s prototype the second sketch and see how that feels.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3aT42GNPx_8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3aT42GNPx_8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3aT42GNPx_8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/208f702f57774bf6c1a5a5e35a578e63/href">https://medium.com/media/208f702f57774bf6c1a5a5e35a578e63/href</a></iframe><h4>What’s working?</h4><p>I notice here, even though we’re not directly manipulating the text, it feels much less overwhelming. The pop up directs my attention to where I need to be editing. And since my page is directly beneath that, I feel oriented.</p><h3>Recap</h3><p>What we learned about designing websites for mobile:</p><ul><li>It’s possible to do a seemingly complicated task on the phone that we’d ordinarily relegate to the desktop, like designing and new website and editing it.</li><li>To communicate one’s design choices, images work better earlier in the decision-making process whereas more specific selections work better later in the process where users have more clarity on what they want.</li><li>An in-line insert mode surprisingly feels very clunky when editing a website, we should opt for a pop up instead.</li></ul><p><em>Credits:</em></p><ul><li><em>Thanks to Rob Cobb, Ryan Murphy, Javier Ivan Nanni, for helping with drafts of this.</em></li><li><em>Ed Sweezey, Matt, Chetan for building the app with me.</em></li><li><em>Built with Expo.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32c5f98555e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good design vs. bad design]]></title>
            <link>https://medium.com/@adriennera/good-design-vs-bad-design-73861420b28?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/73861420b28</guid>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Sun, 31 Dec 2017 06:06:16 GMT</pubDate>
            <atom:updated>2017-12-31T06:06:16.829Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started as a designer, I thought frequently about experiences that were well-designed compared to those that were not, and how the outcome differed. What was the value of design? For example, when I click a button and expect a drop down menu to appear, I feel cognitive dissonance when the menu suddenly appears. When the menu slides out however, I feel more at ease. When I use a UI with a lot of jump-cuts (a la things suddenly appearing) my brain has to pretend that all the in-between frames are there. When we use interfaces that actually animate all those in-between frames, however, we can take a shortcut through our visual cortex. The change in interface no longer disrupts the main task.</p><p>Think of the human brain like a computer. You have first, a main thread, and second, a GPU — a graphics processing unit in your visual cortex. You can feed people a lot of information through their visual cortex without interrupting what they’re thinking about. Animation allows the user to continue thinking. Imagine using your smartphone without animations. It would be like a tap and jump cut for everything you do. Would you have still bought it?*</p><p>* via <a href="https://frontendmasters.com/courses/svg-animation/">Sarah Drasner’s <em>Advanced SVG Animation</em></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73861420b28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lowest Common Ancestor]]></title>
            <link>https://medium.com/@adriennera/lowest-common-ancestor-b607be72b270?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b607be72b270</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[trees]]></category>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[algorithms]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 14:41:57 GMT</pubDate>
            <atom:updated>2017-09-14T14:41:57.804Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Given two nodes, get the lowest common ancestor of the tree.</em></p><pre>var Tree = function(){<br>  this.children = [];<br>};</pre><pre>Tree.prototype.getClosestCommonAncestor = function(n1, n2){<br>  // TODO<br>}</pre><p>To start, consider how to break this large problem up into subproblems. What information about these two nodes, if I knew, would enable me to easily solve this? Well, if I had the path of each of these two nodes, from the root of the tree, to the end of the node, all I would need to do is compare the paths and find the last one in common.</p><p>So let’s start by writing a getAncestorPath.</p><pre>Tree.prototype.getAncestorPath = function(target) {<br>  <br>}</pre><pre>// Example<br>var queen = new Tree();<br>var jack = new Tree();<br>queen.addChild(jack);<br>queen.getAncestorPath(jack); // =&gt; [queen, jack]</pre><p>If we’re trying to get path from a root to target and we’re traversing the tree, what are the two cases we have to consider?</p><p>Have we found our target?</p><ol><li>If yes, return</li><li>If no, keep iterating</li></ol><p>Thus, we can fill in our function as such (pay attention to the guiding principles in the comments!):</p><pre>Tree.prototype.getAncestorPath = function(target, path = []) {<br>  // Do we have a solution?<br>  if (this === target) {<br>    // Deal with the fact that we have a solution<br>  } else {<br>    // Iterate over possible decisions (in this case, children)<br>    for (var i = 0; i &lt; this.children.length; i++) {<br>      // Make the decision and check if its valid recursively<br>    }<br>  }<br>}</pre><p>We have our skeleton. Now we can start filling things in:</p><pre>Tree.prototype.getAncestorPath = function(target, path = []) {<br>  // Do we have a solution?<br>  if (this === target) {<br>    // Deal with the fact that we have a solution<br>    // Add to our path<br>    path.unshift(this);<br>    return path;<br>  } else {<br>    // Iterate over possible decisions (in this case, children)<br>    for (var i = 0; i &lt; this.children.length; i++) {<br>      // Make the decision and check if its valid recursively<br>      if (this.children[i].getAncestorPath(target, path)) {<br>        path.unshift(this);<br>        return path;<br>      }<br>    }<br>  }<br>  return null;<br>}</pre><p>OK, phew. Now that we have this subproblem done, we can use it to help solve our closestCommonAncestor problem:</p><pre>Tree.prototype.getClosestCommonAncestor = function(n1, n2){<br>  // Get paths of n1 and n2<br>  var path1 = this.getAncestorPath(n1)<br>  var path2 = this.getAncestorPath(n2)<br>  if (!path1 || !path2) return null<br>  ancestor = null;<br>  <br>  // Get the shorter length<br>  var shorterLength = Math.min(path1.length, path2.length)<br>  <br>  // Compare each index and get the furthest common index<br>  for (var i = 0; i &lt; shorterLength; i++) {<br>    if (path1[i] === path2[i]) {<br>      ancestor = path[i]<br>    }<br>  }<br>  <br>  return ancestor;<br>}</pre><p>This problem is a type of decision tree problem. All decision tree problems generally have the following framework:</p><ol><li>Check if you have a solution<br>- If so, deal with the fact that you have a solution</li><li>Iterate over possible decisions<br>- Make the decision<br>- Recursively check if the decision you made is valid<br>- Go to the next decision</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b607be72b270" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying Node, Mongo to AWS EC2]]></title>
            <link>https://medium.com/@adriennera/deploying-node-mongo-to-aws-ec2-1bdd7f73f87?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bdd7f73f87</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 29 Aug 2017 20:27:26 GMT</pubDate>
            <atom:updated>2017-09-04T19:51:55.523Z</atom:updated>
            <content:encoded><![CDATA[<p>This guide assumes you have already set up the environment and downloaded the .pem file. Make sure you put the .pem key somewhere safe.</p><h3>Connect to environment</h3><p>Click on your instance and hitting “Connect” — you’ll see a URL like this. Copy and paste it into terminal:</p><p>ssh -i “&lt;LOCATION OF PEM KEY&gt;” ubuntu@&lt;amazon aws url&gt;</p><h3>Install Mongo on your VM</h3><p>The documentation is on point: <a href="https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/">https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/</a></p><h3>Install Node on your VM</h3><pre>curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -<br>sudo apt-get install -y nodejs</pre><p>Installing Node installs NPM.</p><h3>Install Express on your VM</h3><pre>sudo npm install -g express</pre><h3>Change IP tables on your VM</h3><pre>sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8080  <br>sudo iptables -t nat -A OUTPUT -p tcp --dport 80 -o lo -j REDIRECT --to-ports 8080</pre><p>See <a href="https://gist.github.com/kentbrew/776580">this guide</a> for reference.</p><h3>Edit your security groups on AWS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SSIqUX-LjLhyqo_JQP-1hw.png" /></figure><h3>Clone your git repo</h3><p>In /home/ubuntu:</p><pre>git clone <a href="https://github.com/ViserionHr/viserion.git">https://github.com/&lt;YOURUSERNAME&gt;/&lt;YOURREPO&gt;.git</a><br>npm install</pre><h3>Start your server</h3><pre>node server.js</pre><h3>Visit your new page</h3><p>Get your public DNS from your Amazon console page.</p><p>&lt;amazon public DNS here&gt;:8080</p><p>e.g. <a href="http://ec2-54-203-8-222.us-west-2.compute.amazonaws.com:8080/">http://ec2-44-146-1-324.us-east-1.compute.amazonaws.com:8080/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bdd7f73f87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the power of writing]]></title>
            <link>https://medium.com/@adriennera/hamilton-and-his-facility-with-words-b7b9d1d55028?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7b9d1d55028</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[professional-development]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 01 Aug 2017 03:49:23 GMT</pubDate>
            <atom:updated>2017-09-14T14:43:18.042Z</atom:updated>
            <content:encoded><![CDATA[<p>When I was in grade school, one of my favorite English teachers would often remind us, “if you can write, you can do anything.” I would always think, “well of course she’s saying that… she’s an English teacher.”</p><p>I’m reading Alexander Hamilton’s biography, and he had quite a facility with words, even when he was a teenager growing up in poverty-stricken St. Croix. When a storm devastated the island inhabitants, Hamilton wrote, “…the ear-piercing shrieks of the distressed, were sufficient to strike astonishment into Angels,” in a letter to his father at the tender age of seventeen.</p><p>Hamilton may well have stayed in St. Croix for the rest of his life had the Gazette not picked up his letter and published it in their newspaper anonymously. The island governor demanded to know who wrote the letter, and a group of local businessmen raised a fund to send Hamilton to America to be educated.</p><p>Before we had writing, we always needed to be in the same place at the same time in order to communicate. The appeal of writing is that it allows you to exchange ideas without time or place needing to be relevant. When I look at some of my role models — I often realize that they’re not particularly smarter than many of the other people in my life — rather, they document their thoughts and ideas. Writing is much more scalable than conversations.</p><p>Also published at <a href="http://eatlovecode.com/hamilton-and-his-facility-with-words/">http://eatlovecode.com/hamilton-and-his-facility-with-words/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7b9d1d55028" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Those cryptic Session attributes]]></title>
            <link>https://medium.com/@adriennera/those-cryptic-session-attributes-9b5d38ac99fa?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b5d38ac99fa</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 23:49:51 GMT</pubDate>
            <atom:updated>2017-09-04T19:45:16.218Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re creating a new session in Express, what do the keys in the session object mean?</p><pre>app.use(session( {<br>  secret: &#39;snapcracklepop&#39;,<br>  resave: false,<br>  saveUninitialized: true<br>}));</pre><h3>secret</h3><blockquote>Documentation: This is the secret used to sign the session ID cookie.</blockquote><p>In short, the encryption key.</p><h3><strong>resave</strong></h3><blockquote>Documentation: Forces the session to be saved back to the session store, even if the session was never modified during the request.</blockquote><p>Was the session updated in any way or not? Rather than checking for when the user comes back, it re-saves the session whenever you make a change. Why would we ever want resave set to false? Some session stores will delete old sessions unless they have been changed, so if we’re not using a session store that would delete all sessions, we don’t need to resave.</p><h3>saveUninitialized</h3><blockquote>Documentation: Forces a session that is “uninitialized” to be saved to the store. A session is uninitialized when it is new but not modified.</blockquote><p>Middleware will run for every request. Sessions are being created for every single request, whether the user is logged in or logged out. This could be a completely useless session — why create a session if the user won’t log in? In this case, we are saving it as a true. That means we can go back and look up the session for a particular user, even if they have not been logged in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b5d38ac99fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The impact of improv on your professional success]]></title>
            <link>https://medium.com/@adriennera/staying-flexible-always-de213f40c090?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/de213f40c090</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[improv]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 13:56:13 GMT</pubDate>
            <atom:updated>2017-12-31T06:07:57.364Z</atom:updated>
            <content:encoded><![CDATA[<p>During my last improv class, we did an exercise where everyone had a monologue. I was surprised at how each person was able to make a scene come to life with a beginning, climax, and end so seamlessly. When one of my classmates Olga went on stage and was given the location ‘ice cream shop’, she immediately transformed into an ice cream shop server. As she pranced around the shop, she sampled a taste of ice cream and made the ice cream cone come to life. She took a few licks, and then scolded the ice cream cone for making her butt big, but wrestled with how delicious he was. She finally decided to toss the ice cream in the trash. Every person appeared as if they had been preparing for this scene for the past week.</p><p>But none of them had any even preconceived notions in mind. They had all been given a random location on the spot, and had to create a scene based on that location.</p><p>I notice an analog in programming. When I was pair programming with our front-end developer Bruno today, I asked why he had defined a function in class A but not in class B, I expected him to be prepared with an answer. Instead, he said “Let’s investigate” and opened class A, going line by line to trace back where the method was being used. He realized that there actually was no need for that method and we ended up taking it out.</p><p>You can’t know the answers to some things in life. And trying to hold everything in your head is exhausting. What you can do is be quick to adjust in the moment and execute on the spot.</p><p>Also posted on my blog <a href="http://eatlovecode.com/staying-flexible-always/">http://eatlovecode.com/staying-flexible-always/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de213f40c090" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Callbacks explained in 3 minutes]]></title>
            <link>https://medium.com/@adriennera/callbacks-explained-in-3-minutes-7367319bc6f9?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7367319bc6f9</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Mon, 24 Jul 2017 18:12:14 GMT</pubDate>
            <atom:updated>2017-07-24T18:12:14.949Z</atom:updated>
            <content:encoded><![CDATA[<p>To understand callbacks, we’re going to use an example that gets a file from the file system and displays the content in the file to the user.</p><p>We’ll start by building out the helper function. We can use filesystem, a library for Node.js that allows you to work with the file system. readFile takes two parameters: a file path and a callback.</p><pre>fs.readFile(filePath, callback);</pre><p>What does readFile do with the callback function? Let’s look at the callback itself. A callback function generally takes in two arguments: an error and the data. Why the term <strong>callback</strong>? The function will read the file at the filePath, and then call the callback function when it’s done. Specifically, it will invoke the callback with an error if there was one, else the file’s contents if the file data was successfully retrieved.</p><pre>var callback = (err, data) =&gt; {<br>  if (err) {<br>    callback(err, null)<br>  }<br>  callback(null, data)<br>}</pre><p>We put these two together in a helper function:</p><pre>var getFileData = (url, callback) =&gt; {<br>  fs.readFile(filePath, (err, content) =&gt; {<br>    if (err) {<br>      callback(false)<br>    } else {<br>      callback(content)<br>    }<br>  }<br>}</pre><p>Finally, we invoke our callback getFileData where another function needs the file data before proceeding (hence the term asynchronous).</p><p>One such case is when a user is making a GET request to load a page and we want to display a file’s contents to them. In the request handler, we can call this textInFile function and don’t execute our next line of code until we receive the file’s contents.</p><pre>var filePath = &quot;~/index.txt&quot;;</pre><pre>handleRequest = (req, res) =&gt; {<br>  if (req.url === &#39;/&#39;) {<br>    if (req.method === &#39;GET&#39;) {<br>      getFileData(filePath, (err, content) =&gt; {<br>        res.writeHead(200)<br>        res.end(content)<br>      }<br>    }<br>  }<br>}</pre><p>Imagine if we didn’t have callbacks and we tried to write this code in a synchronous manner. Our code would be trying to get file data that has not yet been retrieved. Callbacks allow us to more control over the execution of our code, so we can tell pieces to only execute once a dependency is ready.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7367319bc6f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a generalist vs. a specialist]]></title>
            <link>https://medium.com/@adriennera/becoming-the-jack-of-all-trades-vs-specializing-c0bc8d78c707?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0bc8d78c707</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 23:00:14 GMT</pubDate>
            <atom:updated>2017-09-04T19:47:45.621Z</atom:updated>
            <content:encoded><![CDATA[<p>Many people I know are afraid of not reaching enough depth in one discipline. They want to be the “T-shaped” person.</p><p>I’ve realized I’ve increasingly become less afraid to be the Jack of All Trades, particularly when I trust myself to connect new concepts with ones you already know. In a sense then, I’m actually reaching depth when I am learning something new.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0bc8d78c707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Something that seems trivial at first glance is never trivial at network scale.]]></title>
            <link>https://medium.com/@adriennera/something-that-seems-trivial-at-first-glance-is-never-trivial-at-network-scale-4f3d418231e9?source=rss-3a9f137fb4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f3d418231e9</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[capitalism]]></category>
            <dc:creator><![CDATA[Adrienne Alyzee]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 22:59:30 GMT</pubDate>
            <atom:updated>2017-07-18T22:59:30.487Z</atom:updated>
            <content:encoded><![CDATA[<p>While many chastise corporations for creating a superficial and materialistic America, the capitalist environment fuels innovation driven by the high pressure</p><p>The video advertising industry, is a key driver in pushing high-efficiency video compression algorithms — the same algorithms that allow your latest episode of House of Cards to get streamed almost instantly (instead of the hours it took years ago).</p><p>Orthogonally, while the video game industry drove the development of faster graphics cards, pushing GPUs to reach faster processing speeds than CPUs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f3d418231e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>