Turning starch into scalable architecture! π₯β¨ | π» Learning JS & sharing the bugs π wins π | Documenting my #CodeNewbie journey π±π
Joined March 2026
- Tweets 301
- Following 135
- Followers 75
- Likes 1,508
35 Photos and videos
Day 1/7 - Async JavaScript Reset.
Going back to rebuild last week(Day 36-39) from scratch.
Today: understanding why async, how time works in single-threaded engine, and and what setTimeout(0) actually does.
Foundations before speed. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
2
5
Day 39 - learned AbortController for cancellation, timeouts, and proper cleanup.
Seeing how to gracefully kill async operations instead of letting them hang is a game changer. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
2
17
Day 38 - learned concurrency patterns: race conditions, mutex, and semaphore.
I also built a simple Mutex class to handle shared resource access safely. π₯π§βπ»
Async is feeling more and more structured.
#100DaysOfCode #JavaScript #BuildInPublic
1
1
42
Day 37 continuation - struggled 3 days with async iterators and generators. I will say like 70% Finally clicked.
Built a retry function inside an async generator. Failed a lot, kept fixing, eventually worked. π₯π§βπ»
Persistence > talent.
#100DaysOfCode #JavaScript #BuildInPublic
1
9
118
Day 37 - Being tackling async iterators and generators for 2days now. Honestly stressing me out π₯²
Still trying to wrap my head around how for await...of and async yield actually flow.
Any good resources or advice? Drop them please. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
3
53
Day 36 - Did a deep dive into the event loop, microtasks vs macrotasks, and CPU-blocking.
Also touched sequential vs concurrent async, timeouts, retries, and debounce.
Async feels less like magic now. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
8
99
Just hit 50 followers.
Still coding. Still posting. Still showing up.
This is just the warm-up. π₯π§βπ»
#100DaysOfCode #BuildInPublic
1
1
3
212
Day 35: review day.
Audited my previous code for memory leaks, fixed unmanaged listeners, and tightened cleanup patterns from this week. Inspected my Day 14 Logger class code for memory leaks as well.
Memory makes way more sense now. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
2
4
162
Day 34 - learned event listeners, proper cleanup, and memory-safe patterns...
Started with " import { EventEmitter } from 'events' ", then dove deeper into how unmanaged listeners quietly cause memory leaks.
Todayβs lesson connect well with this weekβs memory work. π₯π§βπ»
1
8
512
Day 33 - learned performance profiling with Chrome Memory tab and heap snapshots.
Also answered AI-generated questions on Day 31-33: garbage collection, memory leaks, and profiling.
Still solidifying the under-the-hood knowledge. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
1
5
154
Day 32: picked up from yesterdayβs memory management lesson and focused on memory leaks today.
Learning how they happen, how to spot them, and how to prevent them early.
Still under the hoodπ₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
1
4
103
Day 31: garbage collection and V8 internals.
Learned how JS cleans up unused memory with mark-and-sweep, and why memory management matters more than I thought.
More under-the-hood work today. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
5
106
Day 30: review day.
Implemented day 27-29 compose(), pipe(), curry(), and memoize() while revising this weekβs functional patterns.
Slowly getting more comfortable with functional JavaScript. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
3
90
Day 29: memoization and caching patterns.
Learned how to avoid repeating expensive work by storing results and reusing them when the same input shows up again. With that, I was able to memoize a recursive function.
faster logic. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
2
57
Day 28: currying and partial application.
Learned how to break functions into smaller reusable steps by pre-filling arguments using the 'lodash' JS Library. I was also able to build my own curry function.
Small shift, but better. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
4
42
Day 27: higher-order functions and function composition.
Learned how functions can take in other functions, return them, and chain logic more cleanly. I went on to walk on a functions pipeline.
JS is starting to feel more expressive. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
10
291
Day 26: pure functions, immutability, and side effects.
Learnt how to write functions without mutating data or relying on hidden state.
Functional thinking is starting to click. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
4
73
Day 25: review day.
Reviewed Maps, Sets, WeakMaps, Symbols, Iterators, and Generators.
This week really changed how I think about handling data in JavaScript. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
1
2
98
Day 24: learned generators and how yield can pause and resume execution.
Built an infinite ID generator, which made lazy sequences click for me.
Less code, cleaner iteration. π₯π§βπ»
#100DaysOfCode #JavaScript #BuildInPublic
6
104