Skip to content

Azizi's user manual #5

@azizi-a

Description

@azizi-a

Azizi/Zi (he / him / they / them)

How I get my best work done:

Coding:

  • I often like some time to consider the problem quietly when getting started or when hitting something particularly sticky.
  • I also like to talk through a problem as I'm working it out - Feel free to join in and ask if my steps are unclear.
  • I like to draft code steps into the code to outline the logic or comment them in as pseudocode, then returning to fill out, tune up and/or debug them.

Generally:

  • With pauses for thought.
  • With a good outline of a plan.
  • Talking to myself.
  • Without to many noises to distract me. I have to turn music off if something is particularly mentally taxing.
  • In the morning (madness I know).

The role I usually take in a team:

I tend to lead, but I'm very happy for others too. I have a lot to learn to be a good leader, but like to get the ball rolling if there is initial hesitation in a project.
I would appreciate feedback about this if you have any to give.

My communication style:

  • I am vocal and animated.
  • I like to understand exactly what you mean and I like to make sure I've been properly understood.

What I value:

  • Honesty and empathy.
  • Asking questions when you don't understand.
  • Asking questions to make sure I understand.

What people misunderstand about me:

  • I often take a deep breath when thinking. If you hear that it's not an expression of frustration or relief. I'm trying to work out what to say next or what that function does.
  • I'm always happy to change my mind. I don't stick to choices just because they are mine, so if I explain why I think something is the best option I am not saying that we have to do things that way. Feel free to point out the floors in my reasoning or come up with a better option. I will do my best to hear, understand and be persuaded by you.

How I like to get my feedback:

Work:

  • As a mix of things done well and where improvement's could be made.
  • Verbally I appreciate key points at the end of a lengthy explanation if there is one.
  • Written I like bullet pointed lists, or another brief written form I can respond to point by point.
  • I like being given the chance do do something wrong once before I'm corrected.

Personal:

  • If you find I do anything that is making your day harder please say and I'll do my best to stop. A common one is forgetting to mute my mic so you hear my very loud keyboard. ⌨️ 🔊 Don't hesitate to remind me. 🤫
  • Similarly, if I'm doing anything that's making your day easier, tell me and I'll keep it up. 👍

Technical strengths & weaknesses:

  • Dyslexic, so slow at reading and bad at spelling but great at spotting abstract patterns and spacial understanding.
  • Limited but varied coding knowledge.
  • I forget names of things all the time; people, films, words - names of functions is the tricky one for code.
  • Good at breaking down the problem into logical steps for JS, though I'm finding React a little tricky atm.
  • Good at logical problem solving in general.
  • Good at mathematics but sometimes oddly bad at it (mixing up numbers etc. - dyslexia again)

Interests (programming or otherwise!):

  • Systems - How things works (machines, technologies, economics, politics, history, etc.)
  • Science - Both scientific knowledge and the process of science.
  • Entertainment - Which I care deeply about (video games, TV: mostly big budget and well written stuff like West World atm, Reading: Lots of Sci-fi and non-fiction)
  • Exercise (Climbing and cycling mostly)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions