Hannah Clarke

@hannahc.bsky.social

Design System UI Engineer Music listening, photo taking, road tripping, app building, void staring. (she/her)

Does anyone know of a cross-border US/UK accountant who can help with company registration in both countries? Bit of a longshot ask, but figured someone might have a recommendation 🤞🏼

So far today I've made my last student loan payment (finally debt-free from that international politics degree I finished 15 years ago and get so much use out of 😑), *and* got tickets to see Phoebe Bridgers in November. Pretty solid Wednesday so far.

When you've been in a year-long battle to convince teams that your coded DS component packages will help them, and an engineer tags you out of the blue suggesting your component is a far better alternative to implementing something new because you've already done the work for them 🥹

I think I'd assumed after moving from full stack to frontend and then specialising further as a UI Engineer, that I'd spend pretty much all my time writing frontend code... and yet here I am again lost in a sea of yaml trying to get pipelines working.

This week I have learnt that a lot of unnecessary stress and confusion can be avoided by clarifying what you mean by terminology you assume everyone uses in the same way. In this case - "components". We meant buttons, links and other atomic stuff. They meant entire dashboards.

Research question for you - if someone shares a playlist (or a track, album, anything) that you like the look of from Spotify, but you're an Apple Music user, what do you do? (Swap either streaming platform for one you don't use and one you do) #music #musicsky

I've been using Stencil to build our Design System web components and it's really great, but the amount of time I've spent figuring out things that are a little too niche for the documentation is insane. Time I could be using to write up the things I've been figuring out without documentation... 🔄🙃

After spending a lot of time getting our Design System infrastructure ready to go using Stencil for web-components, writing custom processing scripts to make generated React components *perfect* for React product devs, being told we should just be building in React is so incredibly demoralising.

Feel like I should get time-off-in-lieu for the nights where I try to debug an unresolved issue in my sleep. Dreaming about an inconsistent build script is in no way restful 😴

Hey #frontend developers! Someone has put forward the argument that "the future of React is React Native" as a way of fighting a Design System built with web-components (outputting wrapped components for React). Has anyone else come across this? I've not heard anything that suggests it's likely.

I've mostly been pragmatic about losing my job, but now I'm officially on my last day and the saddest thing is seeing so many great, talented people in the same boat. This industry can be so ruthless.

Without fail, every time I try to test something I'm building with a screen-reader, everything inevitably crashes and it berates me with "Chrome is not responding" over and over. Sure, cool, it's not like I have to submit this assignment in 2 days or anything 😒

Finally won the waiting list game and got an ADHD diagnosis last week. Great to know I'm not useless and lazy, but all I actually won was a place on another waiting list. Turns out knowing what you already suspected doesn't make anything better.