article thumbnail

8 questions to answer before your startup faces technical due diligence

TechCrunch

Will your organization and your code pass technical due diligence when it’s your turn? Let’s start with the positives: If an investor is proceeding with technical due diligence (TDD), you’ll likely pass. Here’s the not-so-good news: Companies can pass the business test, but fail TDD.

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?

Insiders

Sign Up for our Newsletter

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

article thumbnail

A prep checklist for startups about to undergo technical due diligence

TechCrunch

8 questions to answer before your startup faces technical due diligence. Previously, the author offered a detailed overview of the technical due diligence (TDD) process investors conduct before injecting cash into early stage startups. Code quality. Which software languages do you use?

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

Bliki: TestDrivenDevelopment

Martin Fowler

Test-Driven Development (TDD) is a technique for building software that guides software development by writing tests. In essence we follow three simple steps repeatedly: Write a test for the next bit of functionality you want to add. Write the functional code until the test passes.

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.