DEV Community: Sui

What I Learned 4 Months Into My First Developer Role

Sui — Mon, 21 Sep 2020 19:05:52 +0000

Hi there, if this is the first you’ve seen of me, you may gain some insight into who I am here, where I discuss my neurodivergence! In brief, I have been diagnosed with adult ADHD, Depression and Anxiety, all things that I strive to manage on a day to day basis. And these facets of me help to define how I’ve managed to navigate and grow in the world of web development!

Being someone who graduated from a Bootcamp, there was a small learning curve when I realized that when I left Juno College of Technology, formerly known as Hacker You, we were given foundational knowledge. The building blocks so to speak, towards curating and crafting our own journeys. We received hands on guidance on how to work and navigate mark up languages, like HTML and CSS, and then taught about programmatic and logical thinking via JQuery and JavaScript, and then launched in the realm of frameworks and databases via ReactJS and Firebase. Throughout it all, we were given opportunities to learn how to work with Rest APIs, and manipulate data from external libraries and databases to work with our own projects. And the reason why I say this was/is foundational knowledge, is that, we aren’t supposed to stop here.

I started looking into what a potential job might require of me, what I’d need to learn, and how I could get a job. I hope to land something quickly, because my financial situation was one that needed an injection of cash ASAP in order to help alleviate some of the pressure from debts and creditors. I had made a few poor decisions in the last few years that I needed to pay off, and start fresh from. So I hit the ground running.

I found my first role, with an amazing team, and a super star lead within a month of looking seriously after graduating. Something I credit to the amount of daily networking and studying I was doing on a consistent basis. I talked to everyone in the tech twitter community, joined several online communities, Facebook groups and just went all out. While working on my portfolio, applying to jobs, and looking into the next set of languages I wanted to learn once I felt more comfortable with my foundational skills. When I landed my first role, the decision was made for me. I’d be working with Wordpress, PHP and React-Native.

Some things I learned in my first 4 months:

Every day was, and sometimes still is, a constant battle against feeling absolutely fraudulent, and wondering if I’d be found to be insufficiently skilled, and fired. A mistake. To this, I think we all feel this way starting out, for me, learning to figure out the answers to my challenges, and being positively received by my seniors and my lead/boss whenever I had a question helped to alleviate a lot of the self doubt I was feeling. To further combat this, I’ve picked up courses via udemy and a few others to help speed up my learning, and help gain more of the fundamentals of the core stack I’d be working with. You’ll be able to follow along with my progress on my twitter!
Working from home means that the work follows you everywhere, it’s important to have boundaries with yourself, and carve out time where you’re not at the computer, beating your head against the keyboard, and/or frantically researching on stack overflow… or is that part just me? When I first started out, I spent every day in front of my computer, determined to just force as much time and knowledge into my brain as possible. I swore I’d defeat my impostor syndrome through just, learning more, and doing more! By the end of the first month, I found myself staring blankly at a very simple line of JQuery code and drawing blanks. I walked away, like they said to in Bootcamp, took 15 minutes, and came back, and cranked it out. Breaks are important. Especially now when the world around us is going through some radical changes. Now, I like to take Saturdays to get out of my condo, go spend some time somewhere where tech isn’t the predominant thing. I go for hikes, learn something different and new! I’m thinking about taking a pottery class! I’ve been in LOVE with hand made mugs lately! Sunday evenings, I’ll sit down to do my courses, and spend a few hours on each, before I go to bed for the night. Get my head on for the week!
Don’t wait until you hit a roadblock to learn more. Take the time to learn a little everyday, even if it’s an hour and nothing more. I found that when I took the time to sit down and dedicate time to learning the fundamentals of the stack I was working with, when I returned to the projects I was working on, suddenly it didn’t feel like I was wading through quick sand, with each function creating uncertainty and more questions as I strove to figure out what was happening. The process of learning the fundamentals helped to reassure my understanding of the code, the language and the framework I was working with; and today I can recognize that alot of the frustration and anxiety I had been faced with, was with being unfamiliar with the fundamentals of the functions/code base I was working with. I drew blanks often, and didn’t trust in my own ability to read/understand the code I was working with. Which leads to my next point!
Trust yourself, and believe in your ability to learn. I felt so small next to the great senior devs on my team. I looked up to them like gods of my tiny universe, who could do no wrong, and would never make mistakes. Thing is, they make mistakes too, the difference is that they know enough to undo, repair, or fix whatever went wrong, faster, smoother, and more efficiently than I do/did as a junior. MY fears, were absolutely rooted in doing something I could not repair or undo; or not knowing enough to make sense of what was happening enough to try and figure it out. And once I learned my way around the environments I would be working with, this too eased. I still panic, but it’s a manageable panic, where as before, I was sure I’d get kicked to the curb at the slightest ‘dumb mistake’.

