Take a quick glaze to see the blogs posted by the challengers. Now we have concluded to pick the winners among the best of best.

We have picked 4 winners from the challengers for their consistency, dedication, and active participation in the challenge.

🥇1 st prize - Winner

With no doubt, we are so happy to announce the right talented winner. The First prize goes to Shreya 👋 and here is her journey for the 14 days.

She won 1000INR worth Amazon gift card and a brand t-shirt from 100daysof.codes👕.

Right from day 1 to the end of the challenge, she stands out from the rest of the others with her amazing daily projects. We are so glad to give the first prize to her.

🥈 2 nd Prize - Winner

The second prize goes to Deepakshi Sood and here is her blog. When comes to the second prize we discussed deciding the prize for the winner. For her consistency and dedication, we decided to give her a special prize.

She won a special prize of 500INR worth Amazon gift card and a brand t-shirt from 100daysof.codes👕.

She built her website Find a place and her profile on the challenge.

🥉 3 rd Prize - Winner

We are learning and trying out new things daily, but when it comes to challenges, seeing what you have learned daily motivates you to do more when you are down. We are so happy to give this prize to the interesting learner and challenger Nitesh Thapliyal.

He won a brand t-shirt from 100daysof.codes👕.

🏅 - Special prize

At just 16 years old, with his charm and enthusiasm, he won a special prize from us. The special prize goes to Manish⚡Nayak. He motivates and inspires even the grown-up to take the challenges. Here is his blog written by him.

This little young man, decided to giveaway the prize won and sponsored a Udemy course for the fellow learners.

There are still lots of unsung hero's to mention. Special thanks to all the challengers who have taken up the challenge consistently. We are so happy to be in the part of their journey. Sure we are with lots of interesting challenges in the upcoming days.

Feel free to contact us anytime on Twitter. Don't forget to check out our chrome extension which makes several learners to be in consistent in their learning.

Regards, Rams and Karthi from 100daysof.codes .

Breaking out of our first loop & the beginning of Gigahertz

The idea to start the #14daysbreakloop challenge comes after we launched our product - 100daysof.codes. The idea of Gigahertz - our startup behind 100daysof.codes came long back before 2 years. But there were other personal commitments we couldn't really bring a shape to our idea. #100daysofcode and the learnings we had between these 2 years all put an end to this loop, and we launched our product. #100daysofcode challenge shapes this one day at a time to bring it into reality. Now for us, it's a new beginning.

Breaking out of the second loop & posting 14 articles in 14 days on hashnode

I have been thinking about blogging for years. Whenever I sit down to write, I expect it to be the best one. So when I did write one, I would tell myself somebody would find this as a low-quality blog and they wouldn't read it all. Even though I could say it to myself without writing and posting it, I wouldn't know I am improving. I was reluctant to write one. When we planned for the #14daysbreakloop challenge, I decided to break this. Now I have successfully written 14 articles in 14 days and published them on hashnode. I make the #14daysbreakloop challenge as a system to work on this. But this time, all I did focus on was to share the values & experience with others. If you want to make the best to reach your goals, build around the system that expects the best out of it.

Here we are, at end of the #14daysbreakloop

Dream goals would still be a dream unless we build around a system to work on it every day. It doesn't have to a perfect one, but make sure it would get out of you to learn the best. For us, #100daysofcode turns out to be a system to learn consistently newer and build crazy ideas. #14daysbreakloop turns out to be a system to share our experiences with the community. And the startup wants the best in what we do to provide value in the scale.

The idea of the #14daysbreakloop challenge is not to put an end to your dream goals after 14 days. But to help you to build the system that pushes you throughout the process. For us, the #14daysbreakloop challenge may be an end today. But I wish you all this learnings should be a beginning for greater accomplishments ahead.

It's a big day for both of us. Congratulations on successfully completing the

#14daysbreakloop challenge.

Action items

1. Do a retrospective reflecting on your journey so far - What went well? What didn't? What have you learned? This will be your key learning for next cycle.
2. Write down your learnings in a journal. Documenting your learning will help you to take key decisions in future when things repeat.
3. It's the moment for you to celebrate for your accomplishment. Tons of wishes from us to smash more down in the future. Good luck.

Thought for the day

This article is written by Karthikeyan and co-authored by Rams

