It’s been 6 days since my IAAP Web Accessibility Specialist exam and I’m still recovering from the marathon study session the led up to it.
I feel OK/good about my performance, but I’m still unsure about what the results will be. A couple things are for sure though: after studying for the exam, I’ve felt far more confident in my understanding of expected widget interactions, and my fear of the official WCAG and WAI-ARIA documentation has subsided a bit. 🧛
One of my new favorite haunts is the Web a11y Slack. If you’re at all interested in delving into web accessibility, there are some great teachers in there who are always available for questions. 👩🏫 Join us!
Oh Wednesday, glorious Wednesday. This week has been a perfect emotional storm of work deadlines, impostor syndrome/panic attacks, wet weather, and npm issues (I’m talking to you, v3). But I’m making it through (read: barely hanging on) with the support of many a vitamin D tablet and green smoothie.
On a more positive note, tomorrow will be my one-year anniversary at my current company, and I’m feeling so grateful that I magically ended up here after a long and windy road following my dropping out of grad school. It’s amazing to be part of such a tight-knit, supportive group doing work I love.
Next week I’ll be taking the IAAP WAS certification exam so that we can highlight our expertise in web accessibility and serve our clients and their customers better. ✌️I’ve got those pre-exam jitters — wish me luck!
React has on my to-learn list for what seems like ages. I’ve tried diving in numerous times over the last few years, but either the time wasn’t right or I couldn’t find the right course or project to work through. Some courses were too hands-on, while others were too hands-off and quickly led to frustration.
So I just sat with my skill set and waited to find the motivation to jump back in.
However, with work projects on the horizon that will most likely be built using React, I decided it was high time to jump on the framework bandwagon.
You’re wondering if you’re smart enough — talented enough — to make this career change into web development. You try hard for a week and then your motivation finally takes a nosedive when you can’t get your code to work.
You can’t wait until you’re confident in your skills and feel equipped to tackle any problem.
Let me tell you something.
It will never feel like that.
Part of the job is learning to be OK with feeling ill-equipped, underprepared, and like you’re just barely scraping by. It’s called impostor syndrome, and we all have it.
In this field, there’s so much to remember and things are amorphous and ever-changing, and The Right Way™ is up to interpretation.
You’ll grow the most when you’re wedged in that uncomfortable spot where ‘what you know’ juts right up against ‘what you don’t know.’
So don’t stick with what’s comfortable.
Don’t avoid a certain popular technology because, in your opinion, it’s a nightmare to work with.
That probably means you haven’t worked with it enough. You haven’t gotten to know it well enough to appreciate its quirks, nuances, and special powers.
Never stop learning, and you’ll never stop exceeding your own self-imposed limitations.