article thumbnail

TDD or Test-Last? One Thing at a Time

Xebia

Disentangling Programming Concerns At first glance, all the activities I mentioned seem inseparable, like a big blob of spaghetti code. What do we want to achieve with the code we’re creating? In most cases, we need the ability to evolve the code. We introduce design to our software. How should it behave?

article thumbnail

Technical Review: A Trusted Look Under the Hood

TechEmpower CTO

Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our software team? We hear them explain that their current software development is expensive, deliveries are rarely on time, and random bugs appear. What does a business leader do in this situation?

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

TDD saved the day

Xebia

Sometimes, the coding task in front of you can be overwhelmingly complex. To tackle each operation, I started with a small test, following the principles of Test-Driven Development (TDD). If the tests became too complex, I knew something was missing. This description takes the form of a test.

article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Why do people apply TDD? Here’s a secret: it’s not for the tests. Learn about the actual goal and values hidden under the surface of Test-Driven Development. What Are the Real Reasons for Doing TDD? Test-Driven Development (TDD) is a controversial topic amongst developers. Feedback on what?

article thumbnail

When TDD Is Not a Good Fit

Henrik Warne

I like to use Test-Driven Development (TDD) when coding. However, in some circumstances, TDD is more of a hinderance than a help. Writing tests only makes sense after the solution is viable. Last week, I came across examples of where I developed new functionality without using TDD. Avoiding Premature Tests.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

It all has to be very reactive; you keep fiddling with the code until it gets traction. Under those conditions, it doesn’t make sense to cross all the t’s and dot the i’s as the life expectancy of the code is weeks or months. We see the same kinda thing with unit testing. So you build, pivot, build, pivot, etc.

article thumbnail

8 Best Practices for Writing Clean and Maintainable Code

The Crazy Programmer

In the fast-paced world of software development, writing clean and maintainable code is not just a good practice; it’s a crucial factor in determining the success of a project. Code Organization Modularization: Breaking down your code into small, manageable modules is akin to organizing a cluttered room.