This article was written as part of day 14 of the #14daysbreakloop challenge. Get the new tab extension from [Chrome Web Store] (https://chrome.google.com/webstore/detail/100daysofcodes/cecmfhlijbbeeeobbgnoaajmhckdganc?utm_campaign=hashnode) and start working on your #100daysofcode.

It came to my realization point if I haven't stubborn about starting a startup while in college, spending much time exploring that, doing nothing and failed. When I indeed start building one for the past two years and have to quit for the undeniable circumstance, Rams and I wouldn't have started 100daysof.codes.

Every moment of failure and success that happens in the past is the chance I have to learn and move forward. Yes, learning happens only backward. But we have to push ourselves consistently forward and make an action. So how fast and efficient we learn from our actions is how better we build our feedback loop.

Do an action, measure, learn and repeat.

Building a feedback loop

Building feedback loops are essential to optimize our learning cycle. Feedback loops build on three steps.

1. Measure - Track what we do. This improves accountability and awareness of tracking things around us.
2. Compare - Comparison between the measurement of where you are now to where you want to be.
3. Adjust - Adjust is the action we do to close this loop. Bridge the learning from previous cycle and open the next cycle of learning.

It arrives us to the recap of our learnings in past days. Every objective we work on, the task we enter in our new tab extension was to begin this loop. Every note we took daily, small wins, failures are what starts building this forward loop. Without them, we couldn't measure the path we traveled. We don't know what we lack to reach our destination. Keep the loop short and learn as fast as you can to speed up your path to success.

Keeping ourselves accountable to our mistakes

Keeping an accountability partner pushes us to learn faster and avoid procrastination. I would like to share an incident read recently, YC founders used to have Tuesday night dinners where startup founders would discuss their progress past week. This forces the founders to innovate constantly every week as they need to present their work public to other founders.

If the environment isn't pushing you to learn more, create the environment.

Action items

1. Most important thing is to keep tracking what we do. List down what you have learned so far - It might be skills, shortcomings, best moments, every thing that helps you to take action next.
2. Staying accountable to the actions is key to learning & prevent making mistakes regularly. Choose a accountability partner - might be a friend or committing public to twitter.

Thought for the day

This article is written by Karthikeyan and co-authored by Rams

This article was written as part of day 13 of the #14daysbreakloop challenge. Get the new tab extension from Chrome Web Store and start working on your #100daysofcode.

A system to learn from failures - "5 Why"

Eric Ries, the author of Lean startup, uses these 2 rules for him and his team - 1. Be tolerant of all mistakes the first time. 2. Never allow the same mistake to be made twice. The first rule is about being compassionate about making mistakes. The second rule is about taking action to prevent it next time. We have talked about the importance of the system to choose valuable tasks. Also, we need a system to focus on the mistakes that will impact us most, avoiding working on mistakes that are not so important. "5 why" is a technique used to find the root cause of a failure and also create the opportunity to learn and make an action. The technique is to question five why repeatedly on a problem that impacts a lot. This also opens up room to face the unpleasant truth about ourselves which we must confront and try to provide proportional investments to learn from it.

"5 Why" - Example Scenario

Be it any mistakes we might encounter from personal productivity to a development bug - "5 why" helps us to identify the root cause. Below is a scenario that happened in IGN when they encountered a production issue on editing or posting comments. Asking 5 why opens an opportunity for improvements in each stage. And also two outputs in each stage - learning & doing.

1. Why was the edit feature not working ? Reason - API is throwing 500.
2. Why was the API throwing 500 ? Reason - ruby gem added was incompatible with others. Fix - Remove the gem
3. Why was the gem incompatible ? Reason - Added a version of gem in addition to existing version, app used incorrect. Fix - Use bundler
4. Why added in production without testing ? Reason - Didn't think needed for updation. Fix - Add a functional test to API to capture this
5. Why are we deploying weekends ? Reason - We used to wrap the sprint by deploying at the end. Fix - Avoid deployments on weekends as there will be fewer resources available for support.

Action Points

1. List down the most recent thing you have failed and cost you a lot
2. Try to apply the five why technique. We have added a spreadsheet template that you can use to validate and identify the root cause
3. List the incremental action items in each stage and make sure what you should have done, if this should not be here the next time.
4. In times you have failed, remember you are not alone. There are lots of people out there who can help you. Feel free to share & raise feedbacks.

