Running my first event practicing BDD with what I hope will be a room full of nice people keen improve communication. Learn more and sign up if you are in Cologne:
When the software developer community comes up with a way of collaborating with the business to ensure solutions solve business problems, both business and developers have a tendency to downplay it as "a developer thing" , and once business involvement is removed from the equation, it gets reduced to a bureaucratic burden on developers until they drop it, too.
#TDD#BDD#DDD#Scrum: These are tools for alignment between business and development. They require business involvement.
Wer mehr teilt, wirft weniger weg!
Deswegen erweitern wir unsere Bibliothek der Dinge (#BDD) mit Mitteln aus dem Haushalt. Darunter ein Akku-Schrauber, eine Heckenschere oder eine Kofferwaage. Diese Dinge und noch mehr sind ab Morgen verfügbar.
While there are still vocal proponents of #TDD, #BDD, #ExtremeProgramming & variations, it struck me today that people getting into software development now probably don’t realize how hyped those concepts were a decade-ish ago. These days they feel more like a personal preference for some than an organizational, or even team, decision.
I’d attribute some of that to the shift towards statically types languages, but also that the developer role today feels more individualistic in general.
At the #SocialHub developer community that evolves the #Fediverse and the #ActivityStreams / #ActivityPub open standards we are thinking of using #Gherkin and #BDD test suites to formally define the expected behaviour of the protocol and AP vocabulary extensions that various apps use.
Among others this will be part of Fediverse Enhancement Proposals or #FEP's. See: