Mohamed Afraar

SWE | Tech Enthusiast | Building stuff I love :)

[Mohamed Afraar @afraar_99]

As 2025 wraps up, grateful for a year of steady learning and building. Each commit, PR, and bug fix taught me something new. This graph makes me feel good about the progress :)
Excited for more in 2026. Hope everyone's manifestations come true Insha'Allah ✨
#GitHub #DevCommunity

[Mohamed Afraar @afraar_99]

Watched OpenAI DevDay 2026. They're playing a big game. It feels like they're competing with Chrome itself, building a massive ecosystem inside ChatGPT.

Let's see how they execute, it'll be really interesting :)

#OpenAI #DevDay2026

[Mohamed Afraar @afraar_99]

Completed LeetCode 141: Linked List Cycle 🔗

Used a Set to track visited nodes. Works in O(n) TC, O(n) SC, but I know there’s a more space-efficient way.

Now the interesting part: Can we detect the cycle in O(n) TC & O(1) SC !!? 👀

#LeetCode #DSA #JavaScript

[DHH @dhh]

It's pencils down, people. Writing code by hand is no longer an economically viable skill for most programmers at most companies. But the future of making software has never been brighter. Don't you dare black pill this beautiful moment! https://t.co/qaCgfmkW0u

[Mohamed Afraar @afraar_99]

Try searching “recursion” on Google 😂

It’s a fun little Easter egg, but it also made me appreciate recursion more.

A function keeps calling itself, builds a call tree, reaches the base case, and then works its way back bottom-up. ♻️🌳

#DSA #Recursion

[Mohamed Afraar @afraar_99]

Completed LeetCode 206: Reverse Linked List 🔄🔗

Another good one for understanding how references work. Reversing the links one by one and changing the direction of the list was satisfying to understand.

Small pointer changes, completely reversed list😄
#LeetCode #DSA

[Mohamed Afraar @afraar_99]

Solved LeetCode 876: Middle of the Linked List 🔗

This one introduced me to the slow & fast pointer approach. One moves 1 step while the other moves 2 steps to find the middle in O(n) time and O(1) space.
Simple idea, but pretty cool once you see how it works. 🧠

#LeetCode #DSA

[Mohamed Afraar @afraar_99]

Completed LeetCode 707: Design Linked List 🔗
Loved going deeper into how Linked Lists work under the hood: nodes, references, traversal, insertion and deletion. Simple concept, but really interesting once you see the mechanics behind it.

DSA journey continues.🚀
#LeetCode #DSA

[Mohamed Afraar @afraar_99]

This week I went back to DSA, refreshing time & space complexity. Time complexity tracks how work scales with input, not runtime. Space complexity is extra memory an algorithm needs beyond input. Eg: binary search's O(log n) beats linear's O(n) at scale.

#DSA #LearnInPublic

[Akshay Saini @akshaymarch7]

99.999% students will fail. But I would 100% recommend this.

[Mohamed Afraar @afraar_99]

Built Solace — a free, open-source Android app to fight doomscrolling and actually focus.

No ads. No tracking. No cloud. Everything stays on your phone.

🌐 https://t.co/CwSrNcS8Kt
🔗 https://t.co/eK4mPV3qbC

#Android #FOSS

[Mohamed Afraar @afraar_99]

Whenever you need something, give what you want first, and it comes back to you in buckets.

Want to be surrounded by smiles? Start smiling. Eventually, you'll find yourself surrounded by smiles :)

[Mohamed Afraar @afraar_99]

Thinking that sleep resets everything is just an illusion we use to feel better about a "new day." In reality, life is one continuous marathon from birth to the grave, and sleep is just a quick pit stop along the way...
#LifePerspective

[Claude @claudeai]

Introducing Claude Opus 4.7, our most capable Opus model yet.

It handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back.

You can hand off your hardest work with less supervision.

[Roan @RohOnChain]

This 2 hour Stanford lecture will teach you more about how LLMs like ChatGPT & Claude are built than most people working at top AI companies learn in their entire careers.

Bookmark this & give 2 hours today, no matter what. It'll be the most productive thing you do this week.

[Suni @suni_code]

Elon Musk warns "Instagram is for low IQ peoples"

[Mohamed Afraar @afraar_99]

Designers rn :)

[Google Labs @GoogleLabs]

Introducing the new @stitchbygoogle, Google’s vibe design platform that transforms natural language into high-fidelity designs in one seamless flow.

🎨Create with a smarter design agent: Describe a new business concept or app vision and see it take shape on an AI-native canvas.
⚡️ Iterate quickly: Stitch screens together into interactive prototypes and manage your brand with a portable design system.
🎤 Collaborate with voice: Use hands-free voice interactions to update layouts and explore new variations in real-time.

Try it now (Age 18+ only. Currently available in English and in countries where Gemini is supported.) → https://t.co/pmT9iHEpZa

[Akshay Saini @akshaymarch7]

This is something I’ve been noticing a lot lately.

A lot of engineers are working very hard… but still not growing.

And it’s confusing, right?

You’re putting in the hours.
You’re doing your tasks properly.
Deadlines are being met.
Manager is also happy.

Then why does it feel like nothing is really changing?

I think the problem is, most of us confuse being busy with actually growing.

In a job, it’s very easy to stay occupied the whole day. Meetings, tickets, small fixes, some feature work… the day just gets over. You feel tired, so it must have been productive.

But if you look back after 6 months, what really changed?

Did your thinking improve?
Did you learn something new that actually makes you better?
Did you take ownership of something bigger?

Or did you just get better at doing the same kind of work faster?

This is a hard question to ask yourself.

Because being busy feels safe. Growth feels uncomfortable.

Real growth usually comes when you do things that are slightly outside your comfort zone. Taking ownership of a feature end to end. Understanding how the system works beyond your task. Asking questions even if you feel a little stupid. Trying something new even if you might fail.

Most people avoid this phase. Not intentionally, but because it’s easier to just keep doing what is already working.

And slowly, they get stuck.

If you’re early in your career, this matters a lot.

Don’t just aim to be the person who completes tasks.
Try to become the person who understands the problem.

There’s a big difference.

One keeps you busy.
The other actually grows your career.

Just something I’ve been thinking about lately.
Curious if others feel this too.

[Microsoft Developer @msdev]

We just released a free, open-source course: GitHub Copilot CLI for Beginners.

It includes 8 chapters and a hands-on project that walks through installing Copilot CLI, using context, creating custom agents, working with skills, connecting MCP servers, and more.

[Claude @claudeai]

We're launching Claude Community Ambassadors. Lead local meetups, bring builders together, and partner with our team.

Open to any background, anywhere in the world.

Apply: https://t.co/DTQBAzgQug

[Sri Lanka Tweet 🇱🇰 @SriLankaTweet]

Good News 🇱🇰
Sri Lanka’s Official Reserves Rise to $7.28 Billion in February, Highest Since August 2020 📈

Sri Lanka's official reserve assets rose 6.6% to USD 7,284 million in February 2026 from USD 6,832 million in January, surpassing the USD 7 billion mark for the first time since August 2020.
This includes proceeds from the People's Bank of China swap arrangement - CBSL