From coder to product engineer: the shift in perspective

I used to measure my success in lines of code. 💻 Now I measure it in user impact. 👨🏻💻 Transitioning from a developer mindset to a product mindset was humbling. 😇 As a dev, I focused on clean architecture and scalability. As a PM, I realized — no one cares about your code if it doesn’t solve a real problem. Once I started asking “Why are we building this?” instead of “How do we build this?”, 🤔 everything changed — user satisfaction, delivery speed, even team motivation. If you’re a developer thinking about product — start by learning to fall in love with the problem, not the solution. 🚀 #Technicalwriter #Techlife #TechComm #TechnicalWriting #ITProfessionals #LifeInTech #developer #productmanagement

Back to Code. After 10 Years. I hadn’t written a line of code in a decade. Years in Product Management can do that to you. But here I am, back at it. It started with a push from a friend, then the right tools. Cursor IDE for code, Vercel or Replit for frontend. Frictionless stacks make learning addictive again. Patience was key. You wrestle with syntax, hallucinations, and humility, but friction builds fluency. LLMs changed the game. They won’t write perfect code, but 70% right is enough to move fast and build momentum. There’s never been a better time to code not as an engineer, but as a builder. With prototypes, workflows, and AI agents, the line between PM and dev is disappearing. If you’re a PM or founder thinking of jumping back in, happy to share what worked. This time, coding feels less like typing… and more like thinking in motion.

The best PMs are secretly becoming indie hackers. As a former dev who’s played with low-code for years I’ve always believed the future of Product Managers was to become Product Builders. When I started learning programming, I just wanted to build my own applications. But what it really taught me was how products are built. And that changed everything. When you know how things are built and monetized, you understand better what to build & why. You speak the same language as your developers and CEO. You understand trade-offs, constraints, & opportunities. It’s not a requirement but it builds empathy & alignment. You’re not just a bridge between design and engineering, you’re building with them. Are PMs turning into solo builders or is this just a phase?

Engineering Beyond Code: What Senior Developers Often Learn the Hard Way When I started my career as a software engineer, I thought success meant writing the cleanest code, mastering every framework, and fixing bugs faster than anyone else. Years later, as a senior engineer, I’ve realized that technical excellence is only half the equation. The real differentiators are communication, empathy, and decision-making under ambiguity. I’ve seen brilliant engineers struggle — not because they lacked skill, but because they couldn’t explain their ideas, align with product goals, or mentor others effectively. Today, my biggest wins don’t come from the most elegant algorithms I write — they come from: Unblocking a teammate who’s been stuck for hours. Saying “no” to a technically cool but strategically wrong feature. Designing systems that others enjoy maintaining. Turning complex problems into clear, actionable discussions. Being “senior” isn’t just about writing better code — it’s about amplifying the impact of everyone around you. If you’re an engineer on your way up, here’s my advice: 👉 Keep learning your craft — deeply. 👉 But also learn to listen, teach, and influence. That’s how you evolve from a great developer into a great engineer. #SoftwareEngineering #Leadership #CareerGrowth #EngineeringCulture #SeniorEngineer

Hello product lovers 💃💃💃 STORY POST — “Last Week Was Hard… But It Finally Started Making Sense.” Last week at Tech4Dev pushed me far outside my comfort zone. I won’t lie — stepping into the technical side of product management was confusing, overwhelming, and honestly… a little intimidating at first. But that’s exactly where the growth happened. 🔹 Programming The first time I looked at functions, conditionals, and logic flow, my brain said, “What is this??” But as I kept going, I began to see the beauty in how logic turns into real user actions. Now I understand why PMs must think in terms of flows, states, and edge cases — not just features. Understanding different programming language help PM communication better with engineers , also help make more technical inform decisions. Databases Databases were another stretch. Tables, relationships, foreign keys — it felt like trying to organize a world I couldn’t see. But once it clicked, I realized how essential a solid data schema is to every product. A product can look perfect on the surface, but without clean data… everything breaks. 🔹 APIs APIs confused me the most at first. Endpoints, status codes, JSON responses — it felt like decoding a new language. But then I saw how one API call can power login, payment, notifications… That’s when it hit me: APIs are the communication layer that holds the whole experience together. And here’s the biggest insight of the week: Technical understanding gives PMs clarity. Clarity gives confidence. And confidence changes how you build products. The confusion, the struggle, the “wait, what?” moments — they were all part of becoming a better thinker, collaborator, and decision-maker. If you’re learning something new and it feels hard… stay with it. One day it clicks — and it’s worth it. 🌱✨ #Tech4Dev #ProductManagement #TechnicalPM #API #Databases #Programming #GrowthMindset #LearningInPublic #Storytelling