Thought for the day

This article is written by Karthikeyan and co-authored by Rams

This article was written as part of day 12 of the #14daysbreakloop challenge. Get the new tab extension from Chrome Web Store and start working on your #100daysofcode.

If you have a habit of skipping days, try the 2-minutes rule

There may be days we could have a second thought of maybe tomorrow. In case you find it harder to maintain, use this famous 2-minutes rule by James Clear - When you want to start a habit, do it for 2 minutes. Say, if you need to read a book every day, start reading a page. The idea is to do small things that make an insignificant impact. It is also helpful in maintaining a way to stick us to a schedule.

It's all about falling in love with not to break the streak chain

Streaks are the best way to maintain ourselves to keep doing what we do. Motivation is a myth, which fades away quickly. But whenever you feel down, if you maintain the visual streak, it helps you to improve your confidence level. Each streak has its end, but the more important part is recording our actions and measuring us for the next journey.

Streak was not about quantity, it's quality - End the day with an value

Sustaining the good things with us is a hard thing. If you stop doing, it will wear down in a few days. While taking the #100daysofcode challenge, I would say to myself not to miss the streak. In the past, I start a task, do it for a while and stop randomly. This time I was much cautious not to break the streak. The more I build the streak, the more I committed to doing it every day. I am still surprised I maintained the streak for 91 days, even through the time of health issues. There may be unavoidable circumstances you need a break, but keep it short, maybe once in 14 days. Maintaining the streak each day is not just to complete some random tasks and convince ourselves we have done it for the day. It's about going back to bed you have made satisfying progress for the day and turning it into a habit.

Action items

1. Maintaining the streak can be hard if we haven't plan the day earlier. Always keep yourself committed by adding the task for the next day.
2. Setup a routine to start working in specific time frame suitable for you. Repeating actions in specific time builds personal reminder over time to action.
3. Clear up distractions while you are in your task. This will help you to focus on completion.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 11 of the #14daysbreakloop challenge. Keep track of your streak and best moments in your new tab. Install the extension now from Chrome Web Store and start working on your #100daysofcode

“Goals are about the results you want to achieve. Systems are about the processes that lead to those results. Goals are good for setting a direction, but systems are best for making progress.” - James Clear

While we were doing our college graduation, the ultimate goal for most of us will be to secure a good job. We would spend hours every day learning every concept and successfully land a great job. But do we ever think about continue learning to improve our skills after the job?

Goals are objectives we wish to achieve sometime in the future. But after we achieved, we might forget the purpose of the goal. If we aim for long term success, we should reframe our goals and focus on the systems to reach that. A commitment to a system will make the difference in the long run because systems give you the freedom to do your best work every day without making the same mistakes over and over again. If your current system of work doesn’t work or give the desired results you expect, make a change, create a new system and take steps every day to stick to it.

If you're working towards a goal, reframe it to system first

Before I started to write each day to post a daily blog, I felt doubtful about my writing competency skills. I used to read tons of blogs, get inspired, and tell myself to write a blog by the weekend. When I did write and publish a blog the first time, I expect it would bring lots of people to the blog. And as expected, it didn't happen. When I set a goal to publish an article, my instant gratification brain would expect a positive outcome immediately. If it didn't happen, it would get disappointed and never start it back.

For the past few days, I have been writing blogs daily without expecting any immediate outcomes too. Now I can sense the improvement in my competency skills. Having the system helped me to focus on researching content, taking notes, and structuring the content. Like James Clear says in his book, "If you’re a writer, your goal is to write a book. Your system is the writing schedule that you follow each week".

Choose a system that will take you past the goals.

Action points

1. Having a journal recording your daily activities, opens up room for optimization.
2. List down the skills required to reach the goal.
3. Build a habit to work on those goals. Like if you want to write a book - read & write daily. If you want to build products - build solutions that helps you, may be an automation.
4. If you are taking #100daysofcode challenge, think of it as a system for consistent learning to make this a routine beyond 100 days.

Thought for the day

This article is written by Karthikeyan and co-authored by Rams

This article was written as part of day 10 of the #14daysbreakloop challenge. Get the new tab extension from Chrome Web Store and start working on your #100daysofcode

