After completing all the steps in your Mission 1 email, post your "Code More" goal in the thread below! If you feel up to it, post some of...
For further actions, you may consider blocking this person and/or reporting abuse
Sometimes I don't feel like touching the computer at all for similar reasons. Then I find myself thinking about the code when I am trying to sleep!
I like using the Pomodoro technique. I ended up getting a 30 minute sand hourglass timer because I want to give myself the opportunity to keep coding after time has ran out, in case I have gotten in the zone or flow. I didnt want to get distracted by the ding of an app or timer.
Wow, this is just the thing i do. I haven't touched my laptop for whole day. And i know that, i'll think of coding just before i go to sleep. Then i have no time and have to go to sleep, so i aspire to do it tomorrow and then... it all starts again.
I find getting to bed early and getting enough sleep is hugely helpful in waking up early and then I do some of my most productive coding in the early morning. If it works for you too, you are on the right track!
Be careful focusing too much on tools like Pomodoro. The timer alone is not the answer. You will find you get a lot done, but it might not be very meaningful work. Before you time yourself, make sure you have prioritized your to do list well. A helpful practice I have been doing is writing down everything on my mind, then crossing out everything that isn't essential. Then figure out the things you need to get done to have peace of mind when you go to sleep that night and tackle those items head-on from most important (typically hardest) to least important. This is where you can start using the Pomodoro technique.
Good luck!
I think coding first thing in the morning is a great idea! Might have to steal it from you :)
yeah, no problem =)
I find I code best in the morning. Afternoon after lunch is deadly for code. Zzzz
I want to code more because: I am looking to make a big career change!
I know I’ll have reached my “code more” goal when: I have comepleted the Front-end devloper course on codecademy and i'll have a portfolio of work to allow me to start looking for new jobs.
My top three assumptions for reaching my goal are:
I'll have enough time to complete the course.
I'll have enough discipline to work hard towards my goal.
I'll have lots of resources to keep learning and keep me interested in coding even when it gets hard.
Of these assumptions, my riskiest is having enough discipline.
When I think about my riskiest assumption, three possible root causes are:
Procrastination and worrying about making a big career change.
I get stressed when thinking about the risks i'm taking and then use avoidance so I don't have to think about it.
Not having a routine will make keeping up with work hard.
3 ways I might address these root causes are:
Being more mindful and using therapy techniques to tackle anxiety.
manage my time by building a routine and following this everyday, but not beating myself up if something becomes to hard.
Try to code for atleast 2 hours a day
Of these, the biggest cause that’s worth tackling first is building a routine so I can carve out time in my day to code!
Hey everyone! Here's my Mission 1.
Is wonderful that you're aware of these things about yourself.
Perfectionism is certainly something I've struggled with for years.
One thing that has really helped break down that "all or nothing" mentality is to approach things like "experiments".
Think of yourself as a scientist, a "coding scientist", and test different options out there. You'll find things that work better or others that just don't work but everything is part of the experimentation process.
In that sense, there's really no "failure" only feedback to know when you're doing things right and when to course correct.
Also, you're now part of this community so...
Thank you! I like this change in perspective. ::writes it down in notebook:: 😆
Way to go! This is like a self-learning journey on top of skill learning! Let's not forget to always be kind to yourself through this process. This seems to be a recurring theme with a lot of developers whether they are new or a veteran in the field. We all tend to burn out and leave self-care as an afterthought. Treat yourself with small rewards after each smaller accomplishment :)
Yes, it's so easy to be hyper-critical and burn out. I continually have to remind myself that it's okay to be kind and self-compassionate. Thank you for reading & responding.
❤️
My top three assumptions for reaching my goal are:
o I need to spend at lest 1 hour a day on working on a personal project a.k.a. practice coding
o I need to learn Wordpress in order to improve my mothers’ website (starting with design; maybe add some functionality), to have first product on my portfolio
o I need to learn React
Of these assumptions, my riskiest is spending time every day for working on a personal project.
When I think about my riskiest assumption, three possible root causes are:
o I don’t know, what exactly I would like to make
o I feel scared to publish something I created without understanding how can I un-publish it, for example, if something goes wrong, I don’t want anybody to see what I’ve done, etc.
o I afraid, that I will “waste time” practicing something that isn’t that valuable for the “real life’’ jobs/situations
3 ways I might address these root causes are:
o Remember – there is no pressure to publish anything. For now, I am doing a job with added value for Visas Iespējas, so no need to put pressure on actually putting something out there just yet.
o First, practice WordPress by making a simple blog/website for HipstersGlasses – add section about Balkan Trip, section with photos and introduction/landing page. This is to practice and get familiar with Wordpress. I don’t need to publish it just yet.
o While practicing, I will come up with questions and I can ask them in morning “podcasts” with my team members. Also – by practicing and searching information I will find information related to what’s actual and what’s not.
Of these, the biggest cause that’s worth tackling first is I just opening the Wordpress and starting to play around.
My main goal for the "Code More" challenge is to finish the C++ software portion of my current project. Hopefully I will have the time and resources necessary to complete this goal in the coming weeks. I will definitely need to learn more about building GUIs for C++ programs. Happy coding everyone!
I want to code more because: Because I am stubborn. Two years ago I tried to learn JavaScript and decided, “this is just too hard." It’s always bothered me that I quit, and relying on cut/pasting from Google or hacking other people's code together is a total drag... And also because I am in a JavaScript Bootcamp and I should be writing and reading code on the daily without fail. I have committed to sharing my code via Twitter, having joined the #100daysofcode challenge. Lot’s of reasons. :-)
I know I’ll have reached my “code more” goal when: When JavaScript is as familiar as HTML and CSS.
My top three assumptions for reaching my goal are:
Due to the pandemic, I definitely have time. When life gets busy, I’ll make time.
At this stage of the game, it doesn’t take a lot of time to sit down and research some facet of JavaScript that I don’t know, because that's just about everything.
Will I be disciplined enough? I think so, because failing at this because I lack the brain for it is more acceptable to me than failing because of not trying as hard as I humanly can.
Of these assumptions, my riskiest is: That I will be disciplined enough. History shows that this has been an issue in the past.
When I think about my riskiest assumption, three possible root causes are:
a. Lack of confidence
b. A propensity for frustration when things become difficult
c. Falling behind has been a good reason in the past to throw in the towel
3 ways I might address these root causes are:
*Of these, the biggest cause that’s worth tackling first is building things vs. just writing sample code. I know from past experience that is how I learn best. *
Is there something that grabs your attention usually, like "gaming", "puzzles", etc? Sometimes it is easier to learn through the Super Mario Effect where you learn by tricking your brain into learning a new thing with something you already enjoy.
I feel like everything is so different this time around. Last time, I was just doing FreeCodeCamp with no support. I felt like a failure because it got to a point where I could not solve the challenges. Now I have found a few communities, like Flavio Copes Bootcamp, this platform and others where people are so willing to help. The other difference is that I realize I have to build stuff in addition to studying and doing code challenges. I am seeing a lot of growth just by changing these things around. Lastly, seeing code that throws an error or won’t execute used to really frustrate me. Now, these failures are my teachers. Just a different midset.
I do like gamified stuff. I wish there was something like flexbox zombies for JavaScript 😀
Good luck with all of that.
Thanks Andrew. I am going for the full immersion experience. I know it's going to be intense but that's how I learn best :-)
I want to code more because: I want to regain my feelings of exicitement and accomplishement that I used to have when I coded. I don't want my poor experience in bootcamp to end my journey and permanently effect my confidence. I miss the way I used to 'zone out' and lose time when I was fully envolved in my learning. I want to feel like I have solid JS skills so that I can branch out and experiment with other topics that interest me (Python, Data Vizualization, GIS, Data and automation, security, etc).
I'll know I've reached my code more goal when: I complete one ticket per week in my open source project, finish my 4 short courses in Advanced JS concepts/interview prep, complete an interview (no matter the outcome).
My top 3 assumptions for reaching my goal: I have the time, financial resources, and physical/mental health necessary to code more each day.
My riskiest assumption is physical/mental health related.
The prolonged pandemic, and environmental stress has caused a lot of anxiety. I don't sleep well or do as many healthy things as I used to before the pandemic. Everything feels like another chore instead of self-care.
Ways to address the root cause:
find people who have recovered
Find burnout resources
I want to code more because:
I want to create a system for coding and learning things and eventually get to a point where I can get a job or do some freelancing work. I want to overcome my fear of getting into work too.
I know I’ll have reached my “code more” goal when:
I have established a routine and successfully maintained that for some time. That may be 100 lines of code for a duration or two mid-scale projects. And as the lower boundary, i’ll accept even less if I can work for at least a few days consecutively(two weeks) on the project I am getting trouble to start on.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is my fear of getting started.
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 my dreadful procrastination.
MVP's! I need to focus on that too. I was reading The Lean Startup by Eric Reiss and need to keep remembering to relate those learnings to my work. MVPs even work when ultimately I am the customer.
I want to code more because: I'd like to build a robust front-end skillset that includes all the learning areas I've whittled down from entry-level FE job listings.
One of my assumptions is: that I might not know how to apply what I've learned.
A root cause for that is: not knowing exactly what type of front-end work I'd like to do, so I don't know which projects to come up with to build out a portfolio.
I want to code more because:
The ability to code seems to provide a good opportunity. It is also a thrill to be able to create something out of thin air! And I feel as I grow more and learn more about different fields, I can use the knowledge of the field and combine it with programming to make work easier. .
I know I’ll have reached my “code more” goal when: I'll say I have reached my goal when I have completed my Android development course. .
My top three assumptions for reaching my goal are:
I need enough time to work on it. Mostly, college work comes up and i have to prioritise things.
Due to the lack in flow or just procrastinating sometimes, i loose the interest and things become a little slow.
The quality of the reason can be a hame changer.
Of these assumptions, my riskiest is Interest.
When I think about my riskiest assumption, three possible root causes are:
Bad resource.
Other priorities kick in.
The inability to stick to it when things get twisty. I definitely need to work with it.
3 ways I might address these root causes are:
Get a buddy to work with? I have always been alone in the journey and it's less fun. Write a journal and keep a record of the progress.
Talk to people more from the field.
Instead of relying on burst of interest, I should develop a habit of sitting down and to code.
Of these, the biggest cause that’s worth tackling first is building a habit.
I want to code more because:
I know I’ll have reached my “code more” goal when:
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is balancing the many aspects of my life to make time for coding.
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 getting enough sleep. Get into a habit of a 9:30PM-5:00AM sleep routine and don’t break it.
I want to code more because: I’m looking for job and I want to learn new skills/technology to get job in IT
I know I’ll have reached my “code more” goal when: I can show my new skills in my website and I know I can do, what I want to do.
My top three assumptions for reaching my goal are:
○ I have a clear goal in my mind (getting a job)
○ I know I can get help if I get stuck
○ I have passion and will to get through the hard stuff
Of these assumptions, my riskiest is getting through the hard parts
When I think about my riskiest assumption, three possible root causes are:
○ I try too hard to do myself than ask for help
○ Impostors syndrome
○ I don’t trust that I can do this
3 ways I might address these root causes are:
○ Meditate, be kind to me
○ Seek and ask for help if you get stuck
○ Have a day off
Of these, the biggest cause that’s worth tackling first is being kind to myself and meditate
My 'code more' goal for the five weeks challenge is to complete the React course I'm currently doing, complete the React Pro content on Codecademy, and complete my tasks for 2 sprints of the volunteer project I am working on.
Anyone else's biggest risk related to parenting responsibilities - high risk of changing circumstances outside of my control that I nonetheless have to prioritise if happens.
Parenting is in my near future. I'm curious what tips you have to deal with this added layer of responsibilities and continuing your self learning. I would guess part of being successful in parenting/coding is sacrificing some of your hobbies to make room for coding?
Part of my assumptions and solutions is Giving myself the grace to skip a day when something else is more important than coding, and then being disciplined about effectively using the days that I actually have time. Maybe this would help in your situation too?
Some tips for parenting & coding:
All the best! I hope some of this helps.
Yeah, I agree with your solution. Sometimes, some tasks become more prioritize in our day to day life and we have to spend, May be more time, for those tasks because they are important to our life. I remember a saying in Transformers Last knight movie "Without a sacrifice, No victory." So, sacrificing some unimportant tasks and make some time for coding is a good practice.
I want to code more because:
I want to expand my software development skills.
I know I’ll have reached my “code more” goal when:
I have a good grasp on a specific skill and am able to apply it to a small project.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is:
having enough time with my other responsibilities of work & life.
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:
time management.
Hi everyone!
I want to code more because: I want to build up my expertise in the field of development/programming. To be able to build something new and to be creative and be more employable, and of course in the same time hopefully make money.
I know I’ll have reached my “code more” goal when: I will code more fluently and with purpose and I will be more confident in what i do and to know that i did it well. I will finish a few simpler React tutorials, build some simple app for managing buildings and post it online. Then I will finish freeCodeCamp on full stack development with React to further develop my skills. After that, I will try to contribute to some interesting open source project. Then I will build a few more complex apps.
Then, (if I will still be unsure of myself :) ) I will follow plan from this site and further expand my understaning of computer science and programming in general.
Then I will apply for programming jobs AND further build on that and start to work with my colleague on his startup.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is perservering when things get hard, lose focus and start to learn and work to wide… feeling stuck and not good enough.
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 _not having a buddy who knows how to program and to speak about problems who will try to declutter my thoughts and help me move on and believe in myself. Therefore, I will try to find someone on CodeNewbie, and I will also ask my ex-work-colleague who introduced me to React for further help when I will feel confident that I am not too-unexperienced for him.
Bye,
A. I want to code more because I want to be skilled in something which helps me to get a solid foundation in my future. and want to build some projects on my own and within a team also. and able to take part in the hackathon.
B. I know I’ll have reached my “code more” goal when:
C. My top three assumptions for reaching my goal are:
D. Of these assumptions, my riskiest is not having a proper roadmap kinda a thing. That's why I always messed up and confused about what to do next.
E. When I think about my riskiest assumption, three possible root causes are:
F.3 ways I might address these root causes are:
G. Of these, the biggest cause that’s worth tackling first asks for advice.
I want to code more because:
I will be able to improve my skill and build consistency which in turn will translate to self-growth
I know I’ll have reached my “code more” goal when:
I am able to increase the hours in coding per week
Consistently code for specific hours every day
3.My top three assumptions for reaching my goal are:
Dedicate specific hours everyday to code
Stick to one thing at a time
Seek feedback
Of these assumptions, my riskiest is to Dedicate specific hours every day to code
When I think about my riskiest assumption, three possible root causes are:
Discipline to follow through
Inconsistency in the days coded
Goal to be achieved in the dedicated hours
Three ways I might address these root causes are:
Have a plan for the set Goal to be achieved
Build discipline in being consistent
Manage time well
Of these, the biggest cause that’s worth tackling first is Build discipline in being consistent
1) I want to become not just a coder, I want to be a competent and skilled coder.
2)When I feel confident about my coding without second guessing what I am doing; when I can sit down and code a block for a project without automatically reaching for textbooks or aids.
3) a-Time to practice; b-Finding a project that engages me, keeps me involved, c-Not stopping because I have reached a problem, not getting frustrated and quitting.
4) Stopping is my biggest risk
5) a-Fear of being incompetent, unable to deliver, b-seeing a frustration as a problem and not an opportunity to learn, c-My age will not let me be seen as a skilled and competent coder that adds value
6) a-Find an accountability buddy, b-Delivering solid code, c-Meditation and yoga
7) Fear of being incompetent
I want to code more because: I want to improve my coding skills. It boosts my confidence as a tech student. Also, it helps me build, work on projects, contribute more in open source, and helps in getting internships and jobs.
I know I’ll have reached my “code more” goal when: I’m confident to code at any time, anywhere, anything, and When I can write and debug code.
My top three assumptions for reaching my goal are:
I have enough time, I will not be stuck anywhere, I can code using best practices
Of these assumptions, my riskiest is: I will not be stuck anywhere
When I think about my riskiest assumption, three possible root causes are:
Lack of study buddies, like tech friends - where We can talk, discuss code and projects. This would lift me up, Lack of self-confidence, Imposter syndrome
3 ways I might address these root causes are:
Should involve more in the community, Should not hesitate to ask for advice/help when needed, code more, and should believe in myself.
Of these, the biggest cause that’s worth tackling first is to be confident and believe that I can do this.
I want to code more because: I want to transition into a career I'm interested in, that I can take on the road for my family, and where I can actually build things.
I've gone through a few spells of burnout - somewhat due to life situations happening and taking a lot of attention away from self-teaching.
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.
I want to code more because:
I want to get really really good at Vue and JavaScript. I would like to be able to contribute to open source projects.
I know I’ll have reached my “code more” goal when:
I have completed 1 or more side projects outside work, I have re-built my portfolio sight using Vue instead of React. I am dedicating a few hours a week to my own coding projects outside of work.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is:
Energy and motivation to keep coding outside work or at the weekend.
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:
Write down a road map for the side projects with small manageable chunks of task so that it does't feel like an overwhelming amount of work to get it finished. If I can cross of only a few small tasks each week that will give me a sense of accomplishment and motivate me to keep going.
Hi Kajsa! I related to some of the obstacles you have. I also currently do coding for my regular job and have very little desire to code outside work. Keeping a road map is a great tip, I might have to try that for myself!
I want to learn the Rust programming language. I hope this will improve my memory management skills in code and learn some best practices out-of-the-box.
I know I will have reached my goal if I feel confident working on a non-trivial project in Rust.
I am assuming I have chosen a project with a small-enough scope for this challenge, that I will have the time to do it (full-time work and part-time student) and that I will actually manage to finally understand Rust.
Most at risk is the time constraint issue.
The reasons are: bad work/life balance, being too scattered with my concentration (going down rabbit holes I shouldn't be going down) and life bumps that come along and swallow up all your time rather suddenly.
Ways to solve these: leave work at the time I want to and not the time my colleagues think I should leave (i.e. no meetings that go on into the night), make time to really concentrate on what I love doing (coding and studying) and finally sometimes delegating certain life bumps to other people (like lawyers... yeah sometimes they can help you even if you have to pay them a lot).
The biggest one to tackle first is to leave work when I feel it's reasonable to. I failed learning Rust before because of the time constraint :(
I want to code more because : I want to practice what I’ve learned during the bootcamp and develop new skills, so that I can land an exciting and well paid first role.
I know I’ll have reached my “code more” goal when : I’ll have more complete projects to show and I’ll feel comfortable making my GitHub profile public.
My top three assumptions for reaching my goal are :
Get organised and stick to my set schedule
Not to procrastinate, stay motivated and reach my daily targets
Complete my projects
Of these assumptions, my riskiest is not to procrastinate; keep being motivated
When I think about my riskiest assumption, three possible root causes are:
I’m new to this
Lack of confidence
Imposter syndrome
3 ways I might address these root causes are:
Educate myself through online courses and know when to stop and actually start coding
Complete challenges on codewars or other websites as such
Don’t hesitate to ask for help and get feedback on my code
Of these, the biggest cause that’s worth tackling first is actually start coding my project
1.I want to code more because: I enjoy it, to have a job in programming and to improve my skills.
3.My assumptions are: I will have enough time, resources, self-discipline and motivation to focus on coding more.
4.Of these assumptions, my riskiest is: Focusing.
5.When I think about my riskiest assumption, the possible root cause is:
I get bored very very easy and fast and likes to try and learn different things that's why by time it was harder for me to focus one one thing even if i enjoy it since i'll get distracted by many different things at the same time.
6.3 ways I might address these root causes are:
7.Of these, the biggest cause that’s worth tackling first is: try to stick to schedule.
I want to code more because:
I want to acquire the skills necessary to make a career change to software development/engineering while completing the project I am currently working on.
I know I’ll have reached my “code more” goal when:
I will have reached my “code more” (I’m assuming this is the 5-week goal) goal when I have completed my project for the non-profit and my portfolio page.
My top three assumptions for reaching my goal are:
I think I have enough time to work on my projects, but I need to do a better job of managing and allotting that time.
I know I have the interest and motivation, though they sometimes wane when I get discouraged by how much more I have to learn, and how little it feels like I have accomplished so far.
I need to nail down what resources I am going to use to get comfortable and confident with the MERN stack, and what resources I will use as a reference as I work on my project.
Of these assumptions, my riskiest is time management and organization of resources.
When I think about my riskiest assumption, three possible root causes are:
Maybe I incorrectly calculated how much time I actually have to code.
Maybe I’m not sticking to the schedule I designed.
3 ways I might address these root causes are:
Take another look at my schedule.
Modify the non-coding parts of my schedule to more align with my coding goals.
I may look into having an accountability buddy, preferably one who is also working on a project and learning at the same time.
Of these, the biggest cause that’s worth tackling first is time management.
I want to code more because:
I want to get better at coding and solving real life problems and also to get a good job. ____________________________________________________________________________________________________________________________________________.
I know I’ll have reached my “code more” goal when:
I’ve finished with the courses I’m presently taking and also when I’ve been able to build numbers of projects by myself.
____________________________________________________________________________________________________________________________________________.
My top three assumptions for reaching my goal are:
Time management. ________________________________________________________________
Limited resources . ________________________________________________________________
Discipline to stick with coding
Of these assumptions, my riskiest is:
The assumption of having enough time.
When I think about my riskiest assumption, three possible root causes are:
Finding ways to sort out my Bills takes most of my time. ________________________________________________________________
Most times I do think I don't know enough.
Accessing the 2 major resources is a big problem where I live.
3 ways I might address these root causes are:
Sorting my bills out much earlier. This will give me more time to concentrate on coding more.
Overcoming imposter syndrome. ________________________________________________________________
Easy access to the major resources affecting my time to code. ________________________________________________________________
Of these, the biggest cause that’s worth tackling first is:
the difficulty in accessing the 2 major resources to code more __________________________.
I want to code more because I want to learn more from different people, and also transition careers.
I know I'll reach my "code more" goal when an employer is willing to take a chance on me and offer me a position with a team that cares about mentorship, my network of developers has grown, and I can talk someone through my code confidently without hesitation of hoping I know what I said.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is not respecting the time I dedicated to coding vs everything else in my life.
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 knowing when I can have time to myself and focus.
Hi D,
You said one of your goals is:
What are standups?
Hi Matt,
Thanks for the great question! Standups are basically check-ins with people to keep yourself accountable for what you are working on, for example, when I check in with my former classmates/friends, we usually indicate the following:
DONE: Wireframe (sketches of layout)
DOING: Working on frontend routes for react-router
BLOCKERS: Unsure of how to set up component hierarchy
I hope this clarified it a bit better, if not, please let me know :)
Thanks for the explanation ;)
Anytime!
⭐️
Goals, Assumptions, Risks🎯
Obviously, i want to be a highly competent web developer; so naturally enhancing my coding skills requires me to code each day. Also, it feels great & seems dope! 😎️🎯
I'll have reached my "code more" goal when......., i doubt if i'll be able to ever resist the urge to try and outdo myself whenever i get started. Every single day.🎯
Be that as it may, i'll have some semblance of reaching my goal when-🎯
The riskiest assumption would obviously be to have considered myself "competent" enough & go "full-stack".😁️🎯
Three pet peeves regarding my "riskiest" assumption would be-🎯
There are, however, corrective measures that i would adopt to mitigate the above grievances. Three of them being-🎯
The most infuriating aspect of the "coding more" conundrum, is NOT being consistent/persistent/tenacious (whatever that means) enough. THIS will be dealt with alacrity & put into action with immediate effect.🎉
Ciao!I want to code more because:
I would like a job, but I also want to have the ability to make my own programs with confidence and less stress.
I know I’ll have reached my “code more” goal when:
I can come up with program solutions efficiently.
My top three assumptions for reaching my goal are:
I need a solid understanding of Data Structures. Dare I say appreciation for them.
Developing patience and reading through errors and documentation.
Getting involved with other coding projects to benefit the community.
Of these assumptions, my riskiest is getting involved with other coding projects.
When I think about my riskiest assumption, three possible root causes are:
Letting strangers down when I said I would deliver
Looking like a fool in front of other developers
Breaking something I can’t fix
3 ways I might address these root causes are:
To remind myself that most developers are in a similar position as me.
Developers love the help and are willing to offer input when requested.
Github & version control make it much less likely I’ll legitimately break something.
Of these, the biggest cause that’s worth tackling first is learning more about Data Structures.
I want to code more because:
I have few ideas that I want to implement, they have been there for a while now and I feel like I owed to myself make the time and develop them.
I know I’ll have reached my “code more” goal when:
When I have “coding my own projects” as one of my every day activities and I began to feel the urge of start programming every day.
My top three assumptions for reaching my goal are:
○ I have the necessary resources to start developing my personal projects.
○ I consider that I have the necessary discipline to face any difficulty and remain focus.
○ I’m highly motivated and I love programming.
Of these assumptions, my riskiest is the availability of the necessary resources.
When I think about my riskiest assumption, three possible root causes are:
○ Internet connection with low availability, poor quality and expensive prize.
○ Limited access to the latest or at least the most appropriate tools.
○ Limited access to the latest documentation and to the development communities.
3 ways I might address these root causes are:
○ Increase my connectivity expenses.
○ Find the appropriate way to get the necessary tools, no matter the cost.
○ Get more involve and ask for advice on the different development communities
Of these, the biggest cause that’s worth tackling first is Increase my connectivity expenses.
I want to code more because:
I am on a career change and just finishing a front-end Bootcamp. Nowadays the pace seems so slow. I want coding to be my new habit. I want this to be my career until my old day. By code more I want to build more and help more, and I believe coding really pays well so I can be living comfortably in the future.
I know I’ll have reached my “code more” goal when:
I am having a real job or I can earn money from my coding skill.
My top three assumptions for reaching my goal are:
Coding early in the morning
At least spend 3 hours coding a day
Be a part of CNC2021. It helps me to feel that this can be done together.
Of these assumptions, my riskiest is
Writing code comfortably in the morning
When I think about my riskiest assumption, three possible root causes are:
Staying up late so I am not waking up early
Procrastinate and letting my “entertainment” first before tackling code in the morning
Comparing my current milestone to someone else’s and getting lost in thinking that I cannot do (anxiety) or that this current path I’m on is not worth the effort (discouragement).
3 ways I might address these root causes are:
Not making a coffee after 6 PM
Put away the phone and think that coding is fun as it’s a part of the entertainment
This is a long path and the current solution is contributing to CNC2021 so I can work this together with all these amazing people
Of these, the biggest cause that’s worth tackling first is procrastination in the morning.
1 I want to code more because:
I want to get better at coding to get a job that will eventually change my life as a career
Move For me. it been such a big dream and want to reach it someday
2 I know I’ll have reached my “code more” goal when:
I will be able to get into the interview process and get rid at least of a bit of imposter syndrome and of course having a strong portfolio
3 My top three assumptions for reaching my goal are:
Getting better at writing code and implementing concepts
Learning a javascript framework (probably react)
Fighting both ADHD and Imposter syndrome
4 Of these assumptions, my riskiest is:
Throwing away my 4 university years (Aquatic Science) and dive into a new world to start from scratch.
5 When I think about my riskiest assumption, three possible root causes are:
Unemployed situation and being graduated puts me under stress with my financial situation
Imposter syndrome AGAIN!
Saturated entry-level job positions and high qualification need for getting a job is a big hassle for me as i need to be very skillful in everything
6 3 ways I might address these root causes are:
Trying to get more confident and fight my imposter syndrome
Getting more relations in dev community
Work harder and get into open source projects
7 Of these, the biggest cause that’s worth tackling first is building a solid routine i can stick to every day.
1. Why do you want to code more?
I wish to start a career in tech. It has been my passion since my childhood, and I want to push myself into the productivity zone again.
2. How will you know when you’ve reached your goal?
I think the best way to measure my progress would be to see how consistent I am working on my coding skills. Say, for example - Leetcode submissions streak, Github usage, or the time i spend each week learning from tutorials. I plan to log what I learn into a doc.
3. What are your assumptions about being able to reach this goal?
I need the push to stay consistent with my progress and I think I would get that from the community. I'm assuming I have the time to manage consistency well. I'm also assuming that I will have the motivation to stay on track despite my serial procrastination history.
4. What’s your riskiest assumption?
There are occasions where I contemplate dropping something because I'm not able to stay consistent with it. I think that is something I shouldn't be doing but impulsively have, and going with these missions makes me assume that I won't drop out of this.
5. What’s the root of your riskiest assumption?
I think it is the fear of not being able to deliver as promised. I expect to deliver to my fullest when I set my mind to something, but when I face obstacles, I feel like dropping it because I overestimate the significance of my delay. Another constraint is time, as I'm involved in multiple bootcamps + college at once, which is already heavily demanding.
6. What are 3 ways to address the root of your riskiest assumption and make it less risky?
I'm thinking of getting someone, maybe a friend or mom, to hold me accountable. I think it should help me keep on track. I'm going to try to align my bootcamp work with these missions so that I can manage things efficiently. Hopefully my newfound productivity apps will help. Since all of my bootcamps are about coding i think i can find a way to put them all together and de clutter my schedule. I sleep early so I guess I can push that to accommodate everything as well.
Hey Guys!
Malcolm here!
I want to code more because:
I want to code more because I wish to be able to change my career and earn more.
I want to hone and develop these skills I have started to apply on this journey.
I want to be able to become more self-sustainable in the job market, and be able to freelance or work for myself one day.
*I know I’ll have reached my “code more” goal when: *
When certain topics become more clearer and relatable to me.
When I have been able to create more diverse projects.
When coding starts to become more natural to me.
My top three assumptions for reaching my goal are:
To continue sticking to coding on a regular daily basis weekly I will get better
The more coders I build connections with, talk to and collaborate with I will get better.
That the hard parts will become more and more easier the more I practice and get help on them from others.
Of these assumptions, my riskiest is :
That the hard parts will become more and more easier the more I practice and get help on them from others._
*When I think about my riskiest assumption, three possible root causes are: *
The coders are not always available when I need them
Can be hard to reach out to people with all different schedules
Feeling imposter syndrome
3 ways I might address these root causes are:
Don't give up on reaching out to other coders
Try different ways to reach out, make yourself more available and interact more.
Know that every developer has felt this way through certain periods of their career and that's ok, it will take time to get out of this.
*Of these, the biggest cause that’s worth tackling first is *
Try different ways to reach out, make yourself more available and interact more..
Welcome to the community!
My end goal is to get a job, but to achieve that I want to build some projects to showcase what I'm able to do. My biggest fear is the loss of momentum which leads to the loss of motivation. I have ample amounts of time and possibilities to achieve my goal, but if I have to take a long enough pause I could lose my motivation to continue on after it.
The solution for this I think is to build a routine of coding every day. Of course in the long run I should do it more, but to keep my motivation up even as little as ten minutes a day could do the trick. I think... And hope...
I want to code more because: I want to create a portfolio, build the skills I already know and create a project for work.
I know I’ll have reached my “code more” goal when: _I am coding every single day as a habit and building the foundation I already have.
My top three assumptions for reaching my goal are:
○ __I have remembered what I learned
○ __I have the motivation and energy
○ __my work schedule will allow me to code
Of these assumptions, my riskiest is _finding the time
When I think about my riskiest assumption, three possible root causes are:
○ __my job takes too many hours
○ __I procrastinate
○ __I get discouraged when I am researching things and not moving forward in a project
3 ways I might address these root causes are:
○ __Code in the morning or at night? Pick a time that works for me
○ __Have the discipline to start, use the Pomodoro timer
○ __Be kind to myself, it is difficult, maybe have a coding buddy
Of these, the biggest cause that’s worth tackling first is _time management .
Code More worksheet
“Goals, Assumptions, Risks”
1.I want to code more because: I want to learn new skills to become a full-stack web developer so that I can apply to jobs after my graduation ends.
2.I know I’ll have reached my “code more” goal when: I will be able to code my self web apps which have been my dream for me till now.
3.My top three assumptions for reaching my goal are:
a)If I am able to self-discipline myself to work hard.
b)Less time on social media.
c)If I am able to keep my concentration for a longer time.
4.Of these assumptions, my riskiest is keeping myself self-discipline
5.When I think about my riskiest assumption, three possible root causes are:
1.My social media addiction, I tend to go to Twitter every 30 minutes.
2.Unable to concentrate for a longer time.
3.Can get distracted quickly.
7.Of these, the biggest cause that’s worth tackling first is social media addiction.
I want to code more because: short-term goal: to improve my coding consistency in order to better my skillset and get a well-paying job. Long-term goal: building profitable web applications and start-ups.
I know I’ll have reached my “code more” goal when: I’m able to consistently code for at least 4 hours everyday.
My top three assumptions for reaching my goal are:
○ I’ll always have 4 hours to dedicate to coding daily.
○ I’ll always have self-discipline to stick to my daily coding goals.
○ I’ll always have the motivation to keep learning.
Of these assumptions, my riskiest is self-discipline to stick to my daily coding goals.
When I think about my riskiest assumption, three possible root causes are:
○ Waking up late in the morning.
○ Procrastination.
○ Lack of daily consistency.
3 ways I might address these root causes are:
○ Ensuring that I wake up at the same time every morning (to improve consistency).
○ Dedicating the first 4 hours of every morning to coding.
○ Getting an accountability partner to ensure I stick to my daily goals.
Of these, the biggest cause that’s worth tackling first is getting an accountability partner.
I want to code more because I want to find a better job, so I want learn JavaScript and to build my portfolio by making cool projects.
I know I’ll have reached my “code more” goal when:
I have mastered JavaScript and built some cool projects with it.
What are your assumptions about being able to reach this goal?
What’s your riskiest assumption?
I will stay motivated.
What’s the root of your riskiest assumption?
Facing difficulties in understanding the language / framework
3 ways I might address these root causes are
Practice , practice and more practice.
Asking for help
Of these, the biggest cause that’s worth tackling first is looking for a good project to learn on.
-code in the mornings.
-set schedules and meet them in those hours remove distractions.
-Take breaks so as not to spend many hours in front of the computer and you are tired.
-separate the content into parts so that it is not too much and to assimilate what has been learned.
I want to code more because:
I want to improve my problem-solving skills, learn and move from a Frontend developer role to a Full-stack role, want to create a personal portfolio, and contribute to open-source, feel more confident about my code.
I know I’ll have reached my “code more” goal when:
I have completed my portfolio, able to keep up my Github profile updated. Get a job in a Full-stack role, participate in hackathons and solve Leetcode challenges efficiently.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is “discipline”
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 “Procrastination”.
My goal for the 5 weeks of #codemore challenge is to stick to writing more JavaScript and learn as much possible.
I've been trying to learn JavaScript on my own for a while now and it has been difficult. It'll be nice to pair up with someone who is learning it too. Please hit me up if any of you are in a similar situation or want to study together!
Your welcome :) First thing is to realize, how you talk to yourself when you have a hard time: instead of blaming and saying you are no good, try to say i.e. ok, today isn't a good day and I feel I need some time off. Talk to yourself like you talk to your friend who has hard time :)
I want to code more because: I would like to be more confident in finding a developer job ____________________________________________________________________________________________________________________________________________.
I know I’ll have reached my “code more” goal when: I am able to start and finish my own personal projects and have a full time job coding____________________________________________________________________________________________________________________________________________.
My top three assumptions for reaching my goal are:
Having enough time to code_______________________________________________________________
Am I progressing enough if I’m having a hard time on mini exercises ________________________________________________________________
Am I learning the most effective aspects of the programming language ________________________________________________________________
Of these assumptions, my riskiest is am I Learning the most effective aspects of the program language ________________________________________
When I think about my riskiest assumption, three possible root causes are:
Self teaching ________________________________________________________________
Depending on materials and resources ________________________________________________________________
Not knowing the industry standards ________________________________________________________________
3 ways I might address these root causes are:
Speak with someone working with that language day to day________________________________________________________________
Increase my resources ________________________________________________________________
Looks at requirements for various jobs________________________________________________________________
Of these, the biggest cause that’s worth tackling first is speak with relevant working programmers__________________________.
This was extremely emotional for me. I realized that I have been stagnant for a long time. Since Nov/Dec. Holidays in the U.S. I was working along pretty well and then once I fell into that depression I have been trying to claw my way out. I have been doing the minimum to get back to where I was prior. Just not have not gotten there. The excitement is still there but the effort is not. I have plenty of work to do to meet this timeline.
The best thing that I learned in it all is that I don't have to have the perfect timeline and I don't have to be as fast as those around me and I do not have to live up to other's expectations of where I should be.
I am praying that this will be the motivation that springboards me.
docs.google.com/document/d/1SBbeF6...
Mission 1 Goals
Had to be sincere with myself to come up with these ones
I want to code more because: I’m trying to improve on my skills and work on more relevant and production ready code. I want to build larger projects that really emphasize my skill-set but I usually fall short due to procrastination. I am also working to get a good paying remote job and establish my self as a software developer.
I know I’ll have reached my “code more” goal when: I build 3 major full projects and 5-7 mini projects that show at least one of all the technologies and tools that I have under my belt and I create a portfolio that I am proud of.
My top three assumptions for reaching my goal are:
I have the discipline to achieve this goal
I visualize and come up with suitable projects and break them into smaller parts
I have enough time to complete these projects
Of these assumptions, my riskiest is I visualize and come up with suitable projects.
When I think about my riskiest assumption, three possible root causes are:
I tend to look at large projects and get frustrated at the amount of work involved
I tend to just pick a project and attempt to start without properly planning out every piece that’s needed
I was stuck in tutorial hell for a while and I start multiple projects at the same time.
3 ways I might address these root causes are:
I should plan out a project before I start building, accessing what I’m trying to achieve, the tools I would need to achieve them and the amount of time it’ll take.
I break my projects into smaller bits and work on them individually.
I take up one project at a time.
Of these, the biggest cause that’s worth tackling first is: I should plan out a project before I start building, accessing what I’m trying to achieve, the tools I would need to achieve them and the amount of time it'll take.
I want to code more because:
I need to achieve the goals I made as a freshman in college. I started well but got indulged into too many things( learning web dev, practicing competitive programming, took Udacity scholarship course on Cloud Services), stuck into tutorial hells, couldn’t manage college work along with it, started procrastinating and now my current situation is I have not completely gained expertise in any of these nor did them consistently, just have partial knowledge in all. I am in my pre-final year now and want to land in a good company as a SDE. For that I need to sharpen my problem solving skills and as well as have a bunch of projects to showcase in my portfolio.
I know I’ll have reached my “code more” goal when:
I have a lot of questions solved in my Leetcode profile, have some open source contributions on my Github profile and made a couple of real world projects to gain experience.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is to keep consistency
I keep 2-3 major things(out of DSA practice, college studies, competitive programming, web dev) in my to-do list for the day but seldom get all of them ticked off 😥. Problem is sometimes I get exhausted, sometimes worrying about having no time in the future to complete and getting FOMO all the time!
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
starting good habits that stick for long.
I want to code more because:
To look for a job career and because coding is something that I (mostly) enjoy doing compared to other hobbies.
I know I’ll have reached my “code more” goal when:
As long as I’m doing Habits including coding and other stuff everyday then I’ll know
That I’m on the right path. Goals are just stairs, you can fall on the stairs easily and by that I mean I can fail easily which is why going up stairs all the time without falling is no easy task.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is: Depression and mental health issues getting in my way of learning which causes an 8-month-break for example.
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: getting through the big information
1.
I want to code more because: I am ready to turn my coding hobby into a new career path.
2.
I know I’ll have reached my “code more” goal when: I have a portfolio ready to begin the job hunt.
3.
My top three assumptions for reaching my goal are:
4.
Of these assumptions, my riskiest is making time for coding daily as life happens
5.
When I think about my riskiest assumption, three possible root causes are:
6.
3 ways I might address these root causes are:
7.
Of these, the biggest cause that’s worth tackling first is exhaustion as I have a full plate but that doesn't mean I can’t do it...I just need to do it the smart way!
I want to code more because: I want to become golang developer & open source contributor.
I know I’ll have reached my “code more” goal when: I code any website backend or system program in Golang ,also doing open source contribution in organization under CNCF.
My top three assumptions for reaching my goal are:
I have enough interest to reach my goal.
Imposter syndrome
timing issue & hurry up for getting developer job
Of these assumptions, my riskiest enough time
When I think about my riskiest assumption, three possible root causes are:
I am college student and my lot's of time spent on college work :(
whenever i see , I have to learn lot's of thing that feel me exhausted.
3 ways I might address these root causes are:
Even if I have college work ,I will give time to reach my goal.
Just try to keep learnig for great future & no matter how much time it will take and how much resources.
Of these, the biggest cause that’s worth tackling first is keep learnig no matter what.
Reasons to code more:
Achieving my code more goal:
Three assumptions for reaching my goal:
Riskiest assumption is having resilience and passion to get through the hard parts
Root causes of my riskiest assumption:
Acknowledge root causes:
The biggest cause that is worth tackling is hindrance due to wanting perfection
Hey all :) It's really nice to read all your thoughts and it's a great source of ideas as well.
I want to code more because I used to really enjoy coding when I had time before finding a full-time job and I left that to the side because my current job doesn't involve coding. The process of coding fits well with the way I think, learn and work, and that's why I would like to change careers and get into tech. My goal is to get a job in tech (or more likely a tech job in another field) where I get to use technology to address social issues (mobility, healthcare, social services, etc.). Getting a better salary and being in a industry that embraces remote/flexible work is also a goal.
I'll know I have reached my goal when I have a GitHub profile with at least 2-3 personal projects related to data analysis and visualisation and that I can apply to a job without feeling like I am embellishing things when I write that I have this or that skill. I will have had enough actual practice on projects that I can confidently say that I am skilled.
My assumptions to be able to reach this goal:
My riskiest assumption is being able to balance everything. If I have the energy and motivation to code, I can get so focused that I lose track of time, forget to deal with / ignore basic day-to-day chores, get to late in bed so I am tired at work.
How to address the roots of the riskiest assumption? I need to plan my coding sessions and my life more squarely. It could have a two-fold effect: 1) making sure I have penciled down that I will code this and that day and 2) making sure that I think about when it does make sense to code and get other stuff done before that day.
I want to code more because:
I like solving problems and I want to be able to solve any problem I can encounter in the languages that I am learning (PHP,Python,Javascript).
I know I’ll have reached my “code more” goal when:
When I build my first project idea from scratch.
My top three assumptions for reaching my goal are:
I have enough resources to continue going on
I have enough time to learn the skills needed
I have the discipline to reach my goal.
Of these assumptions, my riskiest is having enough time to learn skills I need.
When I think about my riskiest assumption, three possible root causes are:
Too many skills to learn
Change in learning environment
Procrastination
3 ways I might address these root causes are:
Focus on the priorities first and master them
Keep habits even if the environment changes
Start with the task asap as I have it and set deadlines for each step
Of these, the biggest cause that’s worth tackling first is plan ahead and keep goals in mind do not settle
I want to code more because:
I want to increase my productivity, increase competitive programming skills, learn new skills and technologies and build useful products using them.
I know I’ll have reached my “code more” goal when:
I will be able to code for at least 8 hours a day.
My top three assumptions for reaching my goal are:
I will have developed the immense focus required for programming huge tasks.
I will have developed the patience and logic for long hours of programming.
I will have developed the interest and passion to keep learning always.
Of these assumptions, my riskiest is developing necessary patience and focus.
When I think about my riskiest assumption, three possible root causes are:
Situation due to pandemic causing lethargy
Continuous inactivity causing boredom and lethargy
Less focus due to distractions
3 ways I might address these root causes are:
Gradually prepare my mind to work more
Converting boredom and lethargy into active energy and work more
Training myself to avoid distraction
Of these, the biggest cause that’s worth tackling first is preparing my mind to work more.
I want to code more because:
I love to build things and solve problems.
I want to get better at my job, contribute to open source, write about my work and improve the way I share with others.
I know I’ll have reached my “code more” goal when:
I’m less afraid to build things independently, rather than through my job or study.
I feel more comfortable submitting a pull request on an open source project.
My top three assumptions for reaching my goal are:
That I have time or energy to work on non-study related projects after work
That I can battle through the impostor syndrome to write about my learning
That I can avoid yak shaving my evenings away...
Of these assumptions, my riskiest is the one about time and energy.
When I think about my riskiest assumption, three possible root causes are:
My job is exhausting and unfulfilling even though I am already a software engineer so I don’t always want to code on my free time
Being inside all the time due to covid has melted my brain
It’s very easy for me to just read articles for hours instead of practice because my brain is done for the day
3 ways I might address these root causes are:
Work with a tech stack that is totally and completely separate from what I use at work
Walk during the day, move to a different room when studying or take a break after work
I don’t know...it feels related then I look up and it’s midnight.
Of these, the biggest cause that’s worth tackling first is the discomfort with doing my own thing.
I want to code more because I want to feel more confident in my skills and gain a career in Web Development.
Somes hurdles I deal with are finding time to code, having distractions due to taking care of family and struggling with self doubt and imposter syndrome. The latter also affects me to struggle with sharing projects and making connections.
The ways I want to remedy this is carve out a time where there is minimal distractions. I also want to organize my time by setting up timers so I won't dwell on one thing for too long. Also start slowly and try to share on social media what I've been working on one day at a time.
I want to code more because:
My ultimate goal is to get a developer job, a career change. To achieve this I need to practice a lot more using the knowledge I have gotten over the last year from all the tutorials
I know I'll have reached my "code more" goal when:
Of course, getting a job would be nice. But I feel that actually finishing my portfolio with some actual nice projects to display and not just tutorial projects. Also, complete a JS project from start to finish on my own.
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is:
Being motivated to keep going and push through my barriers
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:
To do what I actually schedule for the day and stop goofing off.
Code More worksheet
“Goals, Assumptions, Risks”
*I want to code more because: *
I want to be able to get a job and earn some money and work on/build awesome projects
I know I’ll have reached my “code more” goal when:
I get a job or be able to make some money
My top three assumptions for reaching my goal are:
Having enough time
Getting the right resources
Being able to stick to the code newbie challenges
Of these assumptions, my riskiest is having enough time
*When I think about my riskiest assumption, three possible root causes are: *
3 ways I might address these root causes are:
don't know yet what to do
try to code with any little free time I can get
don't know if i can do anything about this, since a general problem here in my country
Of these, the biggest cause that’s worth tackling first is meeting up with school activities .
Code More worksheet
“Goals, Assumptions, Risks”
Why do I want to code more?
I want to code more because:
• I'm eager to learn a new Technology and want to understand everything about it
• I want to get a job so I can be financial free ( you know get what I need without newito asking my parents)
• I want to get involved in the evolution and this tech craze and buzz, I want to see ways I can change my world positively from proferring solutions on Problems to Startups to Social services so I thought writing code is good headstart
I know I’ll have reached my “code more” goal when:
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is
When I think about my riskiest assumption, three possible root causes are:
3. ways I might address these root causes are:
Good luck with all that!
I want to code more because: I enjoy coding, I like learning new skills and practicing them, it's like trying to put a puzzle together and being excited when all the pieces fit. I want to give myself time to do the things I enjoy including coding.
I know I’ll have reached my “code more” goal when: I have a consistent coding practice that includes creating practicing skills with small projects or challenges that require me to utilize my own skills and not just follow along with someone else’s code.
3.My top three assumptions for reaching my goal are:
*That I learn the skills well enough to implement them on my own rather than just enough to understand and copy/paste.
*That I will have the time to code a little everyday without feeling overwhelmed.
*That I can find the resources to help me learn skills in the way I want to with out giving too much support or not enough.
5.When I think about my riskiest assumption, three possible root causes are:
*Over the years through school I got really good at regurgitating information back without actually absorbing any of it. And using templates and SOPS to create things without actually absorbing the why behind each step.
*I have a really bad working memory
*I get impatient and want to move along rather than put in the work
Ways I might address these root causes are:
*Go slow and give myself plenty of chances to practice. Commit to learning one thing, one piece before moving on to the next bit.
*Write things down. Even if the notes are sloppy, or unorganized. The notes don’t have to be perfect, they just have to be functional.
Of these, the biggest cause that’s worth tackling first is learning to slow down and actually learn the pieces rather than faking my way through regurgitating code and information
I know I’ll have reached my “code more” goal when I complete these 5-weeks course in Coursera: Python for Data Science, AI & Development
My top three assumptions for reaching my goal are:
Of these assumptions, my riskiest is to balance my time.
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 health routine.
I want to code more because:
I want to get a job as a developer.
I know I’ll have reached my “code more” goal when:
I have a job! I can make money coding.
My top three assumptions for reaching my goal are:
Need a lot of passion and motivation.
Need to network with other devs.
Need to study and build consistently.
Of these assumptions, my riskiest is: study and build consistently
When I think about my riskiest assumption, three possible root causes are:
I get distracted by new resources -- I’m afraid that I’m not using the best resource
I am afraid of failure -- it’s hard and I feel like I forgot everything from boot camp
I can’t decide on a project -- undecisive
3 ways I might address these root causes are:
Stop looking for more resources and explore the ones I have.
Write about my fears and experiences on CodeNewbie. Find people who can relate. Don’t worry about what you know or don’t know, just keep going.
Write down my project ideas and work on them one-by-one. Don’t start another one until the first is done. Think of it as an assignment.
Of these, the biggest cause that’s worth tackling first is: getting distracted with new resources and being overwhelmed with the amount of information available.
As a DevRel engineer I don’t have to code as much as a regular developer, but still, I want to be part of the conversation, so being consistently coding will help with that.
Love this!!!
I want to code more because: i need to improvel ______________________________________________________________________________________________________________________________________.
I know I’ll have reached my “code more” goal when: _when i can solve hard coding challenges easily_____________________________________________________________________________________________________________________________________.
My top three assumptions for reaching my goal are:
practice__regularly____________________________________________________
study theory____________________________________________________________
__time________________________________________________________
Of these assumptions, my riskiest is _______practice___________________________
When I think about my riskiest assumption, three possible root causes are:
laziness_______________________________________________________________
disorganization______________________________________________________________
lethargy__________________________________________________________
3 ways I might address these root causes are:
__motiviation________________________________________________________
small steps______________________________________________________________
___fun with others_______________________________________________________
Of these, the biggest cause that’s worth tackling first is _practice___________________.
I want to code more because I so love the feeling when code works - the more I’ve struggled, the better it feels.
I know I’ll have reached my ‘code more’ goal when I have 2 fully working projects on GitHub.
My riskiest assumption is: that I can find learning resources that suit my needs and follow through on using them. Root cause: a lack of focus on the challenge immediately in front of me and not following through when I start to understand something.
3 ways to address this: 1. Take time to organise a system to store links and other references to resources, 2. Approach learning resources mindfully, 3. Take notes on paper.
Hi there, here it is
docs.google.com/document/d/1hUnqRk...
Hi Adnan! Thanks for being part of the challenge!
Heads up that you are not expected to share your doc here. That worksheet is just for you! Instead, you'll want to use these threads to actually respond to the assignment prompts. Thanks!
Lovely
My goals (in 5 weeks) are:
I want to improve my coding skills and learn new things. I want to complete my portfolio which has been pending.