HTTP 200: Paige Found
Chances are, I’ve either directed you here, or you’ve been spelunking through my open-source projects and talks: in which case, welcome! Take a look around, read through my principles (listed below 👇), and let me know if you have any questions.
Looking forward to working with you!
I prefer to work from home, but love serendipitous hallway conversations + getting to know my coworkers. My ideal work week would have 3 - 4 days in the office, and 1 - 2 days working from home, or from a coworking space.
Speaking of coworking spaces: let me know if you’d like to explore a new one, or if you have recommendations! I will spend at least a couple hours in one in each city I travel to. Some favorites:
This list is continuously evolving, so keep checking back!
I am currently based in beautiful Palo Alto, CA, just northwest of the Google campus - and have mapped every coffee shop within a two mile radius. Let me know if you’re in the area, and let’s caffeinate! ☕
Previously, I’ve lived in:
I am available via text message, email, and Twitter at all times - sans plane rides and sleeping hours. I will respond to all of the above within 5 minutes of receipt, if urgent. Always feel free to text me if you need something and I have given you my number.
My email response times are extremely right-skewed, and look a bit like this (x-axis = days):
Folks who are adept at spotting opportunities to apply machine learning and automation to existing business processes will inherit the earth. That’s the only way to win: by bringing data to opinion fights; and making every decision data-driven.
On a similar vein: the most effective engineers (and leaders) are curious humans — scientists, even if they don’t know it — and they’re always, always asking questions, formulating hypotheses, running experiments.
If you can’t communicate your findings or collaborate with others, your career will be over before it begins. Science and engineering are team sports. Any successful open-source project will have a strong emphasis on communication, collaboration, empathy, and respect - not just engineering. A thread.
“Try never to be the smartest person in the room. And if you are, I suggest you invite smarter people… or find a different room.” Always choose an opportunity to learn, to grow new skills. Always.
Communities are powerful, fragile things and must be nurtured over time. Be kind; have empathy; respect differing paces. Everything is about the community: making it collaborative, caring; a collective. A group of passionate people who care about each other’s success. If you can build this, you can build anything.
Am so impressed by the level of care and effort each @docsmsft article, tutorial, quickstart, etc. receives before it’s pushed to production. It’s a commitment to empathy and respect: welcoming people at whatever level they are, and patiently helping them move up to the next level. Docs are a developer’s first impression of your product. Make them awesome.
Someone very wise once told me that throughout a career, you’ll meet people — and you’ll help, support, and encourage them, not even thinking about it. But those influences will change lives; and if you’re lucky, you’ll find out later.
This year was the first time I’d ever heard the phrase “PhD or GTFO”, and I don’t believe I’ve ever been more nauseated. Acronyms don’t equate to worth, or industriousness, or character. Have met many brilliant folks without a degree; and PhD’s without creativity, empathy, or work ethic. I’ll choose the former, every time.
I would be delighted to speak at your [meetup / event / conference], and I am definitely open to [writing a book / creating a course / creating videos or written content]! There are just a few items we need to address beforehand.
If you would like to have me come speak at your event, please donate all suggested speaker fees to either Women Who Code or The Last Mile.