Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jennifer's user manual #4

Open
jenndroid opened this issue Jul 14, 2020 · 3 comments
Open

Jennifer's user manual #4

jenndroid opened this issue Jul 14, 2020 · 3 comments

Comments

@jenndroid
Copy link

jenndroid commented Jul 14, 2020

Jennifer

How I get my best work done:

I use a lot of diagrams and pseudocode!

You might see my video off- I'm still here! When I really need to concentrate I might ask if I can leave audio for a few minutes as well so I can give something my full attention, like reading Heroku logs or setting up the project files, but I will only be gone a few minutes and will come back to discuss a fix before I start working.

The role I usually take in a team:

Co-ordinator- I think the best way to work is to make a provisional plan early, even if it's far from perfect. Open dialogue will help us solve problems with it as we go along, and it's much more efficient to improve an rough, imperfect plan than spend time creating a flawless one at the outset. If no-one is speaking I will usually say something to ensure we have some direction.

My communication style:

When stressed out, I have been rude without realising it and if this happens, please tell me that I have done so straight away. I genuinely don't mean to be rude and would hate to think I have hurt someone.

I will communicate early & often- I like to make sure we all know what we are doing so we can get on with it.
I check in quite a lot with other team members to make sure I know where we are!

What I value:

  • A sense of humour and not taking things too seriously!
  • Time to get a full picture of what working on, and to make sure that my partner has the same mental model. This will save us a lot of time and really ensure we can move on together, look for fixes together, and see if our fixes and plans are good ideas.

What people misunderstand about me:

If I ask to take some time to read something with my camera off it's also for concentration reasons, and not personal! I will be a better partner if I have absorbed the task first. :)

How I like to get my feedback:

Solution-focussed please!

  • It would be great to get some feedback on how I've been as a team member at the end of the week. I had a great team mate open up this suggestion, as it can feel awkward to broach without an invitation, but I do want to be supportive and contribute a lot to the team so please feel free to DM me on Slack and let me know anything I can work on to be a better co worker! <3

Technical strengths & weaknesses:

What I like:

  • Walking through tricky code and learning new functions

What I need to do more of:

  • CSS!

Interests (programming or otherwise!):

  • Surfing
  • Drawing and painting
  • Zines, any DIY stuff & outsider art
  • Nature! Will usually totally leave my computer alone on weekends and explore a park
  • Depths of Wikipedia Instagram
@aissshah
Copy link

From what I've seen this week, calm, good at diagrams and pseudo code, knows server/router stuff

Would employ in a heartbeat 💓

@mhtien
Copy link

mhtien commented Aug 21, 2020

It was a pleasure working with Jennifer for the past two weeks! Really calm, collected and organised! Really enjoyed pair programming together and sharing the feeling of when the code just works, and also when it doesn't - it was great to debug and solve the errors too!. Jennifer was always happy to explain any code I didn't understand to ensure that the teams learning was put first.

@jessica440
Copy link

I love working with Jen! I get stressed out a lot and put a lot of pressure on myself to try and understand, Jen is very calming and helped me to understand more of the project ☺️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants