Unit testing is overrated.

by Jun 20, 2024

Unit testing is overrated.

I don’t think that unit testing is as important as people make it out to be.

Is it something that is required for junior developers to learn?

Juniors are supposed to make errors. It’s good for them to screw up. Even be the cause of a production outage.

You learn so much from failing. It’s the best way to learn programming.

Unit testing give you protection from screwing up, that you don’t want in this phase.

Also, when you are explaining unit testing to juniors, they will not grasp the value. They didn’t screw up enough.

Unit testing also sits in the way of learning other values that are much more important.

Think about learning defensive programming and good logging.

About understanding why your code is wrong, just by reading it without using a debugger.

When you are medior, becoming a senior, that’s when unit testing is interesting to learn.

You screwed up a lot. You already learn to manually test your work before deploying.

Unit testing helps to automate that work.

What do you think? Is unit testing really the needle that made you move forward in learning coding?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more