<?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 Tara Ojo on Medium]]></title>
        <description><![CDATA[Stories by Tara Ojo on Medium]]></description>
        <link>https://medium.com/@tara-ojo?source=rss-cfb91694fe5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LkhX_1eXHgtEEo4vO-9j7A.png</url>
            <title>Stories by Tara Ojo on Medium</title>
            <link>https://medium.com/@tara-ojo?source=rss-cfb91694fe5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:09:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tara-ojo/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[The vibe coding mental shift]]></title>
            <link>https://tara-ojo.medium.com/the-vibe-coding-mental-shift-36cd5e2422fb?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/36cd5e2422fb</guid>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[chrome-dev]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 11:02:16 GMT</pubDate>
            <atom:updated>2025-12-16T11:02:16.809Z</atom:updated>
            <content:encoded><![CDATA[<p>I am back from a long leave, maternity leave, to be specific, and in the time it’s taken me to see a cute newborn baby grow into an agent of chaos, the tech world I took a break from changed <em>dramatically</em>. I stepped back into Developer Relations, this time in the Chrome team and everything was different. New words and acronyms were flying around: Agents, MCP (Model Context Protocol), and A2A (Agent-to-Agent). I would snicker at these LLMs before because the hallucinations were so bad, but now they are the default. Everyone, including my mom, has been using these AI tools.</p><figure><img alt="A laptop with a Chrome sticker, the screen says “Welcome back”. There is a baby rattle, coffee mug, baby bag and baby monitor on the desk." src="https://cdn-images-1.medium.com/max/1024/0*Y9o073MRAG1NyKFH.png" /></figure><p>There was so much to learn and catch up on, so I thought what better way to start than to try this “Vibe Coding” thing that people keep talking about in my LinkedIn feed. What a name 👀</p><p><strong>Tara</strong><br>What is vibe coding?</p><p><strong>Gemini</strong><br>Of course. Here is an explanation of “vibe coding.” “Vibe coding” is a modern approach to software development where a person uses artificial intelligence (AI), particularly a large language model (LLM), to write code. Instead of writing every line of code manually, the developer provides the AI with high-level goals, descriptions, and feedback in natural language — essentially describing the “vibe” of what they want to build. The AI then generates, refines, and even helps debug the code based on this conversational guidance.</p><p>[…extra AI fluff here]</p><p>Like many, I have a list of side-projects that I think would be cool to make, but I’ve just never found the time to do. So this felt like the perfect opportunity to give one of them a go, while experimenting with some new tools.</p><p>My husband is from Ghana and speaks Twi. I’ve always wanted to find the easiest way to learn. So, my goal was to build a simple web app to help me learn his language, including a flashcard feature using spaced repetition (inspired by <a href="https://www.google.com/search?q=Fluent+Forever"><strong><em>Fluent Forever</em></strong></a>) and a chat feature to help me learn conversational Twi.</p><p>Given the way people are talking about vibe coding, I had high expectations; I thought I’d just tell it what I want and it would give me an incredible fully functioning application. Not quite 🙃</p><h3>Getting started</h3><p>I asked Gemini to recommend some tools to get started with. There were too many so I went with what looked like the quickest to get up and running and that was Google AI Studio. Everything was in the browser and I didn’t have to download anything.</p><p>I had very little knowledge of prompt engineering other than you should tell AI who to be, so this is how I started.</p><blockquote>“You are a language learning expert and a native Twi speaker, create an application to help an English speaker learn common phrases and conversational sentences based on images.”</blockquote><p>Looking back, my initial prompt was way too vague. The app generated random landscape photos and generic translations. <em>But</em> it had automatically connected to the Gemini Text-to-Speech API. I didn’t even know this existed; that was pretty cool. Each Twi phrase had an audio option and it was actually pronouncing some of them with decent accuracy!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xek3roRtH5IZDdMx.png" /><figcaption>The initial Twi learner app generated by Google AI Studio</figcaption></figure><p>But then came the bugs. Every time I tried to play certain phrases, it would fail. Repeatedly. I kept hitting the helpful “Auto-fix” button, which kept tweaking the code to no success. So the coding on vibes didn’t last very long as I had to look at the code to figure out what was going on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eJvuGPQAkmEskoPZ.png" /><figcaption>Google AI Studio</figcaption></figure><p>I found that the generated code was swallowing the actual, helpful error message from the text to speech API. The app would catch the error from the API and throw a different custom error message. The AI tool looked only at the API output and the custom error message to figure out what was wrong and apply a fix. I removed the custom error so the original error would be thrown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/0*Cbh9LQuYWaj5t3ei.png" /><figcaption>Google AI Studio console errors</figcaption></figure><p>That tiny snippet unlocked the fix. It pointed to a problem decoding the string passed to the API, which meant the API wasn’t returning valid audio data in the first place. The underlying issue was an API configuration problem, likely using a voice model not trained for the Twi language. The AI finally “understood” once it saw the <em>real</em> error.</p><blockquote><strong>My first takeaway</strong>: The core job of the engineer is still needed. We still need to understand the code, and know where to look to find issues. The AI model might write the code and understand the errors, but <em>we</em> need to figure out the problem when it goes sideways.</blockquote><h3>Going through a mental pivot</h3><p>As a Software Engineer, especially one working on side projects, I would be focused on building smaller features that would take a while to complete depending on how familiar I was with the tech. With vibe coding I realised there was so much more I could achieve in such a short amount of time. That made me think about all of the features I could add, and iterate on. I spent less time thinking about how to build/style/deploy this feature and more time thinking about what order I should add them in. What is the most important? And how should I phrase the prompts so I would end up with clear commits that only did one thing. While I still needed Software Engineering experience, it seemed <strong>I also needed more of a Product Manager mindset</strong>.</p><p>My initial vague prompt had led to those random landscapes in an app that was nothing like what I was thinking. To get the app to go from “general Twi stuff” to the conversational UI I had in mind, I learned I had to stop giving vague <em>goals</em> and start giving <strong>precise, specific instructions</strong>.</p><p>It felt like the classic “Peanut Butter and Jam sandwich” coding exercise I used to do at kids coding clubs. The kids are given the task of getting the “computer” (a person) to make a simple PB&amp;J sandwich. In their enthusiasm they’ll say something like, “use the knife to get some peanut butter,” and the computer responds by hitting the jar with the knife without taking off the lid, much to the amusement of young kids. The AI model, like that literal “computer”, takes your instructions to the letter; it doesn’t read your mind.</p><blockquote><strong>My prompt before</strong>: Create an application to help an English speaker learn common phrases and conversational sentences based on images.</blockquote><blockquote><strong>My prompt after</strong>: Update my application so it teaches Twi using the Spaced Repetition System as detailed in the book “Fluent Forever” by Gabriel Wyner. Focus specifically on conversational phrases one might use in the home like “How are you doing?”, “I’m going out”, “Can you get me something from the shop?” and “Have you eaten?”.</blockquote><p>I tried this out with some different tools. I used <a href="https://cursor.com/"><strong>Cursor</strong></a> for a while and then switched to Google’s new <a href="https://antigravity.google/"><strong>Antigravity</strong></a>, using a few of the different models, to compare the types of output. With my new prompts, the apps generated were much closer to what I had in mind, although with quite the confusing user experience. I realised I also needed to pop on my User Experience hat and detail exactly how I want the app to work and look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VbmvWzEv9DQc5yGQ.png" /><figcaption>The Twi teacher app homepage generated using Cursor</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fNZZz0WRFa76jGAo.png" /><figcaption>The learning page generated using Cursor</figcaption></figure><blockquote><strong>My second takeaway</strong>: Models require a significant level of detail I was not used to verbalising. This level of detail, this mental pivot to explaining <em>every single step</em> a user would take and <em>every element</em> on the screen, was tiring but important. It created the cleaner UI seen in the screenshot above. The generated images were a bit “rogue,” but at least the structure was getting there!</blockquote><h3>Working in tandem with the AI model</h3><p>My biggest breakthrough came when I stopped treating the AI like a magical genie and started treating it like a smart, junior developer. You wouldn’t give a junior dev one massive, vague task and walk away. You’d help them break it down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2L6UsVvkh7GUn80A.png" /></figure><p>My new workflow became:</p><ol><li>Give a clear and specific task</li><li>Review the code and UI changes</li><li>Manually make any small tweaks in the code</li><li>Provide feedback to the model if it wasn’t quite right</li><li>Commit and push</li></ol><p>While these AI models are amazing at handling the standard boilerplate, project setup, and connecting to APIs I know nothing about (saving so much time!) I did miss the fun of writing the components myself. The satisfaction of crafting the perfect CSS animation or optimising a React component.</p><p>I’ve found “Vibe Coding” to be great for speed, but the feedback loop can feel slow. You’re waiting, hoping it builds what you want, then refining. It’s a different kind of coding.</p><h3>Where I’m at</h3><p>I’ve built something that works and looks ok, and I’ve deployed the front-end to Netlify. It’s wild how much you can accomplish with just a few prompts, despite the niggles. I’ve got a lot more to learn about backend integration and deployment in this new way of working. I intentionally hadn’t read up on these topics or taken a single course, to test the ‘beginner’ experience and my first reactions. I have to admit it’s been a great, if sometimes frustrating, start.</p><p>Honestly, I wouldn’t have made the time to build this app using the “old way.” Even though it’s a fun app to build it would have taken so much longer to get to this point. So, vibe coding didn’t just make me faster; it made a project that wouldn’t have existed possible.</p><p>I’m truly curious to hear from other engineers. How are you working with AI in the workplace vs on your side projects? What are your favourite AI tools? Or, are you like me, finding the fun of component building a little bit… missed?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36cd5e2422fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2022 in review]]></title>
            <link>https://tara-ojo.medium.com/2022-in-review-37a03b089f5c?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/37a03b089f5c</guid>
            <category><![CDATA[2022-review]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Mon, 23 Jan 2023 13:05:03 GMT</pubDate>
            <atom:updated>2023-01-23T13:05:03.091Z</atom:updated>
            <content:encoded><![CDATA[<p>2022 has simultaneously been both my most productive and unproductive year at the same time, which really doesn’t make sense. But, I say that because my definition of what it means to be productive and making progress is changing. It used to be solely career focused, for example, how much tech knowledge am I learning? Am I working towards promotion? Is my personal brand growing? How many people am I helping? That was fine, but there was a whole area of my life that it didn’t include. The “life” part of the sought after “work/life balance”. This year life became my main priority and work and work related interests took a back seat.</p><p>I’ve been trying not to feel guilty about this, but I have spent so many years focused on growing my career that it’s been pretty difficult to put it on pause. It’s like seeing an F1 car whizzing around a track at 200mph on its way to their first win and saying wait, pause for a second, why don’t you focus on this other thing while every other driver passes them. But, it was necessary. In an ideal world, work would be a means to an end, not my whole identity. Even though I have fewer tech related milestones to talk about this year, in reality that’s actually a good thing.</p><h3>Work</h3><p><strong>I got promoted!</strong> In 2021 I left the Financial Times and joined Google Health, I now work on a <a href="https://health.google/caregivers/care-studio/">product for Clinicians</a>. I got to go on my first ever business trip to San Francisco where many of my colleagues are based. I visited the HQ in Mountain View and a bunch of the new offices they’ve just built out there.</p><p>One of the coolest projects I got to work on was part of the Black Googler Network. We ran our annual hackathon and invited students from across the UK to join, and win prizes. Around 40 students came to the offices, worked all weekend to design and create their ideas and they presented them to a panel of judges who are senior leaders at Google. One of them was an angel investor that wanted to invest in the winning team’s idea because he thought it could be a great business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IeLXcBn0qp2aLNRWo6aWTQ.jpeg" /><figcaption>BGN Hackathon attendees and volunteers</figcaption></figure><h3>Speaking</h3><p><strong>I was on a podcast!</strong> My public speaking this year was almost non-existent, but I was invited by the lovely Glowing in tech team to talk about a range of tech topics. I also spoke at a school for their careers day about what it’s like to be a Software Engineer, which I often get invited to do and love doing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6EoCrXtQ6_Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6EoCrXtQ6_Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6EoCrXtQ6_Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/94ff5d5e5c6e6a0237cbd6c4dbed3e94/href">https://medium.com/media/94ff5d5e5c6e6a0237cbd6c4dbed3e94/href</a></iframe><h3>Writing</h3><p><strong>Meh?</strong> Honestly this has been my biggest fail! I’ve had a draft article in progress since October 2021, but could I bring myself to finish it and post? No. But, 2023 is the year. I’ve already put in place lots of dedicated time to focus on writing and sharing what I’ve been learning, starting with this review of the year! I’m looking forward to doing this more.</p><h3>Teaching</h3><p><strong>Also meh?</strong> I would love to get back into teaching, but since my role as a bootcamp instructor for the Black Codher bootcamp finished, I haven’t made the time. I met some previous students at Google and it’s so cool to see the girls I taught progressing in their new tech roles and say they remembered what I taught them 🥲. I would love to do this more. I have taken on some mentees and have been flexing my mentoring muscles. Though, this is a skill I definitely need to get better at!</p><h3>Life</h3><p><strong>I became a wife!</strong> Planning a wedding is something I would very happily never do again, but maybe it improved my project management skills? In hindsight a small, intimate (and cheaper) wedding would have been the way to go.</p><p>We also moved into our own place, so it was the double whammy of life updates, getting married and moving house, within the space of a few months was pretty stressful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ng1NG94btl6-JqDK" /></figure><h3>Other cool things</h3><p><strong>I travelled!</strong> All cancelled trips were back on and as well as my work trip to America, I had a beautiful honeymoon in Santorini and also visited Paris and Barcelona. I went to so many weddings (Love is sweet o!). And I really enjoyed the Google perks. The Black Googler Network had a cool party to celebrate Black History Month with Stonebwoy and Adekunle Gold, and the tech Christmas party was probably one of the biggest parties I’ve ever been too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*buRXVp64aZlSTc1qlQqAEA.jpeg" /><figcaption>Santorini sunset</figcaption></figure><h3>2023</h3><p>This year I’ve relaxed my goals. I still have them but they are higher level instead of the detailed goals I’ve had in previous years. I want to see where God takes me. I did set a word for the year inspired by a show I watched recently — my word is <strong>“growth”</strong>. I want to see growth in all dimensions, spiritually, mentally, physically, career wise, health wise, marriage, everything. Let’s see what this year brings. God willing, it will be another great one.</p><p>Sometimes life takes over and you just have to go with it. I’m honestly so glad I did. 2022 has been amazing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37a03b089f5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One year later — Lessons learned from remote onboarding]]></title>
            <link>https://medium.com/ft-product-technology/one-year-later-lessons-learned-from-remote-onboarding-122142e0173c?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/122142e0173c</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Thu, 29 Apr 2021 13:03:00 GMT</pubDate>
            <atom:updated>2021-04-29T13:03:00.846Z</atom:updated>
            <content:encoded><![CDATA[<h3>One year later — Lessons learned from remote onboarding</h3><p>Twelve months ago, in the midst of COVID-19, lockdowns, quarantining and social distancing, I was one of many people to start a new job. I joined the FT in April last year, about a month after the first lockdown started in the UK. I’ve not yet met my team and I only know some people in the company solely by their Slack profile picture / cartoon character!</p><p>The FT like most other companies had to quickly switch to remote everything, including figuring out remote onboarding on-the-go. Time has somehow flown by, but also felt incredibly slow moving, and while compulsory remote working started out as a novelty, it has now become our new normal. After 12 months at the FT and over 12 months of remote working it seems like a good time to reflect on what I have learned through the experience…</p><h3>1. Be intentional about networking and meeting new people</h3><p>I always knew that working remotely would make meeting people more difficult, I wouldn’t get the impromptu moments of bumping into someone in the coffee area or sitting next to someone new in a company meeting. Onboarding at home definitely hindered my opportunities to quickly develop working relationships.</p><p>In my first few weeks, meetings were scheduled for me with each member of my new team, which was a great way to be introduced to the people I would be working with day-to-day. Continuing this momentum was difficult though, especially when the only opportunities to talk to people were in more “official” team meetings so I didn’t have much non-work chat which, let’s be honest, makes work a lot more enjoyable! Some of my interviewers also messaged to welcome me to the FT, they were the only people I knew when I started so it was nice to have them reach out during my first few days/weeks.</p><p>In my previous role I had already built relationships with work colleagues over years and I had a good handle on the work I was doing! No longer having this in a new company felt pretty isolating. But, it forced me to be extra intentional about finding ways to develop those working relationships, so I reached out to people individually when there was a non-awkward reason to do so! It definitely helps to know more people across the company.</p><p>I wasn’t the only person in the new starter boat though, there were a few initiatives that started across our group and department to give us all the opportunity to connect informally. There was already a company wide coffee roulette Slack group that randomly pairs you with someone else to have a catch-up with. This is a great chance to meet people across the business, though it was a big group for me as I mainly wanted to meet others in my department to start with. We also tried a more manual smaller version within our Customer Products group which worked well until we had logistical challenges keeping the random pairings going!</p><p>I felt the most welcomed when I was invited to a small Slack group for random chats and hype, though, this relies heavily on some friendly colleagues making the effort to include you in a group!</p><h3>2. Great onboarding is massively underrated</h3><p>Working from home has been a good test of the onboarding process for a lot of companies! If you don’t have many new people, you may not consider the importance your onboarding process can make to a new starter. When you’re not working remotely you can get away with a lot by just showing a new person around the office and introducing them to lots of people in the space of a few minutes. On the other hand, working remotely means trying to find the right balance between ensuring your new starter is supported and not overwhelming them with video call fatigue.</p><p>After going through the onboarding process myself I was interested in working on the FT’s onboarding process, so I started the work to do this with help from other new starters at the time. My colleague, <a href="https://medium.com/@jennifer.elaine.mairead">Jenn</a> and I ran an onboarding retro for recent starters and their buddies to get an idea of what worked and where there was still work to be done. There were lots of good things raised like the friendliness of team members, and the useful communication and proactiveness from our Tech Leadership.</p><p>On the other side we saw lots of inconsistency with each person’s onboarding experience, some people had great experiences, others didn’t get so much support. Some had been assigned a buddy, while others didn’t realise that was an option. There was also a desire for a learning plan to help get up to speed with our tech stack, tools and best practices quickly.</p><p>The retro was a great way to learn straight from the people who have recently gone through the experience. The first thing it prompted was a new process to be introduced so we could get some consistency across the group. We crowd sourced ideas and created a Trello board template for each new starter. The board has a number of cards with tasks to be completed over their first 6 months. We also created a similar one for Line Managers, Tech Leads, Delivery Managers and Buddies to collaborate on, so they can ensure they’ve got everything ready for their new starter before they join.</p><figure><img alt="Four columns in Trello board: Info, To do, In progress, Done. Card in Info: “Create a copy of the board for each new starter”. Cards in To do: Intro to team, add to team mailing lists [first week]. Cards in In progress: Identify work to start on, ensure whole team is aware of new start date [pre-joining]. Cards in Done: Choose a buddy, complete new starters form [pre-joining]." src="https://cdn-images-1.medium.com/max/1024/1*02kXnTTQP9_FHnt6OsABkg.png" /><figcaption>Manager Onboarding Template in Trello</figcaption></figure><p>We’ve already had a bunch of great feedback from introducing a more formal process but still plan to address more of the feedback from the initial retro and keep iterating on this process.</p><h3>3. Be kind to myself</h3><p>I’ve seen many people say that remote working under normal circumstances is very different to remote working in a pandemic. I’ve only experienced the latter so I can’t comment on how true that statement is, but I can say that working during a worldwide pandemic has not been normal. I’m usually pretty organised when it comes to career development and jumping on new opportunities with the aim to grow my skills and meet my career goals. I expected to be doing the same after a few months of settling in and getting to know how things work at the FT. In hindsight, this was ridiculous thinking.</p><p>Work did become a welcome distraction from the likes of Covid, Black Lives Matter protests and SARS protests, but all these were still having an effect on my mental health and I needed to look after that. Fortunately, the FT leadership was clear that they didn’t have the same delivery expectations from us in these “unprecedented” times and we still celebrated the milestones we did achieve which was encouraging.</p><p>What I did end up doing was being more flexible with my working hours, starting later in the morning sometimes and starting earlier in the morning other days and taking some opportunities to work in my PJs, in bed. The extra wellness days the FT have provided have also been valuable for extra downtime.</p><figure><img alt="Laptop showing the Financial Times homepage on a bed with a cup of tea in hand and funky red and pink nails" src="https://cdn-images-1.medium.com/max/862/0*IRagkFjiy5DrU4cA" /></figure><p>We’ve all had similar experiences over the last year and there is something quite humbling about us all being in the same bubble of talking on mute, talking while not on mute, children joining meetings, doorbells ringing and video call fatigue. But, it’s still been a year of learning and I’ve been grateful for that!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=122142e0173c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/one-year-later-lessons-learned-from-remote-onboarding-122142e0173c">One year later — Lessons learned from remote onboarding</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2020 in review]]></title>
            <link>https://tara-ojo.medium.com/2020-in-review-223b629d1cc?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/223b629d1cc</guid>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Wed, 30 Dec 2020 14:33:17 GMT</pubDate>
            <atom:updated>2020-12-30T14:33:17.970Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever seen a cage fight? Where two MMA fighters go head-to-head until one of them concedes?</p><p>I think of it as the more gruesome older sibling of boxing. Every so often there is a fight where one of the fighters gets completely destroyed. Just imagine, you are an MMA fighter jumping into the cage. You’re feeling hyped and ready to prove that this is your time. The fight starts off well. You get in a few punches, start getting confident, maybe even a little cocky. Then the other fighter shows you who is really stronger. You get a jab to the face that makes you feel dizzy, a right hook to the ribs which has you in agony and an uppercut to the jaw that floors you. You’re trying to find the inner strength to get back up, but the other guy is on you throwing punch after punch until they are dragged off you because they’ve knocked you out completely. Before you even know what’s happening the fight is over. You’ve lost and you’re left in need of serious recovery and time to heal.</p><p>That for me, is the story of 2020…</p><p><strong>Covid 19</strong>. Jab.</p><p><strong>#BlackLivesMatter</strong>. Right hook.</p><p><strong>#ENDSARS</strong>. Uppercut.</p><p><strong>Grief</strong>. Sucker punch.</p><p><strong>Everything else</strong>. Punch after punch after punch.</p><p>What’s wild is that we can’t really be in recovery yet as none of this is over, it may never be over, so we’re just getting by. Which for some people it has meant putting goals on hold, or even goals in the bin, and for others they’ve had the time they’ve needed to excel and put the work in. I’m definitely on the former side considering some of <a href="https://tara-ojo.medium.com/2019-in-review-2fae2cb3e2d2">the goals and achievements I had last year</a>. Though, I’ve had bursts of “productivity”. So, while 2020 has been an absolute ‘mare, I will still reflect on the good things that have happened in 2020.</p><h3>Work</h3><p>I got a new job! 🎉</p><p>I bid farewell to the amazing people at FutureLearn after working there for over 2 and a half years. This year I started at the Financial Times as a Senior Software Engineer. It has been an interesting change to go from my Tech Lead role at FutureLearn to the role I have now at the FT. In my time here I’ve worked on some interesting and challenging problems on FT.com and in the app and on all parts of the stack. My technical skills have already grown lots and I’m looking forward to developing them more.</p><h3>Speaking</h3><p>I didn’t attempt any conference talks this year, not that there were as many this year, but towards the end of the year I spoke on two panels.</p><ol><li>The first was at the <a href="https://www.girlstalklondon.com/opportunities-events/the-black-girls-tech-summit/">Black Girls Tech Summit</a> in November where we talked about navigating the workplace as black women.</li><li>In December I spoke at a <a href="https://leaddev.com/culture-engagement-motivation/strategies-creating-environment-continuous-learning">LeadDev panel</a> on strategies for creating an environment of continuous learning.</li></ol><p>I find panels much more daunting than giving pre-prepared talks and I still need a lot of practice! I want to get better at these so I’m keeping an eye out for tips and articles for being a great panelist.</p><h3>Writing</h3><p>At the start of the year I had the aim of writing something once a month to work on improving my writing skills. I did start my blog and managed a whole seven out of twelve posts (not including this one!) which considering how this year has been, that’s not too bad 😎</p><p>I’ve predominantly written about career development and some front-end development bits I’ve learned. The most popular has been the one I wrote on <a href="https://itnext.io/animating-list-reordering-with-react-hooks-aca5e7eeafba">animating list reordering with React hooks</a> which has been seen almost <strong>5000</strong> times 😱</p><h3>Teaching</h3><p>I have always enjoyed teaching through learning hours and giving talks, but this year this role became more official when I became an Instructor for the <a href="https://blackcodher.com/">Black Codher programme</a>. Black Codher is a six month coding bootcamp for black women, empowering them to progress into digital roles. I taught JavaScript and React and learned a lot about teaching, and teaching remotely, that I shared in this <a href="https://twitter.com/tara_ojo/status/1322144457832222720?s=20">thread on Twitter</a>.</p><p>I’ve also started using Instagram as a way to document and share what I’ve been learning, I’ve spent a lot of the last few months getting to grips with data structures and algorithms. As I’ve translated that content into Instagram posts it’s helped me understand the topic better and has been a nice way to get to know some of the tech community on Instagram too. So far I’ve talked about Big O notation, recursion and binary search. Take a look at my <a href="https://www.instagram.com/taraojo/">Instagram page</a>.</p><figure><img alt="Screenshots of some of the Instagram posts shared by Tara in 2020" src="https://cdn-images-1.medium.com/max/1024/1*uY1mQT_IouF6ELdKUtwGkQ.jpeg" /></figure><h3>Other cool things</h3><p>I started learning to touch type this year and honestly it is great and has made me more efficient already. I was a slow typer before, keeping my eyes on the keyboard, which is why I decided to learn. It was pretty difficult to build up the new muscle memory and for a while it completely slowed down my typing as I tried to adjust to the new way. I am much faster now than I was previously and I plan to keep improving my number of words per minute. I have been using <a href="https://www.typingclub.com/">Typing club</a> to learn which is really good.</p><h3>2021?</h3><p>Let’s not even go there, I just pray I’ll be alive to see it through…</p><h3></h3><p>There will be a lot of posts soon with people sharing how much they achieved in 2020, in the midst of a global pandemic, etc. But in case someone needs to hear this, I&#39;m here to tell you that just making it to Dec 2020 is an achievement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=223b629d1cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Leadership in Customer Products]]></title>
            <link>https://medium.com/ft-product-technology/technical-leadership-in-customer-products-cec00bf983bd?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/cec00bf983bd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 16:25:14 GMT</pubDate>
            <atom:updated>2021-04-22T11:55:53.490Z</atom:updated>
            <content:encoded><![CDATA[<h3>Technical Leadership in Customer Products at the FT</h3><blockquote>“A Tech Lead is a software engineer responsible for leading a team and alignment of the technical direction” — Pat Kua [1].</blockquote><p>While this is a useful high-level definition of the Tech Lead role, it’s not very specific to an actual business. You’ll find that technical leadership roles vary greatly between companies and even departments within the same companies. So, as someone who is fairly new to The Financial Times I wanted to better understand what the Tech Lead role looks like here, especially in the Customer Products group that I’m a part of, to see if it could be a good fit for the future me 🙂.</p><p>To do this, I went straight to the people that are doing the job currently, some of the Tech Leads in Customer Products, and got lots of great insight into how they lead their teams. I quickly started to understand some of the main themes between their roles, as well as some of the tasks that were unique to their individual teams. I see these themes fitting into four categories, our Tech Leads are:</p><ol><li>Advocates for their team members</li><li>Responsible for technical direction</li><li>The technical representative for the team</li><li>Software Engineers</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*RhcORwAeYFMr25iS6TGUVQ.png" /></figure><h3>Advocates for their team members</h3><p>This came across the biggest and most important responsibility for each of the tech leads I spoke to, which makes sense as it fits into the leadership part of the role. As I understand it, being an advocate for your team members can include a number of tasks, such as:</p><ul><li>Finding and creating growth opportunities</li><li>Providing general support</li><li>Championing their achievements</li><li>Ensuring a safe environment for them to learn and grow</li><li>Shielding them from outside pressure (when completely necessary)</li><li>Being honest with them</li></ul><p>James, the Tech Lead for the US Growth team, shared the benefits of having one-to-ones with each team member. James uses this as an opportunity to understand how each person is doing and a way to find out what they need. This can help with a bunch of the areas in the above list, and I’ve personally found it useful with Tech Leads I’ve worked with to develop rapport and build that working relationship.</p><p>Tech Leads have a good oversight of all of the different tasks happening within the team as well as the interesting initiatives happening at the wider programme level. This puts them in a great position to find opportunities to help the personal growth areas of each team member. Rowan, the Tech Lead for the apps team, mentioned that this could include delegation of Tech Lead responsibilities for those wanting to develop their leadership skills, and this would also work just as well for non-leadership specific skills like programming and communication.</p><p>Glynn, the Tech Lead of the Content Innovation team, talked me through the importance of ensuring psychological safety in this team. This is around making sure that team members know that they won’t be punished if they make a mistake and that they can be their authentic selves at work, which is essential for any team to perform well. Part of the Tech Lead role is to make sure people are comfortable sharing their thoughts and concerns so we can get the best out of them, enabling them to build better products.</p><p>Also, as part of my chat with Rowan, we discussed the interesting topic of protecting team members from outside pressures and company politics. Rowan has learned that it can actually be a good thing to allow team members to see some of those pressures. It can give them exposure to the realities of the role, and can also be another career development opportunity. It reminded me of a great talk at a Lead Dev conference I went to. Nickolas Means gave the talk called <a href="https://www.youtube.com/watch?v=RNGZTkM2xOU">Eiffel’s Tower</a>, in this talk it was noted that the common take on leadership has been to protect your engineers from <strong>all</strong> external pressures and act as the “poop” umbrella (💩☂️). While this has benefits, your team can become disconnected from the goals of the company which is useful for their role. Nickolas instead introduced the idea of the Heat Shield (🔥🛡) usually used in space. The heat shield doesn’t completely stop heat from coming through, but it shields enough heat to keep you alive. As a lead, you shouldn’t be the barrier between your team and the business, but instead you should let some of the heat in and block the really big fires that happen in your organisation!</p><h3>Responsible for tech decisions and direction</h3><p>Depending on the company and department you’re in, the responsibility of deciding the tech direction and making the decisions isn’t always on the Tech Lead. Sometimes this sits with a Technical Architect or a Principal Engineer. Here, in Customer Products a lot of this work is the responsibility of a Tech Lead, although for much larger cross-team changes the Principal Engineers will also be responsible.</p><p>Nick, the Tech Lead for the Acquisitions team, shared how autonomous the teams are. Each team is trusted to make the best decisions for their team, giving them the freedom to choose how they work. Tech Leads aren’t left alone to do this, they have regular catch-ups with other Tech Leads and Principal Engineers in the group to discuss these kinds of decisions, especially where it could benefit or impact other teams.</p><p>While Tech Leads regularly meet as a group to share information, many of the Tech Leads also regularly catch-up with the Product Manager and Delivery Manager within their team. This is what Rowan shared as the three amigos approach to team leadership, where, in our case, there is a representative from Product, Tech and Delivery. This can include deciding the next big thing to work on, discussing priorities for the next sprint and generally combining the interests of Product, Delivery and Tech. Practically, Tech Leads will be involved in roadmapping, providing estimates, and setting OKRs for the team. This is also a big part of Jen’s role as the Tech Lead for the Ops Cops team, which has a slightly different setup. Ops Cops is responsible for handling incidents that arise across the Customer Products tech estate and has rotating team members each week. This team doesn’t have a dedicated Product Manager so the prioritisation tasks and general management of what the team works on is all part of Jen’s role.</p><p>One of the things I learned from James was the importance of knowing how you’ll measure success for the work the team plans to do. Before starting work on any new project or task, we should be able to know afterwards if that change was beneficial. This is all discussed as part of the three amigos meetings.</p><h3>The Technical Representative for the team</h3><p>Umberto, the Tech Lead for the Content Discovery team, and Rowan both shared how Tech Leads are naturally the point of contact for technical questions. Fielding a wide variety of questions from external stakeholders, being the tech representative present in meetings, and sharing thoughts on things like technical feasibility are all responsibilities that will fall to the Tech Lead. Since they have the official title it makes sense to reach out to the lead if you have a general tech question. Being the technical representative also includes answering questions from within the team; engineers tend to go straight to the Tech Lead with areas they need clarification on.</p><p>On the flip side, it’s also up to the Tech Lead to surface technical risks to the stakeholders. Tatiana, Tech Lead for the Accounts team, shared the importance of ensuring stakeholders understand the risks of unmaintained tech to the users.</p><p>These areas are great opportunities to start delegating parts of the Tech Lead responsibility to others in the team, which is what Glynn does in the Content Innovation team. This gives people development opportunities and lessens the load on the Tech Lead.</p><p>As a Tech Lead you automatically have a bigger impact in the company given the nature of the role, this was something I talked to Glynn about. Tech Leads are the team representative in regular tech lead catch-ups, and are involved in larger tech strategy conversations which is a good opportunity to have a say in making things better for the product, our readers, and also the people we work with.</p><h3>A Software Engineer</h3><p>And finally, the thing that seems the smallest, but is still an important part of the Tech Lead role. While being a Tech Lead is about leading a group of engineers, you are still a software engineer. So, writing code, keeping up-to-date with new technologies, pairing with your team members and generally delivering software are still part of the Tech Lead role. Almost everyone I spoke to wished they had more time to spend on this!</p><p>One of the big differences in going from a Software Engineer role to a Tech Lead is that big reduction in how much time you’re able to spend writing code and figuring out problems by yourself. James spends a good chunk of time pairing with team members, giving advice on code and reviewing PRs; these are the tasks of many software engineers, but they are also leadership tasks. Similarly, Umberto talked about spending time reviewing PRs as a great way to get team members unblocked. This is actually one of our <a href="https://www.ft.com/tech-principles">Tech Principles</a> at the FT, we treat unblocking others as our priority.</p><h3>But, what are the differences?</h3><p>I’ve shared a lot about the similarities of the Tech Lead role between teams after talking to these Tech Leads, but there were differences. This is mainly because of the differences in what each team is responsible for. The Ops Cops team does a lot less stakeholder management, so Jen, unlike many of the other leads, also does product management, making sure work is clear, divided up and ready to be picked up by rotating team members. The Content Discovery team is the opposite of this and a lot of work is done with the Editorial team which takes time away from other tasks like fleshing out stories to be picked up by the team.</p><p>Also, I learned from Glynn that each Tech Lead leans on their own personal strengths; if they are naturally inclined to support other engineers then it’s easy to spend a big chunk of your role doing that, otherwise if you’re great at handling stakeholders then that can become the priority. Either way there is a lot of opportunity to make the role something that suits you, while incorporating the four themes I outlined.</p><p>It was really interesting to hear everyone’s experiences of being a Tech Lead in Customer Products. Learning about the role from each person’s perspective made the idea of being a Tech Lead here a lot less daunting! Advocating for team members, ensuring they get personal development opportunities and celebrating their achievements, is definitely a part of the role that appeals to me, though, I don’t need to be a Tech Lead to do that part!</p><p>On the other hand, I would benefit from getting more opportunities to make decisions about technical direction. Or, work with a Tech Lead as they go through the process of doing this for their team. I think this would put me in a better position to do this role effectively.</p><p>So, is the Tech Lead role a good fit for the future me? I think it could be…</p><p>Thanks to all of the amazing Tech Leads across customer products for taking the time to share their experiences with me!</p><p>[<a href="https://www.patkua.com/blog/the-definition-of-a-tech-lead/">1</a>] The Definition of a Tech Lead — Pat Kua</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cec00bf983bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/technical-leadership-in-customer-products-cec00bf983bd">Technical Leadership in Customer Products</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lazy-load images with the Intersection Observer API and React]]></title>
            <link>https://javascript.plainenglish.io/lazy-load-images-with-the-intersection-observer-api-and-react-4fd8ae19e195?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fd8ae19e195</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 19:30:25 GMT</pubDate>
            <atom:updated>2020-11-13T20:18:35.493Z</atom:updated>
            <content:encoded><![CDATA[<p>The Intersection Observer API allows you to observe and react to changes when an element enters the viewport or a parent element. It’s very commonly used for lazy loading but can also be used for things like animations or changing the active state of links in a navigation bar as you scroll to different sections of a page. Lazy loading images stops the user from having to download resources on initial page load, instead, deferring it until a more appropriate time.</p><p>I’ve been playing around with different effects for lazy-loading images and I like this one where instead of swapping a placeholder image with the real image, we’re instead revealing the image with CSS opacity transitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*7pBrGBsizwtLsJSbKB-XAA.gif" /><figcaption>What we’ll be building!</figcaption></figure><h4>Install and import packages and styles</h4><p>To do this let’s start with some imports, we’ll be using React hooks, CSS modules and the classnames package to get this working. You can see the completed code below in the CodeSandbox using create-react-app.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc73b3633fa3a3a184e4e47622b3795d/href">https://medium.com/media/fc73b3633fa3a3a184e4e47622b3795d/href</a></iframe><h4><strong>Create the component</strong></h4><p>We’ll create a functional component that returns a div element that we’ll use as our placeholder. We’ll also use the useRef hook to get a reference to our placeholder in the DOM. Later we can use this ref to see if the placeholder has come into the viewport.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3848621a293fa5bc349d88eb69f271cd/href">https://medium.com/media/3848621a293fa5bc349d88eb69f271cd/href</a></iframe><p>The useRef hook gives you a way to store a mutable value using the .current property on the object returned. I won’t go into why this can be useful, but in our case when we do ref={placeholder}<em> </em>on our placeholder element, React sets the .current property to the corresponding DOM node and keeps that value up-to-date whenever it changes.</p><h4>Add styles</h4><p>The styles for this are pretty minimal, the element wrapping the image and placeholder has its display set as relative to constrain the absolutely positioned placeholder. Essentially, the placeholder is a yellow box with a bottom padding set to match the aspect ratio of the image we’re using. Adding the transition property means we can use CSS to fade out our placeholder when we programmatically add the hidePlaceholder class.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc2f9e562533aca8902d5d0c15f26418/href">https://medium.com/media/dc2f9e562533aca8902d5d0c15f26418/href</a></iframe><p>At this point we’ll have nothing but a yellow rectangle on the page… exciting!</p><p>The next step is to make that box fade out, we’ve already created the CSS class so we just need to add it to the placeholder div. First, we’ll create a new piece of state with the useState hook to let us know whether our image should be shown or not. By default this is false, we don’t want to show our image on first render. Then, we’ll use our showImage state to decide when to add our hidePlaceholder class. To do this, I like to use the <a href="https://www.npmjs.com/package/classnames">classnames</a> package, because it’s a bit cleaner than writing it myself and handy for doing conditional logic with class names.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ce0cb3ac94bc89584e3b9367aabd60a/href">https://medium.com/media/3ce0cb3ac94bc89584e3b9367aabd60a/href</a></iframe><p>Now that is sorted we can update our placeholder element to use the new classes variable.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3bbc38283ea2a8102cf5eb474eb373f5/href">https://medium.com/media/3bbc38283ea2a8102cf5eb474eb373f5/href</a></iframe><h4><strong>Add our image</strong></h4><p>Now we’re at the point where our box will fade to nothing when the value of the showImage state changes. Though, we still need to actually show the image, so let’s do that next. I’ve picked an image and created a variable for it outside of my component called IMAGE_URL. We already have our showImage state so we can also use this to conditionally render our image.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5632b1d89e5898d3b8d16cdc5633264f/href">https://medium.com/media/5632b1d89e5898d3b8d16cdc5633264f/href</a></iframe><h4><strong>Set up the Intersection Observer</strong></h4><p>All we have left to do is change the value of our state when the placeholder comes into view. We need to set up the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API">Intersection Observer</a>.</p><p>The Intersection Observer takes two parameters, the first is the callback. This is what will be called when your element comes into view, in our case, when our placeholder comes into view. <em>Do note that this callback will also be executed the very first time the observer tries to watch your element.</em></p><p>The callback will be given a list of <a href="https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserverEntry">IntersectionObserverEntry</a> objects as its first parameter. Each item in the list represents each item being observed who’s intersecting status has changed. In our case the list will always have a length of one, as we’re only watching one element (our placeholder).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f011e4e35644f5aedbfb0a7b03f0def/href">https://medium.com/media/8f011e4e35644f5aedbfb0a7b03f0def/href</a></iframe><p>We can check the value of the <em>isIntersecting</em> property on the entry to see if our placeholder is inside the viewport and when it is, then we should update our showImage state to true.</p><p>The second parameter passed into the Intersection Observer is the options object. There are a few different options we can set to configure the observer but we’ll just focus on the threshold. The threshold determines when the callback should be run. It can either be one number or an array of numbers. By default this is 0, so if 1 pixel of the element we’re watching comes into the viewport then our callback is fired, I’ve changed this to 1.0 which means our showImage state will not change until the whole placeholder is in the viewport. This also means we can watch it fade in smoothly.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3a6a86f5a09e52f2eb5798f62f487842/href">https://medium.com/media/3a6a86f5a09e52f2eb5798f62f487842/href</a></iframe><p>Now we can create our new instance of the Intersection Observer, passing in our callback and options, and use it to observe our placeholder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/459075730f01c2ff19d8f41e12ed6dde/href">https://medium.com/media/459075730f01c2ff19d8f41e12ed6dde/href</a></iframe><p>You’ll notice that I’ve put it all inside of a useEffect. We use the useEffect hook to run code (an effect) after the render when our components are on screen. We need to wait for this to happen before we observe our placeholder. By default the useEffect will run after <em>every</em> render, but we can change this to run when specific values have changed.</p><p>We can do this by passing an array as the second value to the useEffect hook, this array should include any dependencies your effect uses to ensure it always has the up-to-date value. In our case the effect doesn’t have any dependencies and we only want to set up the Intersection Observer once so I have left the array empty. This means the effect will only run once on first render.</p><figure><img alt="Girl wearing VR headset with a yellow fading overlay" src="https://cdn-images-1.medium.com/max/1024/1*rPWYFaGV18sS6QBDKuMS4g.png" /><figcaption>Image: UK Black Tech</figcaption></figure><h4>UseEffect cleanup</h4><p>We should also ensure we run cleanup functions in a useEffect we can do this by returning a function inside the useEffect which will be called when the component is destroyed.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d40dbf709e45478244770a00bd3c55e/href">https://medium.com/media/0d40dbf709e45478244770a00bd3c55e/href</a></iframe><p>Here we are using the disconnect method on the observer to stop it from watching all of its target elements for visibility changes. This means it will stop watching our placeholder.</p><h4><strong>We’re done!</strong></h4><p>Once you’ve added enough content above your image you’ll see as you scroll down your image fades in smoothly after the placeholder is completely in view. Check the CodeSandbox below to try it out. 🙂</p><p>Thanks for making it this far! Follow me on <a href="https://www.instagram.com/taraojo/">Instagram</a> for other JavaScript tips and tutorials 👩🏾‍💻</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fzek38&amp;display_name=CodeSandbox&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fzek38&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fzek38%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/3457eef44f7238146d923c4c10cd2ea5/href">https://medium.com/media/3457eef44f7238146d923c4c10cd2ea5/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fd8ae19e195" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/lazy-load-images-with-the-intersection-observer-api-and-react-4fd8ae19e195">Lazy-load images with the Intersection Observer API and React</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Animating list reordering with React Hooks]]></title>
            <link>https://itnext.io/animating-list-reordering-with-react-hooks-aca5e7eeafba?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aca5e7eeafba</guid>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[uselayouteffect]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 08:01:01 GMT</pubDate>
            <atom:updated>2020-10-26T09:55:39.401Z</atom:updated>
            <content:encoded><![CDATA[<p>A little while ago I was given a cool design for an Instagram story styled bubble component where each bubble would smoothly slide into its new position when we got its new order from the API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/0*ofgpW_7pmx5xMTZB" /></figure><p>While it can be straightforward to do a whole load of animations and transitions with CSS, it took me a while to find an example of animating the reordering of list items, especially with React. Since I’ve also started to get used to the concepts of React Hooks I wanted to use them to implement this animation too.</p><p>I found this difficult to do using React hooks because my component would automatically rerender, in its new order, when it got new data. I was trying to hook into the moment before rerendering to smoothly transition from one state to another. Without the <strong><em>componentWillReceiveProps</em></strong> function call from the class components, this was hard to do.</p><p>I was under the (incorrect) assumption that there would be loads of React hooks examples out in the wild. I honestly just wanted a copypasta solution that I wouldn’t have to tweak too much 👀. I also didn’t want to bring in some huge, usually overly flexible package to reorder one small thing. I did come across a great post by Joshua Comeau (linked below). It explains how to do exactly what I needed, but with class components. With React hooks I needed to re-think some of the concepts to get it to work, but I’ve based the majority of this work on that post.</p><p>What we want to happen:</p><ol><li>Keep an eye out for when our element list is going to change</li><li>When it changes we want to calculate the previous positions and the new positions of each element in the list before the DOM updates</li><li>Also before the DOM updates with the new order of the list we want to “pause” the update and show a smooth transition of each item in the list from its old position to its new position</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*nB-0tkPafPwkKQh-R8XuAA.png" /></figure><p>Let’s start with a parent component that just renders the children that is passed into it, <strong><em>AnimateBubbles</em></strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ed7d5349585253dffb47c9d2c04a9c2/href">https://medium.com/media/2ed7d5349585253dffb47c9d2c04a9c2/href</a></iframe><p>Then we can use that component by rendering our items inside of it. In my case I’ve created a <strong><em>Bubble</em></strong> component that adds the styles to make each image a circle, <a href="https://codesandbox.io/s/reorder-elements-with-slide-transition-and-react-hooks-flip-211f2?file=/src/Bubble.js">the full code is here</a>. The <strong><em>Bubble</em></strong> component also forwards the ref onto the DOM element. This is important as we can use the ref to find where the element is rendered in the DOM, then we can calculate its position. Another important prop is the <strong><em>key</em></strong>, this is not only needed for React when mapping over elements, but we can also use later to uniquely identify each item and match its old and new positions in the DOM.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7bfe6dd90d2af22a5582902ddfbfe13e/href">https://medium.com/media/7bfe6dd90d2af22a5582902ddfbfe13e/href</a></iframe><p>Now that we have the foundations of our components we can start building out the logic of our <strong><em>AnimateBubbles</em></strong> component.</p><h3>Keeping an eye out for React rerenders</h3><p>With React hooks, we no longer have access to lifecycle methods like <strong><em>componentWillReceiveProps</em></strong> or <strong><em>componentDidUpdate</em></strong>, instead it’s all about effects. If we want to do something when a prop changes we can do the work inside of a <a href="https://reactjs.org/docs/hooks-effect.html"><strong><em>useEffect</em></strong></a>. The <strong><em>useEffect</em></strong> hook tells React that our component needs to do something after it renders. In our case we only want to do any work if our list changes and the new order is rendered. Adding children as a dependency allows us to do that.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7ac5d96fa66a2dc3816fae477f373fd/href">https://medium.com/media/c7ac5d96fa66a2dc3816fae477f373fd/href</a></iframe><h3>Measure each position in the the DOM</h3><p>To calculate the position of each child in the DOM whenever the children prop changes, we can use <a href="https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect"><strong><em>getBoundingClientRect</em></strong></a>. I created a separate helper function to do this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a407d85967c66e9f2dce9f26d7a2b10c/href">https://medium.com/media/a407d85967c66e9f2dce9f26d7a2b10c/href</a></iframe><p>In this function we pass in <strong><em>children</em></strong> as an argument and use the <strong><em>forEach</em></strong> function on React.Children to iterate over them, getting the measurements of each item in an object that we can later store in state. This is where setting a key on each child is important as we store each box with its key as the object key so we can match up the old position with the new position later. It is also why creating a ref for each child is important, as we use that to find the element in the DOM and measure the bounding box for it. Now, when we call this function inside of the <strong><em>useEffect</em></strong> we will get the bounding box for each child updated every rerender 🎉.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d665d4033996a4ad018e666ffc7bae0/href">https://medium.com/media/8d665d4033996a4ad018e666ffc7bae0/href</a></iframe><p>The problem now is we’re only getting the new positions, but we also need the old positions so we can do the slide animation from old position to new position.</p><h3>Getting the previous state/props with the usePrevious hook</h3><p>One way in which we can get the old positions of the children is by keeping track of the previous state of the children. The React docs already suggest a hook for this called <strong><em>usePrevious</em></strong>. They say that it may be provided out of the box in the future since it is considered a common use case. Using <a href="https://reactjs.org/docs/hooks-faq.html#how-to-get-the-previous-props-or-state"><strong><em>usePrevious</em></strong></a> means we can do the exact same thing to measure the bounding box of the old positions as we do for the new positions.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f140feb60388626a43dbbe78b8a2638b/href">https://medium.com/media/f140feb60388626a43dbbe78b8a2638b/href</a></iframe><p>I’ve put this into a separate <strong><em>useEffect</em></strong> as they don’t need to be done together and they both have different dependencies. These previous positions will now be recalculated every time children change.</p><p>Now we have these two important pieces of information, we can move on to the actual transition 😅</p><h3>Making moves</h3><p>When making the actual animation I looked more into <a href="https://aerotwist.com/blog/flip-your-animations/">FLIP</a> as was talked about in Joshua Comeau’s post. FLIP stands for First, Last, Invert, Play, coined by Paul Lewis as a principle for rendering more performant animations.</p><p>So in our case, we find the first position of each child. We have this stored in state in <strong><em>prevBoundingBoxes</em></strong>. Then we find the last position of each child. We also have this stored in state in <strong><em>boundingBoxes</em></strong>. The next step is to invert, which is to figure out how each child has changed and apply those transformations to each child so it looks like it is in its first position.</p><p>We can set up a new useEffect to do this with dependencies on <strong><em>children</em></strong>, <strong><em>boundingBoxes</em></strong> and <strong><em>prevBoundingBoxes</em></strong> as we’ll use all of those values in the effect. Remember when React rerenders, it instantly updates the view with the new state, but we can use <a href="https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame"><strong><em>requestAnimationFrame</em></strong></a> to tell the browser that we want to perform an animation. The browser will call the function you give it before the next repaint.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5cc8e3da82e1987fd71026802ece2297/href">https://medium.com/media/5cc8e3da82e1987fd71026802ece2297/href</a></iframe><p>This we can do with <strong><em>first - last = inverted-value</em></strong> on the <strong><em>left</em></strong> values of the box. Since we also have a reference to the DOM node, we can apply the transform straight onto the node with a transition of 0 seconds so it inverts instantly.</p><p>The final step is to play the animation. To do this we wait for the child elements to be inverted, then we remove the transform and apply a smooth transition. The elements then slide into their new positions 💃🏾💃🏾💃🏾.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f27aae7850977895a96b0d04744f8505/href">https://medium.com/media/f27aae7850977895a96b0d04744f8505/href</a></iframe><h3>Remove the glitch</h3><p>While I started work with <strong><em>useEffect</em></strong> I found that it was looking super glitchy, then after digging around in the React docs I found this tip:</p><blockquote>“Unlike componentDidMount or componentDidUpdate, effects scheduled with useEffect don’t block the browser from updating the screen. This makes your app feel more responsive. The majority of effects don’t need to happen synchronously. In the uncommon cases where they do (such as measuring the layout), there is a separate useLayoutEffect Hook with an API identical to useEffect.” — <a href="https://reactjs.org/docs/hooks-effect.html#detailed-explanation">React docs</a></blockquote><p>Since our aim is to measure the layout of elements in the DOM, what we actually need is <a href="https://reactjs.org/docs/hooks-reference.html#uselayouteffect"><strong><em>useLayoutEffect</em></strong></a>. As noted, <strong><em>useLayoutEffect</em></strong> has an identical API to <strong><em>useEffect</em></strong> so I could easily switch out one for the other and it made the whole animation look super smooth 😎</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2F211f2&amp;display_name=CodeSandbox&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2F211f2&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2F211f2%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/fba4f89204c9a584565af38c7bd0b8c0/href">https://medium.com/media/fba4f89204c9a584565af38c7bd0b8c0/href</a></iframe><p>You got to the end 🎉 Find me on <a href="https://twitter.com/tara_ojo">Twitter</a> for more tech musings 😁</p><h3>Extras</h3><ul><li>Joshua Comeau’s <a href="https://medium.com/developers-writing/animating-the-unanimatable-1346a5aab3cd">Animating the Unanimatable</a> post was the foundation for this work so I recommend reading, Joshua talks a lot more about DOM rendering and the FLIP concept.</li><li>I initially tried this using the “Magic Move” concept based on <a href="https://www.youtube.com/watch?v=z5e7kWSHWTg">Ryan Florence’s React.js conf talk</a>. The <a href="https://codesandbox.io/s/reorder-elements-with-slide-transition-absolute-positioning-6jv6z">codesandbox for this is here</a>, but this version is pretty complex and incomplete.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aca5e7eeafba" width="1" height="1" alt=""><hr><p><a href="https://itnext.io/animating-list-reordering-with-react-hooks-aca5e7eeafba">Animating list reordering with React Hooks</a> was originally published in <a href="https://itnext.io/">ITNEXT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you Learning, Earning and Advancing?]]></title>
            <link>https://tara-ojo.medium.com/are-you-learning-earning-and-advancing-eb7306441a02?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb7306441a02</guid>
            <category><![CDATA[career-planning]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Fri, 01 May 2020 17:52:46 GMT</pubDate>
            <atom:updated>2020-05-01T17:52:46.180Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Evaluating your role and comparing it with others</strong></h4><p>I once got great advice while overhearing someone else’s conversation. My old tech lead was chatting with another engineer in my team and he said something along the lines of:</p><blockquote>“In any job I regularly think about whether I’m <strong>Learning</strong>, <strong>Earning</strong> and <strong>Advancing</strong>. I don’t stay anywhere if I’m not getting at least <em>two</em> out of three of them.”</blockquote><p>I have followed this advice for years and it has really helped me to evaluate positions I was in and compare potential job opportunities. My old tech lead went into a little detail on what he meant by each of them, but I’ve since made up my own criteria for assessing them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/0*KeE9ClzkdyWNtQhX" /></figure><h3><strong>Learning</strong></h3><p>This one is pretty self-explanatory. I don’t want to be in a place where my knowledge is getting stale, or where the company I work for does not understand the value of learning new skills on the job.</p><p>It’s important to know what you’re aiming for, as with all of these areas, so I’ll have a target in mind for what areas I want to develop in. Currently, I want to get better at building out bigger and more complex features, and I want to learn more about the architecture of applications.</p><p>I also think about how I like to learn and whether that can be catered for. I’m an online course and conference kind of gal. Though, I know others can be book people or are happy with online articles. Check that these can be organised for you!</p><h4><strong>Questions I ask myself</strong></h4><ol><li>What do I want to learn?</li><li>Will this job give me the opportunities I need to learn it?</li><li>Will this job pay for my learning opportunities?</li></ol><p>We can’t know everything, but having the opportunity to spend time learning new skills at work is a great way to check that you will grow in your role.</p><h3><strong>Earning</strong></h3><p>Money is important.</p><p>The more you learn and advance in your career, the more you would expect your salary to increase too. In the classic talk / book ‘Drive’ by Dan Pink he talks about what really motivates people at work and money is one of them. He outlines how lack of motivation can come from salary and benefits being too low.</p><p>Though, there is a limit. Apparently more money as an incentive for a job like a software engineer can lead to poorer performance.</p><blockquote>“Pay people enough that you take the issue of money off the table” — Dan Pink</blockquote><p>We want to be paid enough to feel comfortable, which is a different amount for each person. I would also say that “feeling comfortable” isn’t just earning enough to pay the bills, but being paid fairly in the context of your industry, geographical area and in-line with your colleagues doing similar roles.</p><p>I deffo recommend watching the talk <a href="https://www.youtube.com/watch?v=u6XAPnuFjJc">Drive</a> if you haven’t seen it, I picked up a lot of gems from that video when it came out many years ago. I also recommend sites like <a href="https://www.payscale.com/">Payscale</a> to get a better idea of how much your skills are worth.</p><h4><strong>Questions I ask myself</strong></h4><ol><li>How much could I be earning in a role like this with my experience?</li><li>What salary do I want to be earning?</li><li>How much is this job willing to pay?</li><li>What is the lowest amount I could earn to feel comfortable?</li></ol><p>While people like to tell me “it’s not all about the money”, a really big part of work actually is.</p><h3><strong>Advancing</strong></h3><p>So this one is a bit wishy washy but, it’s about getting formal advancements in your career, i.e. promotions, job changes or extra responsibilities.</p><p>Again, it’s useful to think about where you want to get too in your career and the steps you could take along the way. This could be a promotion into a more senior version of your role or the opportunity to transition into a different role that you’re interested in. Like going from a Software Engineer to a Site Reliability Engineer or from a Data Engineer to a Product Manager.</p><p>I see myself in some type of senior leadership role some day. So, while I am developing my skills as an engineer, I am also thinking a lot about improving my leadership skills and looking for opportunities to work on problems that aren’t just technical.</p><p>While I’m a long way away from actually doing that role, there are steps in between that I can take sooner rather than later. In the past I’ve taken up line management and tech leadership responsibilities, which have both been huge learning curves and soo useful.</p><h4><strong>Questions I ask myself</strong></h4><ol><li>Are there advancement opportunities into other roles?</li><li>Are there extra responsibilities I can take on formally?</li><li>Will I get support in moving to other roles?</li><li>How often do those roles open up?</li></ol><p>Having formal steps in the direction you want to go in is a great way to prove that you’re making progress towards your desired goal.</p><p>There is definitely crossover between the three areas and if you’re working in the sweet spot where all three areas crossover, then lucky you.</p><p>I also think there are different phases in my life where different areas are more important. Right now, learning and earning are more important than advancing as I’m enjoying the role that I’m in. On the other hand, I can totally envision a time where advancing becomes the most important thing for me.</p><p>As a side note, I spend a lot of time looking to other people in tech to get inspiration for what my future career could look like. I’ve found it useful to remind myself that while other people’s careers always seem to be super inspiring and wildly unachievable, I am on my own path and making the decisions that suit my skills and interests. My journey isn’t a straight line to some promised land, it’s a squiggle. I try things out here and there and change my mind about what I want to do almost every week. C’est la vie 🤷🏾‍♀️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7306441a02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Widen your impact as an engineer]]></title>
            <link>https://tara-ojo.medium.com/widen-your-impact-as-an-engineer-2360a12d5026?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2360a12d5026</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[impact]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Thu, 27 Feb 2020 09:01:01 GMT</pubDate>
            <atom:updated>2020-02-27T18:19:56.093Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the years, my understanding of what it takes to grow as an engineer and climb my career ladder has changed dramatically. When I started out, I was confident all I needed to do was to become an amazing coder. I thought I just needed to know how to build complicated features.</p><p>Though, when I looked at the careers of more senior people in technology, this didn’t really add up. Most CTOs and Technical Directors aren’t spending their time in the codebase and worrying about code quality in their day to day roles. Even technical architects and leads don’t always spend lots of their time writing code. While it’s still important, writing code isn’t their highest priority.</p><p>Now, my thoughts on growing as an engineer are pretty different. Seniority develops as your impact grows. Particularly as your work starts to impact and influence larger groups of people. When you think of a CTO, their job isn’t about the details. It’s more about the wider questions that impact the team they look after. When you think of a principal or an architect they’re all about defining technical strategy for the future, and making sure engineers have everything they need to do their jobs and do it well.</p><figure><img alt="Groups of impact: me, my team, tech team, company, community" src="https://cdn-images-1.medium.com/max/917/0*epbFY2IhCoxMMDr_" /><figcaption>Where is your level of impact?</figcaption></figure><p>I’ve grown most as an engineer when I was doing things that were unexpectedly widening my impact. Firstly, I started <strong>developing my specialism.</strong> This meant people would start to come to me for support as someone experienced in a specific area. And secondly, I <strong>made things happen</strong>, thinking less about what could be better and instead taking action to make things better.</p><h3>Develop your specialism</h3><p>When you’re confused about a concept and can’t figure it out, who do you go to for help? For me it depends on the subject. If it’s a weird React thing then I know just the person for that, if it’s infrastructure related then I know the girl for that too. If it’s an accessibility question, I know a guy.</p><p>While there are lots of great full-stack developers out there, I generally go to specific people for more specialised questions. Lara Hogan has this great concept of developing a <a href="https://larahogan.me/blog/manager-voltron/">manager Voltron</a> and I like to give it a technical spin. The idea is to have a diverse group of people that you can reach out to for support for different things. In my case, React, Accessibility, Infrastructure, CSS, etc. To flip this idea around, what could you help with in someone else’s Voltron?</p><p>Maybe people already come to you with certain questions because you have a bunch of domain knowledge in that area. Otherwise, think about what you would want that area to be. While it’s still important to develop a foundation in different areas, picking one or two as your “specialism” will help you focus your learning. The next step is making sure people know you’re the person to ask if they have questions. Be vocal about that topic and share your opinions in discussions, pull requests and essentially at any opportunity you get!</p><figure><img alt="T-shape: The top of the T is your base knowledge and skills and the main part of the T is the depth of you knowledge" src="https://cdn-images-1.medium.com/max/952/0*wXEVT_EJQTthOmyi" /></figure><p>Having base knowledge in a wide variety of areas, and developing depth in some specific areas is commonly known as having T-shaped skills. As a new engineer, you’re generally feeling different areas out, but as your skills develop you’ll start to find areas to develop technical depth and as people come to you with questions, you’ll start to widen your impact.</p><h3>Make things happen</h3><p>I’ve met so many people in life with great ideas but lack the motivation to actually make them happen. I refuse to be one of those people! You’ve probably had ideas yourself of things that could be improved or potential solutions to problems. Act. On. Them. I had to force myself to push through the “I don’t know what I’m talking about barriers” and I still need to on a regular basis. So, even if you aren’t the person to do the actual change, make your thoughts known and make things better.</p><p>I’m essentially talking about being <strong>proactive</strong>.</p><p>proactive - <em>adjective</em></p><ol><li><em>(of a person or action) creating or controlling a situation rather than just responding to it after it has happened.</em></li></ol><p>I found this a pretty big mental shift, especially as a technical lead. As an engineer you can spend time picking off a to do list of tasks that someone somewhere in the company has decided is important. When you become more senior, people look to you to make those decisions!</p><p>You can only really prepare yourself for this is by doing it. Keep an eye out for opportunities that support the growth of your colleagues and see if you can work on it on the side of your normal role.</p><p>As an example, I did a 12 month graduate scheme at Marks and Spencer. I was one of nine engineers hired as a graduate software engineer, and we were distributed around the company. Some of the teams were iOS, Android, APIs and I worked on the front-end team. I was super nosey and wanted to know what others were working on around the business. I also wanted to learn a bit more about how the other teams in the business worked. I organised what I called a “Grad show and tell” where the nine of us would get together and share what we’d been working on. It was super low pressure because there were no senior people in the room and I got to see how my fellow grads were building things in Java, Swift and Python. We learned from each other and went away with wider knowledge about what was happening in other parts of the business. This is a small-scale example, but I saw an opportunity and then I made it happen.</p><p>You can apply this idea to lots of things. Generally, it’s about influence. You need to show that the thing you want to do is a good idea so you’ll need to consider how you’ll get people on board.</p><p>When I was offered an internal role outside of my grad scheme, I really put this into practice when asked for a pay increase. I gathered a bunch of data about current salaries in London for an engineer and asked for feedback from my team, so I could prove that I was at the mid-level I hoped I was. My influencing tactic was completely data-driven so when I walked into the meeting I booked with the director of the department, I only had to show him all my evidence and he agreed to the salary I wanted! This also had the benefit of bumping up salaries of my colleagues that would also be starting in similar roles.</p><p>Public speaking is another great way to widen your impact in the external tech community. You’re sharing your opinion in a very visible way with people from other companies. Not only is speaking great advertisement for the company you work for, but it can be great exposure for you personally. If you have a topic idea that not many people speak about or have a unique perspective on a popular topic, conferences and meetups will always want you.</p><p>When I say “Make it happen” I mean take the lead and do the work to improve things for your team, your department, your company and even the wider tech community. Whether that is making a refactor to make building features easier or giving an external talk to help with hiring, it’s all worth it 😊.</p><p>Focusing on these areas generally makes work life better for everyone you work with, as well as helping you build those skills that will help you to climb the so-called “career ladder.”</p><p><strong>This post is a written and updated version of a section from my talk </strong><a href="https://www.youtube.com/watch?v=6sVRVCAcNh8"><strong>Junior.next()</strong></a><strong>. Over the upcoming weeks I also plan to write about the other parts of the talk too :)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2360a12d5026" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stretching yourself as a new engineer]]></title>
            <link>https://tara-ojo.medium.com/stretching-yourself-as-a-new-engineer-ac155206c986?source=rss-cfb91694fe5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac155206c986</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tara Ojo]]></dc:creator>
            <pubDate>Tue, 21 Jan 2020 09:01:01 GMT</pubDate>
            <atom:updated>2020-01-21T09:01:01.297Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>I gave a talk called </strong><a href="https://www.youtube.com/watch?v=6sVRVCAcNh8"><strong>Junior.next()</strong></a><strong> at a few different events. This is a written version of a section in that talk. Over the upcoming weeks I also plan to write about all the other parts too :)</strong></p><p>So, I don’t mean this to sound cringey, because it sounds cringey in my head, but I think stretching yourself and setting stretch goals in your tech career is so important. When I first started out as a software engineer my aim was to say yes to everything.</p><ul><li>“Tara you’ll need to learn Angular” — cool</li><li>“Tara can you fix this bug?” — I’ll give it a go</li><li>“Build a pattern library” — erm sure?</li><li>“Tara can you present the project to our stakeholders” — wait, what?!</li></ul><p>I’d like to say I stretched myself within reason, but I didn’t, I had no social life (not that I could afford one) and regularly took work home with me so I could learn more and get more done (that wasn’t healthy and I do not recommend giving your employers your free labour 👀).</p><p>When you stretch yourself and work outside of your comfort zone, you lay the groundwork for future returns. That’s essentially how things have worked for me so far. In this industry that is constantly evolving, it is impossible to get to the point where you know everything. I feel uncomfortable when I come across things I don’t know, and when I feel uncomfortable I stop talking.</p><p>My biggest challenge in my career has been my ability to communicate well. If you know me you know that I speak quietly and rarely. I naturally speak when I feel like I have something “correct” or important to say. At school I didn’t speak at all 🙈. Every parents evening, my teacher would tell my parents how shy and quiet I was and that I needed to “speak up”. I still haven’t been able to get rid of that feedback 🙃.</p><p>I’ve personally worked on it by stretching myself in a bunch of different ways which has helped me immensely. Looking back, there were some key things I did along the way.</p><h4><strong>Figure out your limits</strong></h4><p>There is such a thing as stretching too far. Sure, you want to develop your skills, but not at the expense of feeling stressed, exhausted and burned out.</p><figure><img alt="Comfort zone circle in the centre with the stretch zone one layer around of it." src="https://cdn-images-1.medium.com/max/1024/1*P2VejL86U-RIXcyUxUBZ0w.png" /></figure><p>This diagram visualises it well, the smallest zone is the comfort zone. When you’re in the comfort zone you feel relaxed and safe, sometimes even a bit bored. When you come out into the stretch zone though, you start to feel challenged in a way that helps you develop. It’s exciting, but can also have you feeling vulnerable and nervous! This is the sweet spot for learning new things or taking new approaches. To people smarter than I am, this is also known as the <a href="https://youtu.be/0JyFHYzpX7g?t=88">zone of proximal development</a>.</p><figure><img alt="Comfort zone circle in the centre with the stretch zone one layer around of it and then panic zone one layer around that." src="https://cdn-images-1.medium.com/max/1024/1*kXKB3TJP1dDnqinuUbpXZQ.png" /></figure><p>Outside of the stretch zone is the panic zone. If you find yourself in the panic zone, you’ve gone a step too far. Work here is too difficult and you get stressed out. This is where learning stops happening. Sometimes, all you need to do is imagine yourself doing the activity, and it’s enough to trigger a response in your body which freaks you out. Listen to your body, it knows what’s best.</p><p>Things don’t stay in the same zone forever. As you grow and develop, your comfort zone grows and things that were in your panic zone move into your stretch zone.</p><h4><strong>Set your goals</strong></h4><p>Now you know where the sweet spot is for the level of goal you should set, it’s time to start setting them. If you’ve already got goals in mind or things you want to achieve, then there isn’t much work to do here, I already knew I wanted to improve my communication. I also wanted to practice speaking and get better at inputting into conversations. On top of this, I also had a whole heap of other things I wanted to work on but there is only so much I can focus on at once!</p><p>If you’re not so sure though take a look at some career development frameworks. Ideally one from the company you work in, but if they don’t have one, there are other companies that share theirs publicly. I did a simple search and found ones by <a href="https://labs.spotify.com/2016/02/15/spotify-technology-career-steps/">Spotify</a>, <a href="https://medium.com/s/engineering-growth-framework/engineering-growth-tracks-b1fad620787e">Medium</a> and <a href="https://about.gitlab.com/handbook/engineering/career-development/career-matrix.html">GitLab</a>. Scan through the kind of things they want from their employees and see if there are things you want to get better at or things that will make you more valuable at your company. Remember to set them within your stretch zone!</p><h4><strong>Share your goals!</strong></h4><p>This is the most important step if you ask me. There is something about being accountable to someone that makes me get stuff done. I tend to share my goals with my line manager, in the hope that they’ll be able to help me find useful opportunities to achieve them. If you don’t think your line manager is the best person to share them with you could share them with anyone else — friends, family or even Twitter 👀.</p><p>When I was on my graduate scheme I worked with my line manager to set objectives for my goals around communication, he suggested I present something I had recently learned at an all-hands meeting. In this case I’d just learned about ES2015 updates, so I gave a very reluctant and awkward talk about the updates that I liked the sound of vs. the ones I couldn’t get my head around. It was reeeally out of my comfort zone, but a good first step into improving my speaking skills.</p><p>He also encouraged me to consider giving an external talk, but I really didn’t think I had anything worth sharing. He taught me that we really don’t hear much from junior engineers, but they have a very unique perspective that people should be reminded of. After a year or so of thinking about it and hyping myself up I eventually did it 🙈 and my <a href="https://www.youtube.com/watch?v=6sVRVCAcNh8">Junior.next()</a> talk was born which went down well at a bunch of events 💃🏾</p><p>Whether your goal is around getting better at coding, teaching or communication. Set your stretch goals, share them with as many people as possible and achieve them! 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac155206c986" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>