Akum Blaise Acha’s Post

You're a great software engineer if you: 1. Focus on the problems and not the tech 2. Help others around you move faster 3. You're the go-to person for some of your team's scope 4. Are a strong communicator both in speaking and writing 5. You're influence others to go in the most impactful direction 6. Proactively identify and address issues slowing engineers down 7. Focus on implementation quality and writing code that is easier to maintain 8. Know how to drive your projects across teams/functions What else makes a great engineer? #devopsengineer #backenddeveloper #teamwork #collaboration

Software Engineer vs Coder: What's the Difference? Many confuse these roles, but they're quite different. Here's what you need to know: Coder: - Focuses mainly on writing code - May struggle with big-picture thinking - Often works on isolated tasks or features - Might not consider long-term maintainability - Less likely to suggest architectural improvements Software Engineer: - Designs entire systems, not just individual parts - Thinks about scalability and performance - Collaborates effectively with other teams - Considers security and best practices - Plans for future growth and changes When building a product, a software engineer can be invaluable. They don't just write code – they create solutions that stand the test of time. #softwareengineer #sharing #code

Writing “Senior Software Engineer” is a poorly defined term. Many tend to equate "seniority" with the length of their career or the number of certificates, which is inaccurate. After collaborating with hundreds of engineers over 20-plus years, I've observed that true seniority extends beyond coding. 👇🏻 - - - - - - - - - - - - - - - - - - - - - - - - - - → I’m the founder of kommit → We provide accountable software engineering for small and medium-sized businesses. → I write about engineering practices, business ops, and management.

You are a senior software engineer if you take on the most boring and annoying tasks of your team. Senior software engineering is a mindset — it shows that you understand the importance of getting things done, no matter how mundane the tasks might be. It shows that you understand that business priorities come before your personal preferences. Being a leader means dealing with both the good and bad aspects of the job. #softwareengineering

How soul-crushing are your code review comments? If you're a more senior software engineer, you have an amazing opportunity to help build a safe place for juniors. When it comes to having code reviewed, many junior software engineers are nervous about getting grilled by the more senior members of the team. It's especially difficult because they haven't had as much practice about being objective and not taking things personally. As a senior software engineer, how do you support the junior members of the team on their reviews? 👇Link to the full video in the comments. Comment below if it's not showing and I'll provide it!👇 ---- 📨 Sign up for my email newsletter 🗣️ Share with your network #SoftwareEngineering #SoftwareEngineer #CareerAdvice #Feedback

Avoid this problem solving trap before it consumes you! If you're a more senior software engineer, you've likely found different times in your career where you're feeling swarmed by more junior software engineers that need help. And... there's nothing wrong with that. It's perfectly normal, and you're doing a great job by wanting to help them! And because you're also super busy, you start giving them the answers they need to they can go off to fix their own problems on their own. But they come back. And they come back with more questions. IT'S GETTING WORSE! Avoid the trap of giving away answers and help teach more junior engineers how they can problem solve. It's more work up front, but it'll be helpful for EVERYONE. 👇Check the full video!👇 https://lnkd.in/gAD9m-5f ---- 🎬 Check out Dev Leader on YouTube for multiple full-length videos weekly! 🗣️ Share with your network! #softwareengineer #softwareengineers #softwareengineering #problemsolving

With a few people you can go fast. With a lot of people you can go far. Everything fits on a spectrum in that. More people will help things go deeper and farther, but it will be slower. Less people will help things go faster, but you won't be able to get as far or as deep. More software engineers to make the project go faster doesn't really mean it will go faster. it's more people touching code, more ideas to sift through, more different opinions to wade through. that takes time. Less software engineers (but good ones) could get things going really fast, but it's not good for going far ( building giant projects) there's so much to do. However, they could pivot and make changes and get the mvp out rather quickly. There's give and take in each scenario, but please understand, hiring more devs for a project WILL NOT make it faster automatically.

Over the course of my time as a #StaffEngineer, I’ve had responsibilities that fall into all of the following categories at one time or another: - Bugs on prod that need to be dug into - Product-wide refactors - Technical feasibility questions - Building/editing pipelines - Implementing brand new patterns or frameworks into a project - Helping maintain a project’s full test suite - Helping other devs with really off-the-wall issues - Random, adhoc mentorship - Fixing process issues or tweaking the process to get around things you can’t fix - Oh and let’s not forget about that one time a client reached out and was like “Oh hey, all of our certs expire Sunday evening can you, like, fix this?” (I probably don’t need to tell you this, but this obviously occurred on a Friday at 2:30 because when else would it have happened.) The point? The responsibilities that land on a Staff Engineer are less a list of responsibilities and more a general comfort and skill-level with the #SDLC process and with #SoftwareEngineering as a whole. #leadership #code #developer Pictured below: A Staff Software Engineer I *guess??*

Understanding software engineering means seeing beyond just coding. The best software engineers know all parts of the Software Development Life Cycle: 1. Needs assessment 2. Strategy development 3. System design 4. Implementation 5. Quality assurance 6. Rollouts 7. User feedback This broad view is why people from different careers bring unique value to engineering teams. There’s a big overlap between music and engineering, and other fields likely share similar ties. There’s room for everyone in this field. Pursue your passion and make it yours. ♻️ Repost if you found this valuable #SoftwareDevelopment • #CareerGrowth • #EngineeringLife

The biggest mistake I made as a Software Engineer? 🤦♂️ 🙈 Not doing enough code reviews. Don’t shy away from code reviews thinking it’s extra work for you. Instead do reviews: - For code written by junior engineers - you level up your team by becoming a mentor. - For code written by experienced engineers - you level up your coding and testing knowledge. - For design docs authored by senior members - you level up your system design, architecture, and domain knowledge. Keep reviewing more and more code and designs. Learn and share! You'll grow 10x faster. Promise. 🚀 #careers #engineers #motivation (Image: Showing my mistake - that I was running in a maze full of huddles)