Almir Mustafic’s Post

Great coder vs. Great Software Engineer — quick thoughts A great coder is not automatically a great software engineer. As a new software engineer, the initial goal is to adapt to the professional environment and enhance coding skills in languages like .NET, Java, Python or similar. However, to transition from a great coder to a great software engineer, one must go beyond programming and be willing to learn from senior engineers, tech leads, and industry experts. This involves understanding the full software development lifecycle (SDLC), developing robust applications, and maintaining them in production. “Developing robust applications” and “maintaining them in production” is such a deep part of software engineering that deserves a lot of experience and knowledge seeking to ultimately challenge the existing performance of your applications and look for better ways. It’s also crucial to first master the fundamentals before seeking help from generative AI or coaching from others, ensuring a strong foundation for advanced learning. Patience and an open mind are essential, as real-world experience and best practices cannot be quickly learned from books or online resources. #softwareengineering #programming #coding

Individuals and interactions over processes and tools Are tools affecting the agility in “Agile” teams? The Agile manifesto emphasizes “individuals and interactions over processes and tools,” yet the tools designed to support Agile software development might influence team dynamics and agility. Companies producing these tools often innovate to satisfy stakeholders, leading to features focused on tracking and reporting, which can sometimes misalign with Agile principles. We know that we cannot improve what we don’t measure, but the focus on measuring cannot happen at the expense of the team chemistry. This prompts reflection on whether these tools help or hinder developers in their daily tasks. Historically, simple tools like Post-it notes effectively managed workflows when we were in the office gathering around a board in grooming and planning sessions; however, now we work in remote or hybrid environments and there are different challenges that can be overcome if we constantly innovate. It’s important to recognize and praise the Project Management Office (PMO) teams that successfully establish the right balance for their teams. These PMOs carefully select tools that enhance productivity without compromising the core Agile values, ensuring that teams maintain their creativity, flexibility, and enjoyment in their work. This article invites all of us to reconsider our use of current tools and whether they might be complicating processes, thus impacting the enjoyment and authenticity of Agile practices. I am happy to say my PMO partners in our organization are excellent in collaborating and always looking for better ways of doing things looking from the perspective of the teams. #projectmanagement #softwareengineering #Agility #Agile

Understanding the limitations of an architecture is crucial to preventing technical debt. Every architecture, whether monolithic or microservices, has its pros and cons.  Overlooking these disadvantages can lead to significant issues. For example, microservices offer many benefits but can become problematic without managing dependencies. It’s important to document both the advantages and disadvantages of an approach at the project’s outset and establish checks to prevent these drawbacks from evolving into technical debt. Continuous review and control of architectural limitations are essential for maintaining a healthy system and avoiding technical debt. #softwareengineering #softwarearchitecture #programming

Study to get good grades or study to learn? — quick thoughts After interviewing numerous candidates for software development jobs, it’s clear that there’s a crucial distinction between studying to get good grades and studying to learn. The value of university credentials often doesn’t directly correlate with a candidate’s skills; it depends on how they approached their studies. Whether attending a prestigious or average university, focusing on genuine learning, even at the cost of grades, is vital for long-term success. Strong fundamentals are essential, enabling individuals to adapt and apply knowledge across various fields in the software engineering industry. Ultimately, prioritize learning over credentials to truly benefit from your education. #education #learning #softwareengineering

Detecting errors promptly — quick thoughts To ensure the success of your launch, it’s crucial to detect errors promptly through effective logging mechanisms. Despite aiming for error-free logs, reality dictates that new and existing errors will occur. Monitoring on day one might not reveal immediate customer complaints, but your systems could be suffering. A robust logging framework and clear error handling guidelines are essential. Developers should focus on the top 20 error scenarios to measure new code success. Automating log scans to track these errors and detect new ones daily is recommended. This lightweight solution ultimately helps you go faster. Keep the approach simple to maximize efficiency. #softwareengineering #softwaredevelopment #coding

Software Architecture #softwareengineering

I wrote about this before and I wanted to emphasize it one more time ;) #softwareengineering #ideas #thoughts #creativity #notes #innovation

Authenticity is key to a team’s success, especially during critical times when intangible qualities like genuine problem-solving approaches make the difference and set teams apart. #softwareengineering #team #authenticity

Embracing Momentum Shifts -- The Surprising Benefits of Losing Steam #SoftwareEngineering #Skills #productivity #Improvement #Career