Thread by @KaanKaraca_

I have decided to share the #dev topics that I will learn or already know. I want to continue this for a long time. Maybe 100 days maybe even more. It will be difficult to make this sustainable, but I think it is necessary for self-motivation. It will be good in the long run. 🚀

https://twitter.com/KaanKaraca_/status/1472638400679321600

#nDaysOfLearning
Day 2:
I continued with the Behavior and Structural Pattern and implemented it in #Golang.

Topics:
- Proxy
- Adaptor
- Iterator
- Observer
- Strategy
- Visitor

#nDaysOfLearning
Day 3:
I prepared a roadmap about data structure and algorithms, system design, and interview behavior. Approximately it will take at least 6 months.

#nDaysOfLearning
#100DaysOfCode
Day 4:
I've read articles and videos about Big O Notation. I looked at not only the programming side but also the math behind it.

Source: github.com/jwasham/coding…

#nDaysOfLearning
#100DaysOfCode
Day 5:
I watched videos and read articles about Arrays. Everything was easy until I saw the LeetCode problems. 🥲

#nDaysOfLearning
#100DaysOfCode
Day 6:
I haven't had much time to study, but I've read a few articles about DDD and CQRS.

Source: threedots.tech
@ThreeDotsLabs

#nDaysOfLearning
#100DaysOfCode
Day 7:
Solved LC problem about DS.

#nDaysOfLearning
#100DaysOfCode
D8:
Solved a couple of LCs. I read an article about how to implement DDD in our Go project in an efficient way and made reviews about code and applied it to my work.
Source:
threedots.tech/post/ddd-cqrs-…
github.com/ThreeDotsLabs/…
thanks to @roblaszczak