Salvatore Argentieri’s Post

Some high-level tips which can really help you in getting to the next level in your software engineering career: 1. Focus on relationship building beyond transactional interactions like PR review, RFC review. Interact with engineers across the board and learn the challenges they are facing. Peer feedback matters a lot! 2. Create crisp PRs with 1-2 changes. This leads to faster reviews, faster shipping and faster landing the impact. 3. Find ways of improving the system or infrastructure while working on features. There will definitely be a lot of instances where you would find if something can be simplified, or a better solution can exist. 4. Be a force multiplier by solving problems for your team and thinking about how to help the wider team. As an example, have you found out an issue with a certain code pattern? Create a product wide lint rule to alert the devs about this issue. What do you think some of the more important things are? #SoftwareEngineering #CareerTips #RelationshipBuilding #Collaboration #CareerGrowth

Something that not only apply to Software Engineers but to anyone.

A conversation with Bryan Mikaelian in Slack has me thinking about recent experiences hiring and managing engineers in a cloud-native world full of specialists and outsourced technologies. Do other engineering leaders struggle to hire product engineers with multi-disciplinary experience, systems debugging skills, etc?

Being a software engineer is TOUGH. I totally understand. Sometimes you just want things to be easy—get paid without having to constantly learn, evolve, or face new challenges. If that’s the path you want to take, here’s the formula: - Write code that’s complex and difficult to maintain. - Keep your knowledge to yourself. - Avoid helping others when they ask about your work. - Become the only one who understands the system. - Repeat this cycle. People might not like you, but you’ll likely keep your job, simply because no one else can manage the mess you’ve created. Or, you know… you could just quit and become a bin man? You’re still working with mess but people might actually like you. 👍

Great insights and advice to all software engineers..

No one told me that software engineering is mostly WORKING WITH PEOPLE 😆 Three years ago, when I started the process of a career change into software engineering, I had so little idea about the real job. Well, even on my first day on the job I actually thought that the majority of my work would be sitting and coding. Before that, I had spent over 6 years in retail consultative sales and I was ready for a bit less communication with other human beings, to be honest :D Imagine my surprise when I spent about 3 hours in meetings on my first day (it was planning and retrospective I guess so really just a bit of bad luck :D) The fact is that our work is a LOT about communication. In software engineering, clear and effective communication is as crucial as your technical level. And that’s the reason why this week the topic is all about communication and some common mistakes you might be making - and sometimes these can be really costly. Literary. Whether you're discussing project requirements with a client, collaborating with your team, or presenting your work to stakeholders, falling into these communication traps can hurt your efforts and even impact your career trajectory. Continue reading here: https://lnkd.in/eKCXhb-4 #softwareengineering #communication #softskillsmatter Follow me for more 🔔. Repost if your network would love it ♻️. ----- I am Pavel ✔ A software developer, daddy of two, and storyteller. ✔ I talk about my dev journey, leadership, self-development, and everything in between. 📩 I write a Soft-Skilled Engineer newsletter - link on my profile.

Fumbled this one... ❌ My first experience of a live technical test did not go well and the fault was really on me but I've come away not letting it deter me from the goal of becoming a software engineer. I've learnt a lot from the experience which I'll be taking with me to the next one because MORE IS ON THE WAY! 🙌 I've written a blog about my experience and the takeaways from it, have a read if you like! (Link is in the comments below) 👇 Top Tip: - ABC in sales, it's Always Be Closing but in code it's Always Be Chatting! Talk out loud to better understand your thinking and approach to a coding problem, even if you're alone!

As a software engineer, I am guided by five basic principles: ➡ First, make it work, then make it right ➡ Prioritize simplicity and clarity over complexity ➡ Base architectural decisions on current needs rather than wishful thinking ➡ Foster a culture of collaboration where everyone has their voice, no matter their experience ➡ Be the kind of person you would want to work with These principles are my roadmap. What are yours? 🙂

Question I'm getting from founders: Are technical personas on LI? Some of the top LI personal and company accounts are catered towards technical personas like CTO's, developers, and product managers. I share 3 examples in this video. Like other professionals, they come to LI to become better at their job, learn best practices, and connect with others in similar fields. If you're looking to market to them, the best approach is working closely with a subject matter expert on your team to create content that resonates. Ex. If you have a product where software engineers are part of the buying process, then work closely with your CTO or staff engineers to build demos and speak to challenges they might be facing in their careers