I want to code more because: I want to be more productive at work. I also want to be able to work on side projects.
I know Iβll have reached my βcode moreβ goal when: I will have completed 5 - 10 hours of coding outside of work projects. Workwise, I will have complete the project due by the end of April and added additional functionality to my other work project.
My top three assumptions for reaching my goal are:
I will get the clarification on the requirements I need for the work project
I will not get stuck in analysis paralysis.
I will find something I am interested in working on outside of work
Of these assumptions, my riskiest is analysis paralysis. I am always questioning the design pattern I am using and not sure if I am applying it correctly.
When I think about my riskiest assumption, three possible root causes are:
My lack of experience
Lack of feedback
So many options
3 ways I might address these root causes are:
Code more and see what works
Reach out for feedback (coworkers for work project and CodeNewbie community for personal)
Stick the option I pick
Of these, the biggest cause thatβs worth tackling first is just picking an option.
For further actions, you may consider blocking this person and/or reporting abuse
I want to code more because: I want to be more productive at work. I also want to be able to work on side projects.
I know Iβll have reached my βcode moreβ goal when: I will have completed 5 - 10 hours of coding outside of work projects. Workwise, I will have complete the project due by the end of April and added additional functionality to my other work project.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is analysis paralysis. I am always questioning the design pattern I am using and not sure if I am applying it correctly.
When I think about my riskiest assumption, three possible root causes are:
3 ways I might address these root causes are:
Of these, the biggest cause thatβs worth tackling first is just picking an option.