blaq_coder's profile picture. Software Developer

Blaq Coder

@blaq_coder

Software Developer

Happy Sunday ! 🙃


Day 47/100 #100DaysOfCode - Continued my backend learning today, covered the Node.js event loop. -Also solved the LeetCode POTD… and it was a hard one 🥲

blaq_coder's tweet image. Day 47/100 #100DaysOfCode

- Continued my backend learning today, covered the Node.js event loop.

-Also solved the LeetCode POTD… and it was a hard one 🥲
blaq_coder's tweet image. Day 47/100 #100DaysOfCode

- Continued my backend learning today, covered the Node.js event loop.

-Also solved the LeetCode POTD… and it was a hard one 🥲

Day 46/100 #100DaysOfCode - Continued learning Node.js today. - Also solved the LeetCode POTD.

blaq_coder's tweet image. Day 46/100 #100DaysOfCode

- Continued learning Node.js today.
- Also solved the LeetCode POTD.
blaq_coder's tweet image. Day 46/100 #100DaysOfCode

- Continued learning Node.js today.
- Also solved the LeetCode POTD.

blaq_coder's tweet image.

Gm I’m convinced we don’t have up to 5M devs/engineers on X… If you’re one quote this with anything

yehhmisi's tweet image. Gm 

I’m convinced we don’t have up to 5M devs/engineers on X… 

If you’re one quote this with anything
yehhmisi's tweet image. Gm 

I’m convinced we don’t have up to 5M devs/engineers on X… 

If you’re one quote this with anything


Frontend isn’t dead. It’s just evolving. Every app still needs interfaces, user flows, accessibility, and performance optimizations. Tools change, but the work doesn’t disappear.

FRONTEND IS DEAD!! FRONTEND IS DEAD!! FRONTEND IS DEAD!! FRONTEND IS DEAD!! FRONTEND IS DEAD!! FRONTEND IS DEAD!! FRONTEND IS DEAD!!



Give juniors a supportive environment and they level up FAST

Most juniors aren’t “not production-ready.” Most teams are “not mentorship-ready.” If you expect senior-level architecture from someone with 1–2 years of experience but can’t provide guidance, that’s a culture problem, not a talent problem.



Most juniors aren’t “not production-ready.” Most teams are “not mentorship-ready.” If you expect senior-level architecture from someone with 1–2 years of experience but can’t provide guidance, that’s a culture problem, not a talent problem.


Day 45/100 #100DaysOfCode Started my full-stack journey today! Kicked off learning Node.js, and honestly, it doesn’t feel too unfamiliar. Also managed to solve 2 LeetCode problems today, steady progress!

blaq_coder's tweet image. Day 45/100 #100DaysOfCode

Started my full-stack journey today!
Kicked off learning Node.js, and honestly, it doesn’t feel too unfamiliar.

Also managed to solve 2 LeetCode problems today, steady progress!
blaq_coder's tweet image. Day 45/100 #100DaysOfCode

Started my full-stack journey today!
Kicked off learning Node.js, and honestly, it doesn’t feel too unfamiliar.

Also managed to solve 2 LeetCode problems today, steady progress!
blaq_coder's tweet image. Day 45/100 #100DaysOfCode

Started my full-stack journey today!
Kicked off learning Node.js, and honestly, it doesn’t feel too unfamiliar.

Also managed to solve 2 LeetCode problems today, steady progress!

Nike made shoes that talk to your brain 🤯!


When you’re winning, the grind doesn’t feel like work.


There’s just this weird sad feeling I feel every Sunday evening, just can’t explain it.


Day 45/100 #100DaysOfCode: Shipped my side project! I built Yumly with my knowledge of TypeScript, React, and AI, a recipe-finder app that lets you search for any meal and get ingredients + step-by-step instructions. I’d appreciate any feedback.👇 yumly-gray.vercel.app


Day 44/100 #100DaysOfCode -Solved 1 LeetCode problem -Wrapped up work on Yumly today, just a few finishing touches left on the UI Can’t wait to show you all soon 🤭

blaq_coder's tweet image. Day 44/100 #100DaysOfCode

-Solved 1 LeetCode problem 