If you ever felt burnout, you might begin to relate this, how this invites more problems & commitments that you wish could have avoided. It might be hard to accept thinking this will make yourself weak, if you take a break. But I hope it's essential in the long run, if you have to make it to the end. If you felt exhausted, get some good sleep. Do what makes you feel relaxed.

Restore your energy and prepare yourself for bigger things yet to come.

Action items

If you're taking #100daysofcode challenge, it's okay to slow down or take a break

#100daysofcode is a marathon, not a sprint. It is what I told myself often if I felt I was pushing myself too hard. There were a few days I had to take the challenge after the long work in the office. Most of the days, I was exhausted to think clearly about what should I do for the day's challenge?

One thing I began to realize lately is taking care of mental health should be the foremost priority. Be it giving yourself a break, relaxing with your favorite music, or slowing a little bit with less intensive tasks for your goal. Do what works for you to restore your energy.

Remember, there are a lot more exciting things ahead. If you feel a little bit down, just listen to what your mind and body says. Do not stress yourself too hard.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan

This article was written as part of day 09 of the #14daysbreakloop challenge. Get the new tab extension from Chrome Web Store and start working on your #100daysofcode

Can I do it? We have the habit of asking this to ourselves. Doubting our competency skills will affect us in the long run. Always ask yourself, are you working on optimizing time & learning that will drive the positive outcome - Will what I do right now make me do it?

You have the choice to work on it every day that will give you positive consequences. Don't do it because you want to avoid failure. Do it because you want to achieve success. It might be the first reason that ends up stop what we are doing.

Don't be the failure avoider, be a success seeker.

Spread yourself with positivity around

We cannot always try to venture alone. There are a lot more things we can learn from each other. Community is the last best thing to surround yourself with positivity. The Twitter community had been the biggest support for me while I was taking my #100daysofcode challenge. I can still remember the first time I asked Twitter how do I change myself from the passive consumer. A lot more people offer their suggestions to not think about being right always. Only after a few months, I realize that I felt doubt about my competency. And how bad it impacted my motivation to continue progress.

Geller's work on self-motivation

Psychologist Scott Geller is at the forefront of research on self-motivation. If you believe the actions towards your goal is worth it, you have weighed the cost against the consequences and decided the consequences outweigh the cost.

Geller considers “consequences” to be one of four vital “C” words that underpin self-motivation:

1. Consequences: To be self-motivated, you sincerely have to want the consequences associated with the actions you take rather than simply doing something to avoid negative consequences;
2. Competence: Can I do it? Will it work? Is it worth? If you answer all three of the questions with a “yes,” you will feel competent in your ability to get things done;
3. Choice: Having a sense of autonomy over your actions encourages self-motivation;
4. Community: Having social support and connections with others is critical for feeling motivated and believing in yourself and your power to achieve.

Action points

1. Embracing the little wins you had will drive the inner motivation with you by amplifying the positive vibes.
2. Join communities & surround yourself with people spreading positivity. For us, the Twitter community motivated us a lot.
3. Set realistic goals and spend some time planning on how to reach them. Get help when you needed it.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 08 of the #14daysbreakloop challenge. Install the extension now from Chrome Web Store and start working on your #100daysofcode

I had this feeling earlier. I knew I was spending a lot of effort than earlier but why can't I see the convincing difference from my past. I realized the point then, making meaningful progress in life goals is more than loading ourselves with to-do lists. I decided to take a pause & look at the path I traveled. There were a lot more bitter truths that unravel, which was hard to confront at first.

Why everyone should do a weekly review

We are always overwhelmed with the current tasks in our follow up. And we often forget the need to take a pause and analyze what we are missing right now. A weekly review is all about clarity and direction. As they say, “what gets measured gets managed”. If you have an eye towards improving your productivity, tracking it closely during your weekly review will help you get more done. It reflects on the following insights,

• What did I get done this week versus what I planned to get done?
• What unexpectedly arose this week that blocked my productivity?
• Why was I so efficient this week as compared to the last one?

David Allen’s "Getting Things Done" methodology for reviewing

1. Get clear - Empty your mind. Write down everything you have done in the past week.
2. Get current - Review the outstanding tasks in the past and important things that need to be done next. It's all about reflecting on what you are doing now.
3. Get creative - Review someday tasks and be open to being creative to shape bold projects to reality.

