In 2020 during the pandemic, I paused all my employment work, went on sabbatical, and decided to work on side projects full time.

At some point, it seemed to me that I lacked discipline and moved too slowly.
That's why I decided to jump into the 100 Days of Code Challenge and see how it would push my progress forward.

Originally 100 Days of Code means a minimum of 1 hour of daily coding. Mostly It's popular among software engineering newcomers as it motivates them to learn systematically.

In my case, 1 hour was not enough, so I picked a modified version: 100 Days of full-time coding.

Simply because why not?

How was it? Well, by the end of those 100 days, I breathe a deep sigh of relief.
Even though I was working only on the things I wanted to, it felt almost like a good old burnout by the end of the challenge.

Weekend days-off matter even if it is pandemic weekends.
Nevertheless, according to my Github account, burnout had no chance to stop me. I just took a day off and continued, lol.

So my challenge lasted a little bit longer than 100 days:

Did it push the progress?

Pretty much yes. I've learned plenty of new things and got done a lot as well.

I've learned how things are done in a server-side swift, and to be more exact - Vapor 4. (I haven't worked on the backend before at all.)

I've learned how to deal with SwiftUI and Redux.

Implemented VaporRestKit to make backend things done faster. and Koalas - a lib to manipulate tabular data in Swift, like with Pandas in Python.

Made a good basement for Portfolius backend and iOS App.

For my lazy ass it's quite a good progress for just 3 months.

Could it be done without 100 Days of Code Challenge?

100 Days of Code Challenge was nothing else but a discipline tool for me.

I'm sure that I could do even better if I had a high-quality rest on the weekends. But only if I could preserve the same commitment during workdays.