yeah, it's something that you intuitively grasp as a developer

domain driven design is a similar design philosophy that concerns itself with isolating things in units and avoiding mixing domains together.

BDD is about focusing on the process flow of the code so things logically follow and are intuitive to the users (or programmers building with them).

they are complementary, really.

both are also derivative of the parent TDD, test driven design, which is about focusing on unit testing and integration testing as a way of deciding how to sequence the development process