-Wrapped up work on Yumly today, just a few finishing touches left on the UI 
Can’t wait to show you all soon 🤭
blaq_coder's tweet image. Day 44/100 #100DaysOfCode

-Solved 1 LeetCode problem 

-Wrapped up work on Yumly today, just a few finishing touches left on the UI 
Can’t wait to show you all soon 🤭

Day 43/100 #100DaysOfCode - Finally fixed the last error Officially integrated AI into Yumly (my recipe finder app) Now it can generate recipes intelligently instead of relying on static API data😎. - Also managed to solve 1 LeetCode problem today

blaq_coder's tweet image. Day 43/100 #100DaysOfCode

- Finally fixed the last error 
Officially integrated AI into Yumly (my recipe finder app) 
Now it can generate recipes intelligently instead of relying on static API data😎.

- Also managed to solve 1 LeetCode problem today

Day 42/100 #100DaysOfCode - Solved 2 LeetCode problems; spent hours understanding the second one (No. 76) - Worked on Yumly, but that error still won’t go 😩 Vercel isn’t recognising my new API key, it keeps using the old (deleted) one 🤦🏽‍♂️

blaq_coder's tweet image. Day 42/100 #100DaysOfCode

- Solved 2 LeetCode problems; spent hours understanding the second one (No. 76) 

- Worked on Yumly, but that error still won’t go 😩
Vercel isn’t recognising my new API key,  it keeps using the old (deleted) one 🤦🏽‍♂️
blaq_coder's tweet image. Day 42/100 #100DaysOfCode

- Solved 2 LeetCode problems; spent hours understanding the second one (No. 76) 

- Worked on Yumly, but that error still won’t go 😩
Vercel isn’t recognising my new API key,  it keeps using the old (deleted) one 🤦🏽‍♂️
blaq_coder's tweet image. Day 42/100 #100DaysOfCode

- Solved 2 LeetCode problems; spent hours understanding the second one (No. 76) 

- Worked on Yumly, but that error still won’t go 😩
Vercel isn’t recognising my new API key,  it keeps using the old (deleted) one 🤦🏽‍♂️

Guyssss!!!! NeetCode is SO good at this DSA thing 😩🔥


Day 41/100 #100DaysOfCode It’s Sunday 😌 Solved the LeetCode problem of the day and took some time to relax. Gotta recharge for the new week

blaq_coder's tweet image. Day 41/100 #100DaysOfCode

It’s Sunday 😌
Solved the LeetCode problem of the day and took some time to relax. Gotta recharge for the new week

Day 40/100 #100DaysOfCode - Spent hours working on Yumly today, still haven’t fixed that stubborn error, and it’s starting to get frustrating 😩 - Also went through all the LeetCode questions I solved earlier this week #BuildInPublic #WebDev

blaq_coder's tweet image. Day 40/100 #100DaysOfCode

- Spent hours working on Yumly today, still haven’t fixed that stubborn error, and it’s starting to get frustrating 😩

- Also went through all the LeetCode questions I solved earlier this week 
#BuildInPublic #WebDev

Day 39/100 #100DaysOfCod - Spent most of today on Yumly (my recipe finder app) Tried combining OpenAI’s API + Google Custom Search to improve recipes, cool setup, but now I’m fighting a 500 error 🥲 - Also squeezed in 1 LeetCode problem

blaq_coder's tweet image. Day 39/100 #100DaysOfCod

- Spent most of today on Yumly (my recipe finder app) 
Tried combining OpenAI’s API + Google Custom Search to improve recipes, cool setup, but now I’m fighting a 500 error 🥲

- Also squeezed in 1 LeetCode problem
blaq_coder's tweet image. Day 39/100 #100DaysOfCod

- Spent most of today on Yumly (my recipe finder app) 
Tried combining OpenAI’s API + Google Custom Search to improve recipes, cool setup, but now I’m fighting a 500 error 🥲

- Also squeezed in 1 LeetCode problem

Every day I try to build something that didn’t exist yesterday. It’s not perfect, but it’s mine and that’s what matters.


United States Trends

Loading...

Something went wrong.


Something went wrong.