RT @thimok_dev: What it really means to 'own' a feature. Most juniors think it's just about writing code. But owning a feature? That's dif….

- Learn to communicate technical concepts clearly. If you're a junior dev right now and you're NOT doing this:. Why are you holding yourself back?. The path to medior is clear. You just need to take that first step.

They wait for instructions instead of taking initiative. They avoid difficult conversations. Want to grow to medior?. - Start owning features end-to-end. - Take responsibility for outcomes, not just output. - Build relationships with stakeholders.

- Planning the implementation.- Documenting everything.- Supporting after release.- Handling deployment.- Testing thoroughly. I've seen countless juniors struggle with this transition. They focus on coding, ignore the rest.

What it really means to 'own' a feature. Most juniors think it's just about writing code. But owning a feature? That's different. You're responsible for:.- Understanding business requirements.- Managing stakeholder expectations.- Writing clean, maintainable code

What's a question you want to ask? Share your thoughts in the comments! 👇.

Did you know I'm on other platforms too?. Follow me on LinkedIn: Follow me on BlueSky: Follow me on X/Twitter:

Follow me ✨ for more tips and insights on how to grow from Junior to Medior Software Engineer, Object Oriented Programming Principes, general software engineering tips, humor and so much more!.

.NET devs: What's a .NET tool or NuGet package you can't live without? #Software #Engineer #SoftwareEngineering #Code #Dotnet #NuGet.

What advice would you give your younger self that wants to grow as a software engineer? Share your thoughts in the comments! 👇.

Did you know I'm on other platforms too?. Follow me on LinkedIn: Follow me on BlueSky: Follow me on X/Twitter:

Follow me ✨ for more tips and insights on how to grow from Junior to Medior Software Engineer, Object Oriented Programming Principes, general software engineering tips, humor and so much more!.

RT @thimok_dev: How to give feedback as a junior without overstepping. Giving feedback is challenging when you're just starting your career….

Your team will value your input more than you think.

The best junior developers don't wait for permission to contribute. They build trust by giving thoughtful, well-structured feedback. Don't let the senior's ego be in the way of your growth. Save this guide. Use it in your next code review.

- Remember there's often more than one right way to solve problems. 5. Know when to step back.- Recognize when a topic is beyond your current experience. - It's okay to say "I might be missing something here.".- Learning when not to give feedback is as important as giving it.

- It shows you've done your homework before speaking up (this is great). 4. Present alternatives, not demands.- Phrase feedback as suggestions rather than corrections. - Share your reasoning and be open to discussion.

- Discuss patterns and practices objectively. - Avoid making it personal or questioning someone's abilities. 3. Back your feedback with documentation.- Reference official docs, style guides, or team conventions. - This adds credibility to your suggestions.

- Ask for clarification before suggesting changes. - This shows respect and helps you understand the full context. - Your curiosity will be appreciated more than immediate criticism. 2. Focus on the code, not the coder.- Keep comments specific to the implementation.

Because they don't feel experienced enough to go against their experienced team members. Don't let uncertainty stop you from contributing. Here's a 5-step guide to giving effective and great feedback as a junior developer:. 1. Start with questions, not statements.