<?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 Ally Eastman on Medium]]></title>
        <description><![CDATA[Stories by Ally Eastman on Medium]]></description>
        <link>https://medium.com/@allyeastman?source=rss-af76825e9f65------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3VhW1gqKHGk3DHFNrH-3iQ.jpeg</url>
            <title>Stories by Ally Eastman on Medium</title>
            <link>https://medium.com/@allyeastman?source=rss-af76825e9f65------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:40:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@allyeastman/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[Top 6 tips for working in Tech]]></title>
            <link>https://medium.com/@allyeastman/top-6-tips-for-working-in-tech-4bc06cead935?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bc06cead935</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Mon, 21 Feb 2022 07:01:21 GMT</pubDate>
            <atom:updated>2022-02-21T07:01:21.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ABz86LYwIbRQRImADoNI6g.png" /></figure><p>I’m celebrating 6 years of working in the tech industry 👩🏼‍💻</p><p>Those 6 years have been an absolute rollercoaster 🎢 of highs and lows — a combination of exciting, scary and scream-worthy times.</p><p>Across these 6 years I’ve evolved across multiple roles — from being a developer, to a designer, to professional services and a few things in between.</p><p>I wanted to share my top 6 tips to coincide with celebrating 6 years 🎉</p><p>These tips are agnostic across any type of role within tech:</p><h3>Remain consistent ⚓</h3><p>The tech industry has more politics than the Australian Government at times (I’m Australian so I can say that). <br>Often, your peers may have strong opinions about topics and their opinions will be favoured if they are consistent in these opinions.</p><p>To best approach any political situations, be resolute and confident in what you share.</p><p>Be ready to sell your ideas and have consistent reasoning as to why your idea should be heard.</p><p>“If you don’t stand for something, you’ll fall for anything”</p><h3>Problem Solving — Time box it ⏱️📦</h3><p>Going down a rabbit hole is common terminology in the tech neck of the woods. Whilst this can sometimes lead to new discovery, it can also demotivate or deter you from your original purpose.</p><p>Try to time box your problem solving to approximately 15 minutes. This allows for a generous window of time without becoming The White Rabbit from Alice in Wonderland.</p><p>Why should you do so? You need to value your time as much as you value anyone else’s.</p><p>Outside of the 15 minute time box, lean on your peers for support.</p><h3>Keep a diary 📖</h3><p>Look, I’m not suggesting you need to keep a diary in which you address each entry with ‘Dear Diary’ *cough* 14 year old me *cough* but have a dedicated space where you keep notes.</p><p>It’s best to take the notes often and write in a succinct way that still allows future you to decode it.</p><p>There are many ways you could achieve this — via a blog, a note taking app (all operating systems have a built in option) or with classic pen and paper.</p><p>I’m a huge fan of <a href="https://www.notion.so/">notion</a> and have most of my life planned out there.</p><h3>Ask questions, often 🕵🏼‍♀️</h3><p>I say ‘there’s no such thing as a stupid question’ often and people laugh in response, but I’m serious.<br>I’d rather people ask me questions sooner rather than later, otherwise I’ll assume they understand — which can later become awkward for everyone.</p><p>The process of learning is one step at a time. It’s an evolutionary process that requires questioning and in turn, constant growth.</p><p>Be comfortable with failure and don’t focus on ‘I need to know everything ASAP’, but more so ‘how can I learn the most at present’.</p><h3>Be an ally for minorities 🤗</h3><p>This tip deserves it’s own, dedicated blog, but I wanted to mention this at a high level.</p><p>To approach the topic of being an ally to minorities — you need to first be aware of your privilege. Consider some of the daily tasks that you follow that others may not be able to with such ease.</p><p>There are many organisations and events that focus on supporting minorities. They typically have done most of the leg work that will simply enable you to support their initiatives.<br>Examples of such organisations or events are some of my personal favourites — such as Django Girls, Muses Code JS, Women Who Code, Ethni.</p><p>These organisations enable your support by accepting sponsorships or general assistance, that will in turn advertise your company as a key supporter.</p><p>If it’s not within your budget to sponsor these organisations, the two best things you can do are to simply <em>talk</em> and <em>listen</em>. <em>Talk</em> and be the voice for those that have trouble speaking up. <em>Listen</em> and empathise with those that lack privilege.</p><h3>Lean on your community 👨‍👩‍👧‍👧</h3><p>Ironically, not everyone in the tech community are basement dwellers with a lack of social skills. In fact, the community is so diverse that it’s quite often the opposite of the (unfortunate) stereotype.</p><p>There are many avenues in which you can lean on your community, but the most reliable way is by first <em>giving</em> to your community — in turn you’ll <em>receive</em> from it. <br>This could be through mentorship programs, volunteering, presenting at a conference or a local meetup etc.</p><p>Investing time, sharing stories or giving guidance to your community will see you reap the benefits of a tech family.</p><p>Finally, I cannot take credit for these tips — most of these have come from mentors I have had the pleasure of working with. <br>I hope someday to be as much of a positive influence as they have been, not just for myself, but for many people.</p><p>It wasn’t easy cutting down the list to 6, but I plan to share more in the coming years :)</p><p>Tune in again soon 💖</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bc06cead935" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a user friendly login]]></title>
            <link>https://uxdesign.cc/designing-a-user-friendly-login-25855ae0cc88?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/25855ae0cc88</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 22:43:05 GMT</pubDate>
            <atom:updated>2018-10-03T01:53:57.494Z</atom:updated>
            <content:encoded><![CDATA[<p>To ensure your users experience is seamless from the beginning, you should design your login and register screens to be as intuitive as possible. These screens are <strong>generally the first step for a user when experiencing your product</strong>.</p><p>I’ve dug around the web — specifically looking at some of my favourite products and have analysed the UX choices to show the <em>good, the bad and the ugly</em>.</p><h3>Separate login from registration</h3><p>It’s easy to mix up ‘<strong>sign in</strong>’ and ‘<strong>sign up</strong>’ considering how similar both phrases are.</p><p>From a user’s perspective, it could be easy to select the <strong>wrong option</strong> and potentially start signing up, when instead they intended to sign in. <br>I’d suggest using ‘<strong>login</strong>’ with ‘<strong>sign up</strong>’. This slight variation will provide more immediate clarity for your users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*etYZJpE0BCH2j9KsSaWGJw.png" /><figcaption>Source: Dropbox. Their terminology uses ‘sign in’ and ‘sign up’ which is too similar.</figcaption></figure><h3>Allow social media logins</h3><p>Let’s face it — <strong>users can be lazy</strong>, I can vouch for this 😉</p><p>Sometimes you see a long sign up form and you’d rather use your Facebook or Google to sign up instead.</p><p>With recent controversy around data sharing on social media sites, you should decide how you want to align your product ethically. However, providing your users with these options will <strong>simplify</strong> their lives, which will make them much more willing to use your product. Win — win!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pNRvnkg9j1WkGnzl4ue-KQ.png" /><figcaption>Source: Airbnb. They allow users to continue with Facebook &amp; Google.</figcaption></figure><h3>Allow contextual details for login</h3><p>When logging in, providing your users with <strong>more than an email address</strong> can make more contextual sense. As an example mobile numbers are heavily associated with your Uber account, as it is <strong>primarily a smartphone app</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4IVeWIYxKtlnnsVMbjG6A.png" /><figcaption>Source: Uber</figcaption></figure><p>On the flip side, consider allowing more than a ‘<strong>username</strong>’ or ‘<strong>customer #</strong>’. If the user doesn’t have auto-fill or a password manager it could be difficult to recall this info.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hS7MZw-NQVUpczotmwQqYw.png" /><figcaption>Source: Godaddy. I’ve struggled with remembering my username and customer # before.</figcaption></figure><h3>Allow users to show password when logging in</h3><p>Nothing is more frustrating than spending time filling out a form and getting validation that your password is invalid — attempting to enter it multiple times but still getting the same error message. 🤦‍</p><p>It’s ideal if users can <strong>toggle showing their password</strong>, so that you can pinpoint where exactly their password is error-ing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqDQL8mm7jNcnnkR8OxU-g.png" /><figcaption>Source: Airbnb. They have a subtle toggle to show password.</figcaption></figure><h3>Keep users signed in</h3><p>It makes users lives so much more efficient if you can <strong>leave them signed in</strong>. This obviously is a security risk, so there must a token time limit implemented to ensure hackers can’t take advantage of this. Adobe allows users to toggle this option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*Ygp5ZyU6LtFZ74z_2DGspQ.png" /><figcaption>Source: Adobe. By default I am set to stay signed in.</figcaption></figure><h3>Warn that Caps Lock is on</h3><p>Similarly to allowing a toggle to ‘show password’, it saves a user time to present them with immediate validation that they have <strong>caps lock on</strong>. Overall, they won’t be as frustrated as they will be able to pinpoint their mistake more efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*O7mZVnqb1ARXV-H7ivPH5Q.jpeg" /><figcaption>Source: WordPress.</figcaption></figure><h3>Present immediate rules and form validation</h3><p>You might waste some of your users time if you wait until they hit the ‘submit’ button <strong>before</strong> they are presented with errors. It’s more time effective if they are able to acknowledge what mistakes they have made early on in the process. You can implement this by showing validation on input entry or exit. Airbnb handles form validation in this fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Tr0kb5LsgO6SaMh3ycp7A.png" /><figcaption>Source: Airbnb. Can you tell I love their UX?</figcaption></figure><h3>Give security warnings before locking their account</h3><p>Indicate to your users <strong>how many attempts</strong> they have before their account is locked — this is especially crucial for websites such as banks etc. as customers then have to call the bank to validate that they are not hacking into their own account. <br>WordPress doesn’t address this <em>perfectly</em> — they choose to lock the account before giving a warning. However, they do allow for a retry in 20 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*Gg0RIrhMc4CSpjTC-9ROfA.png" /><figcaption>Source: WordPress</figcaption></figure><h3>Remember your users when they log back in</h3><p>It’s a friendly approach to remember your users 🤗 They don’t have to re-enter extra credentials and they might feel more <strong>inclined</strong> to log in again in future. In this example, Google has remembered my account. I have hidden my email address for privacy reasons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*llGZuYVjLuuSFraNjiv0ag.png" /><figcaption>Source: Google</figcaption></figure><h3>Indicate password strength requirements</h3><p>It’s important to encourage your users to have <strong>strong</strong> passwords, as they are less likely to be hacked. I’ve seen a combination of pure text or visual indicators for password length. Personally, I prefer the visual approach as it’s a quick and simple overview. Atlassian utilises this perfectly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*hosc0daguSmuunmMS2phxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*t0knZAFQ-LdPfS3bXrRDKg.png" /><figcaption>Source: Atlassian. Indicates from Weak -&gt; Very Strong password</figcaption></figure><p>Good luck with designing your login screens ✌️</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25855ae0cc88" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-a-user-friendly-login-25855ae0cc88">Designing a user friendly login</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to run a productive UX workshop]]></title>
            <link>https://medium.com/@allyeastman/how-to-run-a-productive-ux-workshop-106be1d41a73?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/106be1d41a73</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Wed, 02 May 2018 01:36:17 GMT</pubDate>
            <atom:updated>2018-05-02T01:36:17.290Z</atom:updated>
            <content:encoded><![CDATA[<p>As a small disclaimer, I am certainly no UX expert. I am a Developer with a Design background that has been UX focused. Parts of this agenda are taken from a UX Consultant that my team worked with for a large project last year.</p><p>Before running a UX workshop, I’d suggest the project has already been ‘business approved’ — a.k.a it’s a viable product that your business has approved and created scope around. Having this prepared means you can get up and running much more efficiently 🏃</p><p>Typically, I’d suggest running the workshop over a few different days and scheduling it for the start of the day, as people tend to focus more easily in morning meetings.</p><p>For the last workshop I ran, I broke the sessions into 3 parts:</p><ol><li>An introduction where we ran through the demographics and personas etc.</li><li>A session to draw up detailed views of our layouts on mobile device sizes</li><li>We reviewed a product that has similar features and workflow</li></ol><p>This process worked well enough that we could get started on mockups for the mobile design. However, I suggest that you could swap parts 2 and 3 around.</p><h3><strong>Part 1: Preparation</strong></h3><p>Before running your workshop/s, have a general layout (such as this article) ready. Decide what the outcomes / achievements from the workshop will be. At the start of the workshop, discuss this with everyone to see if there is anything that could be added.</p><p>Decide on the Four W’s (and one h):</p><ul><li><strong>Who</strong> — You want to ensure you only invite vital members. Try to balance between valued opinions but not taking up too much of everyone’s time.</li><li><strong>What</strong> — When deciding on the content covered — make things easier for yourself by writing up a template (you can use this article 😉)</li><li><strong>Where</strong> — Book a room or place that facilitates the number of people invited. I’d suggest choosing one that allows for plenty of sticky notes or has an existing whiteboard.</li><li><strong>Why </strong>- Don’t start planning this session if there isn’t a clear reason why.</li><li><strong>How</strong> — Will you be typing on a word document on a projector the whole time? (I’d suggest not). Decide on how the process will be documented — will someone be taking notes? Most of the time, facilitators of these workshops use sticky notes and encourage the participants to do the same. This is the easiest way to keep track of all the important information. I’d also suggest have a ‘follow up / actions’ list handy at all times.</li></ul><h3><strong>Part 2: Introduction Workshop</strong></h3><p>Okay you’ve prepared yourself as much as possible, now it’s time to run the workshop.</p><p>Gather up all the materials and prepare to be at the meeting room 5 minutes or so earlier than booked, so to ensure everything is ready.</p><p><strong>Introduction</strong>:</p><p>If the participants aren’t familiar with each other, make sure they do a quick introduction. In my workshop, we didn’t have to do this as we all knew each other really well.</p><p><strong>Review outcomes and achievements</strong>:</p><p>Once everyone is ready and comfortable, start by reviewing what the outcomes and achievements of the workshops will be. This ensures that everyone knows what to expect and what exactly will need to happen post-workshop.</p><p><strong>Demographics and Personas</strong>:</p><p>Now that you’ve covered some vital housekeeping. You should start looking at the demographics in four different contexts. <strong>Ensure you document the answers to all of these as discussed</strong> 📑</p><p><strong>Prior Knowledge</strong></p><ul><li>Who is the product for?</li><li>What do users know about similar products?</li><li>What expectations do they have?</li><li>How technologically inclined are they?</li></ul><p><strong>Context</strong></p><ul><li>Where is the product used?</li><li>What device and platform?</li><li>When?</li><li>What are they doing at the time of use and what is happening their surroundings?</li><li>Are they focusing only on this, or is their attention divided?</li></ul><p><strong>Problems</strong></p><ul><li>What issues are we potentially solving with this product?</li></ul><p><strong>Motivations</strong></p><ul><li>What inner force is driving the user to solve the above problems?</li></ul><p><strong>UX Goals </strong>🥅:</p><p>It’s important to look at the goals from each different perspective, including your businesses. Typically in past workshops we have explored the <em>goals of the end user</em>, <em>the company that is facilitating the users</em> and <em>our own business</em>. It’s best to preface the goals with <strong>“We love *insert product name* because …”</strong>. This is a quick way to summarise why the product is so valuable to all parties involved.</p><p><strong>Usability Goals</strong>:</p><p>Once we’ve concluded the UX goals, we can now explore the usability goals. These are different from the UX goals, as they are a summary of 5 adjectives that best describe the overall experience when using the product.<br>In our workshop, I gave the participants a list of approximately 15 adjectives and some sticky notes. They read through the list and chose <strong>5</strong> that they considered the highest priority. Once everyone was finished, we shared our top 5 with each other and picked the final 5 based off what was most popular.<br>Here’s a sample of some adjectives you could use. I’d recommend having 10+ for the participants to choose from:</p><ul><li>Intuitive / easy to learn</li><li>Detailed</li><li>Efficient</li><li>Accurate</li><li>Sense of control</li></ul><p><strong>Tone of the Product</strong>:</p><p>This next activity is a discussion on the tone of your product — this can range from language to overall design aesthetic.</p><p>In the past I have drawn up a 5 point scale for each tone (<strong>See picture below as an example</strong>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOa3nbnBufxwMUvy2tNtow.png" /><figcaption>Tone Scale</figcaption></figure><p>It’s highly suggested that the final decision isn’t normally a ‘3’, although sometimes you cannot avoid being this neutral. These decisions will help you with layout and terminology ideas in future.</p><h3><strong>Part 3: Features and Layout</strong></h3><p><strong>Features &amp; Page Workflows</strong>:</p><p>Now that we’ve covered a lot of the contextual activities, we can start looking at the features and workflows.</p><p>I suggest breaking these up into three stages — <strong>before</strong>, <strong>during</strong> and <strong>after</strong>.</p><p>Here are some questions you can ask the participants to provoke further thought:</p><ul><li><strong>Before: </strong>What all happened before people started using the product? How did they find it? How do they learn about the topic and choose a solution? How do they access the portal?</li><li><strong>During: </strong>Main phases from sign in -&gt; sign out</li><li><strong>After: </strong>What happens after they are done? Do we need to follow up with anything? Is it likely they will spread the word with their friends, family etc.</li></ul><p>Start drawing up some workflows diagrams based on the participants answers. Once these are completed — it will be easy to summarise what each feature is. You should also consider really simple actions that might be outside the main workflow (such as users viewing their user profile).</p><p><strong>Rough layouts (Based on Workflows):</strong></p><p>At this point, you might find you’ve covered a large amount of content for just one workshop and might want to break it out into <em>at least</em> two parts.<br> <br>Now that your participants have concluded what the workflows are, start on some rough layouts. I’d suggest keeping this simple and not over-engineering the designs (i.e. use shapes and minimal words). <br>As you start drawing these up, you might realise the workflows don’t make sense or that you’ve missed some vital steps. Make sure this is an activity that everyone is really engaged in and <strong>expect there to be a lot of debates about things like where a button should go. </strong>🗣️</p><p><strong>Digital Designs</strong>:</p><p>Now that you have some rough layouts for each workflow — you can translate these into digital designs. I’d suggest this is done <strong>post-workshop</strong> with the design team — whether that’s an individual or a group. These should then be presented to the group of workshop participants to get feedback and generate further discussion.</p><p><strong>Polish Designs / Prototypes</strong>:</p><p>Once these digital designs have been reviewed and approved feedback has been applied, the next step is formalising these designs or potentially turning them into prototypes.</p><p>These should then be presented to the target audience / relevant users for A/B testing.</p><p>Good luck with your UX workshops everyone 🤞</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=106be1d41a73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Lessons learnt from HBO’s Silicon Valley]]></title>
            <link>https://medium.com/@allyeastman/5-lessons-learnt-from-hbos-silicon-valley-7b53af2a0aea?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b53af2a0aea</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 07:04:38 GMT</pubDate>
            <atom:updated>2018-01-14T23:13:26.339Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*RFKM04DyqleR1eJ6Xy_HFA.jpeg" /></figure><p>WARNING: SPOILERS ALERT. I highly advise you to watch the entire series of Silicon Valley before you read below.</p><p>During the Christmas and New Year’s break, I binge watched Silicon Valley with my boyfriend Eugene, as it was highly recommended to us both. For context, I am a Developer (focusing mainly on websites and software) and Eugene is a Game Developer, with a range of web and software development knowledge too.</p><p>At first, I was assumed the TV show would focus on highly technological and code related topics, but rather it was the opposite. Instead, the main character Richard, explores beginning his own start up, with very little business knowledge, whilst also being a very socially awkward person. Throughout the show, you learn from his mistakes as they happen and sort of ‘follow his journey’. There were some highly valuable lessons that I will carry with me in future when I inevitably have my own business.</p><p>I’ve collated a list of 7 lessons I learnt throughout the show — as I recall these mistakes, I honestly cringe.</p><p><strong>1.</strong> <strong>Don’t invest in click farming</strong></p><p>For those that aren’t familiar with click farming, it is essentially an online fraud system. Low paid workers are hired to click on paid links, ‘like’ content or create online accounts. This is an alternative to creating bots, as this activity seems more realistic and human-like. However, some social media sites have created algorithms to detect this type of suspicious activity.</p><p>In Silicon Valley, Pied Piper is struggling to keep a steady number of daily active users. This is putting their business at risk, as potential investors will assess those numbers critically. Jared hires a click farm to fake a spike in active users. At first, the rest of the team believes it is genuine growth but upon realising the clicks are fake, they are disappointed.</p><p>Buying fake ‘likes’ can put your brand at risk. In Silicon Valley, if they had gone to investors and shown them the figures, only for the investors to find these were fake — their company would basically go down the drain. Besides, you want your followers to be genuinely interested in your business — engagement rate is more meaningful than general ‘growth’. It’s important that when paying for advertising that your audience does genuinely care, otherwise you are essentially wasting further money on followers that don’t care or even exist. Apart from being a moral and financial dilemma, hiring click farms is a violation of terms of service on most social media platforms — it’s not worth risking getting banned altogether for some ‘likes’.</p><p><strong>2.</strong> <strong>Sometimes you work on boring projects</strong></p><p>Throughout the TV show, there are times where the characters aren’t particularly passionate about what they are working on. Richard decides to start his ‘new internet’ project based off his lack of enthusiasm towards Piper Chat. After Piper Chat falls over, Dinesh has to moderate content for Periscope. Between epic projects, there can be times where what you work on is a little boring. <br>What I learnt from the show is you can either accept the work (and cross your fingers it’s not forever) or do what Richard decided and pursue a project you are more passionate about. It seems that people often deliver their best results when they are truly dedicated to what they are creating.</p><p><strong>3.</strong> <strong>Consider your audience and any moral dilemmas</strong></p><p>Piper Chat has a large group of active daily users and appears to be a highly-valued chat platform. When considering the terms of agreement for the service, they skipped an important fact — age restrictions. As expected today, young teenagers were a majority of the audience — which made the platform an easy channel for pedophiles to talk to teenagers. Upon realising this moral dilemma, Dinesh feels very guilty and becomes worried about a potential billion-dollar law suit, so instead he hands Piper Chat over to Hooli/Gavin Belson. <br>I’d hate to not consider age restrictions and realise my product was morally unwell. This mistake made me realise you need to ensure you cover all basis for your terms of service, especially if your product is not age targeted.</p><p><strong>4.</strong> <strong>Understand how IP and patents work</strong></p><p>Some of the most cliff hanging storylines in Silicon Valley involve Intellectual Property and Patents. Whilst watching the show, I honestly thought both issues would end up not working in the Richard’s favour — but they somehow managed to. However, in the real world this might always be the case. <br> <br>The first encounter with IP in the show is when Pied Piper surpasses Hooli with their Weismann score. Gavin Belson feels threatened, so he attempts to take Pied Piper down. His lawyers advise him that he could sue for IP if they could find evidence that Richard worked on Pied Piper whilst using Hooli equipment. Unfortunately, Richard’s laptop was being repaired and he happened to make one change to the Pied Piper codebase whilst using Hooli equipment. This is highlighted in the court case, but this is not a valid reason to sue as Richard’s work agreement with Pied Piper was invalid. Richard would certainly have been sued if his work agreement was valid.</p><p>Later in the TV series, a patent troll tries to sue Richard for the algorithm for the ‘new internet’ project. Turns out this retired lawyer is just trying to find easy ways to make money. Richard outsmarts him to avoid any law suit. <br> <br>At points in the TV show things seem as though they are not going to work in Richards favour, but this might not always be the case. I learnt that you must fully comprehend what intellectual property is and what exactly it’s grey areas are.</p><p><strong>5.</strong> <strong>Conduct proper user testing</strong></p><p>During the TV show, they are so wrapped up in releasing the Pied Piper Platform, that they only test with their close friends, who happen to be technical people. This would fine, if they were the products target audience. Instead, the platform is targeted to the general population. Upon releasing the product, they release the group of daily active user’s ratio is much lower than the downloads. This would suggest that those who download don’t understand it’s functionality. The team begins brainstorming how to solve this issue, with ideas such as user forums, helpful tips throughout the application etc.<br> <br>I’ve always strongly believed in understanding user’s needs before, during and after a product is released. The team should have spent more time before the products release conduct user testing with non-technical people. This would highlight the products complexity and prompted the team to re-design the user interface, rather than spending so much time afterwards trying to explain a very complex issue to people who can’t fully comprehend what these mean.</p><p>After the Season 4 finished I felt somewhat bittersweet. I think back to what my assumptions of the story and the characters were at the start and how much evolved during the story. Learning these lessons has been highly valuable, but one of the biggest lessons is that even if you try to remember everything, nothing will be 100% perfect. It’s best if you accept that early on and reach for the stars.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b53af2a0aea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Forms]]></title>
            <link>https://medium.com/@allyeastman/usability-forms-85d6c4ffec3a?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/85d6c4ffec3a</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[forms]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 07:16:56 GMT</pubDate>
            <atom:updated>2017-12-30T07:16:56.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVmthLRajFZsvhmA79EJhw.png" /></figure><p>A major part of a website is the usability. As a designer or developer, you should always be looking at ways to optimize the usability of your creations.</p><p>Weirdly enough, I actually love usability testing. It is something that entertains my curious mind. It answers questions I have had about my websites, as well as raises more.</p><p>Usability testing is a whole other blog in itself, but I thought I would first address the forms/questionnaires that you should create for users testing your website.</p><p>There are many different methods you can use to get users to provide feedback. Personally, I love using Google Forms. On this platform, you can have various question formats (such as a 1–10 scale, multiple choice, short answer etc.) and all of this data is saved in a spreadsheet — organising it all neatly. It also is a quick process because no one is writing done what a user is answering — it is all being saved digitally instead. You can also leave open the website/files/wireframes/prototypes/images that you were getting a user to test, so that they can refer back to these while answering the form.</p><p>The most important part of a usability form is the questions. You need to make sure these are simple and concise and allow users to give direct answers.</p><p>Start a usability form by asking questions directly related to the tasks the users had to perform. These tasks should still be fresh in their mind.</p><p>After these more direct questions, change to more detailed questions such as (Did you notice blank? How easily could you find blank? Etc.). It is important to ask questions about content, navigation, information, readability, purpose, activity, consistency etc. here.</p><p>Finish a usability form with more general questions. Make sure to make these short or long answer question formats so that users have more freedom with what feedback they provide. I usually choose very generic questions such as what do you like/dislike about the website and was there anything broken on the website that you noticed. This allows for more personal answers and usually you get a general consensus.</p><p>Make sure that there is some time of thankful gesture after users finish their usability forms.</p><p>Good luck with your usability forms!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85d6c4ffec3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where to find freelance work online]]></title>
            <link>https://medium.com/@allyeastman/where-to-find-freelance-work-online-6f8b48aeaac5?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f8b48aeaac5</guid>
            <category><![CDATA[upwork]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[online]]></category>
            <category><![CDATA[working-from-home]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 07:15:40 GMT</pubDate>
            <atom:updated>2017-12-30T07:15:40.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H7Ewvgel2IDK5_8wRWaYnQ.png" /></figure><p>Sometimes, when doing freelance work, there can be times where work seems minimal.</p><p>I have only casually been completing freelance work throughout my degree and now that I have finished and will be moving on to a full time job — I will still be looking to do freelance work casually.</p><p>One of the most important reasons why I started to look for freelance work online was to build up my portfolio.</p><p>It was suggested to me by an industry person to look further into a website called Upwork.</p><p>I joined the website and within the first day I got my first job. So far I have completed two different jobs on the website, only because I de-prioritized freelance work during the last few weeks of my degree. However, now I am going to be more active on the website and receive more jobs.</p><p>The website has a pretty diverse range of skills. Jobs available include web developers, mobile developers, designers &amp; creative, writers, virtual assistants, customer service agents, sales &amp; marketing experts and accountants &amp; consultants.</p><p>The whole hirer to freelance payment feels secure. You can set up a PayPal account and the money will be transferred there through the website. The overall contracts feel trustworthy and stable.</p><p>It’s so convenient that such a website exists — it makes sourcing freelance work much easier. I will be posting more about my experience on Upwork as time moves on.</p><p><a href="https://www.upwork.com/freelancers/~0111d1fc82cde1aff1?viewMode=1">A Link to my Upwork profile.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f8b48aeaac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to work for free]]></title>
            <link>https://medium.com/@allyeastman/when-to-work-for-free-a7d7e04adeb9?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7d7e04adeb9</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[free]]></category>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[freelance]]></category>
            <category><![CDATA[freelancing]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 07:14:04 GMT</pubDate>
            <atom:updated>2017-12-30T07:14:40.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6x-6phZ7vsSBWF3dszInA.png" /></figure><p>This has to be one of the most subjective topics in the design world — everyone has different opinions and thoughts towards working for free.</p><p>For me — I have experienced times where I have done work for free or for a price lower than I should have been paid. Yes, I have negotiated prices with clients before but sometimes I accept payment much lower than it should be because the work I am doing is an investment.</p><p>My first experience of doing free work was during my degree where we had an Internship unit. During this Internship, I worked for a local magazine that had a great cause for the state music industry. What I learnt in those 80 Internship hours was highly valuable to the work I do now and I also created a close professional relationship with the manager. I’d consider this to be an investment of my time.</p><p>Doing free work can give you leverage for a paying job. This is not always guaranteed but this is something to consider. For example my Internship did not lead to a paying job, but I have heard of many scenarios where people have obtained a paying job through a successful internship.</p><p>If your portfolio is weak — consider free work. Another thing to consider is working for a not-for-profit organisation that means something to you; this will make your portfolio more personal and show you are willing to complete free work for a good cause.</p><p>There are many other scenarios when doing work for free is a good idea — there are also times where you should not work for free. Of course, as I mentioned in the beginning of this blog, this is completely subjective.</p><p>Feel free to leave your opinions or experiences on free work in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7d7e04adeb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with other designers]]></title>
            <link>https://medium.com/@allyeastman/working-with-other-designers-45297d1dd2a0?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/45297d1dd2a0</guid>
            <category><![CDATA[freelance]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[web-designer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 07:06:56 GMT</pubDate>
            <atom:updated>2017-12-30T07:11:59.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CaO7anE5SsSpEpskIaTZ8w.png" /></figure><p>Working with other designers — Is it a blessing? Is it a curse? Is it kind of both? Personally — I love doing collaborations. It means I can mesh my skills with others. Although, these scenarios are not always easy going — collaborating can really push my patience. Lets explore different things to consider when working with other designers.</p><p><strong>The Purpose</strong> <br>Don’t accept an invitation to collaborate with someone just because they asked you to. There should be more criteria that you consider before you proceed. Is this project going to help you achieve anything specifically? Another thing to compare are your skill sets. You have to make sure that what you bring to the project will compliment others.</p><p><strong>The level of contribution</strong> <br>It’s important to determine the level of contribution with collaborating. It may be a split amount or it could even be small tasks — but it is vital to establish this, so that there are no disagreements in the future.</p><p><strong>Portfolio Asset</strong> <br>Will this collaboration be an asset to your portfolio? This question relates to last weeks blog — <a href="http://allyeastman.com.au/www.allyeastman.com.au/when-to-work-for-free.php">When to work for free.</a> If you are going to collaborate with other designers, this will likely be an investment of your time. Is this investment going to go towards your portfolio?</p><p><strong>The Aftermath</strong> <br>Collaboration has an inevitable end. How will this play out? It is likely that you can get involved in some issues that can make the end quite nasty.</p><p><em>Legal Issues</em> <br> • You could enter some legal issues if collaboration rules were not made explicit. To avoid these legal issues — it is ideal to create a specific contract.</p><p><em>Collaboration Issues</em> <br> • There could be general personality/ creative practice clashes that could create issues. If these issues are not resolved, you could end this collaboration with a bitter taste in your mouth. Along with that, it may not be likely that you will collaborate with that designer again.</p><p><em>Emotional Response</em> <br> • When collaborating — it is possible that one designer may receive more recognition than another. Designers can be competitive and have fragile egos — so it is important to stick to what level of contribution you outlined in the beginning and to be mature and reasonable.</p><p>More often that not, collaboration is a blessing. There can be challenges and issues that arise and if these cannot be resolved, you should make an effort to not collaborate with that designer again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45297d1dd2a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Testing]]></title>
            <link>https://medium.com/@allyeastman/user-testing-5259058f4ef2?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/5259058f4ef2</guid>
            <category><![CDATA[users]]></category>
            <category><![CDATA[internet-users]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 07:02:05 GMT</pubDate>
            <atom:updated>2017-12-30T07:03:53.294Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li0yYSxgxPhzGTNYOCx-Pg.png" /></figure><p>One of the most important parts of understanding a user’s experience — is testing this in real time and recording the user’s path, actions, decisions and feedback. <br>In this blog, I will suggest a process to follow to ensure you optimise user testing. This includes the following points: <br>• Outline user tasks <br>• Create user stories <br>• Collect a variety of users <br>• Be aloof with directions <br>• Document actions and reactions <br>• Be generally open minded</p><p><strong>Outline User Tasks</strong> <br>These can be created from different stories — think of a variety of minor to major processes and request the testers fulfill each of these. These stories could be suggested by the client of the product (who have an idea and purpose for the users). However, as a designer or developer, you should be able to create these tasks with your existing knowledge base.</p><p><strong>Create User Stories </strong><br>These are different scenarios that should be outlined before the website or product is created.</p><p><strong>Collect a Variety of Users</strong> <br>Generally, for a smaller website or interface, you should have approximately 5 users participate in testing. This group should be a variety of age, gender, interests, careers etc. However, you should be testing with the intended target audience, as it is vital you are confident this group will understand the product.</p><p><strong>Be Aloof with Directions </strong><br>When directing a user, do not be incredibly specific with instructions unless it is necessary. If you are less direct, there is more likelihood that they are going to follow a task in a more personally inclined way.</p><p><strong>Document Actions &amp; Reactions</strong> <br>There are many methods with these processes. Generally, you want the most efficient process that is also quite coherent. You will get different feedback from when the post-testing, as the users ideas, thoughts and memories could have changed by then. It is important that you document the actions and reactions as they are happening. When doing user testing there is a scribe who records notes. It is up to the individual to decide what the best way to do this is. Personally, I would document notes on a laptop as I can type at 83 words per minute. As long as you feel as though your note taking is not too distracting or intrusive for the testing users.</p><p><strong>Be generally open minded</strong> <br>When guiding testers don’t be too pushy or bossy. Keep an open mind and be patient — after all your testers are doing you a huge favour, so be respectful and professional.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5259058f4ef2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My experience mentoring at Django Girls 2016]]></title>
            <link>https://medium.com/@allyeastman/my-experience-mentoring-at-django-girls-2016-2fb3fb667c58?source=rss-af76825e9f65------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fb3fb667c58</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[django-girls]]></category>
            <category><![CDATA[women-who-code]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Ally Eastman]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 06:54:29 GMT</pubDate>
            <atom:updated>2017-12-30T06:54:29.561Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>December 2015</strong> <br>I finish studying my Bachelor of Design (Majoring in Web). I am relieved that everything went well — especially my final project. I am optimistic but nervous about finding an industry career.</p><p><strong>2016</strong> <br>I then began working at Mandalay Technologies as a Junior Developer. I love my job and it is the exact environment I was hoping to work in (I start questioning what I was nervous about).</p><p>At Mandalay, we break up our year into quarters, and within these quarters we create goals — including personal ones. One of my goals was to get more involved in the community and more specifically meet like-minded women who would mentor me.</p><p><strong>April</strong> <br>My boss Robbie directed me to a meetup, called ‘Women Who Code’. Long story short — I go to the next meetup with a friend Nina (we studied the same degree together). We meet a small group of ladies, some who work in the digital and tech space with minimal coding knowledge, all the way up to senior developers who have many years behind them. In this workshop we learn about the basics of database normalization and I find it easy to follow, especially the SQL component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*tzESlV26NlUErOd1IPTszQ.png" /><figcaption>A photo of the Women Who Code meetup night</figcaption></figure><p>During the night, a lovely lady named Liz Kennedy pitches the idea of Django Girls to us. I’ve never heard of Django prior to this day — but I had heard of Python (which Django is a framework built on). She mentions that they are looking for sponsors for the event. I keep all this information in the back of my mind.</p><p>The following day at work, I catch my boss up on the night — telling him about what I learnt, the general experience and that I was thinking of attending the Django Girls event. I also explain that they are looking for sponsors and Mandalay could be a perfect candidate. I give him a link to the website and write a short pitch for why Mandalay should sponsor Django Girls to the big boss, Simon.</p><p>A little while later, Robbie and Simon tell me that Mandalay is willing to sponsor the event and I shoot Liz (the event manager) a message asking for more information on the sponsorship packages. She sends me a PDF, outlining each of the packages. Afterwards, Mandalay choose a package from the list. At this point I am over the moon — I feel very lucky to work in a place that sponsors my passions. I am still grateful to this day for their contributions.</p><p><strong>June</strong> <br>Fast forward a few weeks and responses are sent out to the applicants. As part of our applications, we had to mention our level of coding knowledge — in which I answered that I have experience.</p><p>My application was accepted. On the response, it suggested that because of the high volume of applicants — if you have coding experience, you should consider being a mentor. I contemplate this and email Django Girls, explaining that I was thinking of being a mentor, but was not confident with my level of knowledge. Will, the lead mentor of the event, emailed me, convincing me as to why I should become a mentor and that I should embrace the role. He also mentioned that the tutorial for the workshop was online, so if I followed this prior to the event, I would be fine. That was enough for me to be persuaded into joining. I am so glad he pitched the role to me.</p><p>I decided to have a look through the tutorial. I started it — but to be honest, I didn’t finish it before the event. Why? 1. Because I ran out of time. 2. It was pretty easy to follow and I was confident that during the workshop I could figure out the rest if necessary.</p><p><strong>Thursday the 30th</strong> <br>The Thursday night before the workshop, the mentors and organisers agree to meet up at the River City Labs. We congregate, getting to know each other, asking questions about the event, have drinks and pizza and start putting the swag bags together. The swag bags are what were given to the attendees on arrival. This included helpful things for the workshop, as well as marketing collateral from the sponsors. We end the night, not knowing what will happen tomorrow night — but we are hopeful everything will go to plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngs3Y8KN_DLGhg-EwMMtfw.png" /><figcaption>The mentors at Django Girls Brisbane 2016</figcaption></figure><p><strong>Friday the 1st July</strong> <br>Friday barrels around the corner and I finish work that afternoon as per usual. I head off to the River City Labs and find my name tag (eventually). We all meet around the front — listening to an introduction from Liz. We also watch an animation created by the founders of Django Girls. I am the mentor for the group #3. We have cute little balloons with our numbers written on them in our assigned desk areas. I wait around the table, anticipating which girls would be in my group. I see a familiar face — a friend Mary, who I met at the Women Who Code meetup and it turns out she is in my group! I also meet two other ladies in my group — Rosie and Zoe. They are all so lovely and very easy to talk to, so I instantly feel lucky as a mentor.</p><p>We begin the installation — which I know can go very smoothly or rather pear shaped. I try to ease the girls through the process, reminding them to read each line so that they do not miss anything. They all install everything with ease and have a few questions about the different things that they are installing. A list of what they were required to install includes: <br>- Github &amp; Git <br>- PythonAnywhere <br>- Python Application <br>- Django <br>- A code editor (if one is not already installed) I attempt to give detailed answers, but it is hard to explain what some of these installations are for until we use them further on in the tutorial. The girls head home and I stick around talking to some of the other mentors for a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UXKdHVF0IWdAy0N-avuGEQ.png" /><figcaption>Helping Mary on Friday Night. We actually did not laugh to make the photo look cheesy — we did just happen to laugh when this photo was taken haha!</figcaption></figure><p><strong>Saturday the 2nd July</strong> <br>We begin our Saturday bright and early at 9am. We are provided with a small breakfast. I have a croissant and a cup of milk. (I would have had a hot chocolate but the machine conveniently broke not long before my turn haha!).</p><p>Just before 9:30, Liz and Will pull me aside and ask if i’d be interested in giving a quick talk about my experiences before the workshop kicks off. I agree to this wholeheartedly. Generally I don’t get too nervous when it comes to public speaking, but I admit I did a little (at least I was given short notice so I didn’t have to overthink it).</p><p>I started off my talk a little shaky but I warm up. I talk about my current role, what brought me to web design, my degree, my current mentors and women who have inspired me in the past. Although I didn’t consider the talk to be ‘brilliant’ I got some good feedback. We then jumped straight into the tutorial.</p><p>Each of the girls started working on the project and it was great to see their reactions when they ran the project locally in the browser and could see what they had created visually. They all seemed to pick up the understandings of creating blog models and how to work around the admin part of the project.</p><p>The next section of the tutorial was deployment. There are many steps in this part and making connections between each platform can seem a little confusing. One of the girls in my group, Rosie, kept getting blocked in a certain part of the deployment. I tried a few different ideas of how to solve it but nothing was working — so I finally consulted another mentor, who suggested that she should go back to the start of creating the project, as we had deleted a file that was in the wrong structure but Python still had the memory of it. Even though this was inconvenient for Rosie, she kept an optimistic attitude and that was refreshing to see.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*WTUjLMbPSiOKPIUA2wte0Q.png" /><figcaption>An overview of us all working away</figcaption></figure><p>Soon enough, lunch time rolled around and we had a guest speaker, Liz Raad. She is a website investor. She spoke about her experience with everything web related. It was great to see that she could go back to supporting her passion for zoology but in the form of the internet. We then had a healthy and delicious lunch supplied to us by our sponsors.</p><p>At about the point where the girls went on the the HTML section of the tutorial, I had to slip out of the workshop to go and vote (yippee!). This was bad timing as I know HTML and CSS confidently, so I was looking forward to seeing how they went. Each of the girls I was mentoring already had a good understanding of the two languages though — but wanted to learn more.</p><p>Eventually it reached the end of the workshop. I was so surprised by how quick the day went, as well as how much learning everyone could fit into that time. We took a group photo of everyone included in the workshop. My group that I mentored and I took some photos together too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*AMR4LUqEF2pXnl1IhjEJuA.png" /><figcaption>A photo we toke with the event organiser — Liz!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*O_SDhGGnczj3Ce9abZdMrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*wJwdyModrvmENXxf8vs2SQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*3DeEseK9DPa7mj_1XPjUug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*f53mXuhl5dxzZ-G6_-qkcA.png" /></figure><p><strong>Reflection</strong> <br>It was great to see each of the girls in my group were really interested in learning more about Django and even I myself learnt much more about Django. Did everything go smoothly? Not particularly. Is that okay? Of course it was, I was actually kind of glad that each of my girls got stuck on something. It is one of the most frustrating but effective ways to learn how to code. Occasionally, they asked me some questions that I attempted to answer, but I don’t think my answers were particularly helpful, they might have confused them further. But I truly tried my best. Will I mentor again? Of course. Expect to see me at the next Django Girls Brisbane workshop ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fb3fb667c58" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>