# Chris's One To One Notes
- Provide feedback (Asa)
- Review previous months (Chris & Asa)
- Discuss things that went well and what can be improved (Chris)
- Review previous action plan (Chris & Asa)
- Define new action plan

## Asa provides Feedback notes
- The quality of the code is till not up to scratch
- Issues with merging because the code was not up to standard
- Bad timing
- Some menu css was overriding other developers code
- Productivity was low
- Positive attitude
- Listen and learn from experience
- Taking initiative

## Actions from Notes
- Work together to improve these
- Improve productivity
- Start with pure JS
- React
- Css
## Wrong expectation
- Asa thought we were on the same page
- Asa saw something was not right
- Shouldn’t have been using dom manipulation.
- Not a matter of communication but rather on the same on the same page.
- Maybe reviewing the logic
- The confusion: how to use javascript was the misleading part
- Work together to review the js skills, and be focussed on the philosophical part
## Assumptions were made on both parts
- Don’t look at these things as negative but rather as learning prospective
- A journey
- Satisfaction on growing

## Previous Months Notes and work
- End of Probation Review 19/03/21 was the last One to One we did.
- Ill 31/03
- Husky automation and UI navigation API 12/04/21
- Menu component started 12/04/21 – 30 /04/21
- KeyBindings started 05/05/21 -10/05/21
- Laptop broke 12/05 – 13/05
- Mobile version of Menu 17/05 - 19/05
- Presentation 20/05/21
- Panel Editor Menu 21/05 – 30/05
- Holiday 31/05 – 06/06
- Grooming all of the tasks for Theseus and planning
- Holiday 14/06 -15/06
- Modal 16/06 – 18/06
- Modal 21/06 -25/06
- Last minute changes causing issues 28/06 – 02/07
- Final Push for Demo more issues 05/07 – 09/07
- Reviewed code and updated locally 12-16/07
- Jsdocs, Storybook, generators and office covid situation 19-23/07
- Finished Jsdocs review, storybook analysis, and deep proxy comments 26/07/21 – 30/07
## Review Previous Months Notes
- Take on smaller chunks of code
- Leave the comfort zone
- Be pragmatic is creating stress because of lack of knowledge.
- Don’t take a ticket that could make me stressed
- Balancing

## Discuss things that went well and what can be improved
### Pros
- Always professional
- Never emotionally reacts to criticism

### Cons
- Typos and naming conventions
- Pressure got to me because I didn’t know what I was doing.
- Struggled with traversing data
- Unforeseen events caused problems
- Lack of modern Js, React, css experience showed.
- Sticking to ES6 standards were not abided by

### Review previous action plan
- CSS day?
- Forget previous work experience?

### Define new action plan
- Even on your own you need to write out the code in order to follow the standards.
- Train eyes and brain to apply the rules first and write code simultaneously
- Even if copy some code refactor to rules.
-
- Excellent React examples to follow.
- ES6 standard reviews
- Css Day
- Review Action plan on 27/08 and then again on 30/09

## Plan
- Writing modern js. Using vanilla js and understanding all concepts and meticulousness.
- Try to find the best way
- Need React, be able to write react component
- Possibly html and css
- All of the rules are implemented the same.
- The only thing different is the solution.

## Questions for Chris to answer
- What is modern js?
- What are the basics of react component?
- What are the Basics of redux?
- Assimilate the knowledge
- Let’s organise things and I get gratification.