I’m not sure that the uncertainty and anxiety will ever fade for me completely, but I feel much more comfortable with my level of knowledge and skill. I have moments of panic, where I make a mad scramble and learn as much as I can within a 24 hour period. And in those moments I’ve often been reassured, comforted, and supported by my team, and the people around me who care and see me. I owe a lot to the people around me, for so much more than being a shoulder to lean on.

As for my job, thankfully I’m still here, and I hope to stay for many more years!

Learning Code with ADHD: Lists

Sui — Tue, 14 Apr 2020 08:47:53 +0000

Things have been rather chaotic lately, and the stress of Covid and everything around it made things a little harder to keep track of lately. Let me start with my official diagnosis received last week, while in my fourth week of self-isolation. Because of this, I decided to share my experience with ADHD while I studied code at Juno College.Those who know me well, will recognize the signs as I go through the various ways I've experienced my ADHD over the next series of posts. Others will be surprised, because on a good day I tend to manage my more obvious symptoms well. In fact, because I managed them well, and because I am AFAB, and the symptoms in young girls can be very different from that of young boys when developing, the signs were missed by my family, most of my friends, and my doctors.

It was often hard for me to focus, I learned patterns and behaviors that would help me skate by most days without notice. So I don't blame anyone around me for not knowing, and not noticing. Like many who aren't diagnosed or have more obvious symptoms, I got really good at pretending to be 'neurotypical'. When in fact, there was a near constant storm of thoughts and ideas demanding my attention inside my head.
No one caught on that I was going through anything, beyond comments and complaints about how careless I was when I slipped and was 'forgetful', when friends complained that it seemed like I didn't care when my attention wandered mid conversation, or when I didn't realize that I had said something that seemed callous and uncaring. And because I lacked the knowledge, the language, and the support; I was often accused of being uncaring, mean, and a bad child/friend. I struggled in my mental space, resulting in a life-long ebb and flow of anxiety and depression.

What most days are like for me, are most easily described as turbulent oceans of thoughts that crash up on the shores of my awareness. I could be watching television, and something would remind me about a time, somewhere else, and while my eyes would still be fixated on the screen; my mind would be wandering off somewhere else. Because of this, organizing my mental space was extremely difficult, and I learned in my late twenties that lists, the presence of a material document of items, whether written or typed, helped significantly to organize and put things into a more defined, solid and clear space. Something I could rely on as an anchor point when my mind was prone to set adrift with little warning. A dock to moor my boat to, so to speak. Without it, I'd start one task, only to find myself on a completely different task minutes later, moving through a mental Rolodex of tasks I suddenly remembered I had to do or complete while in the middle of another, and never getting anything done. What I did manage to get done, was shoddy at best in quality. And that I rarely if ever finished anything was an ever growing pit of despair. I don't know if you can relate, but it certainly crushed my self esteem, and hurt my belief in my ability to get anything done.

I'm writing about my experiences to maybe show people who experience the same or similar that they're not alone. Hopefully my story can help a little. Maybe knowing that I managed to get from where I was, to being a developer now, can give hope to those who doubt that they can.

So how do I manage?

It seems cliche, but I made lists.

I've already expounded on the fact that my mental space is turbulent and sometimes unpredictable, and as a result a list of concrete itemized to-do things helps to act as a stabilizing center for me to return to when I'm lost.
When I started working with lists, I was perhaps, a little over eager, and a bit over-enthusiastic. I had long 20-item-plus lists that I intended to complete over a week to a month. All I did was overwhelm myself with how much I 'needed' to complete. And because I already lacked the self-confidence to believe I could, looking at a list of more than 5 to 6 items felt insurmountable. So the trick for me, was first accepting and believing that I could complete things. My lists are built around attainable accomplishments towards small milestone achievements. I'll start with a few small tasks that would take a few minutes to finish and get out of the way. Even though these tasks were small, and for many, minuscule. It served to build up a degree of self confidence some days, and at minimum, removed smaller tasks and got them out of the way. And then, I will move up to a slightly heavier task that I know I can accomplish, before hitting at the task that presents the largest challenge. But lets start from how I set up the day for myself:

My days actually starts with the night before. I will make a short mental and sometimes written list of what did I need to do first thing in the morning to start the day. It's the same every morning, and in the beginning it used to live as a post-it note on my bathroom mirror. Today, I can remember it without too much challenge if nothing unpredictable happens to throw me off course. Usually it looked something like:

Do I have any appointments? If yes, what do I need to do to prep? If no…
Do I have any deadlines? If yes, am I on time? Do I need to catch up. Do I need to make time for more work to be done? If no…
What are my priorities? Tomorrow? The day after? Check my calendar.
Make my to-do list for the day.

In the morning, I'd run through that list, and then make my work to-do list with those things in mind for the day, which usually looked like:
Small tasks first, usually household necessities:
Send off email to [person]
Call [business] and confirm information.
Pay [x] bill. Record for budget.

This may not seem like a big deal to some, but I had times where I forgot I had to pay a bill. Months, where I would remember and then forget in the next instant that I needed to pay my hydro bill, or my internet bill, or that I needed to book an appointment; any number of small detail. And then my lights would get cut, or I'd lose internet or get a service suspension letter. I once completely forgot I'd made an appointment to meet with a client on a Monday after a weekend, and didn't prepare, didn't remember until hours afterwards, and lost the client, and the potential for income. These 'forgetful' moments resulted in lost time, friends feeling like I didn't care enough, my credit being severely damaged, and so much more. So I make lists, calendar reminders, appointments for myself to help me remember. Because it wasn't just being distracted that was the issue for me, it was that when I realized that there was something I had to do, I couldn't remember what it was.

Having these items crossed off also helped to reassure me that I did complete a task when I needed to, if I suddenly couldn't remember doing it later on in a panic.

It takes a lot of energy to pull myself out of frenzies, moment of anxiety ridden spirals over lost time, distracted wandering, and generally set adrift mentally. More than it takes to have a list handy, and check it, take a moment to breathe, do my best to settle my mind, and move to the next task.

Bigger tasks, and I'd try to keep these to 2–3 at the most:

Review today's lesson, make notes. Did I not do this yesterday? Can I do more 2. today to catch up?
Plan out goals for today's work.
Work on project.

The amount of work I can do in a day varies, but I have a pretty good idea of how much energy I have at my disposal before the effort involved in a consistent state of elevated self-awareness and redirecting mental wanderings to focus and refocus becomes exhausting and I stop working for the day. I also take frequent breaks to help stretch out how much I can do in a day! So your mileage will vary if you're also someone with ADHD. You may be able to do more, you might be able to do less.

And here's something I had to learn to accept about that; it doesn't make you any lesser than, or better than the next person.

You do what you can, and each step forward, no matter how fast, or slow, is still progress.

Making lists also had the unintended effect of attaining personal achievements. Each time I was able to cross off an item, I felt better about myself. It meant that I did something productive, I achieved a goal. It's a stepping stone, no matter how big or small, and enough of those combined, consistently always brought me to my goal.

The hard part about learning to make these lists, was accepting that I needed them; and then staying disciplined to them. I hated myself for a long time for not being able to get things done, forgetting appointments, or getting distracted. And at first, lists made me feel infantalized, and to a degree, like I wasn't capable and therefore broken. I resisted accepting or adopting anything that could be seen and interpreted as evidence of my neurodivergence because I was afraid and ashamed. It took a long time for me to come to terms, and it turns out, that lists did the opposite for me.

Over time, being able to witness my own accomplishments, experiencing daily achievements, being able to finish projects, and get results has done wonders over the last few years I've fully adopted what I now fondly call "structure" into my day to day life. My confidence has grown, and I believe in my ability to grow, learn and function.

I am neurodivergent. I am very capable of learning, adapting, and functioning though my tools may be different.

So how did this look during Boot-camp?

Clearing my life for boot-camp helped to simplify my life and day in significant ways. I put a pause on my real estate career, told friends and family I'd be gone for a few months because I was changing careers. Happily, everyone was supportive and encouraging.

While studying at Juno, my days started at 7am in the morning.

Shower, Eat, Make Coffee, Get out the door. Usually, I was out the door by around 8:30–8:45am nearly every day.

It took me an hour to drive into Toronto everyday, but I liked to try and arrive a half hour early before class started at 10am. It gave me time to settle in, get water, make another coffee, greet my class mates, and clear my head from the morning if I needed to.

10:00am - 11:30am was our first section of the class.
11:55am - 1:00pm, where we'd break for lunch.
2:00pm–3:30pm for another section of class learning, before another 10–20 minute break,
and then from 3:55pm -6:00pm for the last section of the class.

I found the theory and instruction difficult to follow along unless I was able to find a way to gamify the lesson for myself.

By this I mean that if I had a programming challenge to consider while we learned that day. (For example: Can I make a to-do list into a chat application with React and Firebase? Or, What would it take to make a side scrolling game with JQuery?) I could focus on the lesson with a challenge in mind, something that I could unravel and solve along side the lesson we were learning that day. Finding ways to keep my attention span engaged like this, helped me to stay focused and attentive.; preventing my attention from wandering. Still, I would miss things and so in order to make sure I was able to stay on track, I usually set aside time at the end of the day to catch up with the notes provided by the course.

That said…

Thank goodness Juno prioritized breaks as much as they prioritized everything else. Breaks have been fundamental in the conservation of the mental energy needed to maintain focus for a longer period of time without burning out.

After class, I liked to stay anywhere from a half hour to two hours to work along side my classmates, to get help and give help wherever possible on complex lessons I didn't quite understand, or to work on a project we were assigned. The infectious energy of my cohort, was energizing and I was able to work longer and more efficiently. It's for this reason that I genuinely attribute a lot of my love for development to the energy of my cohort. While Juno itself stands on it's own as a large contributor towards my love of coding, and is very much a large part of my journey into being a developer, the people I took this journey with made each day a joy and pleasure.

Leaving Juno between 8:00 and 8:30pm, I often reached home around 9pm when I would eat something light, and take notes and review the lessons we had covered that day.

I preferring to write and jot down thoughts alongside the notes from the lesson instructions provided. Perhaps it's a fact of my generation being one of the last to have gone through a significant stretch of life without being attached at the hip to a phone or keyboard, but pen and paper still work the best to help me remember anything.

So I write.

I take notes of each lesson, pen and paper each block of code, so I notice each fine-text and line that I may have missed earlier.

When I finish that, I do my best to make sure I take a moment to relax, and mentally turn off before I head to bed. This happened usually around 1–2am though I tried to aim for midnight bedtime.

The next day I wake up at 7am to do it all over again.

My days are lists, of routines I can still be flexible and deviate from, but for the most part exist as a framework for what I need to get done on a daily basis.

In following my lists, I find that I can focus and stay on track to accomplish the best and most in my day to day.

This daily practice and schedule is what worked the best for me. I believe it was a combination of the people, my adherence to my own learning structure, as well as the resources made available via Juno's instructional framework, and the learning material that has come together to help me achieve what successes I've experienced thus far.

I said early on in my boot-camp that I liked structure. Perhaps this post will shed some light on why that is now. The experience of boot-camp left me feeling full and accomplished every day allowing for progress in quick and consistent bursts of understanding and application, and along side my understanding, my confidence grew with it.

Well this post is long enough, and if you made it this far, I thank you for sticking with me! I'd love to hear from you! If you are or aren't neurodivergent, or know someone who is, I invite you to share your experience!

(Cross Posted To my Medium Blog)

Nevertheless, Sui Coded

Sui — Mon, 09 Mar 2020 01:52:19 +0000

When Do You Know You’re A Developer?

Those who have listened to me frantically research, watched me pour over various articles, code samples, and listened to me ask what feels often like 10,000 questions will also often hear me speak on how I’m not confident.

I still don’t know so much!

Can I assign a value to a span tag? Can I read that value? How do I push into a specific key in the database? Where should I go to look up how to do …. and the questions go on.

I’m told that this type of questioning, the uneasy sense of uncertainty and lack, the various dreams of code, running after you in dark hallways — no? Okay, maybe that one’s just me. But, in all seriousness, this never stops. I’ve seen various devs on twitter speak on how they’ve been in the game 10 years, 20 years, and so on, and they still often feel like they don’t know what they’re doing. And maybe there’s the lesson.

Get comfortable with being uncomfortable.

