<?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 Perry Eising on Medium]]></title>
        <description><![CDATA[Stories by Perry Eising on Medium]]></description>
        <link>https://medium.com/@perrysetgo?source=rss-d77fd4733ec8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*t6Z5-jQp6jU_gONfaW7RDw.jpeg</url>
            <title>Stories by Perry Eising on Medium</title>
            <link>https://medium.com/@perrysetgo?source=rss-d77fd4733ec8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:25:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@perrysetgo/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[Making the Jump: From Codeschool to Candidate]]></title>
            <link>https://medium.com/@perrysetgo/making-the-jump-from-codeschool-to-candidate-8881ad3563bd?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8881ad3563bd</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[code-school]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 23:00:43 GMT</pubDate>
            <atom:updated>2018-08-09T23:15:29.427Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I spoke to a group of #futuredevs about networking, imposter syndrome, social media and creating themselves as candidates. Here is a roundup of what I shared.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rvOBhPrYiLD8shRGCj-sYQ.jpeg" /><figcaption>Time to lean in. Photo by <a href="https://unsplash.com/photos/T7RHJ3c6s7Q?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Aaina Sharma</a> on <a href="https://unsplash.com/search/photos/hustle?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Hiring is all about minimizing risk. And while knowing that can be helpful to steer your approach, it can still be intimidating to find your path and transitioning from being a student to becoming a developer. Applying for jobs, combating imposter syndrome, networking, mastering social media, and making a name for yourself can be intimidating — but don’t fret! There are surefire ways that you can build yourself an amazing profile. Be authentic, provide value, and teach from your own experience, and you’ll find that hiring managers have no problem seeing your non-trad background as an asset, not an obstacle.</p><p>Here are some notes from the talk I gave at <a href="https://twitter.com/AlchemyCodeLab">Alchemy Code Lab</a> in Portland that you might find useful as you make your way.</p><h3>Alchemy Code Lab on Twitter</h3><p>Hiring is minimizing risk&quot; &amp;amp; how to confidently tell your story to prove you&#39;re a rockstar. Thanks to @perrysetgo for the great conversation at Alchemy today!</p><h3>Standing out</h3><p>Many code school students background as sector-switchers are comparable, and while everyone has different strength’s and weaknesses, their acquired knowledge is largely comparable in terms of stacks, tools, etc. Therefore, many self-taught and code school devs will gravitate towards the same kinds of jobs. It’s important to be aware of this, and take extra steps to differentiate from peers and other self-taught/non-trad educated people in order to get great opportunities that are right <strong>for you. </strong>It’s time to break away and curate your dev profile that is uniquely you.</p><p><strong>Some ideas on how you can differentiate yourself:</strong></p><p><strong>Leverage previous life/job/work experience confidently. </strong><br>Great people, presentation, collaboration, time management skills etc are NOT inferior to great tech skills. Many “rockstar” “ninja” “10x” coders are kind of toxic to be around and not that interesting. What can you leverage? Who have you been? What have you learned? Mine your life/career for skills and experiences. Showcase those on your LinkedIn, resume, profile, cover letter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*aO4WMyOTzsZjOQ-a.jpg" /><figcaption>There is a lot here where previous life experience is very applicable.</figcaption></figure><p><strong>You have a unique perspective. </strong><br>Use your linkedin, resume, cover letter, social media presence, approach to networking, blog etc to tell the story of <strong>You</strong>. Nobody recommends on a dime. Being a great student is awesome, but not that compelling. Show yourself in a memorable way so that people can talk about you and your journey. Find some key things: topics, technologies that are your “thing”. Get associated with certain topic areas, technical and non-technical.</p><p><strong>Write/Tweet/Post from your experience. </strong><br>That way you avoid being judged for your content. It’s true, you probably aren’t senior enough to make high level value statements on certain technologies. But you can offer your experience of learning and trying something new and your experience with how that went.</p><h3>Imposter Syndrome</h3><p>Awful feeling that despite all evidence to the contrary you feel like an “imposter” when it comes to technical stuff because you aren’t (yet) a “Rockstar” “ninja” or “10x” dev. Often afflicted by sinking feeling of NTE (Not Technical Enough) — the wishywashiest and most useless term ever in the history of tech hiring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/0*XklvpphKV0N7mP0P.jpg" /><figcaption>Awesome cartoons! <a href="https://www.instagram.com/gemmacorrell/">instagram.com/gemmacorrell</a></figcaption></figure><p><strong>Remember that knowing “enough” is a moving target.</strong><br>Imposter syndrome is a feeling, not an actual state of <strong>You</strong>. What you need to know will keep changing and “enough” is impossible to quantify. Forgive yourself for not knowing. Focus on improving your knowledge, but also working with your attitude to not knowing and how uncomfortable that is. As long as you are working in tech, you will always need to keep learning. Own what you know and what you don’t. A bad attitude is less workable than a knowledge gap. You will never arrive at a state of complete knowing even if you do nothing but study.</p><p><strong>Commitment Driven Development™ (The Perry Method of Learning A Scary Thing) might help overcome sticking points</strong></p><p>1.Find a technical topic you find intimidating (that shouldn’t be too hard)<br> 2. Find a project that has <strong><em>real world value</em></strong> (NO DRILLS! Must be real!) that is a perfect fit to learn this tech<br>3. Find someone to commit to. A close friend, colleague, family member. Additionally, <strong>commit publicly</strong> (slack, twitter, linkedin) to do this thing<br>4. Build the damn thing. Feel the fear, do it anyway. Reapply deodorant. Have a tantrum. Moderate your caffeine intake. Do it anyway. Take some B-vitamins. Do it anyway.<br>5. Complete with hours or even minutes to spare. Demo. Feel super accomplished. Show the people you committed to.<br>6. Listen to some fave music and journal intensely about how you didn’t feel you could do the thing but you did the thing. Pull this out when you feel low.<br>7. Realize you are someone who accomplishes things <strong>they set out to do.<br></strong>8. Walk down street with a new spring in your step (until next time). Now is the perfect time to apply for a job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*moCB5a_mL3iYBWKh.png" /><figcaption>You did it. You really, really did it. Really!! Now do it again.</figcaption></figure><p>(yes. I have done this. And then I’ve done it again. How else do you think I said yes to<a href="https://twitter.com/jukutch/status/1020715935504584704"> MCing a conference</a>? 😬)</p><p><strong>Ask for specific technical feedback at jobs and internships. </strong><br>If you are only getting soft-skill feedback then raise that is a concern! (This happens to women a lot.) Feedback should always be ASK: <strong>A</strong>ctionable, <strong>S</strong>pecific, <strong>K</strong>ind. Talk to your manager if you are not getting feedback you can use to improve in specific areas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AIa9xDqKAlF1Cm1x.jpg" /><figcaption>Make your feedback Actionable, Specific and Kind. If you are not receiving ASK feedback or only feedback on “soft skills” — please talk to your manager about your experiences.</figcaption></figure><p><strong>Take any opportunity to teach and mentor</strong><br>This can be online of off, for money or free. Teaching and mentoring others who are still learning will show you</p><p>A.) what you know and how awesome you are <br>B.) what you don’t know and where you can solidify your knowledge</p><p>Be gentle with yourself if you realize you knew less than you thought. Journal and blog, tweet and network around these opportunities and your growth.</p><h3>Networking</h3><p>Just applying for jobs at random isn’t enough. But neither is just collecting business cards at the latest networking event and then putting them in a box on your desk.</p><p>Consider networking, real networking, an investment in creating and improving a community that you support (and that, in turn, supports you back!)</p><p><strong>Try and be valuable beyond a compliment.</strong><br>You may well have something to offer — a connection, a resource, your time, your energy, your ability to volunteer, connect, drive around, provide space for a meetup, repost, introduce. Create opportunities for yourself and for others as much as possible. Know what you have to give, and what you don’t.</p><p><strong>Listen more than you speak.<br></strong>When meeting someone new, ask them questions, show an interest. Solve a problem for them. It’s not so much about you being interesting at first, but more about being interested. Don’t show off, but also don’t downplay your accomplishments.</p><p><strong>Build a relationship first.</strong><br>Before you make an ask (for a coffee date, a recommendation, a reference, an intro) build a relationship. Show up. Invest authentically. Be valuable. If someone invests time in you, or recommends you, that is a risk for them that they won’t take for just anyone.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCj98mr_wUA0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCj98mr_wUA0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCj98mr_wUA0%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/345ad37abe0aa17ff5a755f7b49855f4/href">https://medium.com/media/345ad37abe0aa17ff5a755f7b49855f4/href</a></iframe><p><strong>Go to conferences, not just meetups. </strong><br>Conferences offer you a chance to dig deeper into content, spend concentrated type with people who will form your network. Research confs online, follow them on twitter. If you can’t afford a ticket offer to volunteer. Many confs also offer <strong>diversity scholarships</strong> that sometimes even cover travel and lodging expenses. Tweet everything you see, do, experience, learn at confs. Use the conf hashtags appropriately. Follow speakers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yGjAjj3gVjeZYXfi.jpg" /><figcaption>Confs like Write Speak Code are awesome opportunities to spend focused time with people in the same field as you, who are also interested in growing professionally.</figcaption></figure><p><strong>Have follow through</strong><br>Say thank you, send a note, give a card, remember someone’s name. Do what you say, don’t be flaky. Be on time. Be present, but not pushy. People with resources are often busy, and many people are seeking them out. Be ready to act promptly when a connection has something for you. Say no gracefully if it isn’t a good fit. Treat these resources as fragile because they are. Don’t burn bridges, badmouth, or gossip.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YxetqGDHEW9HQQ2t.jpg" /><figcaption>Actions reveal priorities.</figcaption></figure><h3>Social Media</h3><p><strong>Prioritize Slack and Twitter over LinkedIn and other job boards.</strong><br>This is my opinion and you may hear different, but I feel strongly the HR folk and recruiters post on LinkedIn, while the team members and people who want curate awesome teams post on twitter and even more so on Slack.</p><p>Slack also offers the opportunity for a personal referral. If you apply for a job you heard on Slack, follow through the with the person who posted it, chat with them, show your enthusiasm, and ask them to ping the hiring manager. It will improve your chances. I got job interviews after already being turned down due to slack chats. <strong>Ask interesting people at meetups which public slacks they like or twitter accounts they follow.</strong> Livetweet meetups, confs and events you go to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*Gy9gMHDHK5snnL0Gbk7FXg.png" /><figcaption>I belong to way too many slack communities, but thats how I know almost all of them have a jobs channel!</figcaption></figure><p><strong>Curate your Twitter feed</strong><br>Even if you don’t post much, follow the right people who are creating and building networks and who RT opportunities. Show some love for those movers and shakers. Comment authentically. RT things that need amplifying. Check it daily. Post quality content that creates value if you do post. Tweet the shit out of every meetup, conf and happy hour you go to.</p><h3>Blogging</h3><p>Blogging is a great way to get exposure and improve your writing skills and ability to communicate in a 1-to-many way (yes, this phrase exists outside of databases) with your network. It also creates shareable content.</p><p><strong>If you don’t know where to start, talk about that.</strong><br>Your life, your experiences in tech, your experiences learning to code, struggles, confs, meetups you went to,interests, parallels, the role of mentors, awesome learning resources, tools, failures. Technical and technical can be on the same blog, but keep it professional until you are more solidified in your career.</p><h3>perry eising on Twitter</h3><p>Why ___ was a mistake and what I learned&quot;&quot;Why we should be paying more attention to ___&quot; &quot;When I started my current role, I wish I had known ___&quot; Super useful writing prompts from @techgirl1908 #WSC2018Conf</p><p><strong>Aim to create value for people.</strong><br>This is quite easily done if you are trying to reach people more junior than you. Speak from experience. What are the last three technical things you googled how to do? Research them, write a guide, publish, circulate on twitter and slack. (Special kudos goes to Jess Lee for this tip)</p><h3>perry eising on Twitter</h3><p>Go to your browser, go to your history, find the last thing you googled, or documentation you struggled to understand, write a summary of that and explain it&quot; awesome advice on finding topics @jessleenyc #WSC2018Conf</p><h3>Conclusion</h3><p>I know what you are thinking — this sounds like a TON of work! How do I have time for all of this — I also have to code and apply for jobs! And it’s true — spending too much time networking and not enough time pushing code is ultimately not going to be that helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*Zij8rMe7lPLg1Uhc.jpg" /></figure><p>But you are likely going to have some downtime after finishing codeschool before you begin working. This is the perfect time to spend time building your network and profile — and you get to add to the narrative as you build your career. You are in this for the long haul — build a network for the long haul.</p><p>You’ll need it. For referrals, but also for support.</p><p>It’s hard to get started, but you’ll find that once you have these building blocks in place, it’s a lot easier to keep the machine humming with less frequent tweets, blog posts and networking events. You can take some downtime, focus on code, and only come up for air when you have the time, space and energy. But that way, you will have created the backdrop that will allow you to step back into the arena as soon as you feel like a job change might become imminent, as opposed to starting over from scratch.</p><p>Good luck! <a href="https://twitter.com/perrysetgo">Keep me posted</a> on what worked for you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8881ad3563bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take it to the stage! I’ll be your emcee for ACT-W!]]></title>
            <link>https://medium.com/@perrysetgo/take-it-to-the-stage-ill-be-your-emcee-for-act-w-a5b965d7082c?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5b965d7082c</guid>
            <category><![CDATA[portland]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 19:20:48 GMT</pubDate>
            <atom:updated>2018-06-27T19:20:48.961Z</atom:updated>
            <content:encoded><![CDATA[<p>Wow~ 😍😍🙏👨‍🚀</p><p>It’s been barely a week since I published my article “<a href="https://blog.usejournal.com/gender-inclusive-tech-events-a-hands-on-how-to-guide-ec93ee477035">Gender Inclusive Events — A Hands On How To Guide</a>”, and judging by the responses I’ve received on Twitter, Medium, and LinkedIn, it really seems to be resonating with people. I’ll be outlining my next steps for this endeavour soon, but for now, it’s time to share some big news!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/0*wMk-5TZysPq9f8M6.jpg" /><figcaption>Love this sticker, still.</figcaption></figure><p>I’ve been asked to do something I’ve never done before — and so of course I did what I do best — I said yes! As the title gave away —<strong> I will be serving as the first, ever, emcee for ACT-W (Advancing the Careers of Technical Women) conference!! I’ll be on stage all weekend, working it, making sure you have the best conference experience possible. Whatt.</strong></p><p>I’m so excited. I’m a little bit scared. I have <strong><em>soo</em></strong> much work to do. (Don’t expect to see me before July 20th when I emerge from my chrysalis with some new jokes) But beyond all that — I am so honored to be part of this grass roots conference whose goals mesh with mine so deeply — making tech more welcoming, more inclusive, facilitating opportunities for women and underrepresented minorities in tech.</p><p>So humbled. So glad. So pumped, actually. So excited to learn from you all about what makes a great conference, so glad to know I’ve been trusted with this opportunity. I won’t let you down.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohryBIvm4noIAF3Fe%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fmartellusbennett-martellus-bennett-black-unicorn-3ohryBIvm4noIAF3Fe&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohryBIvm4noIAF3Fe%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/416c62276cf14f595a8c986a3a37fb44/href">https://medium.com/media/416c62276cf14f595a8c986a3a37fb44/href</a></iframe><p>I’m especially glad to be participating, given that I have always been vocal about my existence as a nonbinary person who uses they or he pronouns. Some women’s organizations, inside of tech or out, might reject the idea of having someone like me on stage, representing. And while my commitment to advancing women speaks for itself, and I experience the same struggles you do, these can be thorny issues — who should represent and speak for women? I’m excited to help facilitate the space for these difficult conversations, online and off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PE4mGGTM5d0myXVl0SdzMA.jpeg" /><figcaption>Speaking at ACT-W 2015!</figcaption></figure><p>So, if you haven’t been to ACT-W, <strong>make this year the year you commit to going</strong>. Why? Don’t come for me -</p><p><strong>The workshops are hands-on and informative.</strong> I mean —<a href="http://portland.act-w.org/schedule/"> have you seen the schedule</a>?</p><p><strong>The speakers are legit.</strong> All experience levels represented, including some inspiring new voices who showed up at ACT-W first.</p><p><strong>The booths are on point</strong>. I’ve had some fantastic opportunities to speak with motivated employers who eager to hire people like you.</p><p><strong>The community is wonderful and welcoming. </strong>The best conversations, the realest connections.</p><p><strong>The swag is so rad</strong> it gets sold at second hand shops as far flung as Boston.</p><h3>perry eising 🏳️‍🌈 on Twitter</h3><p>At boomerangs in Central Square.</p><p>The tickets are cheeeeep: <a href="https://impactflow.com/event/8108/checkout/tickets">$85 for professionals, and $35 for students.</a></p><p>I’ll be there.<br>With bells on.</p><p>See you soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5b965d7082c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gender Inclusive Tech Events: A hands on how-to guide]]></title>
            <link>https://medium.com/@perrysetgo/gender-inclusive-tech-events-a-hands-on-how-to-guide-ec93ee477035?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec93ee477035</guid>
            <category><![CDATA[gender]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[transgender]]></category>
            <category><![CDATA[event-planning]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 20:41:15 GMT</pubDate>
            <atom:updated>2019-08-14T20:55:35.158Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, I’m <a href="https://medium.com/u/d77fd4733ec8">Perry Eising</a>, and I’m on a mission to make tech more approachable and inclusive. I’m the former faculty lead of Epicodus, and a long-time activist bridging the gap between tech, education, and advocacy. Interested in hearing how you can join in — follow me here on Medium or get in touch on <a href="http://twitter.com/@perrysetgo">twitter</a>.</p><h3>What to expect</h3><p>If you’re reading this article, i’m guessing you already have an interest in making tech events more gender diverse and inclusive. As non-binary and trans people are becoming more visible, it’s important to recognize they deserve a place in our tech conferences and diversity conversations. This guide will provide perspectives and ideas on how to be more gender-inclusive and to make a more supportive and diverse climate for everyone. It’s geared towards those who are already planning, advertising, and orchestrating tech events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAXkqX-3cNpp0EGaXCplFg.jpeg" /><figcaption>In order to grow, we must evolve — either reactively, or proactively. Which will you choose?</figcaption></figure><p>Maybe you arent sure if what you are doing is falling short, or feel you could be doing better but aren’t sure how. Maybe you aren’t attracting the diverse crowd you know is out there, or your group recently gained a few members who are pointing out flaws in your process. Maybe someone has called you or your event out publicly. Maybe you are finding it tough to communicate what you feel needs to change to your co-organizers and ground it in some solid arguments.</p><p>If any of this resonates — read on, this guide is for you! However, it’s nowhere near finished, so if you have an awesome contribution, please comment below or ping me on twitter. Let’s get started.</p><h3>The starting point</h3><p>About a year ago, I came across an opportunity to put my name in a hat for a community award for local tech speakers, organized by the very active local group <a href="http://www.pdxwit.org/">PDXWIT</a> (Portland Women In Tech). It was a long shot, I’ll give it a whirl, maybe I’ll learn something. But as I took a closer look at the form to self-nominate, I realized a major roadblock: There were gender specific questions that ruled me out.</p><p><strong>“Do you identify as a woman in tech? Yes/No?”</strong></p><p><strong>Well shoot.</strong> I don’t identify as a woman, and therefore, I wasn’t eligible. Now, I’m a non-binary person who frequently gets read as a “butch” dyke or “androgynous” woman, and sometimes I pass as a cis or trans man. But that’s not who I am. I’m a non-binary person, generally I use they or he pronouns. But all the oppression women encounter applies to me too — and then some.</p><p><strong>Major bummer.</strong> <strong>I felt confused and left out.</strong> I was experiencing something akin to cognitive dissonance — I was being confronted by mixed messaging. <strong>There was no strong signal here.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xd9PslNemQpco79bpCaWsQ.jpeg" /><figcaption>Actions reveal priorities. Photo by <a href="https://unsplash.com/photos/ukzHlkoz1IE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Austin Chan</a> on <a href="https://unsplash.com/search/photos/voice?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Did the org want me there or not?</strong> My experiences with this group had been very welcoming and inclusive, but the form actively excluded me.</p><p><strong>I could walk away</strong>, not communicating how this process made me feel, or <strong>take a risk</strong> by challenging the policy. I might get shut down or rejected. I might have to do a bunch of explaining around why this was an issue. I might end up feeling less welcome than I did before. <strong>There was emotional labor and risk involved either way.</strong></p><p>This was a small moment, but it illustrates how much was at stake here quite well. Imagine that you experience incidents like these day in, day out. Big ones. Small ones. Imagine how draining, how frustrating, how time consuming it might be to <strong>constantly</strong> push for answers and claim space.</p><p>After thinking things over, I chose to risk over safety and contacted the <a href="http://www.pdxwit.org/">PDXWIT</a> team. It could have gone badly, but I had an <strong><em>extremely</em></strong> warm and supportive email exchange with PDXWIT. The cognitive dissonance was resolved — my trust was restored. It was a <strong><em>huge</em></strong> relief to see talk backed up with action, and the form was changed <strong>right away</strong>. I got a clear signal: <em>Your concerns are important. </em>As a result, I collaborated with PDXWIT to train their volunteers and the materials I’m presenting here are a result of that process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*P-MhtRBrufgUkqzd" /><figcaption>Training PDXWIT volunteers on creating gender inclusive events</figcaption></figure><h3>Understanding what is at stake — underlying assumptions</h3><p>Before we talk gender neutral bathroom signs, zero in on what’s at stake using the example I outlined above.</p><p><strong>“Do you identify as a woman in tech? Yes/No?”</strong></p><p>Now, on first glance, this may seem like a logical question when screening for a speaker award nomination for a women in tech event.</p><p>But when we ask questions like the above, what is happening here is using a <strong>fixed identity qualifier to determine eligibility</strong> for something. Here’s what happens under the hood with the phrase “are you a woman”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*fM3zlIm2sVlq92Oq" /><figcaption>There’s just no way to win with you, Leo</figcaption></figure><p><strong><em>Using the phrase “are you a woman?” to verify eligibility produces erasure because:</em></strong></p><ul><li>It assumes <strong>all women</strong> support the same issues, have the same struggles, regardless of race, class, age, ability etc.</li><li>Excludes gender non-binary people, trans men, cis men. (Definition of women used here includes cis and trans women)</li><li>Does not send a strong inclusive signal that non-cis people will pick up on.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*35qtLClnkWOCNzQZ" /></figure><p>Intention and consistency matter. What the org was trying to ascertain is whether I support women in tech. I do, and even though I don’t consider myself a woman, <strong>I am often seen as such and struggle with the same oppression</strong>.</p><p><strong>Empowering women is good. Having more diversity in tech is good. Learning to value difference is good.</strong></p><p>But if you are still wondering WHY it is so important to use more inclusive terminology, if all this new-fangled-gender-speak feels silly and maybe a little confusing, and you don’t understand it, if you are a “call a spade a spade” sort of person, maybe this will help:</p><p>Some people are<strong> not </strong>women<strong>.</strong> We can agree on that, I think. And you want them to come to your events, work at your company, speak at your conference, lend their expertise, their time, their energy, I assume.</p><p>This also applies to people of colour, people with disabilities, and other underrepresented groups, even if this article focuses on gender diversity. Not everyone is white, straight, and able bodied. That’s simply a fact. We know by now that diverse teams are more successful(<a href="https://www.mckinsey.com/business-functions/organization/our-insights/why-diversity-matters">1</a>,<a href="https://www.msci.com/documents/10199/04b6f646-d638-4878-9c61-4eb91748a82b">2</a>,<a href="http://gap.hks.harvard.edu/impact-gender-diversity-performance-business-teams-evidence-field-experiment">3</a>,<a href="https://www.gsb.stanford.edu/insights/diversity-work-group-performance">4</a>). But throwing dollars at D &amp; I won’t fix anything long term if the process and signals sent are not congruent and on point.</p><p><strong><em>Language shapes reality. By naming things we define them.</em></strong></p><p>Terms we use can include/exclude, create awareness and trust or break it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*-G5tAfCaxsSBuD80" /><figcaption>Create strong signals for people. Then back them up with action.</figcaption></figure><p><strong>When people feel included, they participate. Participate! That’s a money word! </strong>💸💸</p><h3>Guess what:</h3><h3>When people participate, we all win. Winning. That’s what you wanted, right? Winning is also a money word! 💸💰💸💵💸</h3><p>This is where the “how” to part of this article begins. Get ready. Get ready to win. =D</p><h3>Defining eligibility inclusively</h3><p>Instead of relating to people using fixed, identity-based qualifiers, we can achieve the same with <strong>action (process) qualifiers.</strong> Here’s how:</p><p>Replace:<strong> “Do you identify as a woman in tech? Yes/No?”</strong></p><p><strong>With:</strong></p><ul><li>Do you support work of women and other underrepresented minorities (URMs) in tech fighting for gender equality?</li><li>Do you consider yourself part of a underrepresented group in tech?</li><li>Why is it important to you to support women and URMs in tech?</li><li>What struggles do you see women and other URMs in tech facing?</li></ul><p>See what happened here? We expanded the box. Now there is all kinds of room — for non-binary people, cis-men, trans men, but also people of color, people with disabilities, and many other intersecting factors that influence and affect how welcome or how excluded they might feel.</p><p>Instead of dictating the qualifications, we are asking about them — this is much, much more inclusive and roomy.</p><p>Now that we understand what is at stake when we don’t use intentionally inclusive signalling, let’s speed things up a bit, and move to actually implementing inclusivity in our process of planning, promoting, and executing an event.</p><h3>Making Events Gender Inclusive — Planning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/0*KwiV-CQd4w2fF41O" /><figcaption>Workplace toolkits can be useful resources to learn from.</figcaption></figure><p><strong>Planning Events:</strong></p><ul><li>Choose venue with gender neutral bathrooms, or <strong>make sure</strong> the venue will let you temporarily create them. Don’t just assume they will! Some won’t!</li><li>Make sure you have the correct information to book travel for speakers or issue honorariums. <strong>Not everyone</strong> has a government ID in the same name they use publicly</li><li>Include topics regarding trans and non-binary people matter of factly — <strong>we are part of life</strong></li><li>Vet speakers for biased language and content — check with community members regarding prior engagements</li><li>Have inclusive <strong>Code of Conduct</strong> (<a href="https://donutjs.club/conduct/">1</a>, <a href="https://www.recurse.com/code-of-conduct">2</a>) prepared that you feel prepared to implement</li><li><strong>Plan</strong> for pronouns stickers, buttons or tags for everyone as part of the registration process — <strong>not just</strong> for use by trans or non-binary folks</li><li>Don’t ask minority speakers to only speak about minority issues — they have other skills too</li><li>Ask community members what they need instead of assuming</li></ul><p><strong>Key takeaways:</strong></p><p>Be prepared, be proactive, be intentional. It won’t go unnoticed.</p><h3>Making Events Gender Inclusive — Promoting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/0*NDPGUEAr19xBFPrE" /><figcaption>Alternatively, you can write “People who wish to stand” and “People who wish to sit”</figcaption></figure><ul><li>Use diverse stock photos and images</li><li>Explicitly state that you will have gender neutral bathrooms — <strong>this is a strong signal for gender minorities that you see them — and cis people don’t even notice this stuff!!)</strong></li><li>Publicize your event to diverse audiences through diverse channels, don’t expect people to come to you</li><li>Be ready to answer questions about your policy around inclusion</li><li>Publish featured speaker’s pronoun choices on the schedule <strong>ahead of time</strong> so others can refer to them <strong>correctly without guessing</strong></li></ul><p><strong>Key takeaways:</strong></p><p>Don’t make promises you can’t keep — imagine being promised wheelchair access and then having to struggle with stairs.</p><p>Damaged trust can be extremely difficult to repair.</p><h3>Making Events Gender Inclusive — Event Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/0*Q7WwHQnWilRHe5Rc" /><figcaption>Everyone should disclose their pronouns, not just people who “need” to.</figcaption></figure><ul><li>Make bathrooms clearly accessible to <strong>all</strong></li><li>Everyone writes their pronouns, everyone should respect pronouns</li><li>Model key phrases people can use to ask pronouns. “How do you spell your name? “And what pronoun should I use with you?”</li><li><strong>Don’t<em> </em>misgender </strong>speakers, hosts or presenters — it can be very hard to retain professional composure after being misgendered. <strong>Practice </strong>if you are announcing and having a hard time getting it right</li><li>Clearly provide a code of conduct and encourage people to read it, and understand the repercussions of violating it</li><li>Consider implementing Social Rules that help <a href="https://www.recurse.com/manual">manage microaggressions</a>. (Scroll down to “Social Rules”)</li><li>Keep in mind that a person’s current physical presentation, gender, pronouns etc <strong>may not match their ID.</strong></li><li>Be ready &amp; informed to deal with critical pushback. Again, practice can help — talk to your co-organizers, and make sure they have answers to common questions</li><li>Label T-Shirts as “Straight Cut” and “Fitted Cut” instead of “Women’s” and “Men’s”. Some men are curvy. Some women are not.</li></ul><p><strong>Key takeaways:</strong></p><p><strong>Everyone</strong> should have a pronoun button and ask others their pronouns, not just the <strong>people who “need” to.</strong></p><p>Show support promptly should someone report disrespectful behaviour. <strong>Consider the trust being placed in your org getting this right. </strong>Again, you don’t want to have to repair a broken relationship with a person or group. Information spreads quickly through slack, twitter, etc. — your goal should be to try and get it right the first time.</p><h3>Conclusion</h3><p>You may feel that this is a hell of a lot of work for the few people who come to your event who are trans, or aren’t cis? Sure, it involves rethinking your approach, talking to your co-organizers, risking getting it wrong, and tackling sometimes thorny questions. There may be pushback. There are some resources listed out below that might make it easier.</p><p>But consider the following: People are intersectional beings. If a company has a strong inclusion policy around gender, they are more likely than not to be a better place to work for people of colour and other URMs, or at least provide proof that change and rethinking is possible within the org.</p><p>If you are having trouble finding the words and reasons to do this work, let’s recap:</p><p>Terms we use can include/exclude, create awareness and trust or break it.</p><p><strong>When people feel included, they participate. </strong>When people feel excluded, they don’t tell you that they feel excluded, exposing that exclusion is <strong>a personal and professional risk, is emotional labor no one is paying them to take. This means you are likely not hearing from people who feel excluded.</strong></p><p>When people participate, we all win. This is how we change the environments we move through to be safer and more welcoming for all of us!</p><h3>Participation means bigger and better events, more energy, more ideas, more perspectives, and can even mean more funding and more opportunity.</h3><p>I hope this article is helpful in framing the case for more gender inclusive events — not just in terms of the <strong>How, </strong>but also the<strong> Why.</strong></p><p>Thoughts? I look forward to hearing constructive feedback!</p><p>Extreme thanks go to <a href="https://twitter.com/BrennaKutch">Brenna Kutch</a> her amazing editing skills, and <a href="https://medium.com/u/6cc8b0e48648">Brook Shelley</a> and <a href="https://medium.com/u/d2e6b3c52ffd">Nick Luallin</a> for their valuable perspective on this guide. Thank you for your time and energy!</p><p><strong>Resources and further reading:</strong></p><ul><li><strong>Trans 101:</strong><em> </em><a href="http://bit.ly/TRANS_101">bit.ly/TRANS_101</a></li><li><strong>non-binary, AGENDER, ETC:</strong> bit.ly/non-binary</li><li><strong>Why we are discussing trans issues in “women’s” spaces:</strong><em> </em><a href="http://bit.ly/DISCUSS_SPACES">bit.ly/DISCUSS_SPACES</a></li><li><strong>An Incomplete Guide to Inclusive Language for Startups and Tech: </strong><a href="http://bit.ly/VOCABGUIDE">bit.ly/VOCABGUIDE</a></li><li><strong>Diversity Stock Photography:</strong> <a href="http://bit.ly/STOCKPHOTO">bit.ly/STOCKPHOTO</a></li><li><strong>HRC Toolkit:</strong> bit.ly/HRCSTUDY</li></ul><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more stories featured by the <a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec93ee477035" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools are a unit of caring, or: !!Con makes everything better, a 2018 recap]]></title>
            <link>https://medium.com/@perrysetgo/tools-are-a-unit-of-caring-or-con-makes-everything-better-a-2018-recap-dcf4edda602d?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf4edda602d</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[recaps]]></category>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[tech-conference]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Wed, 23 May 2018 23:01:52 GMT</pubDate>
            <atom:updated>2018-05-24T21:39:32.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOJo5P9Z4c3mmIyv1-92eg.jpeg" /><figcaption>The !!Con team</figcaption></figure><p>So I just came back from <a href="http://bangbangcon.com/">!!Con</a>. If you don’t know, !!Con (pronounced BangBangCon) is a once-a-year tech conference in New York City, which took place at <a href="https://medium.com/u/451ec3a2427c">AppNexus</a> on May 12th &amp; 13th. I hadn’t heard of this small-but-mighty conf before, but after hearing the giddy excitement of a <a href="https://twitter.com/allinison">friend</a> (whose opinion on fun I trust <strong><em>almost</em></strong> implicitly) on the subject, I decided to try and get a ticket and go. It had been a really long time since I’d been to New York (read more about that <a href="https://medium.com/@perrysetgo/not-come-back-the-same-a-read-on-love-and-escape-18a5a376193c">here</a> if you dare to get a little or a lot more personal), and my BFF on the east coast had been asking for a visit for a little while. And brother sister daughter mother, am I glad I went.</p><p>Not my first conference. Not my last conference. Not the biggest, not the smallest. But a conference that stood, head and shoulders above, class of its own, outshone them all, in two incredible exciting and meaningful ways: Caring. And tender hilarity.</p><p>None of those things are necessarily what I expected from a nerdy, DIY tech conference featuring talks on Pokémon, maps, undoing all the things things, satellites, and regex.<br> <br>But don’t let anyone fool you: underneath the joy, excitement and surprise of computing (a uniting triptych of ideas) there was a tender beating heart present in many, many talks. But more on that later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*jJbT2zXH91puLYxX1Eir6g.jpeg" /><figcaption><a href="https://medium.com/u/152f65dab15">Julia Evans</a> graphics were a re-occurring theme for the weekend and it was good</figcaption></figure><p>Sometimes granular, linear recaps don’t really hit the spot. These is one of those times, as the <a href="http://bangbangcon.com/program.html">!!Con speaker lineup</a> was 32 strong, and it would be impossible to do everyone justice. But here are some of my (totally biased) favourites.</p><p><strong>Saturday Keynote by </strong><a href="https://medium.com/u/c86588eea6d7"><strong>Mimi Onuoha</strong></a></p><p>Kicking things off with a bang, <a href="http://bangbangcon.com/speakers.html#mimi-onuoha">Mimi Onuoha’s keynote</a> was a gift to my anthropologist-activist-technologist triple-hybrid heart. I was profoundly affected by the unique approach she took to highlighting how mapping technologies affect communities, especially when they render settlements and people invisible. I also found myself turning her reflections on the act of data collection, algorithmic violence, and accidental/intentional invisibility over in my mind again and again after her talk. Emotionally, her art piece that involved projecting her heartbeat on a wall in real time the most affecting — the stunning vulnerability and implication of her body and the audience in the piece was riveting. I could have gone home after this one and felt I got my money’s worth in thought-provocation. Wow.</p><h3>Twitter</h3><p>On-Algorithmic-Violence - Attempts at fleshing out the concept of algorithmic violence.</p><p><a href="http://novalisdmt/">David Turner’s</a> <a href="http://bangbangcon.com/speakers.html#david-turner">Compressing the Library of Babel</a> is harder to define and summarize, but nonetheless left me stunned. I didn’t know much about compression techniques before this talk, and found myself taking frantic notes that read something like “To compress is to predict, to predict is to interpret reality”. Yeah.</p><p><a href="https://medium.com/u/ac59267d3815">Alex Clemmer</a> ’s <a href="http://bangbangcon.com/speakers.html#alex-clemmer">“It’s super effective! Solving Pokémon Blue with a single, huge regular expression”</a> took the medal home for funniest talk on Saturday. The entire room was close to crying with laughter when he described Pokémon Blue and Red “as DDOS attempts on children’s attention”. Thanks for that.</p><p><a href="https://medium.com/u/e1e3aa111bcb">Ahmed Abdalla</a> ’s “<a href="http://bangbangcon.com/speakers.html#ahmed-abdalla">Creating an Arabic Programming Language!</a>” was an amazing learning opportunity. As a native speaker of both English and German, who has worked in both languages, I’m always fascinated by how language differences affect programming and programming culture. I really hope that his project, Noor, helps lessen the barriers for people whose first language is Arabic.</p><h3>Twitter</h3><p>FizzBuzz in Noor, an Arabic programming language (so named for a dialect of Arabic) by @SimplyAhmaz1ng: github.com/SimplyAhmazing... #bangbangcon pic.twitter.com/E1LzV3kKHl</p><p>Also exciting, surprising, and joyful: <a href="https://medium.com/u/eada299b4919">Mark Wunsch</a>’s live streaming demo — so good, and I’m so grateful for him acknowledging his self-taught-programmer status. <a href="https://twitter.com/pzula">Persa Zula’s</a> talk on undefined characters was enlightening and so funny. Karla Burnett’s storytelling-with-traceroute brought back many memories of futzing with tracert. <a href="https://medium.com/u/a4643093bf9f">Aruna S</a> ’s presentation on the flood tracking map she created echoed many of the keynote’s sentiments.</p><p><a href="http://bangbangcon.com/speakers.html#logan-williams">Logan Williams</a> talk on photographic perspectives and SimCity 2000 was funny and impressive. Josh Bowman-Matthews brought us closer to understanding linking in C++, while <a href="http://bangbangcon.com/speakers.html#vaibhav-sagar">Vaibhav Sagar</a> very quickly introduced typed holes. <a href="https://twitter.com/ohaithear.">Ed Medvedev’s</a> talk about communicating with satellites was so cool and very intriguing, especially his DIY antenna, while <a href="http://bangbangcon.com/speakers.html#ayla-myers">Ayla Myers</a> piece on PICO-8 crunching brought back memories of my own 8-bit Mahjongg tiles circa 1995.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNOcZonu65hE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNOcZonu65hE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNOcZonu65hE%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/e84c8143e40b6ab3bf89eff6d2abed4e/href">https://medium.com/media/e84c8143e40b6ab3bf89eff6d2abed4e/href</a></iframe><p>Sadly, I missed the unconferencing sessions and some of the last talks, but did catch <a href="http://bangbangcon.com/speakers.html#mike-lazer-walker">Mike Lazer-Walker</a>’s presentation on GPS and why it can be crappy in cities (TL; DR: Buildings block signals that need to be triangulated to pinpoint — so cool).</p><p>Wow. What a day. Good thing I made a bunch of new best friends, none of which said no to beverages, shopping adventures, conference brainstorms, vegan polenta cake, Janelle Monáe, and discussing the overlap between Linguistics and Computer Science into the wee hours. Thank you <a href="https://twitter.com/AnjanaVakil">Anjana</a>, <a href="https://medium.com/u/d7cb583a6faa">Flaki</a>, and <a href="https://medium.com/u/a3869d3ae9e9">Nicole Orchard</a> for your lovely company.</p><h3>Twitter</h3><p>Post-#bangbangcon-day-one loungtime 🍸 w/ @baelathefox @anjanavakil &amp; co. 💖 (@ Bo&#39;s Kitchen &amp; Bar Room - @bos_nyc in New York, NY) swarmapp.com/c/aLNkx8rpuMR pic.twitter.com/VqCne7PJ8B</p><p><strong>Sunday, Day 2</strong></p><p>I knew a little bit more of what to expect (I guess I forgot to comment on the awesome breakfast spread, the bottomless coffee, the really great awareness about actually making restrooms gender neutral, the friendly, welcoming people, and the hilarious excellence of <a href="https://twitter.com/stenoknight">Mirabai Knight’s</a> steno services…), but that doesn’t mean I was ready for the “firehose of ideas” that was day 2 of !!Con.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5vvVaw3daQHtWnLN3swGQ.jpeg" /></figure><p>Lovely human and friend <a href="https://medium.com/u/bd90167402f0">Liz Fong-Jones</a> delivered the keynote (and, hello, she livetweeted <em>all weekend</em> and stopped only to give said keynote) about the difficult circumstances that gave rise to her start in tech, and how she was able to leverage her skill in troubleshooting (both tech and people problems) that she practiced in online gaming communities into an impressive career. Her talk was heartfelt and inspiring, and maybe won the award for most-quoted on the !!Con TF. Thank you, Liz, for gems such as this one: “Much better to build a resilient culture than rely on a single rockstar who does all the work”. Great stuff. I feel this so hard rn as a rockstar in recovery (rir)</p><h3>Twitter</h3><p>&quot;Oh great, it works! Isn&#39;t it amazing when technology works!?&quot; @lizthegrey kicks of the second day of @bangbangcon solving intricate social puzzles with skills learned playing a pirate! Arrr! ☠️⚔️🐦 pic.twitter.com/w2MKjVnKWN</p><p>Some of my favourite talks from Sunday:</p><p><strong>Relativistic Software Calendars: It’s About Time!</strong> (<a href="http://bangbangcon.com/speakers.html#john-feminella">John Feminella</a>) really made my scratch my head — yes, indeed, how *do* we compute time in space?</p><p><strong>Undo all the things! </strong>(<a href="http://bangbangcon.com/speakers.html#tom-ballinger">Tom Ballinger</a>) was as if someone had turned a ramones song into a talk (maybe Blitzkrieg Bop?). Barely able to keep up, I’m still not sure exactly what happened here, but I do know that it was fast paced, fascinating, and people really loved it.</p><p><strong>Andrew Louis’ </strong><a href="http://bangbangcon.com/speakers.html#andrew-louis"><strong>Talking to my past self</strong></a> was a strong favourite. I have never, ever, laughed harder at a conference presentation. <a href="https://medium.com/u/219c5a8556d8">Andrew Louis</a>’ idea to train chat bots with transcripts from his teenage years, as well as from his current self, and have them hash things out was sheer fucking tender comedic gold. Thank you.</p><p><strong>Whoa, pictures! A visual history of visual programming languages!</strong> (<a href="http://bangbangcon.com/speakers.html#emily-nakashima">Emily Nakashima</a>) Such an interesting topic. I loved the overview Emily was able to present, as well as the pro’s, con’s and use cases for the above.</p><p><strong>Also exciting, surprising and joyful:</strong> The Man Comes Around: and so does his sound! (<a href="http://bangbangcon.com/speakers.html#vince-allen">Vince Allen</a>) brought us closer to Johnny Cash, <a href="http://bangbangcon.com/speakers.html#stephen-tu">Stephen Tu</a> showed us how you might go about estimating Pi using a dartboard, <a href="http://bangbangcon.com/speakers.html#lucy-zhang">Lucy Zhang</a> introduced us to Ray-Tracing, <a href="http://bangbangcon.com/speakers.html#omar-rizwan">Omar Rizwan</a> had a GREAT time showing us screenshots with his talk on fake filesystems, <a href="http://bangbangcon.com/speakers.html#will-leinweber">Will Leinweber</a>’s Using Postgres to `\watch` Star Wars! Was incredibly impressive, <a href="http://bangbangcon.com/speakers.html#hung-truong">Hung Truong</a>’s attempts at cheating HQ Trivia were hilarious, while <a href="http://bangbangcon.com/speakers.html#evy-kassirer">Evy Kassirer</a> had awesome things to say about showing step-by-step math equations. <a href="http://bangbangcon.com/speakers.html#jan-mitsuko-cash">Jan Mitsuko Cash</a> showed off just how Pokémon are put together, while <a href="http://bangbangcon.com/speakers.html#jes-wolfe">Jes Wolfe</a> finished everything off by showing the beautiful pseudofractals they were able to generate with sound.</p><p>After the last talk, we got a chance to hear more about !!Con — it’s history, for those not in the know, and it’s future, which is a <a href="http://bangbangcon.com/west/">West Coast Spinoff</a>.</p><p><strong>Wow.</strong></p><p>I also had a chance to participate in an unconference session on Teaching Tech, which is the specific corner of tech I know the best. During the session, we had a freeform discussion, which could best be described as <em>caring. </em>We got to talk about authenticity, dismantling the pedestal, reaching an audience, and unconscious bias. Thank you Sam, Flaki, and Ed in particular for facilitating.</p><p><strong>Time to…take a breath.</strong></p><p>That night, I took a long walk around Manhattan. Drifting through any city I’m staying in is my quintessential travel activity. It felt uniquely like the perfect place to be. As I walked around, observing the patterns, the way the city moved and breathed and stood and rested all around me, I began to reflect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*c9j_NgcCA_ydcAyynApZvQ.jpeg" /><figcaption>exclamation mark shaped</figcaption></figure><p>I turned my mind to some of the key themes of the weekend: Maps and algorithms and solving cute problems yes, but also the earnest desire to make the connections visible, to highlight the void, to amplify low voices, moments, struggles, concerns unheard (even if those struggles were just solving Pokémon Blue with regex).</p><p>But it’s not just about solving problems, although that’s a big part of it. It’s about solving problems by creating tools. An underlying theme of !!Con was captured here in a tweet by Flaki:</p><h3>Twitter</h3><p>While I been really enjoying the various mapping-themed talks of the first @bangbangcon session my favorite part was probably the subtle underlying notion eventually emerging in every single talk: Humanity desperately trying to make sense of the world, by any tools necessary. 💜 pic.twitter.com/tLUbdBU7Sq</p><p>“Humanity desperately trying to make sense of the world, by any tools necessary.”</p><p>YES, BUT: Let’s unpack this a little.<br> <br><strong>What</strong> is a tool? It’s a unit of solution relative to a problem. Think about it.<br>But <strong>why</strong> is a tool? A tool is a unit of noticing. Huh?<br> <br>Noticing a problem or that needs to be resolved, and responding to that call with an idea, of knowing that something is important enough to warrant a fix or a change. The action of creating a tool happens from a place of caring about making things better. So, maybe we can say: A tool is a unit of caring. Maybe even more than that, and I’m paraphrasing someone famous here, “A tool is caring made visible”.</p><p>So if !!Con is all about making tools, and tools are all about noticing, and noticing is all about caring, then what does that mean?</p><p>It means !!Con itself is a tool. It’s a tool to make the tech space a more creative space, a more fun space, a more collaborative space. A more caring, and intentional space. That investment shows in the way people treated each other all.weekend.long, by the talks that were presented, and the way the conference was organized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IEgDWdE0K0QaIiCIf4c1vQ.jpeg" /></figure><p>One of the phrases that closed out the conf went more or less as follows: “We hope <a href="https://twitter.com/bangbangcon">@bangbangcon</a> is a reminder of why you became a developer in the first place”. Yeah, it’s a tool for that too. <br> <br> And a very, very good one at that.<br> <br> I’ll be back.</p><p>Huge thank you to all the sponsors for this event, especially <a href="https://medium.com/u/451ec3a2427c">AppNexus</a> for providing the space! Videos will be up on <a href="http://confreaks.tv/">Confreaks</a> by the end of May.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf4edda602d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Farewell, this time, Or: End Your Own Era (A Prologue)]]></title>
            <link>https://medium.com/@perrysetgo/farewell-this-time-or-end-your-own-era-a-prologue-c6bbb359f192?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6bbb359f192</guid>
            <category><![CDATA[goodbye]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[portland]]></category>
            <category><![CDATA[code-school]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Tue, 01 May 2018 05:39:01 GMT</pubDate>
            <atom:updated>2018-05-01T06:22:33.765Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s not fuck around: May 10th will officially be my last day as Epicodus’s most longstanding teacher On The Floor, as the one (and probably only) Faculty Lead.</p><h3>perry eising on Twitter</h3><p>Missing these fools, I mean, extremely hireable young graduates! A great last Android class. Proud of all of you!</p><p>2.4 years, ~300 ish students, over 3000 code reviews, and my time has come to an end. I am ending my own era. I am happy and I am sad. I am in love with this important decision for my own sanity and future. I am in deep grieving over losing this role that has meant so much to me, over the team I feel I’m throwing over, over the way I worry I’m fading from your lives as students, coworkers, friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*entwPNcy2Lo_ooY4xu73Qg.jpeg" /></figure><p>But I also can’t stop waking up in the middle of the night with excitement over what I’m going to do next (not sure what that is yet. You can help! I need a new thing! As in: A new job!)</p><h3>Epicodus on Twitter</h3><p>Check out this crocheted mini instructor one of our students made for @perrysetgo Who else loves to craft? Show us your art!</p><p>Teaching at Epicodus and managing the teacher team has been the most formative, heart wrenching, gut-lining destroying, epic adventure of a lifetime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0niZml9Zd74GIBfgx8BTCA.jpeg" /></figure><p>It has allowed me to pour out everything that makes me me, to show up stronger than I ever thought possible. I have literally grown 3+new hearts to hold it all. It’s uncomfortable to care so much.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGIeXEtA-ZKOyniP9rhRHA.jpeg" /></figure><p>I am deeply grateful for what I have been allowed to do, learn, and experience with you, yes, you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrwLzbF0kSKmLZ5Ly5Wm4w.jpeg" /></figure><p>I will be posting a longer (I struggle with verbosity..as you know from standup) wrap up of my thoughts on this event here on my Medium very soon.</p><p>You are the project. Please don’t forget. And learn your acronyms. Backwards and forwards.</p><p>I’m going to miss you all so fucking much.</p><p>Perry</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6bbb359f192" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What exactly IS an API?]]></title>
            <link>https://medium.com/@perrysetgo/what-exactly-is-an-api-69f36968a41f?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/69f36968a41f</guid>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Thu, 07 Dec 2017 17:24:32 GMT</pubDate>
            <atom:updated>2017-12-07T17:24:32.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVGssbsoijih-xMlYFaGog.png" /></figure><p>Have you ever heard the word “API” batted about, and wondered exactly what an this is? Do you have a vague idea, but want to know more about what you might do with an API, and how you might build one?</p><p>Don’t fret. I can help!</p><p>Let’s get down to it and pick apart what an API is, and how building an API is similar (or different!) than building other types of web apps and websites. Here’s a short primer on what an API is, what makes it different, and what you would need to build one yourself.</p><h3><strong>Application Programming Interface (API)</strong></h3><p>In basic terms, APIs just allow applications to communicate with one another.</p><p>When people speak of “an API”, they sometimes generalize and actually mean “a publicly available web-based API that returns data, likely in JSON or XML”. The API is not the database or even the server, it is the code that governs the <em>access point(s)</em> for the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OcmVkcsM5BWRHrg8GC17iw.png" /><figcaption>An API is not a database. It is an access point to an app that can access a database.</figcaption></figure><p>In this post, we will focus on these specific kinds of APIs — web based APIs that return data in response to a request made by a client.</p><p>They allow us to go get data from outside sources.</p><ol><li>We can send an API a request detailing the information we want.</li><li>APIs allow our sites to alter data on other applications, too. For instance, you’ve probably seen “Share on Facebook” or “Share on Twitter” buttons on miscellaneous websites. When/if you click one of these buttons, the site you’re visiting can communicate with your Facebook or Twitter account, and alter its data by adding new status or tweet.</li></ol><h3><strong>But why would we need an API?</strong></h3><p>Imagine the following scenario: You (as in, your application, or your client, this could be a web browser) wants to access another app’s data or functionality. For example, perhaps you want to access all Twitter tweets that mention the <em>#epicodus</em> hashtag.</p><p>You could email Twitter and ask for a spreadsheet of all these tweets. But then you’d have to find a way to import that spreadsheet into your application; and, even if you stored them in a database, as we have been, the data would become outdated <em>very</em> quickly. It would be impossible to keep it up to date.</p><p>It would be better and simpler for Twitter to provide you a way to query their application to get that data, so that you can view or use it in your own application. It would stay up to date automatically that way.</p><p>An API brokers access to a different application to provide functionality or access to data, so data can be included in different applications.</p><h3>Who Creates Public, Web-Based APIs?</h3><p>Large tech companies, especially social media companies frequently make their aggregate data available to the public, but APIs are also maintained by government organizations, conferences, publishing houses, software startups, fan groups, eSports leagues and even individuals, in order to share anything from social media content to trivia questions, rankings, maps, song lyrics, recipes, parts lists and more.</p><p>In short, any person or organization that collects data might have an interest in making that data available for use by a different app. Maybe you have an API you’d like to build and make available?</p><h3>How an API Differs from a “Regular” Database-Backed Project</h3><p>An API is different from a database backed (or static) web application or site in that it does not generally need to contain a frontend — no HTML, CSS is necessary to be shown to the user via static pages or dynamically generated templates that fuse data with reusable layouts.</p><p>Requests to retrieve or write data are generally done without a frontend, by sending an HTTP request to a server.</p><p>If you are familiar with building server side apps with Java, Ruby, PHP, JS via node or other language, you will likely recognize the need for certain <em>routes:</em> URLs that trigger route handlers to issue certain actions when they receive a request with some data. APIs have routes the same way a different site might, they just generally do not serve templates on those routes.</p><h3>So What is JSON and why do we use it?</h3><p>JSON stands for <strong>J</strong>ava<strong>S</strong>cript <strong>O</strong>bject <strong>N</strong>otation and is basically a way of representing data that looks like JavaScript objects.</p><p>Let’s look at a very typical JavaScript Object for a Restaurant, which might look a bit like this:</p><pre>“restaurant”: {<br> “name”: “Fish Witch”,<br> “address”: “214 NE Broadway”,<br> “zipcode”: “97232”,<br> “phone”: “503–000–0000”,<br> “website”: “<a href="http://fishwitch.com/">http://fishwitch.com</a>&quot;,<br> “email”: “<a href="/service/mailto:hellofishy@fishwitch.com">hellofishy@fishwitch.com</a>”<br>}</pre><p>Neat. This is fairly easy to read — our data is stored as key/value pairs. This means that we can see the <strong>key</strong> on the left, and the <strong>value</strong> on the right. The key stays the same for each Restaurant object, but the value would be different. A different Restaurant would have a different address, but its properties would be the same — it would always have a name, address, zip, phone and email.</p><p>JSON is <em>everywhere</em> in modern web applications. It’s readable, it’s lightweight, and it works super well with applications written in JavaScript, as it <em>is</em> JavaScript. But is also comparatively easy to get applications written in other languages to read it and generate it as well — including Java. This means that an API that returns JSON can be accessed by an application written in Java, Ruby, Python, JS, PHP and many more. This makes an API <em>scalable</em> and platform independent. Aha! Scalable! Platform Independent! Good words, powerful words, $$ words.</p><h3>I want to build an API!</h3><p>Awesome! Building an API is totally within reach of any developer who knows a little bit about server side web application programming and routing, such as with Java Spark, JavaScript Express, ASP.net for C#, Ruby on Rails and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlEB6wVHQYeb941qX4fGhg.png" /><figcaption>Example of a simple API built in Java Spark using the GSON library</figcaption></figure><p>In order to build a public API, you’ll need the following:</p><ul><li>A backend with routing of some sort as mentioned above</li><li>A database where your application can store its data. This could be a database server you are running, such as MySQL or Postgres, or it could be a BaaS (backend as a service) DB such as Firebase.</li><li>A server, likely a VPS (Virtual Private Server) that is accessible to the internet, where your application can run. (You might look into DigitalOcean, Amazon Web Services or Microsoft Azure for this)</li></ul><h3>I want to tie an API into my App!</h3><p>So cool. APIs can really extend your App’s functionality in major ways. Adding a map, weather data or other information can be incredibly useful.</p><ul><li>Find a public API that offers the kind of information you want to access. Make sure it is well documented and maintained. Some sites that offer many APIS are <a href="https://www.programmableweb.com/">ProgrammableWeb</a>, <a href="https://any-api.com/">AnyApi</a>, and <a href="https://public.apis.zone/">public.apis.zone</a></li><li>Read through the documentation to make sure the API is workable for you. Many APIs require you to register for an API key to access their data, or they have authentication flows your app needs to go through before you can access information.</li><li>Understand the shape of the data available. Go ahead and check out the Postman tool if you haven’t already, it’s an awesome piece of software that makes many aspects of working with APIs much easier. It helps you send test requests to APIs so you can experiment with the data you receive.</li><li>Call the API from your app and process the data that you receive, displaying it in your app! This is the most exciting part. Once you are successfully able to query the API with a tool like <a href="https://www.getpostman.com/">Postman</a>, you can write the code that integrates the data the API returns into your own work and display it to your users.</li></ul><p>Good luck! Tweet me and share with me what you’ve been able to create!<br> — <a href="https://medium.com/u/d77fd4733ec8">Perry Eising</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69f36968a41f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Death of a Whiteboard: How to crush any technical interview]]></title>
            <link>https://medium.com/@perrysetgo/death-of-a-whiteboard-how-to-crush-any-technical-interview-2e83a8b2149?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e83a8b2149</guid>
            <category><![CDATA[whiteboarding]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Sat, 02 Dec 2017 00:10:23 GMT</pubDate>
            <atom:updated>2017-12-06T21:25:33.448Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*qK2kp2Me14SBZItJwiHmSg.png" /><figcaption>it is true though.</figcaption></figure><p>Today was not <em>quite</em> a typical day at the code school where I teach. Instead of helping students work through lessons, today, teams of four students pitched the MVPs of apps they had been working on to our big room of students, faculty and staff. After a long week of prep, I was excited to be helping my class put the finishing touches on their AngularJS and Android apps. The room was buzzing with energy, and many groups presented work with built out capabilities and beautiful user interfaces that look as market-ready as their ideas.</p><p>I have been teaching at a code school for two years now, and my students are frequently quite diverse, in both age, gender, and background: They are veterans, they are undocumented, they are first generation immigrants whose first language is not English. They are transgender. They are gender non-binary. Over 50% of them are women.</p><p>They love solving problems.<br>They love building things.<br>They’ve completed hundreds of hours of practical, hands on training, and they are hungry for their first real tech job.</p><p>BUT:</p><p>They are super intimidated by whiteboarding — solving problems on a whiteboard with no computer, and technical interviews, where candidates get grilled on technical topics — because they know that despite their awesome, proven skills, they are especially disadvantaged by being nontraditional backgrounds and being minority students. And they aren’t alone: Many developers, whether they are from underrepresented groups or not, <a href="https://www.google.com/search?q=developers+scared+of+whiteboarding">are intimidated by</a> these kinds of interviews.</p><p><strong>But what is important to know is the following:</strong></p><p>Whiteboarding is not about how well you can <em>code</em>, it’s about how well you can <em>think </em>and <em>explain</em>. That’s a fantastic opportunity, if you use it right.</p><p>And so today, I want to share with you some of the tips and techniques we practice with our students to allow them to show up well in whiteboarding interviews. These are not language, platform, or technology specific.</p><p>Just the same way as there are reasonable approaches to succeeding on standardized testing, there are strategies you can use to improve your ability to make a good impression in any technical or whiteboarding interview you come across.</p><p>Let’s jump right in.</p><h3><strong>Know your acronyms</strong></h3><p>One of the easiest ways to flunk any technical interview is to not know your acronyms backward and forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/0*zsTW3M--MIGVolsd.jpg" /></figure><p><strong>Work with the material: </strong>If you are asked an acronym question, or a question featuring an acronym, be sure to spell out that you know what it stands for.</p><p>Why?</p><p>If you are only used to talking about REST or JSON, you might balk at being asked to speak on the finer points of “State Transfer” or “JavaScript Object Notation”.</p><p><strong>Work with the setting: </strong>When you are nervous, your brain doesn’t work very well. Pointing out that API stands for Application Programming Interface might very well jog your memory.</p><p>Make a point of learning and knowing commonly used acronyms in your field of study.</p><h3><strong>Get your setup right for phone screenings</strong></h3><p>If you are like me, and talking on the phone is your version of one of those paralysis nightmares, you’ll feel better if you are getting your setup right. <strong>Prepare for it like the interview that it is.</strong> Make sure you are in a quiet, private environment with a good phone connection. Have a hands-free headphone situation with you so you can speak freely. Have a computer station nearby, as well as a pen and paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/0*R0vdf5_lZ9fX6cyT.jpg" /></figure><p><strong>Work with the setting:</strong> Take advantage of the fact that you are not visible during the interview. Pace, do savasana, or sit on the floor if it calms you down. Have paper notes, or sit at a computer. Have your teddy bear, dog, or grandpa in the room with you. Whatever helps, helps.</p><p><strong>Work with the material:</strong> Write down the person’s name who you are speaking to so you don’t forget it by the end of the call. Show interest. Ask questions. Write notes.</p><h3><strong>Evaluate and Communicate: Ask yes/no questions to buy time and clarify contexts</strong></h3><p>If you are asked to explain a technical concept or perform a whiteboarding exercise, make sure you ask any clarifying questions <strong><em>before you begin</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/0*MfY-Sz8wGGkkW7MD.jpg" /></figure><p>Let’s look at an example:</p><p>Write a function that accepts the following input:</p><pre>let inputNamesArray = [“Dench, Judy”, “Mirren, Helen”, “Andrews, Julie”, “Jolie, Angelina”]</pre><p>and returns the following output:</p><pre>let outputNamesArray = [“Dame Judy Dench”, “Dame Helen Mirren”, “Dame Julie Andrews”, “Dame Angelina Jolie”];</pre><p>You might ask the following of your interviewers before you begin:</p><ul><li>Will the input array will always have a length of 4?</li><li>Currently, the list isn’t sorted. Is this intentional?</li><li>Can I write the solution in pseudocode?</li><li>Can I assume that there will never be duplicate names in the array?</li></ul><p>And so on.</p><p><strong>Work with the material:</strong> Clarifying things before you begin shows you understand the complexity of the problem. Also, can likely rule out unexpected nuances that might trip you up later.</p><p><strong>Work with the setting:</strong> Asking clarifying questions gives your brain an opportunity to start warming up, before you begin responding or writing down code. It also kills a little bit of time, which is a good thing.</p><h3><strong>Never say “I don’t know”. Also Never: Make Stuff Up</strong></h3><p>When you panic, hit a wall after being asked a tough question, and blurt out “I don’t know” , you’d be forgiven to think you are just given an honest response. In reality, you might be showing your too much, and you are not giving your interviewer much to work with to turn things back around. Not knowing the answer is not necessarily a dealbreaker, not handling stress or pressure appropriately might well be. So stay cool.</p><p><strong>Whatever you do:</strong></p><p>Resist. The Urge. To. Allow. Streams. Of. Nonsensical. Rubbish. To. Exit. Your. Face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SaYKB4LoIYYExlHrdTV48w.png" /></figure><p>A crappy answer will be memorable in a bad way. Find a different way that shows you in a better light.</p><p>This is how you get out of this pickle when you point blank don’t know: Take a deep breath. Calm your mind, and <strong><em>ask a few questions.</em></strong></p><p><strong>Work with the material: </strong>If you thoughtfully ask your interviewer to <em>clarify</em>, <em>specify</em>, <em>let you know concretely</em>, or any other phrase you should practice <strong>beforehand</strong>, you may well get some useful information.</p><p>It also, again, gives your brain some time to catch up. Congrats, you just showed grace under pressure.</p><p><strong>Work with the setting:</strong> If your interviewer seems friendly and casual, you might be able to carefully admit to not knowing the answer to a question. How you handle this situation is more important than not knowing.</p><h3><strong>Verbalize and prioritize, plan, execute</strong></h3><p>When you are asked to whiteboard a solution to a problem, you should verbalize what you are going to do before you do it, and write down a list of actions you are going to perform.</p><p>Yes, with the pen you are holding.</p><p>Let’s return to our earlier example: Write a function that accepts the following input:</p><pre>let inputNamesArray = [“Dench, Judy”, “Mirren, Helen”, “Andrews, Julie”, “Jolie, Angelina”]</pre><p>and returns the following output:</p><pre>let outputNamesArray = [“Dame Judy Dench”, “Dame Helen Mirren”, “Dame Julie Andrews”, “Dame Angelina Jolie”];</pre><p>Given that we have an array, it seems like we will</p><ul><li>probs need a loop</li><li>must declare and init outPutNamesArray outside of loop</li><li>split our array element in some way</li><li>remove comma</li><li>fix order</li><li>prefix with “Dame”</li><li>push to outPutNamesArray</li><li>return at the bottom.</li></ul><p>Cool. Now you have a plan, as opposed to running around like this guy.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDMm6bD9VJA8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDMm6bD9VJA8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDMm6bD9VJA8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/46b971ac3310ea0a3964b1ad05bb3698/href">https://medium.com/media/46b971ac3310ea0a3964b1ad05bb3698/href</a></iframe><p><strong>Work with the setting:</strong> Talking through your plan allows you to take the temperature of the room <em>before</em> you are wrangling lines of code. If your interviewer spots an error, they may give you a tip you can use to clarify your approach.</p><p><strong>Work with the material: </strong>You have a whiteboard and a pen — use them! Write the list down as you verbalize it — then, check things off as you code. Keep explaining out loud. Don’t make the interviewer guess your thoughts.</p><p>Whiteboarding interviews are not about writing perfect code — they are about communicating your thought process as you solve a problem. So do just that!</p><h3>Wrap Up</h3><p>Give these tips and tricks a whirl. While you are still going to be nervous, having a structure and ideas in place can help you feel like they have options and maneuvering room as opposed to being painfully exposed in front of a giant empty whiteboard with no plan.</p><p><strong>Remember:</strong> Nobody expects perfect syntax, but they do expect you to show that you can communicate well. Don’t sweat the small stuff, focus on the big picture. Prepare as best you can, hydrate, and practice these tips before you dive in.</p><p>Good luck — and feel free to share how things went! <a href="https://medium.com/u/d77fd4733ec8">Perry Eising</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e83a8b2149" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Deep Dive Part 2: Setting a Custom Font on an Android GridView]]></title>
            <link>https://medium.com/@perrysetgo/android-deep-dive-part-2-setting-a-custom-font-on-an-android-gridview-c43d3411d7d4?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c43d3411d7d4</guid>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 00:07:57 GMT</pubDate>
            <atom:updated>2017-06-01T00:07:57.920Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello! Welcome back, fearless venturer into mobile lands unknown. Welcome to the second installment of advanced topics in Android, where we give an in-depth how to bring a little more sophistication to your Android apps. In my first installment, we covered how to modify a stock ArrayAdapter to be little bit more powerful and interesting. If you didn’t get a chance to give that a read through, that might be a good first primer. Otherwise — Onward!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/0*tV8DCSxdSdZ1zCDY." /><figcaption>Our final result.</figcaption></figure><p>In this installment, I’ll discuss a way to apply a custom typeface to a TextView that is part of a custom layout for a GridView, as this is not a topic I have seen discussed very widely on other sites or StackOverflow.</p><p>Before we begin coding, let’s all get on the same page with regards to what a GridView is, and what we might use it for. If you are completely new to Android programming — you may want to work through some of the beginning lessons that make up the Android track on <a href="https://www.learnhowtoprogram.com/">learnhowtoprogram.com</a> to get the most out of this Deep Dive! Ideally, you should have at least glanced at an Adapter in the form of an ArrayAdapter before we begin. Cool!</p><h3>Review</h3><p>If you recall from using an ArrayAdapter in the past, an Adapter allows us to bind a single instance of an Object to a layout that is held in a collection. If we have an Array of Strings, otherwise known as a String[], an ArrayAdapter pulls out a single String, and displays it in a layout. This process is then repeated until each String in the Array is displayed. Here is an example of how an ArrayAdapter might be implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/0*n5AROa8X6H82vJq6." /><figcaption>A simple ArrayAdapter displays this list.</figcaption></figure><p>Even though we can customize our ArrayAdapter, and change the way data is displayed, for example through <strong>String.format()</strong>, we would still use a standard resource that is part of the Android package, namely simple_list_item_1 to display our data, which works fine for String types, but doesn’t cut the mustard for more complex data types.</p><p>If we have an Orange[], then we need to have something that can visually represent an Orange and all the properties we define an Orange as having. In order to represent more complex data, we’ll need to create a custom adapter and a custom layout file — things can get complicated quickly. This topic is explored in full in our lessons on <a href="https://www.learnhowtoprogram.com/android/web-service-backends-and-custom-fragments/custom-adapters-with-recyclerview">RecyclerViews</a>, but for now, let’s do something a little simpler. Let’s create a GridView, fill it with some data, and style that data with a custom typeface to get our feet wet. This exercise is simple, but will teach you work with custom layouts, custom adapters, and passing information to a custom adapter.</p><h3>Introduction to GridView</h3><p>A <a href="https://developer.android.com/guide/topics/ui/layout/gridview.html">GridView</a> is just what it sounds like — it is a View that represents data in a two-dimensional scrolling grid. The items in the grid come from the ListAdapter associated with this View. Because a GridView gets its data from a ListAdapter, the only data loaded in memory will be the one displayed on screen. GridViews, much like ListViews reuse and recycle their views for better performance. Performance is much more of an issue on mobile than it is for a web app for obvious reasons — your phone or tablet doesn’t have much memory or processing power as your desktop machine, so we need to take extra steps to ensure that apps run smoothly and reliably.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*WS-_Jqj3LBfz1S9d." /><figcaption>A gridview.</figcaption></figure><p>GridLayouts are like LinearLayouts or RelativeLayouts — they organize data on the screen in a grid format. But what they do not do is allow for scrolling, and they do not perform memory management tasks for us.</p><p><strong><em>Note:</em></strong> Please don’t try and show images in a GridView or GridLayout until you have a better handle on memory management for Images (see our topics on <a href="https://www.learnhowtoprogram.com/android/web-service-backends-and-fragments/images-with-picasso">Picasso</a>), otherwise you will almost certainly have an app that crashes consistently with an <strong>Out Of Memory</strong> error, or performs very sluggishly.</p><p>In this example, we’re going to simply display an alphabet on the screen in a grid, as we might do if we were making an app for kids to learn the alphabet.</p><p>We’ll style different views with different fonts to differentiate our views.</p><p>Let’s get started!</p><h3>Setup</h3><p>First, let’s make a new project in Android Studio using all the standard settings (if you are unsure, <a href="https://www.learnhowtoprogram.com/android/introduction-to-android/creating-a-new-project">please review this lesson</a>) , and choosing “Empty Activity” as our first activity. Name your app and package whatever you like, but let’s keep the main activity called MainActivity to keep things consistent.</p><p>When you’re done, jump over to MainActivity.java file. Let’s write out our alphabet first. Let’s use a String[] to hold our letters.</p><p><em>MainActivity.java</em></p><pre>public class MainActivity extends AppCompatActivity {<br> GridView gridView;<br> String[] letters = new String[] {<br> “A”, “B”, “C”, “D”, “E”, “F”, “G”, “H”, “I”, “J”, “K”, “L”, “M”, “N”, “O”, “P”, “Q”, “R”, “S”, “T”, “U”, “V”, “W”, “X”, “Y”, “Z”};</pre><pre> @Override<br> protected void onCreate(Bundle savedInstanceState) {<br> super.onCreate(savedInstanceState);<br> setContentView(R.layout.activity_main);</pre><pre> }<br>}</pre><p>Cool. That was easy!</p><h3>Making our Custom Layout</h3><p>Time to make a simple layout that can handle our alphabet display. Our layout will be comprised of two files:</p><ul><li>The container, a RelativeLayout that holds our GridView (this will live in the XML for our MainActivity)</li><li>The individual grid “item” — the View or collection of Views that get repeated as many times as necessary inside our GridView. (this will live in a separate file.)</li></ul><p>Jump over to activity_main.xml. In here, you should see nothing but a simple TextView, stating “Hello World!” Let’s make the following adjustments:</p><p><em>activity_main.xml</em></p><pre>&lt;?xml version=”1.0&quot; encoding=”utf-8&quot;?&gt;<br>&lt;RelativeLayout<br> xmlns:android=”http://schemas.android.com/apk/res/android&quot;<br> xmlns:tools=”http://schemas.android.com/tools&quot;<br> android:id=”@+id/activity_main”<br> android:layout_width=”match_parent”<br> android:layout_height=”match_parent”<br> android:paddingBottom=”@dimen/activity_vertical_margin”<br> android:paddingLeft=”@dimen/activity_horizontal_margin”<br> android:paddingRight=”@dimen/activity_horizontal_margin”<br> android:paddingTop=”@dimen/activity_vertical_margin”<br> tools:context=”com.example.epicodus_staff.myapplication.MainActivity”&gt;</pre><pre> &lt;TextView<br> android:text=”Learn the Alphabet”<br> android:layout_width=”wrap_content”<br> android:layout_height=”wrap_content”<br> android:id=”@+id/headerTextView”<br> android:layout_alignParentTop=”true”<br> android:layout_centerHorizontal=”true”<br> android:textSize=”30sp” /&gt;</pre><pre> &lt;GridView<br> android:layout_width=”match_parent”<br> android:layout_height=”wrap_content”<br> android:columnWidth=”50sp”<br> android:numColumns=”auto_fit”<br> android:stretchMode=”spacingWidthUniform”<br> android:id=”@+id/baseGridView”<br> android:padding=”0dp”<br> android:gravity=”left”<br> android:scrollingCache=”false”<br> android:layout_alignParentTop=”true”<br> android:layout_alignParentLeft=”true”<br> android:layout_alignParentStart=”true”<br> android:layout_marginTop=”40sp” /&gt;<br>&lt;/RelativeLayout&gt;</pre><p>If you switch to design view, you should see some placeholder text (don’t worry about that for now!) displayed in a grid. That’ll be all we need to do with our GridView at the moment.</p><h3>Styling our Grid Item</h3><p>Now we need to make the layout that will handle our individual alphabet items. We’ll connect the two in a second step shortly, telling the GridView to load the XML for the GridItem for each alphabet letter.</p><p>Let’s right click on the res folder and select <strong>New &gt; Layout Resource File</strong>. Leaving the layout type as LinearLayout is fine.</p><p>This is the XML you want to end up with:</p><p><strong><em>Note:</em></strong> While you can of course tweak the layout, you’ll definitely want to AVOID having your letters require scrolling. If they do, the variable position (more on that soon) will not correctly retrieve values from your arrays.</p><p><em>alphabet_grid_item.xml</em></p><pre>&lt;?xml version=”1.0&quot; encoding=”utf-8&quot;?&gt;<br>&lt;LinearLayout xmlns:android=”http://schemas.android.com/apk/res/android&quot;<br> android:orientation=”vertical” android:layout_width=”match_parent”<br> android:layout_height=”match_parent”&gt;</pre><pre> &lt;TextView<br> android:layout_width=”60sp”<br> android:textSize=”15sp”<br> android:layout_height=”wrap_content”<br> android:id=”@+id/grid_item_label”<br> android:layout_weight=”0.8&quot;<br> android:gravity=”center_horizontal”<br> android:text=”Letter” /&gt;</pre><pre> &lt;TextView<br> android:layout_width=”60sp”<br> android:textSize=”30sp”<br> android:layout_height=”60sp”<br> android:id=”@+id/grid_item_letter”<br> android:layout_weight=”1&quot;<br> android:gravity=”center_horizontal”<br> android:text=”A” /&gt;</pre><pre>&lt;/LinearLayout&gt;</pre><p>We’ll populate this with dynamic data soon. Just a few more steps, then we can test our app!</p><h3>Making our custom adapter</h3><p>Now let’s get a start on making our custom adapter. Create a new class in your main package, name it AlphabetAdapter. Make AlphabetAdapter extend BaseAdapter. We’ve done this before, so if you’re unsure, go back and review how to do this from the <strong>Customizing ArrayAdapters</strong> <a href="https://medium.com/@perrysetgo/android-deep-dive-part-1-doing-more-with-arrayadapters-8d76549aab3b">lesson</a>.</p><p>Similarly to our customized ArrayAdapter, AlphabetAdapter needs to have some member variables. We’ll definitely need a Context here, as well as our String[] that we are passing in from our MainActivity.</p><p>We’ll also need a constructor.</p><p>This’ll work:</p><p><em>AlphabetAdapter.java</em></p><pre>public class AlphabetAdapter extends BaseAdapter {<br> private Context mContext;<br> private String[] mLetters;</pre><pre> public AlphabetAdapter (Context context, String[] letters){<br> this.mContext = context;<br> this.mLetters = letters;<br> }<br>}</pre><p>But then we see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/0*bgtxOiRHex8Mw4vq." /></figure><p>Now we still have an angry, red squiggly line — if we hover over it, we might see that we need to implement a method called getCount(). This should be familiar from customizing our ArrayAdapter. <strong>Remember</strong>: Any time we extend a class, we agree that we will implement that class’ required methods — Android Studio will stay angry at us until we deliver on our responsibilities.</p><p>Let’s let the IDE do some busywork for us. Right click inside the class, select generate, then choose Override Methods… and select all 4 methods from the <strong>android.widget.Adapter package</strong>: <strong>getCount()</strong>, <strong>getItem()</strong>, <strong>getItemId()</strong>, and <strong>getView()</strong>.</p><p>Some boilerplate code appears, and red squiggly lines (should) disappear. Boilerplate code is a term you’ll hear frequently, so be sure to know what it refers to. Boilerplate is no frills, bare minimum code that is either a.) supplied to you, the developer, via a website, template file or some other form of documentation, or b.) auto-generated by an application such as a Command Line Interface (<strong>CLI</strong>) or <strong>IDE </strong>(Integrated Development Environment). It’s represents a starting point for us, but almost always needs to be edited extensively so that it provides relevant functionality to our app.</p><p>As you may now expect, so far all the boilerplate code returns null. Not super interesting or useful.</p><p>Let’s make some changes.</p><p>We’ll leave getItemId() and getItem() alone for now — we need to implement them, but don’t need to customize them at the moment. First, let’s change getCount(). We’ll want to return the .length of our mLetters array, so make getCount(), return that instead of null. getCount(), is necessary so that our app knows how many times the GridView should repeat the Grid Item.</p><p>getView() is where we’ll want to connect our layout with our grid items. Let’s do that now.</p><p>Here’s where we should arrive.</p><p><em>AlphabetAdapter.java</em></p><pre>public class AlphabetAdapter extends BaseAdapter {<br> private Context mContext;<br> private String[] mLetters;</pre><pre> public AlphabetAdapter (Context context, String[] letters){<br> this.mContext = context;<br> this.mLetters = letters;<br> }<br>}</pre><pre>@Override<br>public int getCount() {<br> return mLetters.length;<br>}</pre><pre>@Override<br>public Object getItem(int position) {<br> return null;<br>}</pre><pre>@Override<br>public long getItemId(int position) {<br> return 0;<br>}</pre><pre>@Override<br>public View getView(int position, View convertView, ViewGroup parent) {<br> LayoutInflater inflater = (LayoutInflater) mContext<br> .getSystemService(Context.LAYOUT_INFLATER_SERVICE);</pre><pre> View gridView;</pre><pre> if (convertView == null) {<br> // get layout from xml file<br> gridView = inflater.inflate(R.layout.alphabet_grid_item, null);<br></pre><pre> // pull views <br> TextView letterView = (TextView) gridView<br> .findViewById(R.id.grid_item_letter);</pre><pre> // set values into views<br> letterView.setText(“A”); // using dummy data for now<br> } else {<br> gridView = (View) convertView;<br> }<br> return gridView;<br> }<br>}</pre><p>Take the time to go through this and try and understand what we are doing here, step by step.</p><p>Our getView() method contains some code and arguments we haven’t seen before:</p><ul><li>ConvertView: If a View is a ConvertView, it is actually a View that can be converted to a new View, which means new content can get written into the fields contained in said View. Wait. What? Why would this be necessary? Well — let’s say you have a list of 150 things to display, but only 10 fit on the screen at any given time. We’re going to start our list at the very top, with the 0th (zero’th) item. As we scroll down, the view that was in the 0th place is now off the screen, and can now be removed from the app’s memory storage, until we start to scroll back up again. When we start our list, the convertView is null, and therefore we need to start building our list from our layout. If it’s not null, then the layout already got built, as some scrolling happened. Makes sense! ConvertView is important for your app’s performance.</li><li>LayoutInflater, Viewgroups: We’ll get more into this a little later, but for now it’s enough to know that the Views belong to a Viewgroup. This is how we know which views belong to the unit that gets repeated inside of the layout, and this Viewgroup gets inflated with data. Inflating is the process of sorting out which data goes where. Imagine a truck of groceries arriving at a supermarket. Each item in the truck belongs somewhere in the store. Someone has to determine what goes where, someone who knows what the aisles and departments look like, where the store ends, and how big it is. That person needs to issue instructions to the store’s workers, ensuring they know how to place the goods in the correct locations. Part of this process is the LayoutInflater’s job when it aids in correctly matching data to layout.</li></ul><h3>Invoking our custom adapter in MainActivity</h3><p>Now all we need to do is invoke our adapter inside of our MainActivity, and we can test our app. Place this code in your onCreate(), after setContentView(R.layout.activity_main);</p><p><em>MainActivity.java</em></p><pre>gridView = (GridView) findViewById(R.id.baseGridView);<br>gridView.setAdapter(new AlphabetAdapter(this, letters));</pre><p>Here, we are writing the whole GridView into one variable — including the views that will end up getting nested inside it. Then we need to a.) make a local copy and b.) connect that with the GridView, feeding it the correct arguments so the constructor can run boot up an object.</p><p>Run your app — and congrats! You should see the a GridView on the screen — repeating the letter A over and over again. Now you can tweak your layout if you’d like to make any changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/0*u4R-nRmBSvkb9EvW." /><figcaption>We’ve created a GridView and supplied it some data.</figcaption></figure><h3>Making our Data Dynamic</h3><p>Once our dummy data is up and running, we can use position variable to retrieve Strings from the letters array — just like we did in the customized ArrayAdapter.</p><p>Head back over to your adapter, and try and implement the following logic:</p><p><em>AlphabetAdapter.java</em></p><pre><a href="http://twitter.com/Override">@Override</a><br>public View getView(int position, View convertView, ViewGroup parent) {<br> LayoutInflater inflater = (LayoutInflater) mContext<br> .getSystemService(Context.LAYOUT_INFLATER_SERVICE);<br> View gridView;</pre><pre> if (convertView == null) {</pre><pre> // get layout from xml file<br> gridView = inflater.inflate(R.layout.alphabet_grid_item, null);</pre><pre> // pull views set value into textview<br> TextView letterView = (TextView)gridView.findViewById(R.id.grid_item_letter);</pre><pre> // set values into views<br> letterView.setText(mLetters[position]);</pre><pre> } else {<br> gridView = (View) convertView;<br> }<br> return gridView;<br> }<br>}</pre><p>Now, if you run your app, you’ll see your letter value is generated programmatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/0*_zqjHd2b0i3XGtS_." /></figure><p>Good stuff!</p><p>So far so good, we have a custom adapter and a custom layout. Now, let’s add the finishing touches and learn how to apply a different TypeFace to a View that is not directly referenced in an activity’s XML file, but instead nested inside of a view.</p><p>If you take a look back at the first Custom Fonts <a href="https://www.learnhowtoprogram.com/android/user-interface-basics-637d41b1-35dc-400a-bcc3-65794760474d/adding-custom-fonts">lesson</a>, you’ll see that we were able to run get CreateFromAssets() method, retrieve the typeface, then apply it to a view inside of our activity’s onCreate() method.</p><p>But the view that we are looking to style is not accessible in the same way here — we cannot directly reference it in the MainActivity, as the Views are part of the GridView’s custom layout. Oh no!</p><p>And if we try and apply a font to the whole GridView, or call CreateFromAssets() in the adapter, we’ll see that this won’t work either, as this method only runs inside of an Activity, not an Adapter. Dang.</p><p>Don’t fret. There is a solution. Since we wrote the our adapter ourselves, including a new constructor — there is no reason why we can’t pass the Typeface we want to use to the Adapter as an argument to the constructor, and then apply it inside the adapter when the views are bound! This is great! We can pass all kinds of information around through constructors. This will be super useful later on.</p><p><strong>Here’s how:</strong></p><p>First, let’s download a font (.ttf please!) we like from FontSquirrel or <a href="http://www.dafont.com/">DaFont.com</a>, and place it in the assets/fonts folder as we have done previously. Refer back to the earlier lesson if you are unsure how to do this correctly.</p><p>Once that is completed, return back to your adapter and create a new member variable, called mTypeface.</p><p><em>AlphabetAdapter.java</em></p><pre>private Context mContext;<br>private String[] mLetters;<br>private Typeface mTypeface;</pre><pre>//Edit your constructor and your parameter list accordingly.</pre><pre>public AlphabetAdapter (Context context, String[] letters, Typeface typeface){<br> this.mContext = context;<br> this.mLetters = letters;<br> this.mTypeface = typeface;<br>}</pre><p>Let’s move down to where the text for the view is set, and we can now apply our new typeface.</p><pre>// set values into views<br>letterView.setText(mLetters[position]);<br>letterView.setTypeface(mTypeface);</pre><p>Now, let’s return back to our MainActivity, where we can now pull in our Typeface from our <strong>assets/fonts</strong> folder and pass it to our adapter as an argument to the constructor.</p><p>In our onCreate(), let’s declare and initialize a new variable of Typeface type that can hold our typeface.</p><p>Now, all we need to do is to pass this typeface to our adapter through our constructor. Run your app and see your typeface show up in your super custom layout.</p><p><em>MainActivity.java</em></p><pre>@Override<br> protected void onCreate(Bundle savedInstanceState) {<br> super.onCreate(savedInstanceState);<br> setContentView(R.layout.activity_main);</pre><pre> Typeface typeface = Typeface.createFromAsset(getAssets(), “fonts/musicnet.ttf”);</pre><pre> gridView = (GridView) findViewById(R.id.baseGridView);</pre><pre> gridView.setAdapter(new AlphabetAdapter(this, letters, typeface));<br> }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/0*ZHHxtrbjqtuN5G1O." /></figure><p>Awesome! While the final result may not seem all that spectacular, you successfully learned to further enhance your apps with custom adapters, custom layouts, and to pass important data to your nested views via adapters and their constructors. Now, you have a lot more flexibility. Nice job!</p><p>Questions, feedback, thoughts — I’d like to hear ’em. Get in touch by leaving a comment or tweeting me @perrysetgo</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c43d3411d7d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Deep Dive: Part 1 — Doing more with ArrayAdapters]]></title>
            <link>https://medium.com/@perrysetgo/android-deep-dive-part-1-doing-more-with-arrayadapters-8d76549aab3b?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d76549aab3b</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[portland]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Wed, 24 May 2017 03:54:16 GMT</pubDate>
            <atom:updated>2017-05-24T03:54:16.913Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the first Android Deep Dive to be featured on my medium blog! If you don’t know me yet — I am a teacher at Epicodus, a code school located in Portland and Seattle in the Pacific NW. I teach the Mobile Development Track with Java/Android. Welcome! These Deep Dives will give you the opportunity to explore a new, in-depth topic, in a hands-on way, and get more of an idea of how the Epicodus curriculum is structured.</p><p>To get the most out of this Deep Dive, you should have some experience working with Android projects. Understanding how to create a new project, a new activity, and the basic structure of a class is essential. Also, you should have a basic understanding of what an Adapter is and how it works, specifically an ArrayAdapter.</p><p>If you are not quite ready yet to tackle this Deep Dive, we recommend you familiarize yourself first, either through <a href="http://www.learnhowtoprogram.com/">our curriculum</a>, or through another resource.</p><p>If you are ready to get started — great!</p><h3>Review</h3><p>If you recall from using an ArrayAdapter in the past, an Adapter allows us to bind a single instance of an Object to a layout that is held in a collection. If we have an Array of Strings, otherwise known as a <strong>String[]</strong>, an ArrayAdapter pulls out a single String, and displays it in a layout. This process is then repeated until each String in the Array is displayed. Here is an example of how an ArrayAdapter might be implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/0*0L56J9Jd6jRZHE5y." /></figure><p>Even though we can customize our ArrayAdapter, and change the way data is displayed, for example through <strong>String.format()</strong>, we would still use a standard resource that is part of the Android package, namely simple_list_item_1 to display our data. Great! However, the standard ArrayAdapterreally can’t do very much — it can pull items, usually of type String out of an array, and draw a line underneath each one, but that’s about it.</p><p>But what if we want to change the way our list looks, or how the data is displayed? How do we achieve this? We need to create, at minimum, a custom adapter that extends the functionality of the ArrayAdapter. This is what we will be working through for this Deep Dive. Let’s set up our project and get some basics covered first.</p><h4>Setting up our Project</h4><p>Create a new project with all of the standard settings, as well as an empty activity called MainActivity.java:</p><p>Copy in the following code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d58b13b68d6704495e51564afd3ee277/href">https://medium.com/media/d58b13b68d6704495e51564afd3ee277/href</a></iframe><p>Before we move on, import all the necessary classes, and make sure you read through this code and get a rough idea of what we are trying to do here: We have some member variables that we are connecting to views from our layout (which we have not created), and we are also pulling in some information from our frontend and then what? We are moving to a new activity. So far so good. Let’s make the layout file next that is the other half of our activity — that’ll fix the red squiggly lines in our MainActivity.java.</p><p>In your activity_main.xml, copy in:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ea3a0f68092a55683f0bc03dba723638/href">https://medium.com/media/ea3a0f68092a55683f0bc03dba723638/href</a></iframe><p>Now, we just need to create a second empty activity, namely RestaurantsActivity, that MainActivity is referring to in its onCreate(). Go ahead and create that activity now through new &gt; empty activity.</p><p>Copy in the following code for your RestaurantsActivity.java:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b4c328657e4b4453a397e3d7fcec3b91/href">https://medium.com/media/b4c328657e4b4453a397e3d7fcec3b91/href</a></iframe><p>Use the following code for activity_restaurants.xml:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a20cd545558ef0f4b1a46b39b97faa89/href">https://medium.com/media/a20cd545558ef0f4b1a46b39b97faa89/href</a></iframe><p>Now, lets return to our RestaurantsActivity and invoke our ArrayAdapter correctly. On your onCreate(), add:</p><p>…</p><pre>ArrayAdapter arrayAdapter = new ArrayAdapter&lt;String&gt;(this, android.R.layout.simple_list_item_1, restaurants);</pre><pre>mListView.setAdapter(arrayAdapter);</pre><p>…</p><p>Here, you are creating a new standard ArrayAdapter and providing it with the ArrayList of restaurants created earlier in your code.</p><p>Now, if you run your app, you should be able to enter a zipcode and see the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*HwU_dAekn2XHw_GU." /></figure><p>Great! We have a scrollable list of restaurants taken from our ArrayList. Obviously, these are always the same ones, regardless of zip, but this is a good start.</p><p>Now we can customize our ArrayAdapter to make our display a little bit more interesting.</p><h4>Create the custom adapter</h4><p>First, create a new Java class in the main package called MyRestaurantsArrayAdapter.</p><p>Our custom MyRestaurantsArrayAdapter class will need to extend the ArrayAdapter class.</p><pre>public class MyRestaurantsAdapter extends ArrayAdapter {</pre><pre>}</pre><p>We are already showing the name of the restaurant in our ListView. Let’s add some more information, such as a cuisine type. We’ll store this information in a parallel array to keep things simple. (We could use a HashMap, but we’ll stick with Arrays for now.) We’ll need to pass these two bits of information (restaurants and cuisines) to our constructor, so we can use them when we output the data back to the UI. But we also need to pass in the Context, and a resource. Make sure the cuisines and the restaurants can be reached via the same index (i.e they match up)</p><p>…</p><pre>private String[] restaurants = new String[] {“Sweet Hereafter”, “Cricket”, “Hawthorne Fish House”, “Viking Soul Food”, “Red Square”, “Horse Brass”, “Dick’s Kitchen”, “Taco Bell”, “Me Kha Noodle Bar”, “La Bonita Taqueria”, “Smokehouse Tavern”, “Pambiche”, “Kay’s Bar”, “Gnarly Grey”, “Slappy Cakes”, “Mi Mero Mole” };</pre><pre>private String[] cuisines = new String[] {“Vegan Food”, “Breakfast”, “Fishs Dishs”, “Scandinavian”, “Coffee”, “English Food”, “Burgers”, “Fast Food”, “Noodle Soups”, “Mexican”, “BBQ”, “Cuban”, “Bar Food”, “Sports Bar”, “Breakfast”, “Mexican” };</pre><p>…</p><p>Our constructor for our adapter now looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2248313123aecbb8b0469684c6e4de26/href">https://medium.com/media/2248313123aecbb8b0469684c6e4de26/href</a></iframe><p>Context in Android is a term that comes up a lot, and is frequently required for many methods to run, such as Toasts. Context, simply put, is the current state of the application or object. We need it to get information regarding our app, or other parts of our app. Depending on where you are located in your app, such as an activity class, you can access Context via different methods such as getApplicationContext(), getBaseContext(), getContext(), or simply falling back on this.</p><p>Context is just another Object in Android, so don’t let it scare you! You can also pass Context around like any other variable, including into a constructor, like we are doing here.</p><p>The resource here refers to the XML file we are using in order to display our data. We are not changing this at this time. Remember, adapters need three pieces of information, minimum:</p><p>* Information about where they are being invoked (Context),</p><p>* Information about which layout file they are utilizing (resource, in this case simple_list_item_1)</p><p>* Some form of data storage (an Array or ArrayList of String’s or Objects, most likely).</p><p>So far so good. Our custom adapter is taking shape.</p><p>Because MyRestaurantsArrayAdapter inherits from ArrayAdapter, we need to Override some of ArrayAdapter’s methods and replace them with our own custom versions. This is where we can format out output string! Getting closer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/98258087fb7b9afd136d5cfb75965e06/href">https://medium.com/media/98258087fb7b9afd136d5cfb75965e06/href</a></iframe><p>OK, so let’s take a look at this weird line:</p><pre>String formattedString = String.format(“%s \nServes great: %s”, restaurant, cuisine);</pre><p>is what every list item will look like. We could concatenate with +here, but this is a good opportunity to practice String interpolation. The %s represent each value after the closing “, separated by commas. The \n is how we can create a new line in Java, to make our formatting even nicer. String interpolation is a little more sophisticated than concatenating, so make sure you use it!</p><h4>What else?</h4><p>Calling super() from a subclass allows you to reference a method that was overridden. It also allows you to call <em>both</em> the original and the overridden method from a subclass, or call the method from the superclass from within the overriding method from the subclass. If you remove this line, you’ll see that Android Studio will get unhappy. But why? We need this here as we are inheriting from a class that doesn’t provide a default, parameterless constructor. In these cases, you’ll need to explicitly call super() from the constructor of your subclass, passing in parameters the base constructor needs.</p><p>We don’t need to worry about where the int position is coming from, ArrayAdapter takes care of that under the hood.</p><p>Similarly, as mentioned in the comment, we do not explicitly call getCount(), but we need this to be here nonetheless. ListView requires it, so it knows how many items to draw into the UI.</p><p>Alright, we are nearly done with our adapter — now we just need to change how our adapter is called.</p><p>Jump back over to RestaurantsActivity.java.</p><p>Here, we need to change how from invoking boring ArrayAdapter to invoking our cool custom MyRestaurantsArrayAdapter as follows:</p><pre>MyRestaurantsArrayAdapter adapter = new MyRestaurantsArrayAdapter(this, android.R.layout.simple_list_item_1, restaurants, cuisines); //must match constructor!</pre><p>Take it for a spin, you should see something that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*ZF2IkhxaXx3cdkVhd6CjPw.png" /></figure><p>Great work! You have successfully learned to create and implement your own flavour of ArrayAdapters! Well done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d76549aab3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 easy ways to completely $%^& up your code school experience]]></title>
            <link>https://medium.com/@perrysetgo/8-easy-ways-to-completely-up-your-code-school-experience-180cc77ac83c?source=rss-d77fd4733ec8------2</link>
            <guid isPermaLink="false">https://medium.com/p/180cc77ac83c</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[code-school]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Perry Eising]]></dc:creator>
            <pubDate>Thu, 07 Apr 2016 20:01:35 GMT</pubDate>
            <atom:updated>2018-06-14T17:46:04.010Z</atom:updated>
            <content:encoded><![CDATA[<p>You made the decision: It’s gametime. You applied to a code school of your choice, in the city of your liking. With the rise of coding schools, anyone who can scrape together the tuition can attend, and code schools often tout themselves with 90%+ employment rates after graduating. A $90,000 salary seems just around the corner, right? Tech is easy, right? Wrong. Attending a code school or bootcamp can be a pretty daunting experience, but it doesn’t have to be!</p><p>A teacher at a code school, I see students who are not making the most of their experience, even though they have invested time, energy and money in attending. Code schools are demanding environments, and students are constantly prompted to struggle with unfamiliar material. Some get frustrated and drop out, while others do the bare minimum, only to find that getting hired afterwards is tougher than they thought. A lot of this has to do with your attitude, which is probably the biggest part of learning to code. Luckily, your ability to master regular expressions may be innate, but your attitude is firmly under your control. Here’s all you need to know about making the best of your code school experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*hhbeu61YdY1wLLrUy7HA7g.jpeg" /><figcaption>We All Start Somewhere</figcaption></figure><p><strong>1.Sticking to the story:”How can I do something if I don’t know anything?”</strong><br>The vast majority of our students have very little or no programming background — nothing unusual at all when it comes to coding bootcamps. You’re not alone: According to Course Report’s <a href="https://www.coursereport.com/reports/2015-coding-bootcamp-job-placement-demographics-report">2015 study of Boot Camp attendees</a>, 32% have not so much as even touched code before attending a course. What you do need is a love of problem solving, the tenacity to chip away at something for an extended period of time, the desire to learn new ways of doing things, and the ability to interact comfortably with your computer. Don’t get discouraged if you feel like you are not “getting it” — not everyone has the same learning curve: While some students start strong, others are slower to learn at first, and then end up being the secret “aces” of the class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WBAhMb1Qy8Gsw0cP7ZKP0Q.png" /><figcaption>Taken from The Business Insider</figcaption></figure><p><strong>2. Don’t Read The Fine Print</strong><br>That said — if you school or program explicitly states that you will need 3 months of coding experience, or need to be attending 8 hours a day for 5 weeks, or will find it very tough to work while attending, don’t ignore that. You may have found ways to cut corners that worked at high school, college or your workplace, but code schools, boot camps and vocational schools are generally set up to be accelerated programs. Generally speaking, if a program could be taught in less time, we’d teach it in less time. It takes how long it takes and requires what it requires. Be prepared and set up to do the work to succeed — all of it.</p><p><strong>3. I’ve been an expert since — last week</strong><br>Not everything you come across will be brand new, which is when those who have some experience often get frustrated. It’s a predicament: Most beginners don’t know enough to know how little they know. Most experienced coders will tell you there is so much they still want to learn. <br>If the material you’re learning isn’t new, then it’s extra practice. Awesome! If you really think you should not be in the intro class, talk to the administration about switching (know that programs sometimes accelerate quickly…). But don’t undermine the program in front of others because you find it too easy - that doesn’t help someone who is struggling to keep up. If you know something already, take the opportunity to work with students that are having a hard time, or ask your instructor for extra concepts to explore.</p><p><strong>4. Uh, I’m, uh, sick today and tomorrow and all next week</strong><br>If your program insists on group work or pair programming, that’s probably happening for a good reason. Studies show that pair programming <a href="http://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia.PDF">improves program design quality</a> by cutting down on repetition, and allows programmers to work faster — especially <a href="http://www.cs.utexas.edu/users/mckinley/305j/pair-hcs-2006.pdf">novice-novice pairs</a>. Good communication and complimentary skill level were the <a href="http://www.msr-waypoint.net/pubs/75108/esem-begel-2008.pdf">most sought after traits</a> amongst pair programmers — traits that improve with more experience. Consistent practice and a supportive environment will help you succeed, and you need to be in class for it to work. Even a short absence will impact your learning — keep your attendance solid and you will be much more likely to succeed. When picking people to work with, don’t let your preconceived notions about “typical” coders fool you: Many of the strongest people in your class will be people of color, women, students over the age of 35, and people whose first language is not English. Don’t underestimate your peers — they may become your colleagues further down the road.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dr8eIjztZp-rkn1vLqPueQ.png" /></figure><p><strong>5. Hating group projects</strong><br>In my experience of working in an almost exclusively pair-based coding environment, Group Week was more about teaching our students what they didn’t know than what they did. Don’t remove yourself from this experience by resisting the group process. <br>Group Week taught our students a ton about just how little they know about creating an effective team, and dividing up work intelligently, about having solid habits around commenting their code, about straight forward naming conventions, and about version control (and dealing with merge conflicts.) This is valuable hands on experience, and can’t be replicated any other way. Not everyone loves group work — but most devs do work in teams. Take note of how you act in a team setting: Do you have to be the leader? Do you always defer? Do you try and “manage up”? This is a great setting to experience yourself as a team player, seeing your strengths and weaknesses.</p><p><strong>6. Perfectionism</strong><br>Perfectionism is a super easy way to not reach your goals — ever. It has no place in this kind of learning. Bootcamps are all about getting thrown in the deep end of a totally new skill, and adjusting to that scenario by swimming, any way you can, until you get into calmer waters, and the cycle begins again. This is not the master class where you get to optimize your stroke. At the end, you’ll graduate with a lot of unfinished projects, and skill areas where you feel you know a decent amount but not enough. <strong>That is totally normal</strong>. Having high standards is great and a good reason for a teacher to recommend you for your ambition and curiosity. Getting lost in abstract perfectionism and never finishing something is not. You have the rest of your career to perfect what you have been working on. For now, be proud of what you have been able to accomplish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRwwmD8-L1T6HVA5X9m0kQ.jpeg" /><figcaption>Mobile App Developers are constrained in their language choices, but web app developers can choose from a variety of languages and platforms.</figcaption></figure><p><strong>7. But am I doing it right?</strong><br>Learning to code is like learning any other skill — there are a million approaches that are all slightly different, and while there is some overlap, approaches often vary. Same goes for the important choice regarding which language you should pick. While there are definitely those who are more suited to front end design work than back end programming, which language or “stack” you pick is not the be-and-end-all of your dev career. Blindly picking a program because of the arbitrary salary that it may (or may not) bring you after you graduate is no guarantee for success. Having good communication skills, a regular coding practice, well-documented, thoughtful code, and effective solutions for common problems are the hallmarks of a great coder, along with curiosity, tenacity, and attention to detail. A company can have you cross-trained in a particular platform, language or stack much more easily than they can make you have good habits and traits, or an interest in the field. Make sure you are valuable in more ways than one. Pay attention to your options, but don’t undermine yourself by forcing yourself to train in an area you don’t enjoy or have no aptitude for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*6u51C_pl-UH3X3CbggmCjA.png" /></figure><p><strong>8. I’m here, but I didn’t show up</strong><br>At my school, we record notes every week on each student that completes a solo project for us to review. The way I see it, I write whatever you would like me to. What you’d like me to write is communicated to me via the code you turn in. <br>I always enjoy it when I can write <em>“they tried hard to implement a nice UI”</em>, <em>“Made sure to indent their code properly, solid documentation</em>”, and, probably my favorite, “<em>Consistently thinks about their user”</em>. <br>Sadly, too often I write things like “OK solution, but sloppy”, <em>“Not motivated to go beyond the bare, bare minimum”</em>, <em>“Didn’t read project instructions”</em> and, my least favourite, <em>“Couldn’t figure it out and gave up”</em>. <br>Give me a chance to tell your future employers about how much you care about who uses your code, about how well what you write is documented, how hard you tried, even if you couldn’t make it work 100%.</p><p>After couching students from all walks of life, across gender, race and class backgrounds as well as intellectual abilities, I’ve been able to identify the single most identifier as to whether a student will succeed or fail in and after our program, It’s almost too simple. It’s <strong>Hands On Keys</strong>. I doesn’t matter if you understand the concepts when they are outlined in the curriculum or the homework; and it’s not important if you understand the video we provided or the sample code you read through. What is important is being able to internalize and apply said concepts in an actual project.<br>If you do not spend enough time with <strong>Hands On Keys</strong>, working with focused attention, you will not succeed, pure and simple. Outliers aside, you will not be able to deeply understand and reproduce code without writing it, again and again, from scratch. You will miss the closing brace and the variable declaration if you don’t understand why they are there, and you will not understand why they are there if you don’t spend time writing code. Don’t copy and paste — type. Everything.</p><p>At some point, all students who want to be successful need to break away from being students and start becoming developers. The sooner you can make that transition, the more successful you will be. Remember: You are the project you are working to create, not the stupid pizza delivery app we asked you to build. You are your own killer feature and strongest selling point. Commit to your program, tough days and easy days. If the material is hard, show up and embrace it. Don’t hide away from your choice to attend the program and to work in the format your school requires. Be invested and proactive in your own success, as opposed to just going through the motions and hoping for an easy ride.</p><p>In short, simply attending a code school or bootcamp program is not enough: We are just providing you the environment to help you mold yourself into an informed, trainable asset to your future employer. You cannot learn every aspect of frontend design or backend programming in a short program, and if your program claims that you can, then you should seriously consider attending somewhere else. What you can learn is whether you like programming, some basic programming concepts, some technical frameworks and approaches in the language track you pick, how to communicate when working on a project, and how to document your code. The rest is up to you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=180cc77ac83c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>