article thumbnail

TechCrunch+ roundup: Technical due diligence, web3’s promise, how to hire well

TechCrunch

Then again, I’m not a developer, so I didn’t truly appreciate the value of mobile gaming, GPS and cloud storage until they’d achieved product-market fit and were integrated into my smartphone. 8 questions to answer before your startup faces technical due diligence. ” 3 ways to hire well for your startup.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

Clearly, the best way to test any software is with fully automated ‘system’ testing that is thorough enough that it can be used for full regression testing. In its fullest form, it is at least as much code as the thing it is going to test, and you have to build a custom version of it, every time, for every system. But it got worse.

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 Provides Value to Everyone in the Development Process

Net Objectives

Project Managers and Product Owners are sometimes dubious about the development team doing TDD. They are concerned that the team will slow down because they’ve been burdened with additional work, and that developers might “game” the system with bogus tests to satisfy the process.

article thumbnail

Value vs valueable - another aha-moment

Marcusoft

But it’s also faster to achieve the true goal, with smaller batches than with big batches, as any lean simulation/game will show you. For example; An audit log statement for every action in the system - is too big and will not deliver any value in a long time. For example this: Numbers simulation - less is more!

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

Non-functional attributes emerge from the system as a whole, so even a codebase with 100% coverage can have problems. Here's the thing about TDD. The definition of TDD is that you don't write code without a failing test, and you do so in a tight loop that covers one branch at a time.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

With TDD, you run the tests as often as one or two times every minute. If they don’t, you won’t be able to get feedback within 1-5 seconds, and that’s crucial for the TDD loop to work effectively. Fast, reliable tests are a game changer. Because external systems can change or fail at any time, the real answer is “monitoring.” (See

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

Non-functional attributes emerge from the system as a whole, so even a codebase with 100% coverage can have problems. Here's the thing about TDD. The definition of TDD is that you don't write code without a failing test, and you do so in a tight loop that covers one branch at a time.