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 your assumptions and root causes, too. Maybe someone in the group can help you come up with solutions to try! Be sure to leave a helpful response to another person (or two!) if you can. Mission 1 is in the books!
Congrats on challenging yourself to Code More! If you have any questions about the challenge overall, head to the Code More Help Thread. For any technical questions throughout the challenge (or in general!) write a #help post and share with the community!
Top comments (107)
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.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.