article thumbnail

The Relationship Between Acceptance Test-Driven Development and Design Patterns

Net Objectives

To those who’d like to study along with me as I publish this on linkedin, please ask to join the True North Consortium Linkedin Group where I … Continue reading "The Relationship Between Acceptance Test-Driven Development and Design Patterns". If you are looking for an alternative to SAFe, this is it.

article thumbnail

LLMs Demand Observability-Driven Development

Honeycomb

But if you have a log line that emits both the request_path and the error_code , and a tool that lets you break down and group by arbitrary dimensions, this would be extremely easy to answer. Neural nets are also inherently stochastic, because GPU calculations around floating point operations are inherently nondeterministic.

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

Why ATDD/BDD should be done before your planning event

Net Objectives

This is especially true if the ART doing the planning is <75 people or your entire technology group is less than 400 people & comprised mostly of independent teams with some dependencies. . learn Acceptance Test Driven Development w/ BDD's Given When Then so as to get clear requirements with well defined scope. .

article thumbnail

Why Your Agile Adoption Should Pay For Itself Within the First Program Increment

Net Objectives

This blog is written specifically written for those whose technology groups can readily be thought of as being composed of groups that are 40-75 in size, regardless of the current or anticipated level of SAFe adoption. . Second, it enables the group to pivot based on the feedback learned in the shorter increment.

Agile 40
article thumbnail

AoAD2 Practice: Collective Code Ownership

James Shore

In a remote team room, announce the topic in your group chat, and invite people to join you in a videoconference. Test-Driven Development. You can also use the unit tests as documentation and a safety net. If you’re not sure how something works, change it anyway and see what the tests say. Whole Team.

article thumbnail

AoAD2 Practice: Zero Friction

James Shore

Test-Driven Development. Inside the script, use a compiler or linter to tell you when you make syntax errors, and tests to tell you when you make semantic errors. Although good tests run at a rate of hundreds or thousands per second, you’ll eventually have too many tests to run them all in less than a second.

article thumbnail

AoAD2 Practice: Reflective Design

James Shore

Test-Driven Development. I wanted my new login endpoint to have sociable tests. See “Write Sociable Tests” on p.XX.) Rather than abandon that core idea, I amplified it by making the infrastructure wrappers nullable, which later allowed me to use test-driven development to make a new, cleaner Auth0 login endpoint.