My whole team was a circus:
- Dev 1, the senior: he will be spent his days coding his personal projects and will convince management that everyone else needed to prove themselves so he will have nothing to do and we will do all the work.
- Dev 2, the junior: he was convinced that his mission in life was to be friends with his team. He's desk was far from the rest of the team so he will show just right after lunch EVERY FREAKING DAY with a list on his phone of random things he wanted to talk about like music, artists, art, news, etc., he really thought I didn't notice the list.
- Dev 3: the vegan: you will hear on every chance how she was so awesome for being vegan.
- Dev 4, the expert: if you ask him anything he will stare at you in silence to make you feel like you are a stupid for not knowing the answer and then turn around like nothing.
- Dev 5, the ghost: he will show early every day, code without mouthing a word and leave at 5pm, I think I heard him saying "hmmm" once but I might be wrong.
- Dev 6, the coder by accident: he was a graphic designer and ended up doing front end so he hated his job.
- Dev 7, me: the one who didn't care about anything but doing his job and leave.
- The project manager: she didn't knew anything about technology but will attend meetings with clients on her own, commit to deadlines and then inform us that the project that we estimated for 8 weeks will have to be done in 2 with new additions to the features.

You know the drill, here's your potato :/

I’ve pretty bad ADHD (diagnosed) my entire adult life, so focus has been a huge struggle for me forever. Here’s my strategy:
- Noise-canceling headphones blasting chiptunes (Spotify has some, but YouTube has the best selection of old-school video game music) I’m usually way less distracted if I listen to music without lyrics.
- A chair cushion (I actually use one of those ridiculous donut ones, but I put a normal sized pillowcase on it. SO comfortable, even after many hours.)
- THE POMODORO METHOD. 25 minutes hardcore coding/debugging, followed by 5 minute intervals for breaks, like checking fb, etc. (Breaks are totally optional if you’re in the zone tho 💪) It’s a great way to reward your brain for focusing.
- And if all else fails, the looming threat of unemployment is always there to keep you motivated 🙃 (Sad but true— always crosses my mind when I’m starting to fall behind on a task)

Is it just me or headphones and good music is a must for coding?

Coding while listening to Linkin Park.

"The Perils and Triumphs of Debugging: A Developer's Odyssey"

You know you're in for an adventurous coding session when you decide to dive headfirst into debugging. It's like setting sail on the tumultuous seas of code, not quite sure if you'll end up on the shores of success or stranded on the island of endless errors.

As a developer, I often find myself in this perilous predicament, armed with my trusty text editor and a cup of coffee, ready to conquer the bugs lurking in the shadows. The first line of code looks innocent enough, but little did I know that it was the calm before the storm.

The journey begins with that one cryptic error message that might as well be written in an ancient, forgotten language. It's a puzzle, a riddle, and a test of patience all rolled into one. You read it, re-read it, and then call over your colleague, hoping they possess the magical incantation to decipher it. Alas, they're just as clueless.

With each debugging attempt, you explore uncharted territories of your codebase, and every line feels like a step into the abyss. You question your life choices and wonder why you didn't become a chef instead. But then, as you unravel one issue, two more pop up like hydra heads. The sense of despair is palpable.

But, my fellow developers, there's a silver lining in this chaotic journey. The moment when you finally squash that bug is an unparalleled triumph. It's the victory music after a challenging boss fight, the "Eureka!" moment that echoes through the office, and the affirmation that, yes, you can tame this unruly beast we call code.

So, the next time you find yourself knee-deep in debugging hell, remember that you're not alone. We've all been there, and we've all emerged stronger, wiser, and maybe just a little crazier. Debugging is our odyssey, and every error is a dragon to be slain. Embrace the chaos, and may your code be ever bug-free!

So I start listening to songs on a local platform in the morning while coding, switch to youtube playlists after lunch and have a developed a habit of switching to yet another platform by evening. It's not just switching genres based on moods and workload anymore but also having preferences between various music streaming platforms. Life is great with so many options available.

I hate programming in school. I literally need to listen to music to stay focus when I'm tired.

Coffee, music, code and repeat.

🚀 “I Wanted GitHub Copilot in My Pocket — So I Built It Myself”

