Amber's user manual

[amberrignell]

Amber (she/her)

How I get my best work done:

I like talking through what I'm doing and appreciate it when others do this too.
I like writing a draft of the code even if I know it'll throw some errors and then coming back to debug it rather than trying to get it perfect from the start.
I do a lot of console.logging to figure out what is going on where.

The role I usually take in a team:

I like making lots of suggestions, happy to take the lead if need be but also step back when I am not the facilitator.

My communication style:

I like it when people are direct and open about how they're feeling (confused, frustrated etc).
I always appreciate if people throw in a few jokes to lighten the mood if there ever has to be serious conversations.

What I value:

Directness, no drama, people who are easy to read.

Sharing tips and tricks. If you learnt something cool in your previous group, I'd really appreciate if you could briefly mention it/show me (even if we might not be using it in our project).

What people misunderstand about me:

How I like to get my feedback:

I really appreciate getting feedback and will likely ask you for some during the SGC.
If there is ever something I am doing that is bugging you throughout the week just drop me a message on slack and ask if we can have a quick chat so you can let me know :)

Some things I'm working on:

• I can get a bit too enthusiastic about my own ideas when we're trying to come up with projects - working on being more chill about this !
• Making sure I create an environment where everyone is comfortable asking questions. I love explaining code and find it super helpful to see where my own understanding is at so feel free to ask as many questions as you like. I'm also super happy to take 5 minutes over the weekend or in the evening to go over code if need be.
• Not forgetting to take breaks - I get really focussed on finishing when we start writing code which means I forget to take breaks, but I do need them and believe it's important to take 3-5 minutes every now and then to walk around and switch off for a bit.

Technical strengths & weaknesses:

Figuring out the big picture of what we need to do
Writing pseudo code
I love debugging

Weaknesses:
Not great with design
Not great with css either

Interests (programming or otherwise!):

Psychology, travel and different cultures, books (last read: The Man in the High Castle and L'immeuble Yacoubien --> just started reading: The Aleph, Borges)

[JoshDAO]

Amber is an incredibly strong member of a project team. She has no issues with trying out completely new technologies and doing the hard work to understand how to use them, while also communicating the technical details to the rest of the team. She is also very resilient in the face of challenges - you can count on her to find the root cause of that bug and fix it.