<?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 Danielle Emma Vass on Medium]]></title>
        <description><![CDATA[Stories by Danielle Emma Vass on Medium]]></description>
        <link>https://medium.com/@daniellevass?source=rss-3bd31acc4659------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*H7DagV97FOamk4BUjVnTPg.jpeg</url>
            <title>Stories by Danielle Emma Vass on Medium</title>
            <link>https://medium.com/@daniellevass?source=rss-3bd31acc4659------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:36:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniellevass/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[My notes from Droidcon London 2019]]></title>
            <link>https://medium.com/@daniellevass/my-notes-from-droidcon-london-2019-c6caf8dacc81?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6caf8dacc81</guid>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 20:54:39 GMT</pubDate>
            <atom:updated>2019-10-28T20:54:39.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lEYAa-xUZRHYyYMPZYitCg.jpeg" /><figcaption>Photo by Pathum Danthanarayana on Unsplash</figcaption></figure><p>This year I was very thankful that my employer Pusher sponsored my ticket to Droidcon UK 2019! These are the notes I took at the different talks I attended:</p><h4><a href="http://uk.droidcon.com/skillscasts/13794-keynote-christina-lee">Keynote: Coding Like an Althete — Christina Lee</a></h4><p>Christina spoke to us about the similarities between athletes and programmers (who she then refers to as Brathletes as we’re using our brains), and some things us brathletes can learn from athletes.</p><p>Things I learned:<br>- Programmers are more like athletes than I thought; we have team uniforms, we announce when we’re leaving and joining new teams, we get compensated $$$, our managers want to get the most out of us.<br> — But we don’t really have coaches :( Some companies offer nutritional coaches, but what about other crucial performance enhancing elements like sleep?<br> — Programmers often only get career feedback once a year — not after every game like sports people.<br>- The Monday Morning Quaterback — on monday they look at the game that was played on the weekend to work out everything that went wrong so they can determine which pieces they want to focus on to improve for next time.<br>- People don’t pursue passions, they do things they’re good at which in turn makes them happier. People who have been in a role longer tend to be happier with that role.<br>- Sleep is super important. After being awake for 19 hours straight you have the same symptoms as someone who is drunk.<br>- Flow is important for people to feel satisfied, less stressed, and perform better but our current offices and ways of working are set not set up to help this. On average people switch tasks every 10 minutes, and half of those switches are self imposed.<br>- 5 tips to improve things<br> — Make your whole day as flow — schedule time for interruptions / twitter<br> — Train your memory — your memory is a muscle — concentration can be grown<br> — Block like tasks together to minimise attention residue<br> — Write down unfinished tasks — make a plan on how to finish these which reduces the attention residue left by switching tasks often<br> — Create a shutdown ritual to transition out of work mode — free time is crucial!<br> — Break down large goals into smaller goals — instead of thinking I want to be like Jake Wharton start with I want to understand how build systems work</p><h4><a href="http://uk.droidcon.com/skillscasts/14200-supporting-each-other-growth-for-juniors-and-seniors">Supporting Each Other: Growth for Juniors and Seniors — Lara Martín</a></h4><p>Lara spoke to us about the similarities between growing junior developers and senior developers, and that both seniors and juniors receive immense benefits from working together.</p><p>Things I learned:</p><p>- Focus on the good things people bring and not on all the new things they need to learn. Maybe they had a previous career before joining — are there any things there that could be useful for your team?<br>- Both juniors and seniors should be continuously learning.<br>- Don’t just criticise but offer suggestions. Criticism should always be in private and praise should always be public. Code reviews are in the public sphere.<br>- Be open about what things you don’t know — by opening up other colleagues might also open up that they also don’t know and everyone can learn together<br>- How can you help a junior learn, be specific about starting starting tasks — they can work out and check back with what they think they should be doing → ask for guidance if they get stuck</p><h4><a href="http://uk.droidcon.com/skillscasts/14196-safe-kotlin">Safe Kotlin — Marcin Moskala</a></h4><p>Marcin spoke to us from a chapter from his book, [Effective Kotlin](<a href="https://leanpub.com/effectivekotlin">https://leanpub.com/effectivekotlin</a>), about how to build safer applications in Kotlin.</p><p>Things I learned:</p><p>- Mutability — avoid accidentally exposing underlying objects in interfaces — use `copy` to ensure that the returned item is actually immutable<br> — e.g. if your interface has a mutable list of contacts, don’t return it when someone asks for all the contacts as they could accidentally add to it themselves.<br>- Libraries should explicitly say what types they return, and not infer from what is actually returned<br> — e.g. if you have a car interface that defaults to returning a FiatCar object instead of the parent Car object!<br>- Use `require` to check expectations on inputs<br> — also you can use `check()` and `checkNotNull()`<br> — `assert` is not just in test — we can do that in our runnable code too!<br>- Use standard errors over custom errors e.g. `IllegalArgumentException` instead of a custom error. Other programmers will know how to handle the standard errors better than a random list of custom errors.<br>- Offensive programming — explode loudly when something is broken!<br>- You need to use both offensive and defensive programming for a safe system design. Context of when to use either is important e.g. a developer failing to initialise a library should explode loudly so the developer knows to fix — however when the library in a production app it should be defensive so that the developers customer doesn’t experience any issue.</p><h4><a href="http://uk.droidcon.com/skillscasts/13096-keynote-get-happy-get-known-get-paid">Keynote: Get Happy, Get Known, Get Paid — Stacy Devino</a></h4><p>Stacey gave us a very energetic talk about how we can get happy, get known, and then get paid!</p><p>Things I learned:</p><p>* Love yourself — how can anyone else appreciate you if you don’t appreciate yourself!<br>* It’s okay to say no to things you don’t want to do! It opens up your time for saying yes to the things that really matter.<br>* Invest in yourself! Ensure you have the best tools for your traid you can afford e.g. a comfortable keyboard, a great chair.<br>* Invest in those core/soft skills — skills such as communication are going to be very important as you climb that career ladder.<br>* Ensure you have a personal “brand” — what makes you special? Doesn’t have to be 100% tech focused. Keep your public social media platforms consistently “on” that brand.<br>* Be authentic but also display the best version of yourself. Presentation matters!<br>* GitHub all the things you’ve been working on — even failed projects. It demonstrates to others that you’re keen to learn and try new things!<br>* Work out what your leadership style is (DISC with a facilitator) how you can get the most out of that style, and what weaknesses you need to be aware of.<br>* Hire a career coach to help you work out where you want to go with your career that align with your personal goals too!</p><h4><a href="http://uk.droidcon.com/skillscasts/14145-the-light-way">The Light Way — Lisa Wray</a></h4><p>Lisa spoke to us about how Facebook Messenger Lite works, and why they’ve chosen their to build it that way.</p><p>Things I learned:</p><p>- Messaging has to work offline. Not everyone can be online all the time as it uses battery / data / time to be around.<br>- You need to work out out what’s important to measure for your customers. For Messenger Lite that was apk size / startup speed.<br>- They used the Database First architecture pattern<br> — Transform the data received from the API before it goes into the DB on device — the UI is then simply a wrapper around the DB.<br> — Transform on the server can reduce the complexity on the app e.g. creating the group message title. This has the added bonus of that it can then be consumed multi platform!<br> — Time proximity handled in the transform is important. To create the message bubbles in FB messenger they use a bitwise mask to represent how it displays based on the message before and after to see if they’re part of a series of messages in close time proximity<br> — Complexity is moved to the DB layer not the UI<br> — You have to be careful you aren’t constantly writing / reading to the DB when people aren’t using the device if there’s a conversation that’s very noisy<br> — Infrastructure should not depend on other infrastructure</p><h4><a href="http://uk.droidcon.com/skillscasts/14311-the-android-chef">The Android Chef — Anastasia López</a></h4><p>Anastasia spoke to us about career advancement for chefs, and how there are parallels in expectations between chefs and programmers as we advance our career ladders.</p><p>Things I learned:</p><p>- Commis Chefs (Junior developer) are expected to not know everything, will make mistakes, but ask lots of questions!<br>- Chef de Partie (Mid developer) are expected to take responsibility for their work, operate more autonomously, and look for things to improve in the team.<br>- Sous Chef (Senior developer) are expected to know when to intervene if someone needs support, start planning the menu (or the teams work), mentor more junior team members.<br>- Chef de Cuisine (Lead developer) are expected to set the culture and change things.<br> — There’s a difference between advocating and sponsorship.<br> — Take time to find your cognitive biases (there are good resources online for this).</p><h4><a href="http://uk.droidcon.com/skillscasts/14146-improve-your-code-with-lint-checks-for-kotlin">Improve your code with Lint checks for Kotlin — Emma Tresanszki</a></h4><p>I attempted to hear Emma speak to us about how to improve our code with lint checks. Unfortunately the room was so full that I ended up not being able to see the presenting screen.</p><p>Things I learned:<br>* Droidcon London need to think about getting bigger rooms for the “smaller talks”<br>* [Klint](<a href="https://github.com/pinterest/ktlint">https://github.com/pinterest/ktlint</a>) — Pinterest have open sourced their linter which you can use. Mostly suggests formatting how code looks rather than how the code works.<br>* You can easily write your own linter e.g. maybe as a team you decide never to use `lateinit var` and you want the build to fail if one is introduced.</p><p>— — <br> Finally, where would we be without the friends we make along the way?</p><h3>Corey Leigh Latislaw 🎀 #droidconuk on Twitter</h3><p>feminati at #drodiconuk!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6caf8dacc81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2018 — I learned to exercise]]></title>
            <link>https://medium.com/@daniellevass/2018-i-learned-to-exercise-4bc30292b956?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bc30292b956</guid>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 20:59:25 GMT</pubDate>
            <atom:updated>2019-01-14T21:02:10.001Z</atom:updated>
            <content:encoded><![CDATA[<h3>2018 — I learned to exercise</h3><p><a href="https://medium.com/@daniellevass/2017-why-i-learned-to-crochet-66acb144f93">Last year I wrote a post about why I learned to crochet and why learning a new thing each year was helping me grow</a>. For 2018 I wanted to exercise better. So how did I do?</p><p>First achievement: I actually stepped foot in a gym! I asked a personal trainer for a few sessions and actually I learned how some of the machines worked! I had major anxiety over looking stupid not knowing what to do at the gym. Or being really shit at everything and I’ve definitely conquered that fear! Would definitely recommend a personal trainer to anyone who wants to learn to exercise better!</p><p>Second achievement: I signed up for random exercise classes to try different things. I made some friends doing this and I’ve learned that I’ll push myself a lot more if I’m with other people. This is something I’m going to take forward into 2019 too!</p><p>Third achievement: I ran two separate 5km races and didn’t die! I was really sure I would die. Especially the first one, which my mum, my sister, and I did on the hottest day of the year in England!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6iYMATyqeUMCEuT175RthQ.jpeg" /><figcaption>Me, my sister, and my mum ran the race for life in Bath in July where it was 28C!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yYUp0ia3DCdVM2bqsOTOBg.jpeg" /><figcaption>My friend Jo and I ran a 5km race for life in Finsbury Park but it was mismanaged and we had to make our own 5km route up!</figcaption></figure><p>I also got to run around some exciting and different places too! Turns out it’s a lot easier to run around the Bay Area, California than it is in Singapore or London!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMJ59DoT02S1Q5xyCndO9g.jpeg" /><figcaption>I got to run around Stanford University one morning before work.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dIMxX6lbPqbYdpsYPtAruA.jpeg" /><figcaption>I had to run at like 6am in Singapore so it wasn’t so hot! It was still too hot and sweaty!</figcaption></figure><p>I used some fitness apps to help quantify and track my progress. I ran 24 times in 2018, totaling 98km (I just missed out on 100km!), averaging 4km per run. The fastest I managed to do a 5km was just under 35 minutes. I might try to do some interval training this year and see if I can bring my time down at all.</p><p>A really great side benefit to this was the health benefits. The nurse at my local GP surgery had been worried about my blood pressure over the past few years. She’s noticed that my blood pressure has been significantly lower in recent appointments, which is a great thing!</p><p>I wanted to finish this post with an Instagram-able photo, but in reality I ate too many cakes over Christmas so here’s what peak Danielle looked like in October:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hgg_VLMgJilihBMvf0XvQ.jpeg" /><figcaption>Pretty impressed I got a few muscles!</figcaption></figure><p>I also didn’t forget my crochet skills from 2017 and I’ve learned how to move on from 2D hexagons to making 3D animals! This year for Christmas I made all my friends and family something!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qhov9nwL1i-Vv1oumZsUHQ.jpeg" /></figure><p>So what about 2019? I don’t want to lose my newly developed exercise skills, I’ve already been doing my Barre Classes once a week, and I’ll run twice a week! I’m also signing up to do two 10km races this year!</p><p>But in regards to my something new, I read recently that you should split anything you want to do into 12 week chunks. If you give yourself a year you’ll spend too much time not on task which is totally true for me. This year I didn’t really start exercising until May and that’s already 5 months of the year gone!</p><p>So I’m going to set myself 12 week goals, and I can do 4 of those each year! So firstly, I’d like to learn how to journal! I’ve got myself a few bullet journal guides, and bought the best self journal to more easily get started! But I really like the idea of keeping track of what’s important and staying more organized!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIPMhuVlIJEiR4V14MQ0kg.png" /><figcaption>the books i’ve bought to learn how to journal!</figcaption></figure><p>After the first quarter is over I’m not really sure what to push myself with. I want to learn how to get the most out of my savings. And I’ve been very kindly given a violin (which I’ve *always* wanted to learn). I’ll follow up next January and let you know what happened!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bc30292b956" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[codebar mobile in 2018!]]></title>
            <link>https://medium.com/the-codelog/codebar-mobile-in-2018-a2f48fecb419?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2f48fecb419</guid>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[teaching]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Tue, 20 Nov 2018 14:29:51 GMT</pubDate>
            <atom:updated>2018-11-20T14:29:51.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kI_OI8OTQsRIcP8NlIfmrg.jpeg" /></figure><p>2018 has been a HUGE year for codebar mobile!</p><p>We ran 10 workshops, 5 for Android, and 5 for iOS! This has involved the help of around 100 coach positions, for over 150 students!</p><p>Thank you to everyone who has graciously hosted us:</p><h4>January @ <a href="https://twitter.com/quanderio">Quander</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XBMzodDUpTITdo9d_oNWNQ.jpeg" /><figcaption>We started our year off at <a href="https://twitter.com/quanderio">Quander</a> for a workshop in iOS.</figcaption></figure><h4>February @ <a href="https://twitter.com/TransferWise">TransferWise</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xSZk0TWs-ztSWd06inU_Kg.jpeg" /><figcaption>In February we were at <a href="https://twitter.com/TransferWise">TransferWise</a> for an Android workshop</figcaption></figure><h4>April @ <a href="https://twitter.com/DeliverooEng">Deliveroo</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BBqXyXVcNEPmogXBKf43kA.jpeg" /><figcaption>in April we were at <a href="https://twitter.com/DeliverooEng">Delivero</a> for our very first Kotlin workshop!</figcaption></figure><h4>May @ <a href="https://twitter.com/StarlingDev">Starling Bank</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PSZdxq4FGfrE8DS7uifiHA.jpeg" /><figcaption>in May we were at <a href="https://twitter.com/StarlingDev">Starling Bank</a> to do some iOS and everyone enjoyed taking home a fresh pair of Starling Socks!</figcaption></figure><h4>June @ <a href="https://twitter.com/thetrainline">TrainLine</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2jWv_gdY67TeAi37TwKgQ.jpeg" /><figcaption>In June we joined <a href="https://twitter.com/thetrainline">The Train Line</a> for some Android!</figcaption></figure><h4>July @ <a href="https://twitter.com/Wipro">WiPro</a> with help from <a href="https://twitter.com/DevelopHerUK">DevelopHer</a> &amp; <a href="https://www.lloydsbankinggroup.com/">Lloyds Banking Group</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3NwgJNSnsLhiVA5Oq_X8A.jpeg" /><figcaption>Probably our largest event this year! In July we joined forces with <a href="https://twitter.com/DevelopHerUK">DevelopHer</a> with <a href="https://twitter.com/Wipro">WiPro Digital</a> and <a href="https://www.lloydsbankinggroup.com/">Lloyds Banking Group</a> for an iOS workshop!</figcaption></figure><h4>August @ <a href="https://twitter.com/TwitterUK">Twitter</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbhF9sobyPLFqEdD2B5ZLg.jpeg" /><figcaption>In August we were lucky to be hosted at <a href="https://twitter.com/TwitterUK">Twitters UK</a> offices for some more Android development!</figcaption></figure><h4>September @ <a href="https://twitter.com/DeloitteDIGI_UK">Deloitte Digital</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KX-KUREKB5KRvP6rj4MygA.jpeg" /><figcaption>In September we joined <a href="https://twitter.com/DeloitteDIGI_UK">Deloitte Digital</a> for some iOS development and we tried very hard not to play with all their robots and 3D printers!</figcaption></figure><h4>October @ <a href="https://twitter.com/TheAppBusiness">TheAppBusiness</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVDcRenVLXEiQk251a3niQ.jpeg" /><figcaption>In October we joined <a href="https://twitter.com/TheAppBusiness">The App Business</a> for some more iOS engineering!</figcaption></figure><h4>November @ <a href="https://twitter.com/SkyscannerEng">SkyScanner</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*2hYf-X1tBT7jjIIf6lGZxg.jpeg" /><figcaption>The final event for this year, we were at <a href="https://twitter.com/SkyscannerEng">Skyscanner’s</a> offices to build some Android apps!</figcaption></figure><p>Thank you to all the coaches who gave up their evening to help our students learn something new.</p><p>Thank you to all the students, who even after a long day of doing their regular day came to learn something new and challenged themselves!</p><p>Thank you to everyone who left feedback this year, without it we wouldn’t have made things better!</p><p>For instance, now we send people an email ahead of the workshops so they can install either Android Studio or XCode. Which is far better than using valuable workshop time to watch a progress bar go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bNbWagLjyOIsxHPfaB9p6Q.jpeg" /></figure><p>Another thing we’ve learned through feedback is to diversify our tutorials:</p><p>Thank you to everyone who helped worked on the tutorials to make them better.</p><p>To <a href="https://twitter.com/geeky_android">Savvas</a> who helped me learn Kotlin in one evening so we could write a tutorial which ended up everyone building their own cookie themed tinder!</p><p>To <a href="https://twitter.com/rosaemerald">Rosa</a>, <a href="https://twitter.com/funmmi">Funmi</a>, <a href="https://twitter.com/abdulajet">Abdul</a>, <a href="https://twitter.com/leke_os">Leke</a>, and Yishai who spent an evening help to write new swift tutorials to expand our iOS resources!</p><p>Thank you to Londroid, Google IO Extended London, and NSLondon for allowing us to talk about what we’re doing and why we needed support to achieve everything this year!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghQP_JAExtZO79R5P6J5wA.jpeg" /><figcaption>in April we spoke at Londroid at Babylon Health!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceQMRaMdLQqn7RGY4Gl6vA.jpeg" /><figcaption>Early in May we got a stand AND speaking spot from very kind people at Google IO Extended.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7f-GT7IFxwBX-8CNi4fUHw.jpeg" /><figcaption>Later in May we spoke to people at NSLondon in the Facebook London office!</figcaption></figure><p>So what will 2019 entail?</p><p>We’re looking for support from the community to help run our workshops from February each month on Thursdays, aiming for the start of the month! We’re a maximum of 10 coaches and 20 students (30 people) who only need some food and drink, wifi, electricity and some comfy chairs to run a workshop! If this is something you think you could help us out with please reach out to mobile [at] codebar [dot] io!</p><p>Finally, I like to be held accountable to future goals. This year I had a dream to end the year with a hackathon building apps for social good. Unfortunately too much “life” got in the way to make that happen. In 2019 I want to make this happen! If you’d like to help please find me anywhere on the internet!</p><p>Finally, thank you to YOU for taking the time to read this post!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2f48fecb419" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/codebar-mobile-in-2018-a2f48fecb419">codebar mobile in 2018!</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My notes from Droidcon London 2018]]></title>
            <link>https://medium.com/@daniellevass/my-notes-from-droidcon-london-2018-83944b586e3a?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/83944b586e3a</guid>
            <category><![CDATA[droidcon]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 18:29:00 GMT</pubDate>
            <atom:updated>2018-10-30T18:29:00.071Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sgvOIHYJI6Hfml5RtwCCNg.jpeg" /></figure><p>I really love attending Droidcon London every year, and this year was awesome! Each year is an opportunity to learn new things and experience new and interesting ideas from other Android programmers. So here’s some of the things I wrote down, maybe they’ll be useful for you too!</p><h4><a href="https://skillsmatter.com/skillscasts/12720-applications-should-be-for-everyone-it-s-in-your-hands">Applications Should Be For Everyone. It’s In Your Hands</a></h4><p><a href="https://twitter.com/BrittBarak">Britt</a> walked us through why and how she built an App for her Nana where she could take a picture of something, such as a tub of ice cream and it would say what was in the picture. This is pretty easy now to do with some of the Machine Learning libraries from Firebase!</p><p>Things that I learned:</p><ul><li>There is a device setting to scale view size as well as text size (scales dp AND sp)</li><li>Use sp, not dp for button heights and widths that contain an icon</li><li>Colour contrast is important. Use 3:1 for large text, 4.5:1 for smaller text. You can use <a href="http://www.contrast-ratio.com/">www.contrast-ratio.com</a> to find out.</li><li>Design labels and buttons for text to grow and wrap, think how would your label look if it took up 2 lines instead of 1.</li><li>The average fingertip is 50dp, so make sure buttons are at least 48dp! You can use min_height and min_width if you have programmatic text on a button.</li><li>Using Talk Back if data on the page updates. You can use Accessibility Live Region with either assertive (it stops reading anything else to notify that somethings changed), or polite (let’s the reader finish what it was doing before announcing a change).</li><li>There’s an API to check if accessibility is enabled on the device, maybe consider showing an adapted UI for these people!</li></ul><h4><a href="https://skillsmatter.com/skillscasts/11620-keynote-pragmatic-crafting">Pragmatic Crafting</a></h4><p><a href="https://twitter.com/FMuntenescu">Florina</a> talked to us about how they re-architected their app Plaid. If you’re thinking of re-architecting an app anytime soon (or starting a new app) I’d definitely recommend a watch!</p><p>Things I learned</p><ul><li>Code reviews are an opportunity to share knowledge with the team.</li><li>Create technology champions who are experts and owners in their area of expertise. Set up knowledge sharing sessions so everyone has some knowledge of everything!</li><li>Use short lived branches for version control and make sure things regularly get merged into master. This means no merge issues or lengthy rebasing!</li><li>Try continuous delivery to understand better if what you’re building is actually correct.</li><li>Decisions based on product needs — you don’t have to use all the new shiny technologies think about what you really need</li></ul><h4><a href="https://skillsmatter.com/skillscasts/12727-coroutines-by-example">Coroutines by Example</a></h4><p><a href="https://twitter.com/RunChristinaRun">Christina</a> gave us an introduction to coroutines with a presentation of five things we needed to know before we got started, and then she refactored an rxjava app to use coroutines live on stage. And it ran her first attempt!</p><p>Things I learned:</p><ul><li>Coroutines are a state machine object.</li><li>Coroutines are builders and entry points into suspendible code.</li><li>Coroutines dispatch to threads.</li><li>If you want to cancel things use jobs (in rxjava land disposables)</li><li>Coroutines are synchronous by default. If you want concurrency it’s explicit and you have to opt in.</li></ul><h4><a href="https://skillsmatter.com/skillscasts/12712-smooth-criminals-animation-in-android">Smooth Criminals, Animation in Android</a></h4><p><a href="https://twitter.com/DoesitPew">Stacy</a> walked us through an example animation but using 4 different ways to achieve the animation; XML, animate(), Animation Library, Object Animator, and a bonus property versus holder. If you want to see the code in action check out <a href="http://www.bit.ly/AndroidAnimCode">www.bit.ly/AndroidAnimCode</a>. There were questions and prizes given!</p><p>Things that I learned:</p><ul><li>If you’re using Lottie for animations there’s <a href="http://www.lottiefiles.com/">www.lottiefiles.com</a> to share and use other peoples animations.</li><li>There is a library called <a href="https://github.com/alexjlockwood/kyrie">Kyrie</a> which is an alternative to AnimatedVectorDrawables</li><li>If you’re looking for the best way to add smooth animations to your app, check out <a href="https://developer.android.com/reference/android/animation/ObjectAnimator">ObjectAnimators</a>.</li><li>MotionLayout and ConstraintLayout 2 might solve some of these issues as it will work on a deeper level than canvas. Some issues right now include no API, and only 1 motion scene per layout.xml! However, sometime soon there will be a UI Simple animation orchestration tool which was apparently demonstrated at IO this year.</li></ul><h4>Hire Better, Faster, Stronger</h4><p><a href="https://twitter.com/AnastasiaLopezD">Anastasia</a> and <a href="https://twitter.com/VivienBarousse">Viv</a> spoke about how to interview more inclusively, as both the interviewer and a potential candidate!</p><p>Things I learned:</p><ul><li>Top performers always means something different at different places.</li><li><a href="https://en.wikipedia.org/wiki/Fundamental_attribution_error">Fundamental attribution errors</a> in that people tend to put more importance on the persons character or intentions than on external factors.</li><li>You should look at what gaps do you have in your team currently, how do you look to fill those gaps?</li><li>Think about your red flags when interviewing e.g. being interviewed by 7 white guys doesn’t show diversity from the employer and is for most people a major red flag.</li><li>Document your interview process, do all the stages and questions really need to be there?</li><li>Create a calibration sheet for the interview process, which means you can compare different candidates as fairly as possible with data.</li><li>As a candidate ask expectations at each stage. Is not knowing something really a deal breaker? For example if the technical test requires writing Kotlin and you don’t know Kotlin, would they help you learn on the job if you were successful?</li><li>Use the expectations to take 10 minutes ahead of an interview to get into the right mind frame.</li><li>As a candidate you are also interviewing the company!</li></ul><h4><a href="https://skillsmatter.com/skillscasts/12940-keynote-the-art-of-intentionality">The Art of Intentionality</a></h4><p><a href="https://twitter.com/corey_latislaw">Corey</a> sketch-noted and spoke (!) about her journey through being more intentional.</p><p>Things I learned:</p><ul><li>Joyrney — it’s a journey but with 100% more joy!</li><li>Use your emotions as data point, start journaling and measuring your emotions over time. Think about patterns and what leads to good or bad days.</li><li>You don’t have to take all feedback — saying “Thank you for the feedback but I’m moving on” is okay too.</li><li>Create a diverse board of directors for your life — people you can go to and ask “life” questions but will also push you to be a better person!</li><li>Create a vision for the next 2 to 5 years. Break it up into what you need to do for the next quarter, create 1–3 achievable BIG goals.</li><li>Theme your days to defragment as much as possible e.g. Mondays being for meetings, Tuesdays being for client work etc.</li><li>Personal feedback can be poison, think about how to give feedback as fast but remember to be as kind as possible.</li><li>Read the <a href="https://i.pinimg.com/originals/58/b1/c4/58b1c49aa381624c5ba129f315fb13db.jpg">Sunflowers poem by Rupi Kaur</a></li></ul><p>And finally, my all time favourite activity is catching up with all the friends I’ve not seen since last year, and all the new friends I got to meet. I got a bunch of new stickers for my sticker collection, and an amazing rainbow pin for my backpack. I also got to join the Android Peeps and play Mario Kart on the switch between sessions! Hopefully we’ll see you all again for next year :-)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j3BoMuLHBN9wN_Xi-PKYdg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83944b586e3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Emojis with Code]]></title>
            <link>https://medium.com/@daniellevass/making-emojis-with-code-8da03e87a27f?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/8da03e87a27f</guid>
            <category><![CDATA[emoji]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[svg]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Sun, 22 Jul 2018 17:33:57 GMT</pubDate>
            <atom:updated>2018-07-22T17:33:57.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJ22kfBXEnoKvvQavVaJMg.png" /><figcaption>image from <a href="https://unsplash.com/photos/YfpP8_IxKmQ">https://unsplash.com/photos/YfpP8_IxKmQ</a></figcaption></figure><p>I’ve written a bunch already on <a href="https://medium.com/the-codelog/introducing-codebar-android-d6c79b9bd98c">how</a> <a href="https://medium.com/@daniellevass/things-we-learned-teaching-children-to-code-this-year-fe1c436a89ae">and</a> <a href="https://medium.com/@daniellevass/why-i-m-sad-to-be-leaving-all-the-young-people-i-ve-encouraged-into-computing-here-in-bath-400917751416">why</a> I teach people to code. This article going to be more of a tutorial on something to code!</p><p>This is my favourite activity for introducing people to writing code; building our very own emoji! We’ll use Scalable Vector Graphics (SVG) and animate it with JavaScript (JS). They’re the same building blocks that make up webpages!</p><p>This tutorial will take about an hour, but you could take a *lot* more time making your emoji yours if you’ve got the time! I had one student who spent an entire semester of after school clubs working on their emoji. When they were finished it was truly a masterpiece!</p><p>This article is aimed at those currently learning to code, especially with no previous experience! Or those who have a bit of programming knowledge and want to do something a little different!</p><p>When you are done, please post your emoji in the comments for us all to enjoy and encourage each other on our programming journeys 😊</p><h4>1 Setup</h4><p>So to start, all we’ll need is a web browser, something like Google Chrome, Firefox, or even Internet Explorer. Hopefully you already have one of those already as you’re reading this article!</p><p>Next we’re going to open a website called<strong> </strong><a href="https://jsfiddle.net/"><strong>JSFiddle.net</strong></a> (in a new browser tab so you can continue reading this article!) which allows us to write and run our code without needing to download anything onto your computer.</p><p>JSFiddle also gives us a save button, which will make a custom url which you can then share with other people (or write somewhere safe so you can work on it later). JSFiddle also supports versioning, so every time you press the update button, it increments the number at the end of the url. So if you save often (which you really should!) you can see your work evolve over time!</p><h4><strong>2 Paper</strong></h4><p>So now let’s get started writing some code! The first thing we need for our emoji is a piece of paper to draw onto. We’re going to work in the HTML box (the upper left box) and type:</p><pre>&lt;svg height=&quot;400&quot; width=&quot;400&quot;&gt;</pre><pre>&lt;/svg&gt;</pre><p>So what do those things actually mean? &lt;svg&gt; is a tag, it says start an svg object. You can think of the svg tag as like a piece of paper. Everything we start has to end, so we also have to write an end &lt;/svg&gt;.</p><p>We can add attributes to our svg by specifying height and width. That might not make a lot of sense right now, but let’s come back to this after we’ve drawn a few more shapes!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQMjIh7Vxi70iMIYBuk48A.png" /><figcaption>Click the Run button at the top of the page and the result square should go from dark to white! We’ve successfully created a piece of paper!</figcaption></figure><h4>3 Circles</h4><p>What’s the most important part of an emoji; the yellow face circle! We need to write our code after we declare our piece of paper, and before we end our paper. Our shapes won’t render if we’re not drawing on the paper! I have a screenshot below to help. Circles probably look a bit intimidating at first but write this yourself:</p><pre>&lt;circle cx=&quot;200&quot; cy=&quot;200&quot; r=&quot;150&quot; fill=&quot;yellow&quot;/&gt;</pre><p>Lets break it down together. We have a &lt;circle&gt; tag, our thing which we’re drawing, which has some properties. cx is the center x value (going back to school maths, horizontal axis, left and right), cy is the center y value (vertical axis, up and down), r is radius (how big our circle should be), and fill says what colour should we fill the shape with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ay0uHZ-dwjtKEwBFKvUsSQ.png" /><figcaption>Make sure you click the run button again to see your circle appear!</figcaption></figure><p>Next, try making two more circles for the eyes without my support.</p><p>If you get stuck with the x’s and y’s, the bigger the x number the further right the shape will go, the bigger the y number the furthest down the page. Our origin (0,0) is the top left.</p><h4>4 Paths</h4><p>So now we’ve mastered the circle, what other shapes can we make! Let’s have a go at making a mouth by creating a path shape (I have a screenshot below if you get stuck where to write this):</p><pre>&lt;path d=&quot;M 130,280 l 150,0&quot; stroke=&quot;red&quot; stroke-width=&quot;3&quot; /&gt;</pre><p>So this definitely looks a little scarier! Let’s look at some of the words we understand first; we have stroke which is the colour of our line, and stroke-width which is how big that line should be. Finally, we have a d attribute which stands for data. That d is what makes this look scary.</p><p>So breaking the data property into the pieces, M means move to this coordinate 130,280. We then have the letter l but it’s lowercase, which means we can move relative to where we started, so we’re going to move 150,0 which means straight across, no ups or downs.</p><p>We could have written L 280,280 which would have created the same thing. Capital letter instructions move independent to where we started.</p><p>You can connect multiple of these instructions together to draw more complex paths.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kaBT_FF6TKcFH4eQ0F_EvA.png" /></figure><p>Our poor emoji looks pretty sad, let’s work on making him a little happier!</p><pre>&lt;path d=&quot;M 130,280 q 75,50 150,0&quot; stroke=&quot;red&quot; stroke-width=&quot;3&quot; fill-opacity=&quot;0&quot;/&gt;</pre><p>Where we used the letter l for a line, we can use a letter q to say we want a curve. The q requires two sets of coordinates, the first is where we want to grip the line as if we’re pinching it, the second is in where our line should move it. We can keep the second coordinate the same as our l coordinate.</p><p>Imagine if your line was an elastic band starting, we wanted to grip it somewhere in the middle and move it up and down. That’s what the new set of coordinates mean. We want to grip it right in the middle (75, is half of 150) and move the elastic 50 points down — which makes him happier! What would you need to change to make him look sad?</p><p>The observant of you will have also noticed we’ve added a new attribute fill-opacity. This makes the “shape” part of the path transparent. If we don’t have this, we get a weird black shape in the mouth because we haven’t told it what colour to be, and computers represent no colour as black.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PB1vrCF_I9EpHn-g2NaYsw.png" /><figcaption>Voila! Our happier emoji!</figcaption></figure><h4>5 Colours</h4><p>So, hopefully you’ve tried to write some different colours than red and yellow. We’re all a bit more stylish than the default colours! Let’s look at how we use more precise colours. Typically, computers will use hex colours to represent colour — these look like a hash and 6 (or 8) numbers and letters following e.g #ffcc00 (which is my favourite yellow).</p><p>There’s loads of websites that help you find hex colours. Google has a great website to find shades in many colours — <a href="https://material.io/design/color/#tools-for-picking-colors">https://material.io/design/color/#tools-for-picking-colors</a> (you’ll now need to scroll down to the bottom of that page, thanks Google for making that a lot harder!).</p><p>Let’s work on finding some better colours for your face shape, your eyes, and even your mouth!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbYnxLAJ9fBaW5en2x9iVw.png" /><figcaption>Hopefully you’ve got some better colour usage than me!</figcaption></figure><p>So now’s a good point to take a breather.</p><p>Admire all the hard work you’ve put in, and all the things you’ve learned! Also press that save button at least once. You’ve made it this far, we don’t want to lose your work to your computer deciding today is the day it’ll die!</p><p>Next we’re going to look at making our emoji interactive. If you’re not in a rush, you can spend some time looking at some of the other shapes you could add to your emoji.</p><p>Mozilla have a great resource for other shapes you can learn to add: <a href="https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Basic_Shapes">https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Basic_Shapes</a></p><p>So now let’s get cracking on making our emoji do things!</p><h4>6 Interacting</h4><p>So we’re going to start working in the JavaScript box in JSFiddle (bottom left, below HTML). But before we do, the last thing we need to do is give all the shapes we want to make interactive, an id property.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GzhfMEjPVtRwyIHgw3poCg.png" /><figcaption>Up to you what id you give things, just make sure it’s all <strong>one</strong> word (no spaces or special characters allowed).</figcaption></figure><p>We need these id’s to “bridge” the JavaScript box to the HTML box. We can now create a variable for our faceShape:</p><pre>var faceShape = document.getElementById(&quot;faceShape&quot;);</pre><p>So what have we actually written? We’ve created a new variable called faceShape. A variable is a thing with a name, the thing is the yellow circle, and we’ve named it faceShape. We’ve then had to say that this variable is actually in the document, go find it by the id we gave it. You have to make sure the bit in quotes is *exactly* what you called the shape in the HTML box. Computers are stupid and won’t find it otherwise!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycTH-CzxyIIvkImj0TQrVA.png" /><figcaption>We’ve made our first variable!</figcaption></figure><h4>7 Clicking</h4><p>So, we’ve not actually made it interactive yet. Let’s make it do something! Write the following after your variable.</p><pre>faceShape.onclick = function(){<br> alert(&quot;ouch&quot;);<br>};</pre><p>This uses our variable, and says we want to give it a function when we click on that shape. A function is a thing that does something. We only want this code to run <strong>when</strong> we click the faceShape. The curly brackets act like our piece of paper from earlier, we want to make sure we drawing on the paper, not before or after. So we make our alert inside the curly brackets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbYKTs63_CiMqIL_HZGq4Q.png" /><figcaption>Make sure you click the run button before clicking the emoji! Nothing happens if you don’t run your current code!</figcaption></figure><p>If for whatever reason it doesn’t work, make sure you’ve got the id’s the same and no spelling mistakes. Spelling mistakes are *super* easy to make and *super* hard sometimes to debug!</p><h4>8 Changing things</h4><p>So an alert is kinda funny, but pretty disruptive and boring after the first few times. Let’s look at changing the emoji face colour when we click it. Let’s make him look a bit green and sick!</p><p>I’m going to replace the alert with the following code:</p><pre>faceShape.setAttribute(&quot;fill&quot;, &quot;#A0D468&quot;);</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSDR7umColXOdeCL3aYC_g.png" /></figure><p>What happens now? We can make him look sick but can we make him better again too???</p><h3>9 Conditionals</h3><p>This is where we can write some conditions! If our emoji looks sick, let’s make him better. Otherwise, if he’s better, let’s make him sick.</p><p>We’ll need to create a new variable to keep track of the state of our emoji (whether he’s sick, or not). This is a special type of variable called a boolean. It’s either true (he’s sick) or false (he’s not sick). When we create it we need to give it a default state. How does he start out? He’s not sick when we first run the program, so isSick will be false:</p><pre>var isSick = false;</pre><p>Make sure you write this code before the onClick. We can then update it every time we click the faceShape. We can also write our if statement and update the background colours:</p><pre>if (isSick === true){<br>  faceShape.setAttribute(&quot;fill&quot;, &quot;#FFCE54&quot;);<br>  isSick = false;<br>} else {<br>  faceShape.setAttribute(&quot;fill&quot;, &quot;#A0D468&quot;);<br>  isSick = true;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPUcPHFfWga_5Nx5pxAjCA.png" /><figcaption>If you get confused at all, you can tap on the image to make it make sure your code matches mine!</figcaption></figure><p>Take some time after you’ve proved it work to look at why that happens. What happens if you change the colours? Are the colours where you expect them for the if statement?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*MDFkHwFczb-VHdcLCKzQEQ.gif" /><figcaption>Look at him gooooo!</figcaption></figure><p>So an interesting side note about the setAttribute : we’re currently changing the background colour which was the fill property. However you could change any attribute such as size, or location programmatically! For example, you could make his eye go smaller when you click on it (poor dude).</p><h3>Finishing</h3><p>So we made it to the end! Congratulations 🏅🏆🌟</p><p>Make sure you’ve clicked the save button again — and sent a picture of it to someone you know (or maybe just your mum). Comment below too what you’ve made, what you found difficult, and something you’ve added that I didn’t write about in this article!</p><p>If you’re still looking for things to spend time and add why not look into the following:</p><ol><li>Add more complicated shapes — <a href="https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Basic_Shapes">https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Basic_Shapes</a> — specifically look into adding some polygons — does your emoji need a hat? Trick question, all emojis need some kind of hat!</li><li>Gradients — <a href="https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Gradients">https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Gradients</a> — there’s two types of gradients; linear and radial — can you use both of them (in different places silly)?</li><li>Make more shapes interactive — try doing something with the eyes or the mouth!</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8da03e87a27f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A rising tide lifts all boats]]></title>
            <link>https://medium.com/@daniellevass/a-rising-tide-lifts-all-boats-79fd4e20e73?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/79fd4e20e73</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Fri, 23 Mar 2018 22:09:20 GMT</pubDate>
            <atom:updated>2018-03-23T23:25:19.261Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ClTwlU3Ng45Wnh2JqPqSmw.png" /></figure><p>Last week I was lucky to attend International Womens Day through Women Techmakers hosted at Google UK. I also finished reading the book “To sell is human” by Daniel Pink. These two things shared surprisingly similar themes and learnings around leadership that I thought were important to share!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qL4AoQOwbsmbKTmh." /><figcaption>“Several people fist bumping over a busy workspace” by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Making your partner look good</h3><p>No, I don’t just mean a relationship partner, but anyone you interact with.</p><p>The premise of this is found in improv too. The worst thing you can do in improv when working with someone is to reject their previous statement. Your job as their partner is to build on their ideas and in turn you both look good!</p><p>There are several different facets of this that I think are easy to take and use for your own purposes which I’ll explain in more detail below. How to make more meaningful introductions. Saying “Yes and” to create possibilities. Creating your own press conference to squash the fears of Q&amp;A and ask sincere questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RUpgetQVYT-F3hmF." /><figcaption>Photo by <a href="https://unsplash.com/@simonmigaj?utm_source=medium&amp;utm_medium=referral">Simon Migaj</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Where are you from?</h3><p>When you meet a new person, what do you usually ask? What do you do? Who are they? What can they do for you perhaps?</p><p>These style questions are limiting, they don’t necessarily allow open answers. Perhaps a better question is out there?</p><p>Daniel Pink suggests asking “where are you from?” which can allow the other person to answer in a way that works for them.</p><p>For instance you can answer in the past tense; <em>I grew up in Swindon, went to University in Plymouth, and moved to London two and a half years ago.</em></p><p>You can answer in the present tense; <em>I currently work at Facebook as a Partner Engineer, which is this interesting hybrid role right in the middle of engineering and talking to people.</em></p><p>It even opens the opportunity for talking in other angles such as a potential future; maybe we’re hoping to move to live somewhere new? Perhaps we’re thinking about a career move?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s3MaEXdubfxnqouN." /><figcaption>Photo by <a href="https://unsplash.com/@jtylernix?utm_source=medium&amp;utm_medium=referral">Tyler Nix</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Yes, and?</h3><p>We’ve all been there when you’re super excited about an idea and then someone goes “yes, but” and explains several reasons why your idea won’t work. This sucks for everyone. You lose motivation in your idea. And the potential for your idea is lost!</p><p>Instead of saying “but”, consider its more inclusive friend “and”.</p><p>For example: if I wanted to host a BBQ, my close friends might be like “but what about the vegetarians?!!”. How about we change that to “yes, and let’s also make sure there’s some vegetarian options”. How does that feel now?</p><p>The idea has been listened to (you’ve been heard!) and then worked on and improved. Any problems you might’ve have had has been addressed with solutions.</p><p>You now have more possibilities than problems!</p><p>We’re getting into a space where problems are addressed with solutions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tyO8t4seqeILnoqq." /><figcaption>Photo by <a href="https://unsplash.com/@theunsteady5?utm_source=medium&amp;utm_medium=referral">Edwin Andrade</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Press Conference</h3><p>This activity requires a friend or two to join you. Hopefully you’ve now made some using the <em>where are you</em> from section earlier!</p><p>The scariest part of giving a talk for many of us, is the whole Q&amp;A aspect at the end. What if we get a question we can’t answer? So let’s practice that part in a safe space.</p><p>You pick a theme, perhaps something you’re speaking about soon. Your friends’ job is now to ask you questions. Exactly like you’ve seen at press conferences or on tv. You can take turns in the different roles to experience both sides of being a press reporter and conference talker.</p><p>For example, I might be giving a talk on how to crochet. My friends can then ask me thoughtful questions like; <em>why did you learn to crochet, what have you made, how would you recommend learning</em>. Spend at least 5 minutes on each persons topics, ensuring that you come up with lots of different questions.</p><p>Being the press reporter, you get to deliberate practice listening with the intent to ask questions. You get better at asking more meaningful questions!</p><p>As the conference talker, you get to practice answering questions! The more you experience this the more comfortable you’ll be next time Q&amp;A time happens!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*20GWB95aKIETmE-V." /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Servant leadership</h3><p>The ideas above are just a few examples you can use which form a wider area called <a href="https://en.wikipedia.org/wiki/Servant_leadership">servant leadership</a>. As a leader your job is to serve those around you. Which is typically the reverse from how most people consider leadership.</p><p>If you can help those around you grow, they’ll do better, and go on to help other people grow too!</p><blockquote>“The servant-leader is servant first… It begins with the natural feeling that one wants to serve, to serve first. Then conscious choice brings one to aspire to lead. That person is sharply different from one who is leader first, perhaps because of the need to assuage an unusual power drive or to acquire material possessions…The leader-first and the servant-first are two extreme types. Between them there are shadings and blends that are part of the infinite variety of human nature.”</blockquote><blockquote>“The difference manifests itself in the care taken by the servant-first to make sure that other people’s highest priority needs are being served. The best test, and difficult to administer, is: Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, more likely themselves to become servants? And, what is the effect on the least privileged in society? Will they benefit or at least not be further deprived?”</blockquote><p>All of this has resonated pretty strongly with me. Enough so that I wrote this blog post!</p><p>I love the idea of making your partner look good. I think it’s something I’ve been doing inherently for a while. Giving back is a massive part of my identity from running code clubs for kids and adults, to making sure the new person at work is helped to feel included into the team from day one.</p><p>The surprising learning for me came with the concept of improv. I’ve never considered myself into theatre much or acting, but I now have a real drive to push myself more in this area. I’m scarily (to me) considering joining an improv class in London.</p><p>So with that, my final question to you should be obvious: What are you going to do to help make those around you look good?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79fd4e20e73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2017 — why I learned to crochet]]></title>
            <link>https://medium.com/@daniellevass/2017-why-i-learned-to-crochet-66acb144f93?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/66acb144f93</guid>
            <category><![CDATA[crochet]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Mon, 01 Jan 2018 19:11:46 GMT</pubDate>
            <atom:updated>2018-01-01T19:34:12.140Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NkC1jM5oSkFeVKQ_iVnOMQ.png" /></figure><p>Last year I started a new tradition; I’d learn one new thing a year.</p><p>Many people pick up hobbies and skills and quit as soon as it gets difficult. With the “one new thing a year” theory, it forces me to push through the hard starting bit, and spend real effort getting better.</p><p>This year, I attempted to learn to crochet! I saw an image for a beautiful crochet blanket online and figured I could make that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrjOW4ChK2hiKdA-JvGw4w.jpeg" /><figcaption>Some practice hexagons I made.</figcaption></figure><p>Learning something new each year teaches me it’s okay to suck at something. With deliberate practice and actual effort I can learn to become good. At the beginning my crochet was quite literally just a tangle of wool!</p><p>This is an important aspect that people often forget after they’ve mastered something, what it feels like to be a beginner. As someone who often teaches, this affords me the ability to empathize with students over their struggles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBbkUqwy2TQk-zvodaOwtA.jpeg" /><figcaption>Quite literally a tangle of wool!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ignHRQIqjdd5B-kRACv_Kw.jpeg" /><figcaption>Looks like I might be getting there, if you excuse the tangle in the bottom right!</figcaption></figure><p>One of the nice things about crochet is there are so many different stitches and pieces to learn. It’s feels like I can forever just be a beginner with this. Like below I tried to learn how to make a wavy pattern but I got the maths wrong and ended up with a bunch of extra stitches at the end!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QawlnMDTSz3oCrvDoN5Ppg.jpeg" /><figcaption>Calculating how many stitches you need is hard!</figcaption></figure><p>This experience has served me well in other aspects of my life such as when I moved jobs. Where I’ve felt like I’m sucking and really not good enough to be there. I can reassure myself, that if I just keep working hard, I can make it through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xjMasKOMRvMfAKqaQ8hbRw.jpeg" /><figcaption>My finished blanket! This took over 9 months to make from start and contains 144 hexagons!</figcaption></figure><p>I also got to connect crochet back to one of my other hobbies, programming. Where I built myself two algorithm websites to aid my crochet.</p><p>The first of which was a <a href="https://daniellevass.github.io/blanket-pattern-generator/">blanket pattern generator</a>. I suck at patterns and colours. I can give it a bunch of hex colours (more than 4 or there’s a bug and it’ll crash chrome, oops).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EZ5GQ2hRfTi81mKUTEHbQ.png" /><figcaption><a href="https://daniellevass.github.io/blanket-pattern-generator/">https://daniellevass.github.io/blanket-pattern-generator/</a></figcaption></figure><p>The second was a <a href="https://daniellevass.github.io/scarf-pattern-generator/">scarf pattern generator</a>. You can procedurally add coloured lines which will build up a scarf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_OmxfSncGdh-IJOcM8TAbQ.png" /><figcaption><a href="https://daniellevass.github.io/scarf-pattern-generator/">https://daniellevass.github.io/scarf-pattern-generator/</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8Rp-UEgx5-NUiZmDmFRjA.jpeg" /><figcaption>A close up of a scarf I made using the wavy pattern (I got there eventually!)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_yCLPzvN_8WS8Rzv0SeFQ.png" /><figcaption>A rainbow scarf.</figcaption></figure><p>I’ve really enjoyed learning to crochet this year. Hexagons have definitely been my favourite. They’re convenient to make almost anywhere, even whilst traveling! This is a hobby I’ll take forward, and I hope to always have a work in progress project (yes, I’m building another hexagon blanket).</p><p>This leads me to conclude with what I want to learn in 2018. With the feeling that crochet has become a life addition for me. I’d like to learn how to exercise better. I don’t have a specific end goal yet, like running a marathon. But I want to spend deliberate time and effort this year learning how to exercise and hopefully improving my life in that way for 2018.</p><p>Let me know what thing you’re going to learn for 2018. We can learn together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66acb144f93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using APIs part 2 — JavaScript & Giphy]]></title>
            <link>https://medium.com/@daniellevass/using-apis-part-2-javascript-giphy-73a8bba34bc3?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/73a8bba34bc3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 20:05:51 GMT</pubDate>
            <atom:updated>2017-11-16T20:05:51.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1tvWmJBjf08kueuIfaXHnQ.jpeg" /></figure><p>A long time ago, <a href="https://medium.com/the-codelog/using-apis-part-1-f0d78ee1c9b8">I wrote a blog post introducing the concept of an API</a>; what it is, some examples, and how you might use one. However, I didn’t show you how to actually use one in code! This blog post will help you get started using JavaScript and <a href="https://giphy.com/">Giphy</a> to display cat gifs.</p><h3>Setting up</h3><p>I’m going to be using a website called <a href="https://jsfiddle.net/">JSFiddle</a> to write and test my project. JSFiddle allows me to show the code I’ve written, without any of the boiler plate code of a HTML page, or including the JavaScript file. It also means you won’t need to install anything to get started, you only need a web browser!</p><p>I’m also going to use a library called <a href="https://jquery.com/">jQuery</a> to help us do some of the harder things in JavaScript more easily. Many people dislike jQuery, however it makes doing things easier and less verbose. Writing less code hopefully means you’ll understand the concepts without writing more words to get lost in.</p><p>Once you have JSFiddle open, you can tell it to include jQuery. Find the JavaScript square (bottom left), click the tiny cog (top right of the square). Click the frameworks &amp; extensions drop down menu, and scroll to jQuery. Any version number will do everything we need to today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N8N41rJ285kxGtw_0jx1HA.png" /></figure><h3>Using $.get</h3><p>We’re going to begin by using jQuery (which shortens to the $ character) and getting it to use the get method. This will handle the call to the api for us, we can pass it some properties such as the URL to call, what should happen when the call succeeds, and what to do when that call fails.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d639474391880dc361da140b1ce5adc/href">https://medium.com/media/6d639474391880dc361da140b1ce5adc/href</a></iframe><p>Before we test out our code we’re going to open up the developer console. In the browser right click anywhere and click “inspect element”. Here you should get a window appear over your browser, one of the tabs in that new window should say “console”. To find out more about the console, and what it can do for you, check out this article by google — <a href="https://developers.google.com/web/tools/chrome-devtools/console/">https://developers.google.com/web/tools/chrome-devtools/console/</a>.</p><p>Now that we have the console open, click the play button at the top right of JSFiddle. You should see the result of our call! If you have any mistakes the developer tools will hopefully let you know where the mistake was for you to fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crZ3VbGYduitaz1FdnvfUw.png" /></figure><p>You’ll see we got back 25 items, which is the default number of gifs Giphy will return. Click into one of the objects and try to find which property has a link to the gifs. (hint: it’s inside images / original)</p><h3>Iterating</h3><p>Next, let’s look at how we navigate through that returned data through code. Let’s start by logging to the console the url of each gif we have. Think before you start writing any code; what kind of loops you know and whether they might work for us here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*udWXIKRaxDEYjCnKQQCGhw.png" /></figure><p>I’m not going to link you to the code here, it’s good practice to write it yourself and not copy/paste. I picked a “for each” loop in the above example. So long as you have a bunch of links in the console to gifs any answer is totally acceptable. At this point you can reward yourself with by clicking any of the links to see a cat gif. Gifs are pretty great, right?</p><h3>Rendering</h3><p>Now we have all the links to the gifs, let’s go about displaying them! This might sound difficult to start, but thinking back to our HTML experience, we already know how to render an image. Gifs are only fancy images.</p><p>All I did was make a super long string with the html I’d use if I was to write this code by hand e.g. “&lt;img src=’cat_gif_here’ /&gt;”, and then putting that into a container.</p><p>I had to specify a width for the images, otherwise they took up too much space. There are better ways in future to render images like this, taking a look into templating libraries, something like <a href="https://github.com/janl/mustache.js/">mustache.js</a> would help us write much cleaner code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fOo_qurs2zMrYyXns--VVw.png" /></figure><p>My JSFiddle is located here — <a href="https://jsfiddle.net/daniellevass/yocuzLet/">https://jsfiddle.net/daniellevass/yocuzLet/</a> . Feel free to fork it, break it, and look at how the different parts work!</p><h3>Extension Tasks</h3><p>Not everyone likes lolcats, some people like lolpuppies. How would you go about adding in a text field to allow people to type what they want?</p><p>Maybe you want to allow people to use these gifs in a conversation, and instead of showing many, we’d only really want one gif. How would you go about selecting one, maybe at random?</p><h3>Conclusion</h3><p>Now that you are a pro at consuming the Giphy API you will also be able to consume any API! <a href="https://apigee.com/providers">Go forth and explore public APIs</a> and find your favourite!</p><p>My favourite API is the <a href="https://earthquake.usgs.gov/earthquakes/feed/v1.0/geojson.php">USGS earthquake API</a> which displays earthquakes that have occurred. I like it because it’s a very well formatted API (the documentation just makes sense!). I can also do a lot with the data such as displaying on maps or lists, playing with the data and working out how far away my nearest significant earthquake was (quite far considering I live in England!). The API is refreshed with earthquakes every 5 minutes, which means often when I check if my new bit of code does something a new earthquake has appeared!</p><p>In the next part in this series we’ll look at using an API to talk to things in the real world, which will become our own Internet of Things!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*zIVjvtrVJgl2Q0P1R5rkSw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73a8bba34bc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[introducing codebar android]]></title>
            <link>https://medium.com/the-codelog/introducing-codebar-android-d6c79b9bd98c?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6c79b9bd98c</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Mon, 27 Mar 2017 11:46:24 GMT</pubDate>
            <atom:updated>2017-03-27T11:46:24.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3NjMz_s3SGT7l1-mwaOpg.png" /></figure><p>A couple of months ago we ran our first codebar android dev workshop. Not only did we have the demand from students (we had a waitlist of students who wanted to come). We also had a bunch of <strong>*really*</strong> capable coaches. We even had some super nice people who offered to host us. All thanks to the awesome community in London!</p><h3>codebar on Twitter</h3><p>Serious android-ing happening at our Intro to Android workshop at @ustwo tonight. Phones, laptops, cables, check ✅</p><p>Our first workshop went so successfully students and coaches asked for us to run another. So that we did in February.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-4FHfizA9odkNiKA4jVyg.jpeg" /><figcaption>Our second workshop at 8th Light</figcaption></figure><p>We built a tutorial based off of the historically popular Cookie Clicker game; the premise of which is pretty simple, you tap a cookie picture to increase a counter.</p><p>We start by gently introducing students to <a href="https://developer.android.com/studio/index.html">Android Studio</a>, and it’s multitude of scary looking buttons. Then we move on to designing our user interface. Not everyone likes cookies, students could make a cake clicker game instead. We then finally help by making the user interface actually <strong>do</strong> something! Students can then run their app on their own android device if they have them. If not we’ve got a couple of spare devices, so everyone can play!</p><p>One of the benefits of the way codebar operates is the high number of coaches to small numbers of students, and the discussions that can happen because of this. The tutorial was built with specific break points to encourage those discussions between students and coaches in different areas, such as which version of Android should our cookie clicker app support.</p><p>As an added bonus the tutorial currently appears to be the <strong>*perfect*</strong> length for a workshop. Everyone gets to see what they made work by the end!</p><h3>codebar on Twitter</h3><p>And what we are building tonight - a 🍪 counter! #android #dev #cookie https://t.co/E7cpTnkEil</p><p>Last workshop we ran a mini retrospective at the end. Asking what people liked, and taking on board which things we can do better next time.</p><p>Something we definitely need to get better at is the communication around how students should prepare for the event. Downloading Android Studio sadly isn’t enough. When you open Android Studio for the first time, it will also need to download a bunch of things (like an Android SDK).</p><p>However we also do a lot of things right. Which you don’t need to take from us, these are some of our previous coaches and students voices :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ErRfqXLzfOzTVL7ctm1Pig.jpeg" /></figure><p>We’re making it so both students who have never tried Android dev, and those who have visited us before can benefit. We’re working on more tutorials for the next workshop! Firstly we’re extending the cookie clicker app to persist state and save your scores. And also making new tutorials to explore other interesting concepts such as utilising maps, Bluetooth LE, or connecting to APIs. If you’d like to attend and learn a specific concept feel free to reach out below or privately, we’d be happy to help make sure you get the most out of a workshop with us.</p><p>We’re hoping to run every other month over 2017. The next workshop will be happening on April 20th at Novoda - <a href="http://codebar.io/events/android-workshop-3">click here to register to attend</a>. We hope to see you there :-)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/1*RM1ZbciVNy0-XQdQth2KsA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6c79b9bd98c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/introducing-codebar-android-d6c79b9bd98c">introducing codebar android</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Tigr in 2017]]></title>
            <link>https://medium.com/project-tigr/project-tigr-in-2017-c7c2ff72cbab?source=rss-3bd31acc4659------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7c2ff72cbab</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[teaching-computer-science]]></category>
            <category><![CDATA[parse-shut-down]]></category>
            <dc:creator><![CDATA[Danielle Emma Vass]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 20:46:39 GMT</pubDate>
            <atom:updated>2017-02-27T20:46:39.572Z</atom:updated>
            <content:encoded><![CDATA[<p>3 years ago I built a website called Project Tigr as an aid for me to teach students to code more efficiently. Over the years it has evolved into a system of projects and worksheets which were simple connected markdown files.</p><p>For example, there is an interactive emoji project, which contains a couple of worksheets. One worksheet will contain many much smaller markdown files, which students can work through at their own pace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3x6rwPcNPyR_G4lufI_x6A.png" /><figcaption>How an emoji worksheet currently looks in Project Tigr</figcaption></figure><h4><strong>Why I had to re-write:</strong></h4><p>I had to essentially start completely fresh in December 2016. The backend I used to connect all the information together was hosted on <a href="http://parse.com/">parse.com</a> which Facebook shut down in January 2017. I knew this in January 2016, but like every person with a good intention I procrastinated!</p><p>I spent a long time attempting to learn nodejs, expressjs, and MongoDB to write my own API and backend. In the end I decided I didn’t know enough to make it really happen, and I really didn’t feel confident in maintaining something like that, especially from a security stand point of looking after children’s data!</p><p>So with that decision I looked at moving to the next best thing, which is Google’s Firebase. However, Firebase isn’t the same as Parse at all. Objects are stored and interacted with completely differently. Not to worry though! It would give me a good opportunity to fix the things I hadn’t thought about when I built Project Tigr the first time around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mt_-fxl_iko5l098Y_l2Vw.png" /></figure><p>Another thing I could look at doing was hosting my own markdown files. Historically, I had used GitHub’s Gist and a JavaScript library to display markdown files. This was great because it meant I could edit the files if they were inaccurate on the fly, without having to re-upload. It also acted as kind of a VPN in the schools for displaying the content. I could host all my images on imgur, which for sensible reasons is blocked on most school networks, and it would still work for them!</p><p>Unfortunately, if you have a full classroom of 30 kids all trying to access the same markdown files GitHub think your attempting to DDoS them and start denying rate limiting. Maybe now would be a good make those markdown files local?</p><h4><strong>What currently works</strong></h4><p>I knew I didn’t have a lot of time, I have a “real” job and a bunch of other commitments to keep up with. So I had to think super MVP when working out what to put into the new Project Tigr!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7dvmFvj-GjklWd3FeAmT3w.png" /><figcaption>MVP means some things look a bit broken!</figcaption></figure><p>Currently there are only two projects, with only a couple of worksheets, with worksheet items hosted in Firebase. Many of the demo screenshots use JSFiddle, which has changed significantly over the years. So I’m trying to update all the worksheets before they show up on the new Project Tigr.</p><p>Each worksheet has a markdown element with pre-defined seperators, so I can chunk a worksheet into smaller items using JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UYDp89OVvGNXXLbaVFOK5Q.png" /></figure><p>Firebase doesn’t really have a nice way to add totally new objects, so I wrote my own hack way of doing it! Currently I can create and edit projects, worksheets, and upload blocks of markdown. This also means I’ve had to create a folder for all my hacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*kRTiJ46EPkEqPKtPCe3JjQ.png" /></figure><p>Although I was working on MVP, I wanted to set myself up with better foundation to add to in the future. I decided I needed to be a better web developer; something to do with using gulp, grunt, or web pack maybe? At the start I didn’t really know what I wanted to do with any of these things, or why I’d need them.</p><p>I went to a couple of meetups and asked a bunch of different people what I should do. I decided on using grunt. This meant I could also use the bootstrap SASS project, and convert it into the css files I’d need. This gave me the flexibility to edit CSS in a lot more friendlier manner.</p><p>Using gulp will also let me write some tests! But we’re still thinking super MVP, tests will come later!</p><p>In the last version of Project Tigr I’d used a neat template library called MustacheJs. Templating saved me a tonne of time building things last time, so why change something that works? Somehow I’m now using a different templating called HandlebarsJS. I’m not really sure how that happened to be honest.</p><p>I’d never been able to host the templates outside of the file I needed. I still had to copy paste or only use the templates in specific places. I’ve learned to put each template into it’s own file, and call it on demand. This is pretty good because it means I can kinda cheat and make elements I’ll need more than once into a template. So, now my nav bar is a template, and I can add nav items to it programmatically!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*xP1RAsnJ0WppyEBs4rivMA.png" /></figure><p>Finally, the last piece of the puzzle I needed to accomplish was allowing students to feedback. We’ve spoken to the lovely people at Bath Spa University who have advised us on ways to get quantative data from children. We’re going with a thing called the affective learning scale. It looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*f_lvvmR_y3VIlFIQWsiH1g.png" /></figure><p>The benefit of this is the questions have already been peer reviewed so maybe we could use the answers for proper data? The only thing we’ve changed is emojifying the answers! I’m just really not sure I’m so comfortable asking children this super long list of questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*6h0N7ugcMQrlEpsVv7E2Ag.png" /></figure><h4><strong>Next pieces</strong></h4><p>We’re not at the end yet! There’s definitely a lot of things that I’m still working on with Project Tigr. Firstly, I need to start tracking analytics to see if anyone is actually using this thing!</p><p>After that, I want to be able to create accounts so students can keep a track of their own progress and maybe even earn achievements. I also like the idea of enabling messaging, which means I need to also be able to create teacher profiles too.</p><p>So definitely a lot hopefully to check back on!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7c2ff72cbab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/project-tigr/project-tigr-in-2017-c7c2ff72cbab">Project Tigr in 2017</a> was originally published in <a href="https://medium.com/project-tigr">project-tigr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>