Skip to content

Tag: software engineering

Operational Skills Needed

Over the years, I’ve interviewed many candidates. One crucial skill that often gets overlooked is operational reflexes during oncalls. Surprisingly, few companies test for this, yet it’s a capability that greatly distinguishes engineers. There is a gap in interviewing. Some of the candidates excel in code interviews and system design but not on the operational side of things. Sometimes, they effectively play the system without real operational…

Leave a Comment

Handling Competitive Dynamics

A healthy level of competition can fuel innovation, drive individuals to excel, and push teams to achieve remarkable results. However, when competition crosses the line and becomes overly aggressive, it can hinder the growth and productivity of the team as a whole. I don’t think competition is inherently negative. It becomes problematic when it starts overshadowing the team. Over the years, I observed when team members are…

1 Comment

Becoming a Rockstar Engineer

In the software development realm, people often debate about 10x engineers or rockstars. What does it really mean though? It’s not just outputting the best code, is it? It’s about a bunch of really important qualities that set some developers apart from the rest. With the right mix of feedback, guidance, and personal determination, an engineer can ascend to rockstar status. The challenging part lies in introspection…

1 Comment

Estimation Accuracy

Estimating software project timelines and budgets is a bit like joining in on the centuries-long debate about Irish weather – it’s famously unpredictable, and everyone has their say! Picture this: a fleeting 15 minutes of sunshine followed by an unexpected downpour. What’s our strategy? We put on our trusty raincoats because, let’s be honest, umbrellas are no match for that Irish wind!  In the world of software…

Leave a Comment

Beyond Numbers: Quality in Software Engineering

In the realm of software engineering, it’s a common pursuit to chase quality through tangible metrics like code coverage. Much like a barista striving for the perfect blend, the quest for impeccable code drives us. However, is quality merely about hitting certain numerical targets? Does achieving 100% code coverage ensure our software is free from bugs? The emphasis on numbers might lead us astray from the essence…

Leave a Comment