What you can learn from an open-source project with 300 million downloads - Dennis Doomen

This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences.com
ndclondon.com/
Subscribe to our CZcams channel and learn every day:
/ @NDC
Follow our Social Media!
/ ndcconferences
/ ndc_conferences
/ ndc_conferences
#architecture #devops #programminglanguage #testing #tdd
After more than 10 years of development, our pet project, Fluent Assertions has almost reached the 300 million downloads. Providing a high quality library like that doesn't come for free. We've been trying to write code that is clean enough for our contributors, write tests that are self-explanatory, ensure breaking changes are strictly controlled and try to make it easy to use.
In this talk, I'd like to share the tools and techniques we have been using, how they've enriched our day jobs, and how they may do that for you too.
I'll talk about the release strategy, documentation, versioning, naming conventions, code structure, the build pipeline, automated testing, code coverage, API change detection, multi-targeting and more.

[@marcotroster8247]

Gosh, he printed out code and corrected it with a red pencil. I love this kind of authentic dedication to software quality 😂

[@everythingiscoolio]

I know it's a joke, but small mirror I'm going to hold in in front of you. "I try to stay away from dogmatism", not 5 minutes ago you gave the audience a sincere burn regarding merging vs rebasing. This is dogmatism. TDD is dogma. I'm honestly kind of shocked you have all these refined thoughts about clear concise communication, and then you blast 20 lines of comments above a function with no less than 3 paramaters describing a bunch of behavior. Why did you do this? Why are you defending not pushing to prod? "Strange things?" Literally the most liberating professional environment one can enjoy, I'm sure you meant to say. You're right, don't merge "directly" into production. Everyone commits and pushes on master, and you have your pipeline stop bad code. It's not that hard.