The Decomposition Pattern

Hiring isn’t easy. I’m not saying it isn’t. But I do think that we can improve the overall process in order to both get more relevant applications and to lower the chance of bad time investments. For both parties involved!

Note: I know the episode name is wrong in the video. I didn't noticed until having finished recording, and since my editing skills are below zero, it goes like this! Sorry.

One of the oldest questions in software engineering is how can we deliver the best quality software in a limited amount of time, and I share my experience in software development on how to best use that given time to achieve that.

Being an effective and productive software engineer is an abstract concept, as it depends on your context and expectations upon your work. But let me share what I do to try and achieve it the best I can.

Exception handling has long been a go-to method for managing errors, even though they can lead to unexpected program flow and reduced code clarity. In this episode let’s talk about another way to handle errors.

Do you know what’s a Staff+ Engineer? This was a question posed by my friend, Daniel. So, let’s talk a little about the common definition of a Staff+ Engineer, their archetypes, and what’s like to operate at this level of seniority.

Many engineers ask what are their career development options. Maybe they reached a point that now they need to decide what to aim next. In this episode, let’s talk about the options in front of us, their general expectations, and some personal advice to career development.

I got a question from a friend of mine, Nelson: “Should we avoid using abstract classes?”. In this episode let’s talk about what are abstract classes, what’s their purpose and if, in fact, we should avoid them!

I don’t think AI is going to replace software engineers, and I actually think AI is doing a disservice, overall. In this episode let’s dive in into the promises of AI, its usage as code and study assistances, and my personal valid application for AI!

Daily meetings, retros, and alike ceremonies are part of Agile software development. In this episode I share my thoughts about why I mainly think that all that is a wast of time in most common implementations of these ceremonies, and also share how I think they can be more effective!

I don’t think companies and teams give proper importance to documentation. The irony is that there are many OSS projects with amazing documentation, and many proprietary projects - with decent amount of funding - that have very subpar documentation. As with tests, documentation should not be a secondary thing: it should be implicit in any project.