<?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 Callie on Medium]]></title>
        <description><![CDATA[Stories by Callie on Medium]]></description>
        <link>https://medium.com/@DementedScript?source=rss-332c4f758750------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lTUfrrtTmTM3xH6C.jpg</url>
            <title>Stories by Callie on Medium</title>
            <link>https://medium.com/@DementedScript?source=rss-332c4f758750------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:17:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DementedScript/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[Jesse Cox: Why we’re mad]]></title>
            <link>https://medium.com/@DementedScript/jesse-cox-why-were-mad-dfd414411c70?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfd414411c70</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[twitch]]></category>
            <category><![CDATA[rape-culture]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Tue, 07 Jun 2016 16:58:02 GMT</pubDate>
            <atom:updated>2016-06-07T17:03:24.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2MQDStf0AmI8FnI-MSVibw.jpeg" /></figure><p>Last night was the premiere of <em>Warcraft</em>. A long-awaited film featuring heroes that many of us basically grew up with (including me). This included many pretty god damn amazing costumes (like, can we please talk more about Arakkoa? I like talking about that Arakkoa. I also can’t spell Arakkoa).</p><p>Well then <a href="https://t.co/HByhxec1Ey">this </a>happened. <a href="https://twitter.com/appleciderwitch">Applecidermage</a> was nice enough to transcribe it for us:</p><h3>Just Tits Reigns on Twitter</h3><p>So I got a link to the premiere interview with Patton https://www.twitch.tv/warcraft/v/70991236?t=01h22m23s ... Transcribed it for ppl who can&#39;t see:pic.twitter.com/TNOQkslK2w</p><p>Like, hands down to Paula for handling the way she did. And yet, people just don’t get it.</p><h3>Why aren’t we mad at Daniel Wu? Twitch chat?</h3><p>Eh, I’m a little annoyed, won’t lie. However, he’s not the one who went down that road in the first place. He didn’t need the disclaimer of “Oh well this is going to be creepy.” And frankly, watching the video, I could almost hear is auditory facepalm of “are you seriously going here dude.” (obviously this is me putting words in his mouth because I just can’t fathom being in that situation).</p><p>Someone else pointing out — why aren’t we mad at Twitch chat? Because, frankly, by default we’re mad at Twitch Chat. That’s nothing new (sad as it is). Not to say that this isn’t a problem, but at this point the argument becomes about internet culture itself and devolves outside of the realm of what happened on the red carpet.</p><h3>It’s no big deal, she was laughing!</h3><p>Gamer culture has been attacked on a few sides for this kind of shit. You want to know why I’m mad? Not just because this is the shit that women in gaming have to deal with on a pretty consistent basis, but because many of my guy friends in gaming have to deal with the other side of it — being classified as the “disgusting basement dweller creep” who says uncouth things like this.</p><p>And this guy was chosen by Blizzard to represent us. Are you getting my point now? You can tell me “He doesn’t represent the Warcraft community!” I’m sorry, but <strong>you’re wrong</strong>. He was on an official Blizzard stream for the premiere of the <em>Warcraft</em> movie. Yes, he was representing us, just as the people he interviewed also did.</p><p>Also, women are conditioned to treat this shit as no big deal. Some dude catcalls you on the street? Oh, but it’s a compliment girl. Some dude harasses you and says “show me ur tits?” Oh, boys will be boys! Haha how funny!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*sDoKH_z9r4usq_gFZvdZSg.gif" /><figcaption>absolutely hysterical amirite</figcaption></figure><p>If we get mad, if something happens that we don’t like, we get it blamed on our periods when we’re upset or angry. We’re told we’re being “over emotional” and “unreasonable” and “illogical.” If I were a violent person (I might play Horde and play a melee, but I’m definitely <em>not </em>a violent person), I’d slap the dude who tells me I’m being “illogical” in an argument where I’m laying my god damn — often researched — points out, because this is the shit we deal with all the time.</p><p>And then this bitch gets the idea that it’s okay to ask a lovely lady what it’s like to get beaten off to and we’re supposed to be okay with it, because</p><ol><li>Twitch chat thought it was hilarious</li><li>She laughed it off and acted gracefully after attempting to deflect the god damn question in a way that was pretty uncomfortable</li><li>women are clearly over-emotional</li></ol><h3>Oh, but surely he apologized</h3><p>Oh even worse. Instead, he shows that he — like so much of of the Internet — just doesn’t fucking get it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*_UEwQlVEIR6V_hRo6WLP2A.jpeg" /></figure><p>This tweet was deleted but has been linked in a few places. Then there’s his overall stream — acting the god damn victim that people are mad at him and calling him for enforcing a stereotype that so many of my friends have been trying to get out of for the last twenty or more years.</p><p>Way to set our progress back five years and then not understand why what you did was not just shitty, but completely inappropriate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*T5or0GUedB-FcoQb56uD0A.png" /></figure><p>And yet so many people want to write this off as “just SJWs ruining our fun.” Oh, I’m sorry that there are people like myself who just want a bit of common decency and hate the fact that a really fun event got ruined for us by someone who thought it was okay to ask <em>that</em> question.</p><p><strong>Shit like this is why people avoid gamer culture and why we get these “amazing” stereotypes of being the the creeper with bad hygiene who can’t get a date</strong>. Which I don’t know about you, but this stereotype makes me mad — and seeing it enforced with no apology? Makes me very, very sad.</p><p>And finally, let me remind you: the people in question <em>just don’t get it</em>.</p><h3>Jesse Cox on Twitter</h3><p>Anyway, that&#39;s the last I&#39;ll ever talk about it. I choose not to let fake controversy diminish the great night I had. More videos soon.</p><h3>EDIT: LET ME ADD ONE MORE THING I FORGOT</h3><p>This premiere was in a <strong>professional setting</strong>. Had Cox said what he did anywhere else — let’s say it was in the break room. There’d be a god damn HR case on his ass, he’d likely get fired on the spot, and nobody would be laughing. There would be zero question that it would be sexual harassment. Why are we questioning how this is any different? What, because it was on a Twitch stream <em>sanctioned by Blizzard?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfd414411c70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Document your damn code.]]></title>
            <link>https://medium.com/@DementedScript/document-your-damn-code-5d83bee38243?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d83bee38243</guid>
            <category><![CDATA[good-practices]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cod-documentation]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Tue, 19 Apr 2016 00:22:02 GMT</pubDate>
            <atom:updated>2016-04-19T00:23:07.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*uQGAD1WDumLVQqvYAqlgbg.gif" /><figcaption>Me, recently.</figcaption></figure><p>This gif is more-or-less the last 72 hours of my life. Or at least, a documentary of the internal screaming resulting from dealing with several (read: a week on Wednesday) days of dealing with undocumented legacy code.</p><p>I think these two terms go hand in hand, and you all know where I’m going here. This is going to be my rant of probably not-so-epic proportions of why you should document your code. At times, the arguments will be bad. At other times, hopefully they get my point across.</p><h3>The New Dev — Some Backstory Here</h3><p>Hi. Let me get one thing straight: I fucking love my job. This is, hands down, the best job I’ve ever had.</p><p>Yes, I started a month ago.</p><p>However, this job also happens to basically be my dream job. Not only do I get to work in web, but I also get to do low-level coding — I was the kid in school who actually enjoyed their assembly class, and actually really missed it after I dropped out.</p><p>It doesn’t matter the languages you’re in. If you’re new, things might not make sense. The dev before me wrote reams of fantastic documentation on our processes. The problem is — a change went out last week that basically meant working night/day on code I barely knew, with processes I’ve only sort-of felt comfortable with.</p><p>It’d be a living nightmare if I didn’t absolutely enjoy every god damn moment of it.</p><h3>The Arguments</h3><p>I’ve worked in a lot of places, and I’ve attended two different universities. So let me start first with my rant about people at universities.</p><p>The professors always required code documentation. The university I’ll be graduating from taught C++ when I first started (and only recently — in the last year — transitioned to Java). My code documentation looked something like this:</p><pre>// — — — — — — — — — — — — — — — — — — — — — — — — — — — — <br>// Description: Validates the read data and puts it into<br>// arrays<br>// Input params: rentalUnits — rental array of units<br>// read from file<br>// MAX_RENTALS — max amount of rentals<br>// amntRentals — the count of rentals<br>// Output Params: rentalUnits, amntRentals<br>//<br>// Return: bool<br>// — — — — — — — — — — — — — — — — — — — — — — — — — — — — </pre><p>The code itself even had a few here and there, but nothing too prolific. Your basic main():</p><pre>bool useExistingFile(){ <br>   bool useExisting = false; <br>   char userInput; </pre><pre>   while(toupper(userInput) != ‘Y’ &amp;&amp; toupper(userInput) != ’N’) { <br>      cout &lt;&lt; “Load existing data from a file (Y/N)? “; <br>      cin &gt;&gt; userInput; <br>      // bad input, reprompt <br>      if(toupper(userInput) != ‘Y’ &amp;&amp; toupper(userInput) != ’N’) { <br>          cout &lt;&lt; “Please enter Y for Yes or N for No.” &lt;&lt; endl; } <br>      else { <br>          if(toupper(userInput) == ‘Y’) { <br>             useExisting = true; <br>          } <br>      }<br>   } <br>   return useExisting;<br>}</pre><p>It’s not the prettiest function, but it gets the point across. Reads the user input, if its bad input, then it reprompts. Once it gets an answer, it returns a true or a false.</p><p>Except, notice it has 1 inline comment. And I run into so much code that won’t even do this (I mean, admittedly — I don’t comment <em>all</em> of my code). Because it doesn’t <em>need </em>that much. The documentation above tells you pretty much all that you really need to know.</p><p>Yet so many university students have been marked down because of their blunt resistance to writing simple, documentation comments. Because they’re too “time consuming” (frankly: text macros are your friend. This kind of shit takes you at <em>most</em> a few seconds per function — and if you write them before you write the function, your code ends up better, anyhow.)</p><p>This goes on into the workplace.</p><blockquote>But what if the code changes and you don’t update the comments? Then it’s more confusing!</blockquote><p>So what you’re saying right now is that you’d rather just be lazy? Does it take you this long to type a sentence? Have you stopped to think you aren’t the only developer working on this project?</p><blockquote>If you don’t understand this code, you can just ask.</blockquote><p>Chances are, the original author won’t be there to ask. I’ve run into that far more often than not.</p><p>I’ll also add that I’ve found that this kind of attitude ends up being a bit egotistical, and falls into:</p><blockquote>Code should be self-documenting. There’s no reason for comments!</blockquote><p>We all know what self-documenting code is. Heck, the function I provided up there is pretty self-documenting itself. But doesn’t this contradict your first argument as well?</p><p>If I have a variable named a certain way, or a function, and then I change them to do something “else” — I also need to update my unit tests, and if we’re relying on this code to be self-documenting… Then I also need to update all of their names. So doesn’t it contradict what you’re saying about not having comments (because they’ll be confusing) if I don’t also take these steps with my code? Shouldn’t updating comments if I’m changing the entire damn thing?</p><h3>Let me finish my point</h3><p>First: notice my title is <em>document</em>. Not simply <em>comment</em>. However, comments are — in my least humble opinion — the most effective form of code documentation. I’m not going to read a confluence page while trying to fix a bug or add a feature to an existing code base.</p><p>I don’t believe you should write as many comments in your code as I do when I’m having a hard time figuring out how the hell to fix something:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fddc2d15b97de5d828b45e7de1003b6d/href">https://medium.com/media/fddc2d15b97de5d828b45e7de1003b6d/href</a></iframe><p>(for the record, this was written with a bit of alcohol several hours <em>after</em> the due date).</p><p>But the point is, something like this gets the point across, is readable, and in a few years after I’ve returned from hiding in Fiji after revealing to Medium that I once forgot how to write a basic binary search at two in the morning, I’ll still likely be able to figure out what’s going on (note: I actually did add a few comments to this, as I realized that out of context many of its variables don’t make sense):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6cfad2a346943d08b5d1ed4717e73bc/href">https://medium.com/media/f6cfad2a346943d08b5d1ed4717e73bc/href</a></iframe><p>And yes, I’m aware I can use cleaning for that function. This isn’t a review of coding skills — this is a reminder that comments are <em>very good</em> to have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*2bUbgT-zvPRK1L9T2kdk9w.jpeg" /></figure><p>So stop making excuses for “too many” comments. You aren’t writing comments for your compiler — you’re writing them for the next extremely stressed developer that’ll be taking over the project. And sometimes, that developer will be <em>you.</em></p><p>So treat yo’self: write comments! Because there’s no actual <em>good</em> excuse to <em>not</em> have them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d83bee38243" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wil Wheaton — I love you, and what you do for rescue. But it doesn’t give the full picture.]]></title>
            <link>https://medium.com/@DementedScript/wil-wheaton-i-love-you-and-what-you-do-for-rescue-but-it-doesn-t-give-the-full-picture-8a7d69626b5d?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a7d69626b5d</guid>
            <category><![CDATA[dogs]]></category>
            <category><![CDATA[wil-wheaton]]></category>
            <category><![CDATA[pets]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Fri, 15 Jan 2016 21:06:43 GMT</pubDate>
            <atom:updated>2016-01-15T21:12:59.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*ZGcoxaWbWTV9B6Kx550vlQ.jpeg" /></figure><p>Dear Wil,</p><p>Let me open this up by fangirling for a moment in a few run-on sentences. You’re one of my most favorite people ever because of not just the awesome shows and media you’ve done, but your words of encouragement toward people, animals. You’re one of the very few people that I’d love to meet because I’m convinced we’d become friends because we have extremely similar interests and extremely similar takes on the world, and I love your “depression lies” stuff, and your dogs are adorable.</p><p>However, and while I love the work that you do on behalf of rescue dogs, a Tweet of yours inspired this post. But first, here’s a picture of my dog — she’s a Doberman, purebred and would be papered except I forgot to actually register her properly (its a long story).</p><p>In particular, there’s this tweet.</p><h3>Wil Wheaton on Twitter</h3><p>I seriously doubt anyone following me is the kind of person who would buy a dog instead of adopting. https://twitter.com/RyanWatters2/status/687016736856608768 ...</p><p>Now, disclaimer that I have 0 issues with rescue. In fact, I used to volunteer time at a horse therapy, and I’ve even fostered liters of kittens rather than see them go to a kill shelter. Please bear with my rambling — I know you’re a really busy person, but what’s to come I think is very important for “rabid rescuers” and dog lovers alike to understand.</p><h4>Jaina’s Story</h4><p>Here’s another picture of Jaina, because she’s adorable and she factors into a great deal of my argument.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WOPGZ6gMQ1VE8mUy6IYd2g.jpeg" /></figure><p>Actually, that photo is of both Jaina and her cousin, both of which are from the same breeder. This is where the story gets a tad interesting.</p><p>I bought Jaina in 2012, and brought her home from the Grass Valley Dog Show. This ended a several-month journey in finding the perfect dog companion. I had already contacted several rescues, but none of their dogs were a match for various reasons (most weren’t good with cats, or they had health issues when I knew I wanted to have a pretty active dog).</p><p>Early in this journey, I spoke with <a href="http://norcaldobermanrescue.com/">Northern California Doberman Rescue</a>. First off, Dana is great! Sadly though, none of the dogs were a good fit. However, I did have an interesting conversation with Dana, the owner and person that runs the rescue. She told me that she had retired from breeding when information about DCM (a genetic heart condition that appears in Dobermans) began to show up, and she learned that her line in particular suffered from it. She also related to me how the dogs in her care often did <em>not</em> come from breeders — because she always checked for a breeder’s tattoo and contacted them. The breeders would then pick up the dogs (if it were theirs), and try to contact the owners. These breeders’ dogs did <em>not</em> end up in rescue — they were either rehomed by the breeder, or kept on as part of the breeder’s responsibility. In fact, her dogs generally came as the result of puppy mills.</p><p>Unfortunately, things didn’t work out with the NorCal rescue — the puppies they had at the time were all spoken for by the time I began the process, and none of the adult dogs were good with cats. I began speaking to <a href="http://www.foxfiredobermans.com/">Jaina’s breeder</a> after a few recommendations and dead ends at rescues. I knew I wanted a Doberman — I had grown up with a big, red rescue boy that was everything I wanted in a dog. And Dobers are great — wonderful personalities, incredibly easy to train, and absolute go-getters. As long as it doesn’t involve dock diving, that’s my Jaina in a nutshell.</p><p>Now where things get interesting. The other dog in that photo, as mentioned, happens to be related to my dog. Heck, they’re practically broken from the same mold. However, Jaina’s cousin (we’ll call her B) is a breeder rehome. What we can gather from her story is that the breeder sold her to another show home. B would have been titled and everything, but instead they kept her kenneled and a few other issues. That’s not a good home. As a breeder friend of mine stated — a good breeder would love to see their dogs titled, but they’d rather see them go to a good pet home than to go through what it is implied B experienced. The other home even appears to have attempted to recrop her ears!</p><h4>Breed Specific Legislation</h4><p>Now, let’s look at your dogs, Wil. They’re absolutely adorable! I hope you don’t mind me reposting this picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*LbUgtQ6-pnbCP3GQ-Zh_xA.jpeg" /><figcaption>The Wheaton Family, grabbed from Google Image Search</figcaption></figure><p>Your dogs appear to be pit mixes, and likely what would be termed as a GSD-like dog. I think you know where I’m unfortunately going here.</p><p>The majority of dogs that have appeared in shelters recently have been pit mixes or Staffordshire-types. Now, I love pits! In fact, I’d rescue one if I could. It’s estimated that <a href="http://www.pbrc.net/breeding.html">around 40% of the dogs in Los Angeles shelters </a>are pit bulls or pit-type dogs. For such amazing, adorable, and a genuinely awesome breed, that makes me very sad. However, pits, GSDs, and even Dobermans have something in common: it’s very difficult to live with them.</p><p>Not because they’re hard to manage or are aggressive or anything like that. Rather, breed-specific discrimination means that they <em>very commonly</em> end up on “banned breed” lists. When I owned a house, I had to purchase a very specific and expensive insurance policy in order to bring Jaina home. That policy, while it allowed Dobermans and GSDs, did not allow Akitas, Pit Bulls, or Rottweilers. Its even more difficult if you happen to rent — most landowners won’t go for an expensive policy, and the cheaper ones won’t allow pits or others. Not to mention, the units’ owner likely wants to maintain a certain image. So, they’ll just blanket-ban the most <a href="http://www.zillow.com/blog/pro/property-management-and-pets-most-aggressive-dog-breeds-2645/">commonly discriminated breeds</a>. Considering the state of the US economy in terms of home ownership, <em>most</em> people have to be conscious about what sorts of dogs they can rent with.</p><p>So, that means that getting a shelter dog — which in all likelihood resembles one of these “aggressive breeds” — just isn’t doable by most people. Turning to a breed-specific rescue can fit the bill, sure — except those come from the root of the problem.</p><h4>The most foul thing</h4><p>Puppy mills likely conjure the image of dogs smashed into cages with a variety of health problems, that are overbred, and generally lead miserable lives. While this image isn’t too far from reality, the truth is that the definition goes beyond just manufactured dogs. Mills can even be as simple as a mom-and-pop set up that just breed their dogs for “pets” because they think they have a great personality. Nothing makes me more sick than seeing a setup like this — trying to buy into a person’s lack of education because they want a dog with a certain look, and instead breed these poor dogs that are going to likely live lives of misery from every possible genetic issue that their breed might be afflicted with. It abso-fucking-lutely (pardon the language) disgusts me.</p><p><strong>Greeder</strong>: Someone who breeds dogs for money. This can include your puppy mill, but also people who have their dog in the back yard and heard they could get $400/pup on Kijiji. These also include people who have built a business around breeding “pet” dogs and don’t understand that — yes — they are doing this for money, not for the betterment of dogkind.</p><p><strong>Breeder</strong>: Someone who shows and/or works dogs, and likely spends most of their free time surrounded by said dogs. These carefully select homes. Oftentimes, they are also involved with rescue on some level, or later do.</p><p>The people who are breeding good, healthy dogs like my Jaina aren’t in this for money. They’ve invested their entire lives into dogs. These breeders — the ones I told you about earlier, whose dogs don’t end up in rescue if they can do anything about it — live and breathe dogs. Whether it’s Dobermans, Shih Tzus, or your more-common Labrador, they don’t simply throw two dogs together because they have a good personality.</p><p>If their dogs are good enough to title, pass health checks, and do the work they’re bred to do, then personality becomes an afterthought (and, for the record, dogs’ personalities are <em>part of the breeds’ standard</em>)<em>. </em>Consider this — there are countries where <a href="http://sciencenordic.com/should-dogs-be-neutered">pet overpopulation isn’t even a thing</a>. Wouldn’t it be great if North America could reach that level, too?</p><p>The only way we can solve pet overpopulation is if people vouching for rescue will also support responsible breeders that don’t contribute to pet overpopulation. People like me — who bought their dogs instead of rescuing them — aren’t causing dogs at shelters to die. A shelter dog didn’t die because I bought Jaina. Rather, the unfortunate side-effects of breed discrimination and irresponsible breeding from greeders <em>murdered</em> that dog and prevented it from finding a good home.</p><h4>My Appeal</h4><p>Wil, you and the rest of us followers are all pretty awesome, pretty brilliant people. I hope that you’ve been able to read through this and understand that I think you’re doing some great things. However, bashing responsible breeders who have the best at heart for dogs won’t help us work together to solve the problem of pet overpopulation.</p><p>The only way that we can really over come this comes by educating people. Dogs aren’t just animals we can throw outside to do whatever — they were bred alongside people to be part of our families. That means we need to take responsibility for them, whether through compulsive speutering or other means.</p><p>Can’t we agree that encouraging responsible breeders that work against pet overpopulation is doing the world a lot of good by encouraging more well-bred, well-mannered, and well-cared-for dogs (plus fewer dogs in shelter the more that come from this source)? Can’t we also agree that the kinds of abuse that (responsible) breeders get is pretty unfair, given how much of themselves they’ve invested in dogs?</p><p>Can’t we agree that rather than shaming people who bought their dogs responsibly, we should celebrate the fact that they chose to educate themselves and didn’t encourage the sources that have lead to the thousands of unwanted dogs in shelters?</p><p>Thanks for reading this. As a fellow dog lover, I fully support your work in encouraging people to rescue — I just hope that we can both agree that it’s more about educating people to acquire their dogs responsibly, rather than from a mill or pet store (who, unless they are helping a local rescue, receive their dogs from mills).</p><p>Thanks,</p><p>@DementedScript</p><p>PS — for each recommend this receives, I intend to donate $1 to the <a href="http://www.charitynavigator.org/index.cfm?bay=search.summary&amp;orgid=3286#.VplcRZMrJE4">ASPCA</a>. (Now, keep in mind, I’m broke most of the time, but going to do my best to meet or match this challenge)</p><h4>PPS</h4><p>As the owner of a purebred Doberman, I have already received plenty of shaming.</p><ul><li>“She’s not a rescue?” followed by a disappointed glance.</li><li>“They look so much better with floppy ears.”</li><li>Similar: “It’s so cruel how they cut their ears and tails off.” (I won’t go into that here — but there are actually pretty legitimate reasons that breeders still do this in North America. Perhaps another post later on about why banning cropping/docking may not work for North America)</li><li>“Did you breed her?” Sometimes, but not always, is this shaming — J’s a very pretty girl who… Well, she <em>developed</em> very young and had very large nipples. She was also never bred, and is spayed. People never actually believe me on that count — though some people do, and then indicate they wish I had, simply because she’s pretty.</li><li>“You had the chance to do good by a dog.” I do right by my dog every day.</li><li>“All breeding should be banned.” Except that in the span of the lifetimes of all dogs in North America right now, dogs will cease to exist. That’s not a terribly good choice. Also — I had to pay a higher licensing fee for Jaina her first year because she hadn’t been spayed yet (it’s <a href="http://news.ucdavis.edu/search/news_detail.lasso?id=10977">not always the best choice to spay/neuter your dog within their first year </a>— as long as you’re responsible about it). So yes, we <em>do</em> have fees associated with unspeutered dogs.</li></ul><p>These kinds of comments are why the “rabid rescue” approach aren’t working — because it prevents people from seeing that encouraging <em>responsible</em> breeding leads to great dogs like Jaina and fewer dogs in shelters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a7d69626b5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The most underestimated tech: The Nintendo 3DS]]></title>
            <link>https://medium.com/@DementedScript/the-most-underestimated-tech-the-nintendo-3ds-fbb20662451?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbb20662451</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[digital-divide]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Tue, 01 Dec 2015 17:22:02 GMT</pubDate>
            <atom:updated>2015-12-01T17:22:02.751Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*gLN5E5FQVnfrRzRrh8yDdQ.jpeg" /><figcaption>Image borrowed from CyberiaPC.com</figcaption></figure><p>Remember when we were kids? We had those giant Sega Gamegears, or maybe we had a big old spinach green Game Boy (pictured over there) that felt almost as large as the later Super Nintendo console that would release many years later.</p><p>It’s kind of amazing how they didn’t change all that much over time. Actually, the original Game Boy is older than I am. It was actually released the year before the <a href="https://en.wikipedia.org/wiki/Berlin_Wall">Berlin Wall</a> finally crumbled — maybe breaching its own kind of wall, of having gaming just in the living room vs. having it everywhere (well, as long as you always had spare batteries on hand).</p><p>You know what else is pretty damn amazing? How it’s evolved. How about this image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JRCJME7-VXg9QmgLO2G9Og.jpeg" /></figure><p>And here’s the link to the <a href="http://visual.ly/retro-tech-nintendo-game-boy-evolution">source</a>.</p><h3>Green Screen to 3D</h3><p>I admit it. I skipped several generations. My parents weren’t terribly fond of video games. I went from that 1989 spinach green Game Boy almost directly to a DS Lite (I wanted to play the Game Boy Advanced games I never had as a kid — no regrets!)</p><p>I now own a <a href="http://www.amazon.com/Nintendo-Pokemon-Limited-XL-Blue-3DS/dp/B00EV4O86I/ref=sr_1_2?ie=UTF8&amp;qid=1448989082&amp;sr=8-2&amp;keywords=pokemon+special+edition+3ds+xl">Pokemon Special Edition 3DS XL</a> (except mine is red, not blue), and its one of the coolest pieces of technology that I’ve encountered, and I think you should agree with me for the reasons I’m about to discuss.</p><p>That’s pretty amazing that it’s made this huge jump. My 3DS can run games that I previously needed a full, immobile console to run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*4div4MtO9DckEH0hqYhJyw.jpeg" /></figure><h3>Tiny Tech, Tiny Price</h3><p>Probably the most comparable piece of tech that I can compare it to is your cell phone. I’ve used a few different phones, but let’s take either the Nexus 5 or the iPhone 6 (both of which were mine at one point). First, they make calls. The 3DS does not (sadly or not sadly, depending on how many telemarketers call you).</p><p>My iPhone’s base price is also something like $600, and if I had gotten my Nexus 5 from a retailer without Google’s cushioning on the price, it’d be about the same.</p><p>My 3DS was $200. A normal 3DS (comparable to mine without the super cool Pokemon on it) would run you about $130–150, depending on when you bought it (I think they’re currently $180).</p><p>But my phone surely has other, better features, right?</p><h3>Base Tech</h3><p>The base tech on your phone is generally going to be better. For example, I have a set amount of wifi connections that my 3DS can do. The camera isn’t going to take the amazing pictures that my iPhone does. Its browser can also be a bit lacking at times.</p><p>However, take a look at those prices again. It’s less than 1/3 the price of my cell phone… and it has two screens. One is a touch screen, the other can do 3D (to a really cool extent, and without 3D glasses).</p><p>Side note: many people do complain about 3D. The major problem with it is that it does require you to be at a certain angle, or else it can be a bit disorienting. Luckily you can turn it off. But think about it.</p><p><em>You’re getting a 3D screen as well as a touch screen for $150. In a handheld, at that.</em></p><h3>But what about apps?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/1*rcgHgAZij-6lAXlpdc3Fgw.jpeg" /><figcaption>Current 3DS Home Screen, pink theme</figcaption></figure><p>The DSi, which I skipped, had something called DSiWare. This allowed users to download games or something to play on their DS. It was handled pretty clumsily — you couldn’t really download them to another system, but I believe you could transfer them with an SD card.</p><p>According to our infographic, that was right around 2009. The iPhone debuted in June 2007. That’s two years apart that this hand-held game system began to allow you to download stuff. Oh, and the original DS and DS Lite? Yah, those already had full touch screens. Small ones that scratched easily, but I think we’ve all seen how the original iPhone became the moment it was unboxed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*TQl5YfwdHdDFU_sBQWbBag.jpeg" /><figcaption>This image might be a slight exaggeration</figcaption></figure><p>And now, Nintendo has followed suite with its own app store. I can watch NetFlix and YouTube on my 3DS. Or, I can download a plethora of games released to the Nintendo store.</p><h3>No, it’s not perfect</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*5cMfFsYo19uLhxgsJIlfsA.png" /></figure><p>I’m by no means stating that the 3DS XL is the best piece of tech ever. Hell, it’s twice the size of my iPhone, and if I had to choose between the two while stranded on a deserted island, I’d probably go with my phone well ahead of my 3DS (not that I’d have any signal, but you know… details).</p><p>The thing is, the price and the specs it does bring to the table. It’s pretty impressive what this can do for a third of the cost of my cell phone. And I think that because of how underestimated the 3DS is, that’s held it back.</p><p>I’d love to see more indie developers make titles for the 3DS. I’d love to play their stuff on it. I want to see it get more, better, market penetration. Because this is the kind of tech we need to look at — accessible tech that’s actually pretty durable, and has lots of cool stuff it can still do.</p><p>This is the kind of tech that allows underprivileged children be able to <em>do</em> stuff — better learning software and things. A less privileged child could load this with their music, play games, do things — you know, kid related things. And for those who seem to think technology is inherently bad, it’s <a href="http://one.laptop.org/">empowered kids in less developed nations</a> so that they actually have a chance in a more modern society. This is the kind of tech that helps us bridge the digital divide.</p><p>So yes, I think my 3DS is the coolest thing ever. It’s probably not your thing, but I think you can agree that its not only a marker for how far tech has come in the last 25 years, but it’s also the kind of tech that’s going to empower an entire generation of people. And that’s <em>amazing</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbb20662451" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Google UX Engineer Interview]]></title>
            <link>https://medium.com/@DementedScript/my-google-ux-engineer-interview-d79bb5854c06?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/d79bb5854c06</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[google-interview]]></category>
            <category><![CDATA[ux-interview]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Sun, 01 Nov 2015 01:37:27 GMT</pubDate>
            <atom:updated>2015-11-01T01:58:06.421Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s probably a bit overdue for me to actually write this, as my actual interview experienced occurred some time ago. However, I’ve come to realize that nobody has actually written about this, so I think it’s important that I begin.</p><p>First — hi. I’m a front end engineer here in the Bay Area, and my passions are user experience, CSS, and cat videos. I wouldn’t consider myself to be much more than your run-of-the-mill mid-20s Bay Area front end developer. (Well, I guess I’m not entirely run-of-the-mill in many ways, but let’s just pretend I am, because the rest of the details Don’t Really Matter here). I’m not actually looking for a job, and I’m quite happy where I am now (and intend to stay there at this point). Edit to add, because I think this is relevant — I do not have a degree. I am working on finishing mine, but I absolutely do not have any degrees past high school.</p><p>Several months ago, a recruiter reached out to me. I have a special folder for recruiter emails —Gmail named it “spam” for me, and the cool thing is that it cleans itself out automagically. However, this one actually got through, so I opted to take a look.</p><p>It was, as you might guess, a Google recruiter. I kind of took a second look — verified that the headers didn’t point toward some other odd site and that it wasn’t from some outside recruiting agency (I try to avoid those — poor experiences in the past).</p><p>So I responded.</p><h4>Getting started</h4><p>If you’ve interviewed as much as I have, you know the general way that technical interviews and hiring go. You begin with the phone. In this case, the recruiter had actually emailed me about some really cool full stack opportunities — that didn’t match my passion or skill set. This was Google, though, so I unabashed responded back with how my passion’s not necessarily full stack but with the overall user experience.</p><p>They forwarded me to another recruiter, and we had a quick chat, and I officially applied for an User Experience Engineer position.</p><h4>The phone screen</h4><p>As per most technical hiring processes go, before you ever get to shake hands or see the insides of any campus, you have to do a phone screen. You can probably read a few accounts of how Google does theirs; for UX engineer, it wasn’t too different.</p><p>The question was incredibly easy. I don’t recall the exact one, and even if I did, I’m not really at liberty to say (mostly because I said I wouldn’t, and I like to keep promises).</p><p>Needless to say, I’d classify the question as something that anyone should be able to write if they can do basic DOM manipulation with vanilla JavaScript. The interviewer himself was extremely helpful and polite, and at the end, I had a pretty good feeling about it — and I knew I really, really wanted to get this. There were also a few intermediate-to-advanced CSS questions to ensure I actually knew how selectors and specificity worked (kudos for that — far too many front end interviews completely ignore this).</p><h4>To Mountain View!</h4><p>So, as the header implies — I was very shortly informed that I’d be interviewing in Mountain View! I expected that it’d be some time before I could get down, but boy was I wrong.</p><p>Large companies have become infamous for incredibly slow interviewing processes. This was not a slow interview process, but rather a very quick one. My date was set only a few weeks after my phone interview — not giving me terribly much time to cram.</p><p>The person setting it up asked if I would need any arrangements for travel or anything, really. Because I live just an hour or two away, I opted to pass on travel arrangements — but still stayed closer to campus at a friend’s house. I didn’t want to be tired the day-of.</p><p>In preparation, I consumed everything I could about data structures and JavaScript. I re-read <a href="http://www.amazon.com/JavaScript-Definitive-Guide-David-Flanagan/dp/0596000480"><em>JavaScript: The Definitive Guide</em></a> and <a href="http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742"><em>JavaScript: The Good Parts</em></a>. I picked up <a href="https://play.google.com/store/books/details?id=t4wZBQAAQBAJ&amp;source=productsearch&amp;utm_source=HA_Desktop_US&amp;utm_medium=SEM&amp;utm_campaign=PLA&amp;pcampaignid=MKTAD0930BO1&amp;gl=US&amp;gclid=CKnTqKeB7sgCFUHgfgodbJIGhg&amp;gclsrc=ds"><em>Learning JavaScript Data Structures</em></a>. (Regardless of if you’re interviewing or not, I strongly recommend all of these texts.)</p><p>Additionally, I reviewed everything I could think of in terms of CSS and user experience. I even bought a whiteboard and practiced writing search and sorting algorithms and other similar problems on it.</p><p>By the end of my preparation, I felt incredibly exhausted and ready to go.</p><h4>And finally, the big day</h4><p>I arrived at Mountain View only half an hour early. I stayed in my car, and spent some time doing some last-minute review, and attempting to calm my nerves. (Relevant to mention here — I have an awful anxiety disorder. I become physically ill under pressure. Think test taking anxiety on steroids.)</p><p>The campus was overwhelming. I can’t quite encapsulate the feelings of being there — of being at <em>Google</em>. The excitement felt almost tangible; I’d become a kid in a candy store. The South Bay area can be described as many suburbs, with lots and lots of traffic and lots and lots of big companies. Google’s campus has more or less taken over a greater part of the Mountain View area. Covered in trees, the buildings aren’t particularly towering but they are still formidable and neat. Near the center of the particular part of campus in which I’d be spending my time, there was a bed of rocks. I assume that this would have been a pond if the entire west coast weren’t enduring a pretty harsh drought.</p><p>Finally, with ten minutes remaining before the appointed time, I got out of my car and went to the lobby to check in.</p><p>The lobby area can only be described as purely Googleish. Out here, it’s pretty common to have lots of colors and people dressed casually. This lobby had a Maps car outside, and had the palette that you’d expect from Google. The person at the front desk verified my ID, and then directed me toward a kiosk where I’d make my badge. The kiosk itself was a bit difficult to use; the touch screen lagged a little bit and made it hard to scroll (I’m a UX person so yes — this does stand out to me pretty clearly as probably the most negative experience I had all day. [Please read that sentence with the hint of humor it is supposed to have.][But seriously, if you work at Google, PLEASE fix that poor kiosk’s touch screen!]) I finally found the name of the person I needed to connect with, and out popped a badge. There was a bin of clips that you could choose from — they were all Google colored clips. I chose a red clip.</p><p>Another girl sat in the lobby area; she’d finished checking in just as I’d entered the room. We talked a little bit, about what we were interested in and what we were interviewing for. I’d rather not go into details here, because I don’t want to give anything too revealing.</p><p>Finally — the recruiter stepped out. It was time.</p><h4>Four scores, and several other bad puns ago</h4><p>The recruiter went over the schedule with me. I would be having four interviews, and one lunch that she promised would not be an interview.</p><p>By the time the first interviewer stepped into the room, my stomach was ready to serve my mostly-digested breakfast to him. I’m very glad it didn’t, but I’ll go ahead and use that as an excuse as to why I did poorly on this problem.</p><p>When I worked customer service, we used a term on really angry or upset customers. When a customer is extremely upset, they stop listening and their head gets all tangled up. They kind of withdraw. We call this going turtle.</p><p>I went completely turtle.</p><p>The problem was a much more advanced JavaScript problem. It didn’t involve graphs or anything like that. I won’t tell you the question (as I mentioned — I promised that I wouldn’t), and even though I had never seen that problem before, its still one I should have gotten correct pretty easily. However, by the end, I took a breath and collected my thoughts. I didn’t finish the problem, but I did my best and got pretty close, I think. In fact, I looked it up later — I did get pretty close. Had I not spent the first twenty minutes tied up in a shell, I probably would have been fine. The problem itself dealt with how events are handled with server-side JavaScript — likely because of my background in developing on NodeJS.</p><p>The interviewer just reminded me — when he saw my crestfallen demeanor, I’m sure — that it wasn’t about getting the right answer but actually showing how I thought. I took it as a sign that I wasn’t completely out.</p><p>He left.</p><p>The second interview began shortly after that. This one went so much better! I actually worked through the problem, and even got to do a ton of refinement on it. This problem involved dealing with lots and lots of data, with some performance optimization thrown on top. I felt that it really got into how I approach front end performance on mobile.</p><p>I can’t tell you how well I did on it, or other specifics, but I will say that I feel confident that I did as well as any candidate with my experience would have. The interviewer and I talked a little bit, and she and I discussed other methods of resolving the problem. I’d come out of my shell at least a little bit — maybe I had some hope after all!</p><p>She left.</p><p>My third interview would be with a designer. This would not necessarily be a design interview, but rather more of a soft-type and actual UX interview.</p><p>It’s difficult for me to say what part of the entire day was my favorite, because I greatly enjoyed all of it, but I think this was very high up there. We discussed lots of topics relating to UX, how I — as a front end engineer — interact with designers, and other HR-type questions. In addition, we discussed a few UX-centric questions. I greatly enjoyed this conversation because — in general — I really like talking about UX. Not to mention, I love many of Google’s products. While I use an iPhone, I may as well still be on Android — because the entire Play suite compromises the main apps that I use on iOS. So, discussing UX and Google at the same time would certainly be something that makes me very happy.</p><p>He left, and it was time for lunch.</p><p>In an all-day interview panel at Google, lunch is not supposed to be an interview. I’m not entirely sure that mine was. I met up with the Googler that I’d be having lunch with.</p><p>We went to one of Google’s many cafes. The food there is free, as you might imagine. That cafe happened to be serving some kind of enchiladas. I had those, a salad, and some sort of cookie. The food was very good, though admittedly I barely remember it.</p><p>At lunch, the Googler and I just talked about life at Google, the kinds of projects I was working on, and what interested me. He had noticed that one of my projects pertained to <em>World of Warcraft — </em>so there came the expected question of why I wanted to work at Google more than I wanted to work at Blizzard. I skirted around it, as I always do, and even here I will skirt around that question. I only mention it because — it seems — even the lunch knows your resume and what you’re up to.</p><p>We also just discussed interviewing in general. He apparently worked with the person that I’d be interviewing with next, so we discussed a little bit of what to expect.</p><p>If there’s one thing everyone tells you to study before you interview with Google, it’s your data structures. I’m glad to announce that studying my data structures came into play here.</p><p>He escorted me to my next interview with his coworker.</p><p>All of my interviews — and even the lunch up until this point — had been a one-on-one. Google takes their interviews very seriously, and has people actually train to do interviewing. I mention this because, part of that process is that a future interviewer will shadow another interviewer. In this case, my interview would be shadowed by someone working in a role similar to mine.</p><p>This is the interview I was probably most prepared for. I don’t know how many problems I actually worked through, but it was a <em>lot</em>. And they were fun. At one point, we even did a problem I’d seen before. Word for the wise — if this ever happens to you, gently let the interviewer know. Sometimes, as in my case, they’ll have you work it out then and there. I showed my solution, so the problem was given a twist and we went into a couple of optimizations that were very nit-picky. I think the only data structure we didn’t cover were linked lists and graphs, actually.</p><p>Because I’d blazed through the problems and their variations, there was lots of time at the end for the shadow and I to go over things. We did a few CSS exercises, which I was told would not be part of my overall assessment. This made me sad, because this was the only time I was actually given anything related to CSS all day.</p><p>At the end, we kind of just chatted. My day was done, but these guys were pretty neat. They worked at a company that I could never have even dreamed of ever interviewing with, and they were pretty cool people themselves.</p><p>Oh, and they’d also noticed my project with <em>World of Warcraft</em>. We talked a little bit about the just-announced expansion. I still played coy (I’ve been bred with the notion of never, <em>ever </em>mentioning my gaming life to any employer, ever). But, it’s still cool that the engineers were interested and shared something like that in common.</p><p>I drove home feeling happy, but I had the feeling it would be a no.</p><h4>Why it’s going to be a no</h4><p>Google’s a pretty particular company. For any candidate which passes through their doors, you can bet that they will find anything that they can say no to. They will contact previous colleagues of yours if they work at the company (I had one or two which I mentioned to the recruiter — actually, I’m told they set up my initial phone screen almost immediately after my Googler friend gave his recommendation).</p><p>After your day of interviews, your application is sent to a hiring committee. Google attempts to avoid any type of bias in their hiring process, as they are hiring for the company as a whole — not one single team.</p><p>This committee typically meets on Thursdays. I had interviewed on a Thursday, so I had to wait an entire week to get back the bad news.</p><p>In addition to finding anything they can to deny a candidate, Google cannot give terribly much feedback. In my case, the recruiter informed me that I actually did really well in the interviews. However, I just didn’t have the experience the hiring committee wanted. Reading between the lines, it came down to the fact that I’d mostly worked short-term contracts and hadn’t been at any one company for more than a year and a half at that point. I think that’s fair enough, even if I had good reasons for not having been anywhere for terribly long at that point.</p><p>While many people think the automatic no is a bad thing, the entire process can be incredibly expensive for Google if they do get a false positive. I do agree with their philosophy of preferring false negatives over false positives. It’s much more difficult (and expensive) to get rid of a bad engineer than it is to not hire a good engineer — especially with the many, many applications they receive all the time. I can see where it’s even more expensive if that particular engineer has a history frought with layoffs and contracts. This goes into the rabbit hole of how our generation finds it difficult for many reasons to be at any one gig for a long time, so that’s as far as I can really discuss that.</p><p>Overall, though, I think I will take the recruiter’s advice and reapply next year. The worst that can happen is another no, after all.</p><p><strong>tl;dr</strong> — If you work at Google, could you please poke someone to revive the Google Voice team? The UX is awful and there are still people that use it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d79bb5854c06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Difficulty of Interviewing Front End]]></title>
            <link>https://medium.com/@DementedScript/the-difficulty-of-interviewing-front-end-9e685f9c526c?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e685f9c526c</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[interviewing]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Sat, 31 Oct 2015 22:05:37 GMT</pubDate>
            <atom:updated>2015-10-31T22:05:37.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*p_aUY8fI-63jwR7m2yeKWQ.jpeg" /><figcaption><em>Courtesy of </em><a href="https://stocksnap.io/user/saumya04"><strong><em>Saumya Rastogi</em></strong></a><strong><em> </em></strong><em>at StockSnap.io</em></figcaption></figure><p>Over the years of my career, I’ve encountered many a front end developer — mostly because I’m a front end developer. We all have gotten various starts. While a few began as back end developers that had eventually learned CSS, HTML, and various other things relating to the actual presentation and client-side interactions, most came from pretty varied walks of life and were self-taught.</p><p>In fact, I’d say the majority of front end developers were self-taught.</p><h4>The issues with self-taught developers</h4><p>Mind you, this is using the term “issues” rather lightly.</p><p>First, let me note that I do have some CS background. I haven’t completed a CS degree (though I am slowly working toward it and am certainly taking classes), but I’ve at least taken classes relating to discrete logic and data structures, as well as algorithms.</p><p>A self-taught developer may have worked with control structures and some data structures, but they likely haven’t been exposed to graph theory or a linked list. They probably wouldn’t even be able to describe a visitor pattern. I’m making these sweeping generalizations because in my eight years of having worked as a front end developer, I’ve never had to write a visitor pattern or worried about a linked list (though this hasn’t stopped me from doing it in my free time to stay brushed up on my structures).</p><p>I call this an issue because both of these have appeared when interviewing for front end positions — not full stack, but front end. While I do believe that a full stack developer ought to have an understanding of your most basic algorithms and data structures at the bare minimum, most front ends likely would never even be exposed to these.</p><p>Think about it. We certainly work with trees every day (one could consider the DOM itself a tree), sets (JavaScript objects are actually wonderful for making sets), but it doesn’t really take a knowledge of linked lists to select an element’s parent or child.</p><h4>Let’s go back to how I called this an issue</h4><p>The issue is how front end developers are hired.</p><p>I’ve interviewed at many companies, and I’ve interviewed many front end developers. There are thousands upon thousands of posts about this, so I’ll try to avoid reiterating already good points. Instead, here’s a list of things to consider.</p><ul><li>Some companies care more about whether or not one is advanced with JavaScript. Many of these interviews may never even touch on data structures but rather whether or not the developer understands the basics of scope and closures, and might ask about <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/apply">a</a>/<a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind">b</a>/<a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/call">c</a>.</li><li>Some companies care about a candidate’s logic. I believe that this falls into the general difficulty with interviewing engineers — except I’d say it’s doubly worse for front ends (mostly because we’d typically expect the type of interview I described above). These are the type who ask more in-depth questions, such as the differences between breadth-first search or depth-first search.</li><li>Some companies care about both of these.</li><li>Not enough companies ask anything remotely related to CSS or UX.</li></ul><p>In fact, I have to admit that only a minority of companies I have ever interviewed with ask me a single question about CSS. That’s a damned shame — considering that certain CSS properties will play differently across browsers, other properties, and so on. There are quite a lot of nuances with it, in fact, and quite a lot of discussion. (And, frankly, I fully believe that CSS is still important for performance — not just in terms of actual browser performance, but also in terms of maintenance.</p><h4>Data structures, algorithms, and the general CS background</h4><p>I think that a good background in CS is critical in order to understand the innerworkings of front end development and to actually understand how things interact.</p><p>However, for most intermediate to even advanced front end developers, the simple fact remains that it’s just more important to write performant code that isn’t a migraine to update or change, and can be used elsewhere. This does not involve understanding that each element in the DOM is — theoretically, at least — a node in a linked list or tree or graph or whatever.</p><p>Thus, I can understand how many front end developers believe that in-depth algorithm problems hardly measure whether or not they are great front enders. I’ve certainly been there, and I’ll agree that — to an extent, at least — many companies in our industry overvalue whether or not we can solve a graph-related problem.</p><p>But let’s take a step back into our time capsules through history.</p><p>When I began seven years ago, there was a division between designers and the web. Most designers had never written a single line of code. Indeed, I worked with many of them — and they had no idea how the web actually worked. How many times have each of us had to push back on a design because the designer wanted something that just wouldn’t work in semantic HTML (and then we had to explain the importance of semantic HTML)? Back in those days, I stated that designers needed to learn how to code a page, that way they would not send obviously impossible designs to web developers.</p><p>In a similar sense, I believe that front end developers need to understand how their code connects to the rest of the stack. This requires some background in computer science, and some general understanding of how logic works. This way, we can take better ownership when things go wrong (or when they go right). We can create our own features for applications. It is not to say that I believe front end developers need to become full stack — in fact, I rather dislike this trend because I do not believe it as good for rapid development (front end already requires quite the plethora of disciplines to be good or really good).</p><h4>So how deep should we go?</h4><p>A good front ender does not need to have an in-depth understanding of advanced algorithms. A good front ender does not need to know the super complex algorithms that might be required of a really good C++ developer. I’d even argue a good front ender need only understand prototypal inheritance — I haven’t used classical inheritance in ages, myself.</p><p>A better front ender needs to understand how their application works and the implications of what they are doing. For example, a better understanding of linked lists or trees might make it easier for you to find a certain node on a page (rather than relying on needing an ID on that node, and making your code much more fragile).</p><p>A great front ender should absolutely be able to solve a <a href="https://www.cs.bu.edu/teaching/alg/maze/">maze problem</a> with HTML/CSS/JavaScript. But they probably will never use more advanced versions of graphs (unless it is for a very specific type of position).</p><p>But none of these three should be passed over if they don’t have an immediate answer for your obscure algorithm or mathematics question — especially if you forgot to ask them about CSS and performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e685f9c526c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Branding, and why changing the logo is hard]]></title>
            <link>https://medium.com/@DementedScript/branding-and-why-changing-the-logo-is-hard-1c2bd29fea3a?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c2bd29fea3a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[logo-design]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 16:09:43 GMT</pubDate>
            <atom:updated>2015-09-01T17:15:09.336Z</atom:updated>
            <content:encoded><![CDATA[<p>Yep, it’s another one of those “Google’s new logo” posts! And probably not the last you’ll read today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vNH2zwdSkHbrKpvHvWSPEA.png" /></figure><p>To the untrained eye, the logo probably looks exactly like the old one. I mean, you aren’t correct, but you also aren’t wrong. I mean, they changed to a sans-serif font? Here’s a gif of their last logo change, with credit to the <a href="http://www.independent.co.uk/life-style/gadgets-and-tech/news/google-unveils-new-logo--prepare-to-not-have-your-mind-blown-9440114.html">Independent</a> of the change:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*nYF2DwzCnvIFBfKzeG-lHw.gif" /><figcaption>Credit to Independent for the gif, since I was too lazy to make my own.</figcaption></figure><p>That’s a pretty subtle change, and probably only someone super into typography will even notice. However, keep in mind that their logo also used to look like this (yes, borrowed from the same article):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*jbBVcn3kuEgOibJ8yxSm3Q.jpeg" /><figcaption>Thanks Independent for making this easy!</figcaption></figure><p>In other words, it has changed. It’s updated from 1995, to 2010, to now 2016 (kind of like owning a car, if you think about it).</p><p>I think the thing to drive home is: changing your logo is <em>hard</em>. It’s your main brand — your main <em>you</em>. Redesigns in general are bad; not just because of the amount of work involved, but also because of the need to mitigate user reactions.</p><p>But of course, the new one is even… more polarizing to many people. But that’s simply keeping up with the times.</p><h3>A Gap Study</h3><p>You probably don’t remember this, but Gap actually tried to change their logo once. It didn’t work out so well. Here’s the one we know:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5NAaYhuRGDFRhg-tgcXpKA.jpeg" /></figure><p>Here’s what they wanted it to become:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*TYQpQ13jw4UcIo1RHYJS_g.jpeg" /></figure><p>And here’s what the <a href="http://www.thenextgreatgeneration.com/2010/10/gaps-epic-logo-fail/">internet</a> thought about it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*lD7Ag_oYsAoMMpaTvFlGDA.jpeg" /></figure><p>The “new” Gap logo honestly isn’t that bad. However, it throws away the branding that had become so incredibly recognizable for something that just… well, it didn’t look bad, necessarily. It was simply <em>too different</em>.</p><p>This is why you probably aren’t that blown away by the new Google logo. Because Google’s a tech company, they tend to understand that a wild change to their logo will turn users off — and will cause their branding to take a hit as well.</p><h3>Site Redesign Woes</h3><p>This all ties into how users react to site redesigns, and how we can mitigate that.</p><p>One of the issues I personally had with Android is that it changed pretty rapidly over iterations. However, I also really appreciate that. While there might be huge reskinnings between large version changes, Google tests and sees what works well, and subtlely moves us away from something that might not work as well to something that does.</p><p>This means that version 1.0 might be <em>quite</em> different from 1.9. However, the user has been allowed to adjust to changes over time — this is actually a much better user experience than doing too many large changes in a version number change.</p><p>Consider, for example, the reactions to iOS 7.</p><p>I actually like the “new” iOS. Yes, 7 had its flaws — any major OS change will have that (just consider the jokes we make about every-other Windows version change). However, much of the reaction came as “I don’t like it” because its “different.” We’re creatures of habit — we just in generally don’t like “different”, even if — in theory — it’s a better experience for us.</p><p>Facebook presents another prime example. Gizmodo has a <a href="http://gizmodo.com/the-most-important-facebook-redesigns-in-facebooks-10-1515699149">pretty good rundown</a> of the different facelifts that Facebook’s gotten, so no need to reiterate — other than to point out how wildly different the site has become. Now, pay attention to that timeline change there. That was a major change. How many users thought that was the end of Facebook or other doomsday thoughts?</p><p>Fact is — users hate change. They have to relearn everything from scratch. The best thing Facebook did for their Timeline redesign is that they rolled it out slowly, and made it an opt-in for users at first rather than pushing everyone into it. Now, they’ve done some very subtle changes, but at least appear to have learned exactly what Google and other companies are beginning to pick up on — do changes slowly. Don’t inundate users and make them relearn your site.</p><p>It’s just a better user experience if the only time they notice your changes is when they are delighted by them.</p><h3>Thus, Sans Serif Google</h3><p>This is a pretty huge change for a company that’s previously done incredibly subtle changes. It’s not to the extent of Gap or even Facebook, but it’s a pretty large step to suddenly change typeface like this.</p><p>However, sans-serif fonts read better for people on a wider array of devices. They have taken a greater amount of adoption because well… simply put… they look better. They’re easier to read for people with dyslexia.</p><p>No, this isn’t a step toward comic sans. This is a step toward a more up-to-date Google, and I don’t think it’s a step in a bad direction. People will cry foul and refer to it as “ugly” — but the truth is, it’s just <em>different</em> from the logo an entire generation has come to love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c2bd29fea3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech and Gaming Aren’t So Different]]></title>
            <link>https://medium.com/@DementedScript/tech-and-gaming-aren-t-so-different-dedf92b64e81?source=rss-332c4f758750------2</link>
            <guid isPermaLink="false">https://medium.com/p/dedf92b64e81</guid>
            <category><![CDATA[ilooklikeanengineer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Callie]]></dc:creator>
            <pubDate>Fri, 14 Aug 2015 17:49:31 GMT</pubDate>
            <atom:updated>2015-08-14T17:56:44.848Z</atom:updated>
            <content:encoded><![CDATA[<p>The lines out the door probably should have been an early signal of how successful the #ILookLikeAnEngineer had become — seemingly overnight. Admittedly, I had started one. Commuting over from Oakland, I didn’t trust the BART to be on time, and I had always overcompensated for my inclination toward lateness by arriving no less than fifteen minutes early.</p><p>Hundreds of people appeared, with a line snaking its way through the Rackspace headquarters. Over catered quinoa, locally brewed beers, and other delicious treats, it seems like people of a similar mindset had found their way under one roof.</p><p>The only way to describe this is amazing.</p><p>However, many of the issues discussed last night are so incredibly prevalent that simply discussing them in tech just doesn’t do them justice.</p><p>I don’t speak alone when I state that discrimination raises its ugly head in other parts of society. But let’s consider an area that’s honestly not so different from tech — video games.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*-X2IwtadVX076pJZL5P0cw.png" /><figcaption>Yes, she DOES give me code reviews.</figcaption></figure><p>This is my dog. Her name is Jaina, and she was named after my favorite video game character, Lady Jaina Proudemoore. I wanted to give her a strong name, and Lady J was an incredible character in <em>Warcraft 3.</em> She’s also my Twitter icon because she is that awesome. (It’s also worth noting that she deals with her own discrimination, because she’s a purebred, working Doberman.) This seems pretty disjointed to be in an article about gaming and tech, but A) I love this dog and so should you, and B) you don’t just name your dog after something that’s not incredibly important to you.</p><p>Hi. My name is Kim, and I am both an engineer and a gamer. I’ve had to prove my “gamer cred” almost as often as my “engineer” cred. I play mostly MMOs, in which I have played in top world guilds. I’m currently playing in one of the top ten US guilds for <em>World of Warcraft</em>. I don’t play a healer, but I have in the past. Actually, I prefer playing melee or a tank (I just can’t do casters in general). I also write a column dedicated to my class, write several guides relating to my class, and also interact pretty heavily with the community. In <em>Final Fantasy XIV: Heavensward, </em>I lead a free company (a guild) and a raid, and I am its main tank.</p><p>But I’m not a real gamer. Because I don’t look like one, and I don’t play whatever the acceptable game is.</p><p>Similarly, I’ve had to prove several times that I can be an engineer. I’m actually extremely passionate about user experience (and honestly, front end in general.) I currently work for a relatively well-known company (which I will not reveal here, so as to not get the PR people mad at me!), which is amazing — my team is <em>incredibly</em> diverse. And it’s the most accepting team I have <em>ever</em> been on. That’s pretty special to me, considering the hurdles I’ve had to endure — hurdles that, in retrospect, aren’t too different from the same crap I deal with in gaming.</p><p>Just a month ago, I did a podcast discussing my own class in <em>World of Warcraft</em>. A new tier had just released the week before, and I had only recently joined my guild. <a href="http://finalboss.tv/main/2015/7/13/episode-87-calligraphy-irysheman">Here’s a link</a>. It seems pretty good — Bay and Iryshe are pretty awesome people, and have treated me well. In fact, I’d say that the majority of the community is pretty damn awesome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*MRMEGRRWrzwoMSLdoDQwoA.png" /><figcaption>my monk looks so angry… She honestly isn’t though!</figcaption></figure><p>However, then there’s the behind the scenes. The level 1s that were made on my server to go tell me to “kill a real boss” (keeping in mind — the “real bosses” hadn’t even released yet), the comments to show them my chest, and other things I’ve since tried to block from my mind. Trolling is fine and teasing is fine, and I’d brush it off. Except, I’ve been on this podcast three times now, and these are the kinds of comments showered on me each time.</p><p>Gaming and tech are not so wildly different. I, for one, happened to be brought into gaming through tech. At 15, the person who inspired me to learn how to code in C also introduced me to <em>World of Warcraft</em>. I grew up in an incredibly conservative family that barely even allowed me to play <em>Pokemon</em>, much less anything else. I don’t think it’s any secret that gamer culture is cruel, cold, and unaccepting — everything that tech culture can be, except its more open about it because of anonymity and the issues dealt with by several indie developers that happen to be women.</p><p>It pains me that so many of my friends are treated horrendously by gamers and are afraid to play non-single player games. It makes me angry that minorities have slurs thrown at them in what should be safe, comfortable environments — whether they are women, or trans, or homosexual, or Asian, or Latino, or whatever. It makes me so angry that we have to have our “gamer cred” and our “engineer cred” questioned just because we don’t look the way that people think we should. In fact, I am embarrassed that a guild known to have game developers from a specific company has this <a href="http://www.nurfed.com/faq/">FAQ</a> for their guild (do a quick search for the “fairer sex”) — worse comes the fact that this type of stereotyping remains ubiquitous and simply unspoken in the raiding community.</p><p>And I am so happy — so very, incredibly happy — that we are talking about this. We’re talking about this in tech. We’re talking about this in gaming. Women — who were the <a href="https://en.wikipedia.org/wiki/Ada_Lovelace">first programmers</a>, who were <a href="https://en.wikipedia.org/wiki/Women_and_video_games#Carol_Shaw">game developers</a> before it was a real title and were as common on the Atari as they were in the arcade — are treated like metaphorical black sheep in the fields that we pioneered in. That’s pretty disgusting.</p><p>So, to echo the sentiment of last night — now what? Now, we keep the conversation going. We show companies — both in tech and in gaming, considering how close both of these are — that they cannot shut us out. When we’re asked about our gamer cred, we tell them exactly how it is: we have nothing to prove to them. <em>Nothing</em>. We are pretty awesome how we are, whether our main games are <em>Halo</em>, <em>Call of Duty, Hearthstone, </em>or <em>Solitaire</em>. We’re amazing just how we are, whether we’re working more in JavaScript, Ruby, PHP, or CSS.</p><p>And now we just need to get out there and talk about it. The only way to change these stereotypes is to show them how false they are.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dedf92b64e81" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>