Just dropped some fresh dev reads on Medium 🚀 If you love real-world coding insights, bugs, and lessons from the trenches, you’ll enjoy what I write. 👉 Follow me on Medium: https://t.co/gupsuRaCAp Let’s learn & grow together 💻✨ @Medium

JS: “I’ll handle the layout 😤” CSS in 2025: “Bro… relax.” 😎 Modern CSS can replace a LOT of JS. Here’s what every developer should actually be using 👇 https://t.co/qbgwNK8Ode #buildinpublic #LearningInPublic

https://t.co/vwBNhmtJC3

We’ve been using JavaScript to fix CSS problems for years. Turns out… modern CSS already solved most of them. Less JS. Better performance. Cleaner code. Wrote about it here 👇 https://t.co/qbgwNK8Ode #buildinpublic #medium #article #javascript #GMMTVStarlympics2025

Just dropped some fresh dev reads on Medium 🚀 If you love real-world coding insights, bugs, and lessons from the trenches, you’ll enjoy what I write. 👉 Follow me on Medium: https://t.co/gupsuRaCAp Let’s learn & grow together 💻✨ @Medium

JavaScript Interview question: #QuickCode #google #Interviews #Javascript

React’s latest bug wasn’t just “another React issue”. It quietly reminded us that frontend isn’t just UI anymore — it runs on servers, touches infra, and can break like backend. Wrote my thoughts as a dev 👇 https://t.co/JqpOlvTxos

Didn’t expect this kind of response today 🙌 +34 new followers 🚀 Grateful & motivated 💙 Let’s keep building in public 👨‍💻✨

https://t.co/hqck1MV1MB

Q: What’s the difference between == and === in JavaScript? #JavaScript #WebDev #InterviewPrep #Frontend

What will be the output of this code and why? console.log([] + []); If you can explain it confidently, you understand JavaScript coercion better than most. #JavaScript #JSInterview #Frontend #DevTips

The web spoke JSON. The AI era might speak TOON. 🤖✨ #BuildInPublic #AI #DevCommunity #JSON #TOON #TechTwitter

TOON isn’t perfect (yet). It’s still new. Tools and integrations are catching up.And debugging might make you miss those old curly braces 🥲 JSON walked so TOON could run. We’re entering a world where even data formats are optimized for AI efficiency.

TOON’s idea? Declare your keys once → reuse them → save up to 60% tokens. Simple, but kind of genius. No endless curly braces. No duplicate field names. Just structured data that’s LLM-friendly. Basically, JSON went on a diet and came back optimized. ⚡

Then I stumbled on something new TOON (Token Oriented Object Notation). And it actually made me think, is JSON still the right format for AI? 🤔 Every JSON key = tokens. Every token = money. LLMs don’t just read your data — they charge rent for every bracket and quote 😭

The culprit? Every. Single. Quotation. Mark. Turns out, LLMs don’t just process data, they charge for every token they read. And JSON? It’s token-heavy.

JSON is great… until you realize your LLM is charging you for every { and " 💸 It started like any normal day, just me, my API, and a bunch of clean JSON. Until I checked the OpenAI usage dashboard... and nearly spilled my coffee. ☕

In distributed systems, perfection = impossible. Trade-offs = survival.

So next time your Instagram post takes a few seconds to appear everywhere, don’t blame the devs — blame CAP. It’s doing its job keeping the system sane 😅.

Real-world systems: ⚡ AP (Available + Partition Tolerant) → Netflix, Amazon (eventual consistency is fine). 💾 CP (Consistent + Partition Tolerant) → Banking apps (accuracy > uptime).