For years, I’ve had this weird habit of coding from random places — cafés, buses, hospital waiting rooms, you name it. But every time inspiration hit, I found myself thinking the same thing:

“Man, I wish I could just use Copilot on my phone.”

It’s 2025. We’ve got AI writing novels, generating music, and summarizing 500-page research papers in 2 seconds — yet somehow, GitHub Copilot still refuses to leave the comfort of VS Code on desktop.

So I decided to fix that.

💡 The Idea

It started as frustration — a “wouldn’t it be cool if” moment. I was halfway through an idea for a small project on a train, and my brain screamed:

“Why can’t I just ask Copilot to finish this function right now?”

VS Code was sitting at home, my laptop was dead, and all I had was my phone.

That night, I scribbled this into my notes app:

“Bridge Copilot from VS Code → phone → secure channel → no cloud.”

At the time, it sounded insane. Who even wants to make their life harder by reverse-engineering Copilot responses and piping them into React Native?
Apparently — me.

🧩 The Architecture (aka “How to Lose Sleep in 4 Easy Steps”)

The system ended up like this:

VS Code Extension <-> WebSocket <-> Discovery API (Go + Redis) <-> React Native App

Here’s how it works:

The VS Code extension runs locally, listening to Copilot’s output stream.

A Go backend acts as a matchmaker — helping my phone and PC find each other securely.

The mobile app connects via WebSocket and authenticates with a 6-digit pairing code.

Once paired, they talk directly. No repo data leaves your machine.

It’s like a tiny encrypted tunnel between your phone and VS Code — only it’s not VPN magic, just some careful WebSocket dancing and token rotation.

🛠️ The Stack

Frontend (Mobile): React Native (Expo)

Backend: Go + Redis for connection brokering

VS Code Extension: TypeScript

Security: JWT + rotating session keys

AI Layer: GitHub Copilot (local interface)

🧠 The Challenges

There’s a difference between an “idea” and a “12-hour debugging nightmare that makes you question your life choices.”

Cross-Network Discovery:
How to connect phone and desktop on different networks?
→ A lightweight Redis broker that just handles handshakes.

Security:
I wasn’t making a mini TeamViewer for hackers.
→ Added expiring pairing codes, user-approval dialogs, and local-only token storage.

Copilot Response Streaming:
Copilot doesn’t have a nice public API.
→ Hooked into VS Code’s Copilot output and streamed it over WebSocket.
(Yes, 2% genius and 98% madness.)

UX:
The first version had a 10-second delay.
After optimizing WebSocket batching and Redis latency, it’s now near-instant.

🤯 The “Holy Sh*t, It Works” Moment

The first time my phone sent a prompt — and my VS Code actually answered with Copilot’s suggestion — I legit screamed.

Like, full-on victory dance in the middle of the night.
There’s something surreal about watching your phone chat with your desktop like they’re old coding buddies.

Now I can literally say:

“Copilot, write me a REST API,”
and my phone responds with fully generated code pulled from my local VS Code instance.

No VPN. No cloud syncing. Just pure, geeky magic.

⚡ The Lessons

The hardest problems aren’t technical — they’re psychological.
Fighting “this is impossible” is the real challenge.

Speed matters more than perfection.
Devs don’t want beauty; they want responsiveness. Anything over 1s feels broken.

Security must never be an afterthought.
I treated this like a bank tunnel between devices, not a toy.

Build for yourself first.
I didn’t make this for investors or glory — I made it because I wanted it.
That’s the best reason to build anything.

🧭 The Future

Now that it’s working, I’m turning this experiment into something shareable.
The dream: an app that lets every developer carry Copilot wherever they go — safely and instantly.

Imagine debugging on your couch, or editing code in bed, or just whispering to your AI assistant while waiting for coffee.

Phones today are more powerful than early NASA computers.
Why shouldn’t they also be your code editor sidekick?

So yeah, that’s my story.
I built VSCoder Copilot — because I wanted to code from anywhere, and I refused to wait for permission.

If you’ve ever built something just to scratch your own itch, you already know this feeling.
That mix of frustration, caffeine, and late-night triumph that reminds you why you fell in love with coding in the first place.

Because at the end of the day, that’s what we do:
We make ideas real — one ridiculous hack at a time. 💻🔥