<?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 Will Wearing on Medium]]></title>
        <description><![CDATA[Stories by Will Wearing on Medium]]></description>
        <link>https://medium.com/@willwearing?source=rss-a25687d5edc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rQ5uqQiJA5nZdOXB.</url>
            <title>Stories by Will Wearing on Medium</title>
            <link>https://medium.com/@willwearing?source=rss-a25687d5edc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:49:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@willwearing/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[Labs — An honest reflection on one of the best months at Lambda School]]></title>
            <link>https://willwearing.medium.com/labs-an-honest-reflection-on-one-of-the-best-months-at-lambda-school-c7c7c856d8bd?source=rss-a25687d5edc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7c7c856d8bd</guid>
            <category><![CDATA[okta]]></category>
            <category><![CDATA[labs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[lambda-school]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Will Wearing]]></dc:creator>
            <pubDate>Thu, 04 Mar 2021 17:37:11 GMT</pubDate>
            <atom:updated>2021-03-04T18:01:42.707Z</atom:updated>
            <content:encoded><![CDATA[<h3>Labs — An honest reflection on one of the best months at Lambda School</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhgDJrXizMnbtnHeflk3WQ.png" /></figure><p>For the final sprint challenge (the last homework assignment) in Labs, Lambda (ingeniously)asks students to prepare a blog article on their experience and share it. I’ve never written a blog post before, not a proper one anyway, so thought it would be interesting to share my planning of the blog as well! The plan:</p><ul><li>Intro — who I am, why I’m writing this, how it’s structured and what’s included</li><li>Problem — Describe a problem I had and how it was overcome. If possible, show images/videos of bugs. What problem should I discuss? Few ideas: organising the team, actually figuring out what the bloody hell was going on in the code (the codebase was rather large compared to what I’d seen so far), agreeing on design, getting to know our ‘user’ and fleshing out user stories, overhauling design &amp; styling, help to figure out authentication, implementing a new state management systems, redundant API calls, major browser resource drains or fixing merge conflicts.</li><li>Solution — Describe solution, walk through the steps taken and show off how awesome I/we as a team were.</li><li>Close this blog out with key takeaways and sign off with how peeps can get in touch. (Talk about impostor syndrome and feeling shite compared to other students who murder problems whilst I sit there with little to no clue whats going on — tie this into taking on more of the real engineering challenges next time).</li></ul><p>(^This is embarrassingly short^ - I did say I’ve never done this before!)</p><p>A bit about me: I’m Will, I’m English by birth, a naturalised Australian and now live in Canada (+40&#39;c and bushfires to -40&#39;c and blizzards was a shock). My previous career was in sales (SaaS/eCommerce) and I’m in the middle of a pivot towards becoming a Software Engineer.</p><p>Why the pivot? I’ve always wanted to build. Specifically, I’ve always been interested in tech, finance and helping people make more. After 10 years of sales, the desire to change was greater than the comfort of where my career had taken me, so far.</p><p>So, that’s me, let’s get into the meat and bones of this bad boy…</p><p>First things first, ‘the team’: <strong>labs31_hrf_police_a_taylor. </strong>This team was quite simply a joy to work with. Why? Our Technical Project Lead (<a href="https://www.linkedin.com/in/taylorcurran/">Taylor</a>) was a star and true leader from day 1. All of the other students were kind, brilliant and engaging. How did this come to be? Alignment. Taylor made an active and persistent effort (from the very first meeting!) to make sure we all knew each other, understand our motivations and gave us permission to choose what we each wanted to work on. The result was a team that had self-selected roles, understood each other&#39;s why (and therefore much more capable communicators) and had agreed upon standards + expectations.</p><p>In Labs, the team was given stewardship of the project ‘Blue Witness’: <a href="https://a.humanrightsfirst.dev/">https://a.humanrightsfirst.dev/</a>. In a nutshell, the N.G.O. <a href="https://www.humanrightsfirst.org/">Human Rights First</a> have partnered with Lambda to build a web app that tracks police brutality. Considering some of the projects students are given, I actually found this one super interesting, meaningful and potentially important due to the recent social unrest.</p><p>Our team had been tasked with building an administrators dashboard for receiving, reviewing and approving/rejecting new police ‘incidents’. I, along with <a href="https://www.linkedin.com/in/maria-c-olsen/">Maria</a>, <a href="https://www.linkedin.com/in/samtarullo/">Sam</a> and <a href="https://www.linkedin.com/in/victoria-l-mount/">Victoria</a> chose to work on the Frontend. After spending some time using the site and getting stuck into the code base, we found that we had inherited a well fleshed out product. It did have some bugs that appeared to be fairly simple to fix and then some that we really didn’t know where to start. Considering that a one-page admin dashboard seemed fairly simple for a team of 4, we agreed to develop a list of improvements (thanks Victoria for putting this together) and bugs that could be tackled once we’d delivered MVP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_kILPN0OddINztLlY9sLgw.png" /></figure><p>So, what did I do and what issues did I run up against?</p><ol><li>Built and helped implement the 3rd party authorisation using Okta</li><li>UI and Styling</li></ol><h3>Auth</h3><p>When we started on this project, we knew from the Labs Docs that we were going to be using Okta to handle our authorisation. I signed up (along with Maria) as I hadn’t really practised building auth into personal projects and wanted to improve my skills and learn a new third party integration. I was responsible for building out the login component, styling and was jointly responsible for ‘connecting the plumbing’. Here’s a Loom video I shared with the team to give them a quick overview of what had been done:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F7aca98e8ab4e4c4281a7b6b5626c3154&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F7aca98e8ab4e4c4281a7b6b5626c3154&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F7aca98e8ab4e4c4281a7b6b5626c3154-00001.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1280" height="960" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7b68f25a2e74445d66f1514e16204df/href">https://medium.com/media/c7b68f25a2e74445d66f1514e16204df/href</a></iframe><p>Everything was going smoothly until it came time to actually connect Okta. What went wrong? When attempting to login, Okta would return the dreaded: “There was an unexpected internal error. Please try again”. After reviewing <a href="https://developer.okta.com/docs/reference/error-codes/">Okta’s error docs</a> and not finding anything, following Okta’s “Getting Started” guide (and realising that Lambdas implementation was quite different!), <a href="https://devforum.okta.com/t/okta-sign-in-widget-example-not-working/12956">creating a forum post asking for help</a> and finally some frantic Googling, I discovered one (now lost) Stack Overflow thread led me to realise that one bloody period was causing my issue. More specifically, in my .env file, the Okta login URI looked like this:</p><pre>REACT_APP_OKTA_ISSUER_URI=”https://auth.lambdalabs.dev/oauth2/default.&quot;</pre><p>And it should have looked like this:</p><pre>REACT_APP_OKTA_ISSUER_URI=”https://auth.lambdalabs.dev/oauth2/default&quot;</pre><p>Funnily enough, whilst I was figuring this out and (proudly) got it to work, Maria had the same error (for different reasons), fixed the bug, pushed the code and had it live. This happened throughout Labs and I wanted to quickly take the time to point out the meme (but in this case completely true and justified) of a 10x developer. Maria was, is, and will be an absolute powerhouse of a software engineer. Her ability to take a problem, digest it, work on solutions and have them shipped in the time it took the rest of us just to come to terms with what was actually causing the problem can’t be stated enough. If anyone important ever reads this — look her up, you won’t regret it!</p><h3>UI and Styling</h3><p>When the position of Design Lead, Victoria and myself put our hands up. Normally, this is a one-person only role but as we were both so eager to give it a crack, we decided to work on this together. We collab’d on wireframing (using Whimsical) and built out the basic landing page, admin dashboard and ‘edit’ components. Here’s what we created:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vrKSjlvTM457x2KH3T8NFQ.png" /></figure><p>UI and Styling introduced two new technologies/concepts to me:</p><ol><li><a href="https://ant.design/">Ant Design</a></li><li><a href="https://sass-lang.com/documentation/syntax">SCSS</a></li></ol><p>Ant Design — what a beast. I found it incredibly simple to implement and use but felt that it’s simplicity actually led to us having to taper down our desire to build elements with the exact functionality we wanted. This key take away is something that I will take forward and think about when picking up other technologies now as it really highlights the pros/cons of using existing libraries for speed vs developing custom things for personalisation. A simple example would be for the dropdown “More Info” tabs on the Admin Dashboard. Ant Design provides components that provide some of the functionality we were after but not all of it so we decided that a custom creation was in order! The code can be found here: <a href="https://github.com/Lambda-School-Labs/human-rights-first-fe-a/blob/develop/src/components/AdminDashboard/CompleteIncident.js">https://github.com/Lambda-School-Labs/human-rights-first-fe-a/blob/develop/src/components/AdminDashboard/CompleteIncident.js</a></p><p>SCSS — this was actually really fun. It took some wrangling with the docs to get it working. This command in particular:</p><pre>sass — watch ./src/index.scss ./src/index.css</pre><p>But otherwise was fairly simple. I do have some unanswered questions about why SCSS is better than CSS and honestly, the jury is still out on that one so if you have any suggestions, please see my contact details below and ping over any insights you may have!</p><p>Personally, I loved this part of the process. I found the user story focused design practice really interesting and this is something I want to spend more on.</p><h3>In closing</h3><p>Labs have been a joy, this experience is why I signed up for Lambda. It’s what the school should strive for in all units, in my (unsolicited) opinion. I’ve laughed, cried and learned a lot!</p><p>The main personal takeaways revolve around: the power of aligning teams to a single common goal, effective communication, putting yourself out there, taking on challenges that seem too hard and consistently working on your craft.</p><p>None of what we created would be possible without the team so I feel I have to make some other shoutouts: Sam, you are a workhorse and inspire me through your work ethic! Victoria, your eye for detail is second to none and I’ve loved bouncing ideas off you! Maria, I’ve said it before and I’ll say it again “You’re a wizard, Harry”. And to the rest of the team, you are all champs, I wish you the very best for the future and will watch your careers with eager interest.</p><p>For anyone that’s interested, here is the deployed site: <a href="https://a.humanrightsfirst.dev/">https://a.humanrightsfirst.dev/</a></p><p>To contact me, reach out on my <a href="https://www.linkedin.com/in/william-wearing/">LinkedIn</a> or <a href="https://twitter.com/willwearing">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7c7c856d8bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>