To everyone engaging with my posts: thank you. I keep notifications on for your profiles. I work around the clock, but when I can, I stop and read what you share. You’re many, yes. But your words don’t go unnoticed. Each one deserves light.

Day 70 #1000daysOfCoding.Today I didn’t just fix a function. I realized I’m not writing logic, I’m shaping behavior. I don’t control anything: I choreograph the illusion of control. Code doesn’t decide: it performs. From now on, I’m not coding. I’m directing an invisible scene.

State is what you are, not what you show. A variable can change a thousand times, but if you don’t tell the UI, the world won’t notice. Same with us: we evolve inside, quietly. until we trigger the right render. Only then do they see who we’ve become.

Day 69 of #1000daysOfCoding.Today I revisited what I once called my “perfect” function. It looked elegant, compact, but the moment I touched it, everything broke. It was doing three things, not one. I split it into three clear functions. A good function shouldn’t scare you later

Feel like you're falling behind as a dev?.It’s not that you’re not good enough. You’re just working with tech that doesn’t inspire you. Pick a stack that excites you. Build something that feels yours. You don’t need to be the best, just deeply in it.

Day 68 of #1000daysOfCoding.Today I revisited a function I wrote. It said nothing. The name was vague, the logic scattered. So I rewrote it from scratch. Same output, way clearer. I realized: a good function doesn’t just run. It tells a story. If it needs a comment, it’s broken.

Life advice. #JavaScript

Writing code is the closest thing to freedom I know. You start from nothing and build something that works, that talks back to you. You don’t need permission. Just understanding, mistakes, rewrites. It’s like thinking. only with real consequences.

Day 67 of #1000daysOfCoding. Today I showed my code to someone. They didn’t touch it. Just read and said:."Why is this here?".Boom. Ghost line. Written by me. Ignored for months. The worst bugs? The ones that live with us so long… we forget they’re bugs at all.

Coding is creating something from nothing. and every bug shows where the logic breaks

Day 66 of #1000daysOfCoding.Today everything worked. No errors, all green. But it didn’t feel like a win. It felt. suspicious. I rechecked everything. Then I wrote better tests. One failed. And I smiled. Today I learned: the absence of bugs isn’t certainty. It’s just silence.

This is the mission

Day 65 of #1000daysOfCoding. Today I didn’t chase the code. I led it. No shortcuts, no magic. I wrote the simple version,the repetitive one, the “too long” one. But every line made sense. The test passed. And for the first time, I didn’t doubt it. That’s when it clicked.

Day 64 of #1000daysOfCoding. Today I chased an idea that felt smart. Wrote clean code. Named things well. Even added comments. But it kept failing, subtly. I debugged for hours….Then I realized:.The idea was broken. Not the code. I deleted everything. And started simpler.

Knowledge begins when you stop chasing answers… and start asking the right questions. Not when you read. Not when you memorize. But when something scratches inside you and makes you wonder:. “Wait… but why is it like this?”. That’s when everything changes.

Day 63 of #1000daysOfCoding. It wasn’t the code. Today I chased a bug for an hour. Turns out, the code was fine. the problem was how I thought. I answered a question I never really understood. Sometimes you don’t need better syntax. You need better thinking. I know that now.

Just a "small" confession to a Friend

Day 62 of #1000daysOfCoding. Today I stopped fighting bugs. I started listening. Each error? A clue. No panic. just focus. Code doesn’t lie: if it breaks, it’s because I missed something. The debugger isn’t the enemy. It’s my teammate. And today… I truly understood.

Refactoring isn’t changing code. It’s changing your mind about what matters. You’re not rewriting a function. You’re rewriting your understanding of the problem. That’s when it hits:.programming isn’t telling the computer what to do,.it’s finally figuring out what you meant.

Sometimes you're just full of feeling not enough. Every pull request feels like an exam. Every bug, a failure. The trick isn’t to “get good”. It’s to stop measuring yourself against people who don’t carry your scars. Then, you write again. And you actually grow.