Skip to content
Hallway
0:00 / 0:00

#functionalcoreimperativeshell#tdd#boundaries

Boundaries

Next Day Video

68K subscribers • 19 videos on Hallway

YouTube
  • Recommended by 3 people: 2 in engineering communities and 1 curated list.
  • Presented by Gary Bernhardt

Intermediate. Assumes working knowledge.

21K views11 years ago3 recommendations

Software designTools and practiceDesign patternsSoftware architectureTesting

Gary Bernhardt explores the boundaries between pieces of code, explaining the functional core and imperative shell pattern for better testing and design.

Gary Bernhardt An exploration of the boundaries between pieces of code, including: isolated testing, behavior vs. data, mutation vs. immutability, how data shape affords parallelism, transforming interface dependencies into data dependencies, and wha

Why it's here

3 people recommend this

What people say. Recommended as an excellent explanation of the functional core, imperative shell pattern and how it improves TDD.

u/peanutbutterwnutellain r/programming • Recommends

On “The Grand Unified Theory of Software Architecture”

link to this video link to this video these talks by Gary explain the Imperative Shell, Functional Core and how can it be useful for TDD, it’s pretty good
37View on Reddit

programming-talkscurated list on GitHubRecommends

Under “Software Development”

Boundaries 00:30:19 by **Gary Bernhardt** (2015)
View the list

u/LicensedProfessionalin r/programming • Recommends

On “Tests should be coupled to the behavior of code and decoupled from the structure of code”

If you wrote unit tests for each module/class, you wouldn't need to make a million API calls to verify the correctness of your system. Correctness at the unit level means that you can have only a few integration tests, because all of the corner cases are covered in the unit tests. Check out 6:17 link to this video
1View on Reddit