Day 6 complete ✅
Today I learned about Python project structure, explored pure vs impure functions, and watched some helpful sections from a Python course on Udemy.
#day6#180daysofcode
Day 5 update 😴
Missed the log yesterday because I slept early.
Here’s what I worked on:
→ Learned internal implementation of lists & tuples
→ Understood why tuples are hashable
→ Explored a few more Python internals
Back on track
#Day4#Python#180DaysOfCode#BuildInPublic
Day 16/180 of #180DaysOfCode 🔥
Today I revised Arrays thoroughly and solved some solid problems! ✅
Strengthened my concepts and improved speed on edge cases.
Small daily wins adding up. On to the next! 💪
#DSA#Coding#LearnInPublic
Thanks to @kunalstwt
Day 47&48 of #180daysofcode
- learned authentication and authorisation from cohort'26
- learned how to send emails using nodemailer.
- learned how to structure auth services and create a reusable code.
Not so consistent because of my college stuffs going on,still managing to show up daily.
- next target:- practising auth by myself and become confident in authentication and authorisation.
That's it for today,time to do it again tomorrow.
@Hiteshdotcom@piyushgarg_dev@nirudhuuu@yntpdotme#chaicode#webdevelopment#learninpublic#coding
Day 14 of #180DaysofCode 🔥 Methods (functions) = your DSA superpower.
One good method = reusable magic. One bad method = debugging nightmare. Let's break it down ↓
Day 46 of #180daysofcode
Spent the day diving deep into SQL! 🗄️
🔥 Practiced hands-on challenges at ChaiCode SQL Labs.
🧠 Cracked several SQL interview questions focusing on complex joins and aggregations.
🛠️ Refining those database querying skills to be more efficient and precise.
Getting more comfortable with data every day! 📈
@Hiteshdotcom@piyushgarg_dev
Day 45 of #180daysofcode
Just wrapped up Part 2 of the SQL series in the cohort! 🚀
Today’s deep dive:
🔹 Mastering Joins (Inner, Left, Right, Full)
🔹 Transactions & the power of ACID properties
🔹 NoSQL vs. Key-Value stores
🔹 Mapping out the ER diagram for Instagram
Data modeling is starting to click. Building the backbone of the apps we use daily is a different kind of satisfying. 💻
@Hiteshdotcom@piyushgarg_dev#BuildingInPublic#SQL#Backend#Learning
Day 45 of #180daysofcode
Just wrapped up Part 2 of the SQL series in the cohort! 🚀
Today’s deep dive:
🔹 Mastering Joins (Inner, Left, Right, Full)
🔹 Transactions & the power of ACID properties
🔹 NoSQL vs. Key-Value stores
🔹 Mapping out the ER diagram for Instagram
Data modeling is starting to click. Building the backbone of the apps we use daily is a different kind of satisfying. 💻
@Hiteshdotcom@piyushgarg_dev#BuildingInPublic#SQL#Backend#Learning
Day 43 of #180daysofcode
Finally wrapped my head around JWTs and secure auth flows today! 🔑
It’s one thing to use an app, but building the registration, password hashing, and "forgot password" logic from scratch makes you realize how much goes into keeping user data safe.
Backend development is starting to click. 💻✨
@Hiteshdotcom@piyushgarg_dev@ChaiCodeHQ#100DaysOfCode#Backend#Programming
day 42 of #180daysofcode
Standardization > Speed. 💎
I’m deep into my #180DaysOfCode journey, and today was a masterclass in API reliability. If you aren't doing these three things, your backend is living on the edge:
1. Schema Validation with Joi :- Don't trust the client. Ever. Using Joi allows me to define strict blueprints for incoming data. It’s the difference between a secure app and a broken database.
2. Serialization / Deserialization :- Data shouldn't just flow through; it should be curated.
Deserialization: Converting incoming JSON into usable domain models.
Serialization: Stripping away sensitive data (like password_hash or __v) before the JSON hits the wire.
3. Global Error Handling :- Throwing random strings as errors is a recipe for disaster. By standardizing APIError classes, I can send back consistent error codes and messages that the frontend can actually use to show helpful UI alerts.
Clean code isn't just about how it looks; it's about how it behaves when things go wrong. 🚀
thanks to @Hiteshdotcom for amazing explanation .
@piyushgarg_dev@ChaiCodeHQ#coding#programming#javascript#180DaysOfCode
Day 41 of #180DaysOfCode
Learned how to structure a backend project properly — separating routes, controllers, models, and validations.
Also understood how files connect and how data flows across the app.
Explored validations using Joi to keep data clean and avoid bugs.
At first, everything felt confusing… but now it’s starting to make sense.
Small progress, but moving forward ⚡.
That's it for today,time to do it again tomorrow.
@Hiteshdotcom@piyushgarg_dev@ChaiCodeHQ#backend#nodejs#codingjourney#buildinpublic
Day 40 of #180daysofcode
Today I learned how to properly structure my projects — and honestly, it changes everything.
Clean folder structure, separation of concerns, scalable code organization… this is what turns beginner code into professional-level work.
@piyushgarg_dev
Day 38 of #180daysofcode
- learned typescript and revised some javascript concepts.
- solved 2 questions on stack.
That's it for today,time to do it again tomorrow.
Day 37 of #180daysofcode
- learned typescript and revised some javascript concepts.
- solved 3 questions on stack.
That's it for today,time to do it again tomorrow.