72: Code Review with Pranay Suresh
How many pairs of eyes are needed to ensure the quality of a newly written code? When do you send your code to an impartial reviewer? Is a review always necessary?
How many pairs of eyes are needed to ensure the quality of a newly written code? When do you send your code to an impartial reviewer? Is a review always necessary?
Switching from a monolithic architecture to microservices has become an accelerating trend these days.
Coding with empathy is one of the Corgibytes' core principles, underlying everything we talk about on this show.
When repaying debt, it helps to know how big it is. The same holds for technical debt. The problem is: how do you measure it?
The code is predictable. Binary. It either works, or it doesn't. Working with people is much messier. Their actions and reactions are not easy to predict. Or are they?
To paraphrase Lewellyn Falco, when one person is programming, it is that person's best ideas that are being encoded into the software; when two people are programming together, you get the best ideas…
The easiest way to make your team members feel happy is to give them a sense of personal growth.
It’s never about what you don't know. It’s the difference you can bring to the table that matters. Today we talk with A. J.
In a modern fast-moving business environment, we are obsessed with quantitative measurements. But without qualitative data, we might get the wrong impression and incentivize bad behavior.
Most of the time, we focus on a specific aspect of software development and maintenance and try to see how these small pieces fit in the big picture of working with legacy code. Not today, however.