Being a femme presenting East Asian Queer person, discomfort is a daily experience. And in many ways, it’s almost background noise until something happens to bring it to the surface. Being alone on the way to the car from school after 10pm on a quiet street, being cat called; and that’s just the daily stuff.

I question daily whether my presentation will cause discomfort. Whether I’m not feminine enough, if I’m laughing too loud, too assertive or too opinionated. These questions persist as I consider the vastly male dominated field of tech and software development where I hope to build a thriving career. I’ve heard many things about it being very old-boys-ie, cliquey, and sexist. A younger me, would have found that enough to avoid the field entirely. I’d already been told once before that “girls were too dumb for code”. A sentiment that both embarrassed me in front of my class, as much as it both saddened and infuriated me. As an older me, current me, the me that has lived a little longer, seen a bit more, and done more, I recognize that things don’t change when they go unchallenged.

So I’m challenging, my own doubts, fears and insecurities, as much as the views, opinions, doubts, and actions of those who thing I can’t. I still have my insecurities and I’ll likely continue to have them, though I’m not going to let them stop me from getting where I want to go. Knowing that I’m not alone in this helps. Each day is a learning process, but I’m gaining newfound confidence (one I’d lost years ago) in my ability to learn, solve problems, and find answers. I’m learning to get comfortable with being uncomfortable.

That being said, I’m happy to see that the field is changing on a daily basis. Femme presenting coders are all over twitter, and a reach for inclusion and diversity seems to be the thing. It warms my heart to see people support one another, regardless of identity, race, gender etc., and I’d like to highlight some inspirational people, and in honor of it being #internationalWomensDay,

My Top 5 Inspirational Women in the Tech Industry

Alyssa Miller, https://alyssasec.com/
Hacker, Security Evangelist, and Cyber Security Professional.
Ms. Miller is a chapter leader for the Women of Security meet up group, and currently holds a Certified Information Security Manager (CISM) certificate. A public speaker, with a passion for everything she puts herself into. Her blog is amazing, and if you’re interested in cyber security, or public speaking, her blog will be a great resource. I started following Ms. Miller out of a genuine curiosity about the field of cyber security. Being someone with high aspirations, I wanted to know more about the field, the people in it, and what they’ve traversed in their journey to get to where they are.
Twitter:https://twitter.com/AlyssaM_InfoSec

Helen Anderson, https://www.helenanderson.co.nz/,
The data community moderator at dev.to, who teaches, mentors and focuses on those who are underrepresented in the tech sector. A writer, and a vocal human who has a passion for analytics, database and block chain technologies. She currently has 10 free copies of her book on SQL, AWS, and Big Data on her twitter!
Twitter: https://twitter.com/helenanders26

Kesha Williams, http://kesha-tech.s3-website-us-east-1.amazonaws.com/
Ms. Williams, is a software engineer, an international keynote speaker, a AWS machine learning hero, and among many other things, a S.T.E.M. advocate. She’s passionate about empowering women, youth, and underrepresented people in the spaces of emerging technology and innovation. Ms. Williams is one to keep an eye on, she’s involved with so much of what currently fuels the world of technology as we know it. I hope to one day get to sit in on one of her keynote sessions. Ms. Williams is one to keep an eye on.
Twitter: https://twitter.com/keshawillz

Tracy Chou, https://triketora.com/
Ms. Chou is a start up founder, software engineer, and diversity advocate. Currently building an app to help with online harassment, being someone who has spoken on her being the victim of harassment through her journey. She is starting her own company, to give people a safer experience online, to empower, and protect them from online bullying and abuse. She’s an inspiration, and someone definitely worth following.
Twitter: https://twitter.com/triketora

and last, but definitely not least:

Heather Payne, http://junocollege.com
You can read all about her here, about 2 weeks ago now, my stand-up group and I sat down and had lunch with the founder and CEO of JunoCollege. It was a pleasant, round-table type situation where everyone shared their story about how they got into bootcamp and coding. Heather listened, and I mean, it felt like she actually listened. She offered her own experiences, and shared her journey (quickly because we were short on time, everyone had such unique stories), and imparted some of her own ideas about coding as she was learning it herself. Also a Founder of Ladies Learning Code, she is an advocate for digital literacy for women, seeking inclusion and empowerment for the underrepresented.
Twitter: https://twitter.com/heatherpayne

I could keep going, but this is long enough, and I need to study for my final test before the exam.

Be good friends, keep going and don’t give up.