ABOUT EMILY
A little about Emily.
Emily is a systems architect, with over ten years of experience building both front-end and back-end solutions.
When I think back on my childhood I remember walking across town after middle school and hunkering down in the basement of the law office my mom worked at so I could play Pokemon on my GBA for the couple hours she had left to work before she ended her day.
I also remember my Pokemon obsession leading me to talking about hidden islands and secret event tickets on the Nintendo nSider forums at the city library. I was so enamored by the message board structure and design and all the systems and groups of people talking online.
One thing led to another and eventually I was making my own little crappy Proboards forum, teaching myself CSS via the limited editor they allowed on the free tier.
That feeling is still what hooks me. Sure, everyone (unfortunately) needs money to live, so I have to do this for money, but I still really do it to chase that feeling of building something up and watching it work after it’s deployed.
How I work
Understand requirements
Collect client needs and take notes and ask questions.
Make a plan
Think through what technology is needed and consider the cost for each piece.
Make the thing
Full-send a prototype and get some client feedback on the outcome.
What I bring to a project
A service-led website
Sketch a homepage, service-detail template, and contact journey that help a visitor choose their next step.
A small design system
Define type, spacing, color, and component patterns a team can carry into new pages.
Beyond the brief
I'm a communist who likes to get stoned. My apartment is a mess and I live with a couple of cats (Billie and Loki).
Good projects start with a conversation.
Tell us what you’re trying to make easier. We’ll work out the scope and who can help.