Before you hit "submit" on that code review, you rewrite your comment three times. 🫥 Too harsh? Too vague? Will this demotivate them? 🤔 This is the hidden cost of code review. You're not just evaluating code; you're managing relationships, protecting egos, and maintaining team culture. Multiply that across dozens of reviews each week, and it becomes draining. Here's the thing: developers tend to accept automated feedback more readily. When Refacto flags an issue, nobody takes it personally. It's not their senior developer telling them they made a mistake. It's just the tool, pointing out objective problems. This shifts your focus to where human insight matters most. Instead of itemizing every formatting issue, you discuss trade-offs. Instead of pointing out missing tests, you talk about architecture. Your feedback becomes mentorship, not nitpicking. 🚀 The emotional labor doesn't disappear, but it shifts to where it's actually valuable. 🦾 How do you strike a balance between honest feedback and team morale? #Productivity #Growth #AICodeReviews #CodeReviews #DevelopersCommunity

You’re doing product–dev alignment wrong. Here’s how to fix it: Founders tell us they “just need the dev team to move faster.” Developers tell us they “just need clearer direction.” Both are right. Both are stuck. Here’s what usually goes wrong: – Features get prioritized before outcomes. – Feedback comes too late. – Scope changes don’t reach the people writing the code. It’s not a speed problem. It’s a signal problem. Fix the signals → the team moves fast naturally. Ignore them → you’ll spend months debugging communication instead of code. Your product can’t move faster than your clarity.

"I build great products through software engineering.” That one sentence, from my colleague Tobias Magnusson, might just be the best one-liner summary I’ve ever heard of what a great software engineer actually does. 🔥 It captures something that’s (too) often overlooked — especially in hiring, team building or delivery discussions. We talk a lot about frameworks, tooling and seniority levels, but rarely enough about the core: a product mindset. ✅ Because it’s one thing to write solid code, follow the process and know your tools. 👉 It’s something else entirely to think in outcomes, understand the business context and make decisions that serve the product (not just the codebase). Sometimes it feels like the technology starts to live a life of its own, and the stack becomes a goal in itself. Choosing a “cool” tech stack might indeed help attract developers, but the end user doesn’t care whether their problem was solved using Rust or glue & duct tape. 🙈 They just care that it works. 😌💫 #workisjoy P.S. I love how my colleagues (like Tobias) are always up for a slightly-cringe-and-spontaneous photoshoot with me! 💛

💡 𝗪𝗵𝗮𝘁 𝗜𝘁 𝗥𝗲𝗮𝗹𝗹𝘆 𝗠𝗲𝗮𝗻𝘀 𝘁𝗼 𝗕𝗲 𝗮 𝗦𝗲𝗻𝗶𝗼𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 Being senior is much more than mastering a language or a framework. It’s about 𝗵𝗼𝘄 you think, collaborate, and deliver value. 💻 𝗜𝘁’𝘀 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗮𝗯𝗼𝘂𝘁 𝗰𝗼𝗱𝗲. A senior dev understands the impact of their work on the product, the team, and the business. They know when to refactor, when to simplify — and, most importantly, when not to touch something. 🧭 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆. You become the technical reference, the calm point when things get uncertain. It takes balance — between quality, deadlines, and empathy for your team. 🤝 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝘀𝗵𝗮𝗿𝗶𝗻𝗴 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲. A senior dev doesn’t keep what they know. They mentor, review pull requests carefully, and help others grow. 🌍 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝘃𝗶𝘀𝗶𝗼𝗻. Beyond “solving tickets,” a senior developer understands the why behind every decision. They think about architecture, scalability, and maintainability. 💬 At the end of the day, being senior is about maturity — both technical and human. What does being a senior developer mean to you? 👇 #SoftwareDevelopment #CareerGrowth #SeniorDeveloper #Leadership #Programming #SoftwareEngineering #TechLife #Developers #Mindset #CodeQuality

🚀Thinking Beyond Code: The Vibe Coding Mindset Lately, I’ve been thinking a lot about what separates good teams from great ones. It’s not just technical skill — it’s the vibe. When I say Vibe Coding, I mean that moment when everything aligns — your mind, your code, your team, your purpose. You’re not just writing functions; you’re creating flow. As an engineer, I’ve realized leadership isn’t about titles — it’s about energy. It’s how you communicate, how you help unblock a teammate, and how you keep the rhythm alive when the sprint feels long. I’m still early in my journey, but I want to grow into someone who not only codes efficiently but also helps others find their flow. Because at the end of the day, great code is written by great vibes. ✨ #VibeCoding #SoftwareEngineering #DeveloperMindset #GrowthJourney #TechCommunity #EngineeringCulture