Action items

Some important questions to consider while you review

• How do I feel I did this week overall?
• What enabled me to reach my goals this week?
• Has anything stopped me from reaching my goals this week?
• Which actions did I take this week that will propel me towards my long-term goals?
• How can I improve for next week?
• What can I do next week that will set me up for my long-term goals?

Thought for the day

This article is written by Karthikeyan and co-authored by Rams.

This article was written as part of day 07 of the #14daysbreakloop challenge. Plan your weekly tasks, timeline view to track the progress all in your new tab. Install the extension now from Chrome Web Store and start working on your #100daysofcode

Unless you experience, never knew the importance

Three months back, when I started to learn and build for my product, the hard part each day I had is, What should I do today? I used to think hours what should I do next. Think tons of ideas to implement for the next few days, feeling pumped up, would do nothing. I stuck in the same terrain for a few days. Only then, I started to plan for the week's tasks.

The second thing I got stuck with is postponing important tasks. I would have a list of items on my to-do list. Every time I would start with the easiest one first. I had the feeling those days, at least I would have completed one task if I choose the easiest one. Only then it creates more issues, the most important task I have to finish, keeps jumping to the next day.

Supercharge your tomorrow with SMART todo-list

Charles Duhigg shares a similar experience in his past and how this let to write his book - "Smarter, Faster, Better". For a to-do list to be really effective it has to do two things. Push us to do the most important task first and should exactly tell how it should get done.

He breaks this into elements that make the to-do list effective.

1. Stretch goals - A big ambition, at end of the day, our most important objective.
2. SMART goals - Taking that big ambition goal and breaking it into tasks that are smart, measurable, achievable, realistic, and timeline specific.

Best to-do lists are ones that remind us what to do next.

Action items

1. Let's categorize the goals we break down earlier and check whether it passes the SMART tasks.
2. To start with simple, let's list down the tasks that we are going to do in the next 3 days. Having a objective based on the week might push you to work ambitious every day and measure at end of the week.
3. Add the most important tasks to your personal to-do list and make sure to answer the question, what one thing will push you one step further each day.

Thought for the day

This article is written by Karthikeyan and co-authored by Rams.

This article was written as part of day 06 of the #14daysbreakloop challenge. Plan your weekly tasks - one thing that pushes you towards your big goal and keep an eye on not running out of your task list charge. Install the extension now from Chrome Web Store and start working on your #100daysofcode

Every big win is compounded by small wins. If we haven't thought of a way to celebrate, we should rethink our process. Because falling in love with the process is all we need. Big wins are rare. End we are chasing towards, may be successful or not. Take a look back and amplify the wins you had earlier and enjoy the journey. Celebrating little wins also rethinks the way we define our process.

Fall in love with the process

I still remember the time, I can't focus on much spending time for my #100daysofcode challenge in the initial days. I would do a project one day, then the next day, I would take a break. At first, I used to feel the moment when I completed the 100 days. But I realized this alone won't be enough to push me further each day. Between, it is so long.

A moment that changes me is the time I posted a daily challenge on Twitter. I got more support from the Twitter community for the work. It made me start working on this challenge again. Every day, in the end, I make sure to post the progress on Twitter. For myself, the reward I set for myself is this. This reward feedback loop pushes me each day to love the process of learning and building cool things. It might be a small win to feel satisfied with, but it's what drives us to be consistent.

You can better make use of celebrating these little wins by defining your reward prior, how you will celebrate at the end of the day, and plan your daily task to that moment. Don't worry. Reward you use to celebrate those little wins might be smaller for others. It is your journey. Learn to fall in love with each moment.

Action Points

1. Create your reward for your big win right now.
2. Every time you win, take some time to enjoy the moment 🎉. Just feel it.

Best moment

Between those small wins, I felt I have to secure the best wins from what I do. These drove me to an idea to record the best moment for a day's goal. The more I keep closing the difference between the most recent best moment, I feel better I am on the right track.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 05 of the #14daysbreakloop challenge. Subscribe to our newsletter to receive the guide directly to your mailbox. Install the extension from Chrome Web Store

To my surprise, the #100daysofcode challenge build a foundational system that I need to work on every day towards my goal. On top of this system, I decided to build my first product - 100daysof.codes. Next, I started to list down, list of skills that I need to improve on to reach the end goal.

