Remove .Net Remove Software Review Remove Systems Review Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. We produce high-quality code in small, verifiable steps. At best, mistakes lead to code that won’t compile. No wonder, then, that software is buggy. TDD isn’t perfect, of course. Why TDD Works.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

Fast, Reliable Tests. Our tests don’t get in our way. Test-Driven Development. Teams who embrace test-driven development accumulate thousands of tests. The more tests you have, the more important speed and reliability become. Rely on Narrow Unit Tests. Details here.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

5 Tips for Successfully Implementing Behavior-Driven Development in Your Team

Gorilla Logic

Experiences like these make many developers think about using Behavior-Driven Development (BDD). BDD emphasizes collaboration between developers, testers, and stakeholders to define and deliver software that meets business requirements. For each team member, ask: Are they familiar with BDD or TDD?

article thumbnail

LLMs Demand Observability-Driven Development

Honeycomb

Our industry is in the early days of an explosion in software using LLMs, as well as (separately, but relatedly) a revolution in how engineers write and run code, thanks to generative AI. In theory , all software is debuggable. There is a much longer list of things that make software less than 100% debuggable in practice.

article thumbnail

Ask Miss O11y: My Manager Won’t Let Me Spend Any Time Instrumenting My Code

Honeycomb

You’ll be relieved to hear that you’re in the majority, and also that there are quick (and easy) steps you can do to prove that instrumenting your code is worthwhile. Is the system working? First, let’s talk about what makes a system “work.” If we don’t know that our system is running, then it’s not done.

article thumbnail

AoAD2 Practice: Collective Code Ownership

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Collective Code Ownership. Developers. We are all responsible for all our code. But how does that apply to code? Collective code ownership means the team shares responsibility for their code. It’s your code. Mob Programming.

article thumbnail

AoAD2 Practice: Incremental Design

James Shore

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. It’s Not Just Coding. Computers don’t care what your code looks like. If the code compiles and runs, the computer is happy.