The first week was rough. Not because anything was broken, but because every single thing I reached for by reflex simply wasn’t there. Where’s the solution explorer? How do I see what’s inside /data/data on the emulator? In the last post I told you I was wrong about VS Code. Today I’ll show you the work it took to make it right: every extension I installed, and which Rider feature each one replaced. Let’s dive in!
For years I said the same thing to anyone who asked me about VS Code: it isn’t an IDE. It’s a code editor, and a code editor isn’t enough to write software seriously. I was wrong. It took a broken Android deploy, months of waiting, and a lot of frustration to show me, and today VS Code is where I write all my code. Let me tell you how I got here.
Sometimes the career path feels less like a ladder and more like a roller coaster: thrilling, scary, and impossible to control. Have you ever felt stuck on the downside, wondering if you’re moving forward at all?
In the last few weeks, everybody has been talking about vibe coding and how easily you can develop an entire system, from zero to hero. This is blowing the minds of most people, and I’ll talk about it in today’s post. But, before talking about vibe coding, I’ll talk about “normal coding” 🤔. Let’s do it!
I believe it’s not so difficult to understand what makes us successful in our careers, but sometimes we need guidance to move forward. So, I dedicated time to read “The Software Engineer’s Guidebook,” and I’ll share some of my thoughts about it, based on my perspective and experience as a Software Engineer and Team Lead.