Divide goals into batches

The first thing we might all tempt to do is start right away. I can realize the need to work on skills that I need to improve - Learning React in-depth, optimizing development time, learning firebase. But mostly, the realization happens when I hit the situation. I decided to split my #100daysofcode challenge routine for learning and separate time for product development. Slowly, I can outline my learning & development tasks, and easy to work.

Working in small batches

In the book Lean startup, there was an interesting part I could recall. A father and two daughters got into an argument when they need to stuff newsletters into envelopes. There are 100 enveloped, needs to be addressed, stamped, filled with a letter, and sealed. Father's point is, it needs to processed one envelope at a time. Both the daughters argued at first all 100 envelopes need to be filled and then sealed separately. When they challenged and started to work on it, the father won the challenge.

Our intuition doesn't take into account the time needed for intermediate switching and the cost of failure scenarios. We convince ourselves that we can complete it in a single take. But when we work in small batches, the learning is instant and we act on it our mistakes faster.

The answer I told myself for the right task

After I launched the product, how do I know what part of the task I worked on impacted, and what part not? I realized the importance of thinking backward while planning. Some of the daily tasks have not much impact and some contributed. The efficiency is not working in terms of hours and it is about minimizing the not so impactful task. It's not always about right, it's about learning faster from our mistakes.

Action Items

1. We have provided you a spreadsheet template here. Make a copy and list down every task you think of to work on that goal and try to answer each question below.
2. How impactful this will be to your end goal?
3. Skills need to acquire?
4. Consider you have failed to complete this task and think of listing down the reasons. It might be helpful to forecast and analyze possible failure scenarios.
5. How much time you estimate for completion?

Maintain this sheet every time you work on a task. It might be helpful when you need to analyze for an opportunity to improve yourself in the future.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 04 of the #14daysbreakloop challenge. Subscribe to our newsletter to receive the guide directly to your mailbox.

It's not we are not competent to achieve a goal. Too many goals with their own willpower cancel out each other. The more direction you get pulled in, the less distance you'll travel.

I can relate to this when I was building an app and planning to launch it at the end of the month. First, I immediately start to plan with a bunch of features and push myself to develop them. As the deadline approaches, I had a bunch of fixes and undeveloped features. Sometimes I want to postpone the deadline a little further, hoping I can finish if there's a little more time. By the time I launch, I already exhausted a lot in the process.

We blame ourselves there isn't enough time in a day. We feel endlessly conflicted. And what happens to us is stronger than our ability to combat it. The clocks will never adjust for us to go beyond 24 hours. We should learn to say no to things that are not so important.

Perseverance to success comes with immense will power and self-control to say no to our temptations. We must train ourselves to say no to what doesn't matters to reach the goal without quitting. We can do this together.

Action items

1. Set your goal higher - More powerful and impactful it is, lesser the chance you think about other things.
2. Pick the tasks that only directly impacts your goal.
3. Never work on more than one objective at a time.
4. Always have your decisions noted. Remember why you are doing this. This will neutralize your idle wants.

Willpower - Super strength within to say no

When I was taking the #100daysofcode challenge, I got stuck in the initial days. Only when I said to myself, at the end of 100 days, I should have launched my product, I bring up my willpower to stay consistent. But this will be the hardest thing I think I had in the journey, always boosting my will to stay on track and postpone alternative desires for instant gratification. There were days I had my inner voice saying it's just one day to skip. To my experience, this is far more reason I said to myself for procrastinating.

Saying no to alternatives, preventing distractions all require powerful inner strength. It sure cannot be built in a day, but it's the thing that we should be working to improve every day. Powerful it is, the lesser the chance we quit.

100daysof.codes developed primarily on this, focusing on working in smaller batches and picking one task enough to push one step ahead to the goal.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 03 of the #14daysbreakloop challenge. Subscribe to our newsletter to receive the guide directly to your mailbox.

On day 02, let's start focusing on the goals that matters. We have attached the sheets template with this article to help prioritizing your goals from the wishlist.

Passion + Measurable outcome at a point in time = End goal.

Have you ever felt stuck at some point questioning why are we doing this? And this where most of the time, we take wrong turns or stop what doing. Most of the tasks we intended to choose what we do every day are motivated by this - I can do this? But without passion and measuring how it will impact your life in both positive and negative ways, the likelihood of succeeding is less.

End goals are what remind us why we do what we do every day. And without why, we would lose the motivation to do in the long run.

Mihaly Csikszentmihalyi states it in the book Flow as, "It is necessary to invest in goals that are so persuasive that they justify an effort even when our resources are exhausted and when fate is merciless in refusing us a chance at having a comfortable life."

It's easy to convince ourselves that the dot will connect in the future. Trust us, most of the time, it won't. Sometimes we have to place the dot with the end in mind.

Action points

1. We have provided you a spreadsheet template here. Make a copy and list down the goals.
2. Answer these questions for each goals - How passion are you?, How impactful this will be after X months?, Time expected?
3. It's good to have the list the next time you choose to work on a goal. Just make sure to question yourself, does it offer value more than others in the list. Your reason to why you have to choose to work this now.

Our end goal - At end of the #100daysofcode challenge, launch 100daysof.codes

I started #100daysofcode to improve my coding skills . I couldn't measure what is the right way or the wrong way at first. Choosing the goal to improve code doesn't help me measure. I had to take a break 2 - 3 times in between.

I decided to take some time and choose my end goal to build the product. I felt it was a better one for me, because.

1. Passion to build my own product.
2. Measurable - I can measure the impact it would have on my future.
3. Time bounded - I mark the calendar November 24 to launch it.

I was surprised at the end, how it made me push beyond the limit of what I thought earlier was a limit to me. I can able to measure I was coding better by the speed I could solve a problem. Learned the importance of having the system at first to reach the goal - settling myself every day at 7 pm to code, review the past actions, validating mistakes for positive outcomes.

It might be a harder one, but it is essential to drive you each day when you chose your daily goal. That's why we chose to ask for the end goal on the first screen when you installed the extension.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

This article was written as part of day 02 of the #14daysbreakloop challenge. Subscribe to our newsletter to receive the guide directly to your mailbox.

It might be the easiest thing you said to yourself. And in the end, you always end up doing something else. The most common reason you said to yourself is that you will work on this from this month or year. Waiting for the perfect circumstances to start is the most common way of procrastinating.

I am the person who gets much excited from the arrival of the new year to the weekend to start work on dream goals. I always had a list of goals in the wishlist. And most of them are what I wished some years back. Yes, it indeed became a dream goal for me. Dreams that never became real.

Something interesting starts to happen when I started taking the #100daysofcode challenge. After a few struggles at first, I focused on the systems to reach my goal.

Push yourself to an environment that will help you reach your goals. You will see yourself you are working on it, one by one. For those still waiting for the moment to arrive, we created the #14daysbreakloop challenge.

We started this challenge to clear your top pending wishes before 2020 ends. This is the day 01 guide for the #14daybreakloop challenge and we will be posting a daily guide that we have learned in the #100daysofcode challenge that we wish could have learned sooner. If you are already taking the #100daysofcode challenge, we hope you get most of it or if you are a developer who wishes to get out of your comfort zone, we hope our tops will improve yourself to learn consistently.

If I didn't make the first step to start #100daysofcode, I wouldn't get this far - Learning what I once thought was a limit and support of the Twitter community. Everything begins with the first step.

At the first step, I felt to break your inner loop of procrastinating would be to start doing it right now.

Just pick the goal that you feel will improve yourself & start working on it right from now. Think of yourself at the end of 2021 without the skill in your goal list. How hard would it impact you? Just pick the one that will be most impactful.

Action Items

Feature backstory - Why 100daysof.codes was chose to be a new tab extension?

Being an enthusiastic person, I became to start adding the list of tasks to my task manager. My procrastinating brain never changes much. The tasks never get checked at all. I realize I should learn to be consistent in what I do. I started trying to write one task at a time and place it as post-it notes right before my eyes. Focusing my energy on one task at a time improves my productivity since I didn't have to think about rest.

The nearest design we could think of is when we open tabs in our browser. Hoping it might borrow our attention, we placed the question to what to do now, and once added, the task will be in the focus of each new tab.

Thought for the day

This article is written by Rams and co-authored by Karthikeyan.

Subscribe to the 100daysof.codes newsletter to receive the #14daysbreakloop guide in your mailbox which will be published 14 days, daily from December 18.