What you can learn from an open-source project with 250 million downloads

•Download as PPTX, PDF•

0 likes•115 views

Dennis Doomen presented on FluentAssertions, an open source .NET library for validation of results and state. With over 244 million downloads, it is successful due to its clean code design using test-driven development, extensibility, clear documentation, and support. Doomen discussed tools, practices, and principles from the project, including editorconfig, Roslyn analyzers, approval tests, GitHub Actions, and semantic versioning that can be applied to other projects.

Technology

Tools, practices & principles you can apply in your day job
What you can learn from an OSS project with 250
million downloads
Dennis Doomen
@ddoomen | Principal Consultant | The Continuous Improver | Aviva Solutions

About Me
Hands-on architect in the .NET space with 26 years of experience on
an everlasting quest for knowledge to build the right software the right
way at the right time
@ddoomen | The Continuous Improver

Win a 1-year license for
Jetbrains Rider
twitter: ddoomen
mastodon: @ddoomen.mastodon.social
bluesky: @ddoomen.bsky.social

About the project
Dennis Doomen | @ddoomen | The Continuous Improver

Is it successful?
Tons of Pluralsight/YouTube videos
#35 at nuget.org 600 depending packages
493 GH forks
3200 stars
Used in 75K
Github repositories
244 million downloads.
Used in various
Microsoft .NET projects

Why is that?
It’s a library,
not a framework
Has Clean Code
Designed using TDD
Used in test code
Works with all
(testing) frameworks
Improves
readability
Clear release
strategy
Designed for
extensibility
Documentation
Great support
Clear failure
messages
Catchy name.

Creating issues & having a discussion on it
#avivasolutions

Issue Templates
https://github.com/fluentassertions/fluentassertions/tree/develop/.github/ISSUE_TEMPLATE

Design Challenges
1. Core library vs extension
2. Breaking changes
3. Consistency like Should().AllSatisfy()
4. Behavior like records, tuples
5. Async postfix.
https://fluentassertions.com/extensibility/

Exploring the repository
Dennis Doomen | @ddoomen | The Continuous Improver

Contribution Guidelines
https://github.com/fluentassertions/fluentassertions/blob/develop/CONTRIBUTING.md

Technical patterns & guidelines
Dennis Doomen | @ddoomen | The Continuous Improver

.editorconfig to allow auto-
formatting
(for VS, VS Code and Rider)

Roslyn Analyzers
• XML comment formatting
• LINQ performance improvements
• Nested conditional statements
• Long methods
• Single type per file
• Correct exception types
• Proper async supports.

Getting the most out of
newer C# and .NET versions

Using PolySharp to enable newer C#
features on older frameworks

Main Package
Application
Shared Package
Contract
Contract
Stable Package
Auxiliary Package
Optional
Dependency
Dependency
Package
Principles of successful package management

Building and testing locally
#avivasolutions

Approval tests to catch
unexpected API
changes

Reviewing and merging pull requests
Dennis Doomen | @ddoomen | The Continuous Improver

Releasing
Dennis Doomen | @ddoomen | The Continuous Improver

Semantic Versioning,
GitVersion and GitFlow

• Consistent naming and grouping
• Extracting nice features (e.g. DataSets)
• Capturing design guidelines
• Extracting fluent date/time extensions
• Structural Mutation Testing
• Dependency management with ArchUnit
• Piloting Jetbrains Qodana
• Trying Docusarus.io

Q&A
Also find me at
twitter: ddoomen
mastodon: @ddoomen.mastodon.social
bluesky: @ddoomen.bsky.social
email: dennis.doomen@avivasolutions.nl
slack: fluentassertions.slack.com

Work effectively with other special education professionals who are testing students for learning disabilities. Learn to improve your referrals, improve the interactions on your campus, and reduce the amount of testing time that results in no qualification. This presentation is a collaborative conversation between a speech pathologist and a educational diagnostician (LSSP Licensed Specialist in School Psychology in Texas). We discuss the similarities and differences between Receptive Language Delay and Difficulties with Listening Comprehension and between Expressive Language Delay and Difficulties with Oral Expression. We then explore reasons why we may obtain (apparently) conflicting testing results. Data from a research study sheds light on the commonalities among referrals that were most appropriate.

(책 소개) 실전 카프카 개발부터 운영까지

Jay Park

50 idiomatic expressions you can use in your essays.

mahanifareed

Punctuation

TIKA MONTES

My prezi taking notes

Seemeen Khan Yousufzai

One word substitute by jayson ilarde

Lord Mark Jayson Ilarde

We all love to build greenfield projects, but the reality is that in most jobs you have to deal with a lot of legacy code. This doesn't mean the code is bad. It just means that choices were made that were the right ones at that time, or that the developers were not entire up-to-date with modern development practices. And that's exactly what this talk is about. I enjoy taking such a codebase and gradually introduce architectural seems, add a proper build pipeline, introduce temporary tests and then gradually refactor the codebase to combine more maintainable, testable and reliable. So in this talk, I'd like to unfold my extensive toolbox of practices, principles, tools and mindset to help you improve your legacy code without jeopardizing your business. Understand production environment See which vinaries are running in production and what config files are used Verify the code and the production release are in sync, e.g. DotPeek Analyze logs to understand what features are used Try to get it to run on a local environment Understand code Generate project diagrams and class hierarchies Find origin calls and destination of a parameter using Rider Use navigation options to find inheritors, usages, etc. Use the namespaces and project names to understand the relation Have Rider's AI Assistant or ChatGPT explain the code Track all documentation in a single place Build C4 diagrams Find dead code Reduce the scope of types and members to internal to find more dead code Detect code inefficiencies and dead code using Rider Remove commented out code Build a safety net If therea are tests, add code coverage reporting using Coverlet and use that to find dark spots (HTTP API) Characteristics tests using FluentAssertions, Bogus, xUnit. Use AI to generate them. It's fine, you'll delete them later on Use test containers for .net t lo include the databse Build a couple of end to end UI tests e.g. using Cypress, Playwright, efc Improve deployability Add scripts or builds steps to run the code locally, Nuke build pipeline to get consistency Adopt a version strategy and name branches accordingly Adopt automatic versioning using GitVersion Adopt logging and exception strategy, e.g. Serilog Pulumi to automate PR deployments Improve code Treat all warnings as errors and fix thhem Editorconfig / eslint so auto-format works Configure a personal Rider/R# clean-up profile to auto-format file, project and solution Roslyn analyzers Microsoft.CodeAnalysis.BannedApiAnalyzers StyleCop.Analyzers CSharpGuidelinesAnalyzer Roslynator.Analyzers Meziantou.Analyzer Enable nullable types per file Move new code to .NET 6+ or cross-compile Switch to newer C# versions, possibly using Polysharp File-scope namespaces Target-typed news switch expression String interpolation instead of string.format Use Directory.Build.Props to reduce duplication Improve naming whenever you can Encapsulate prim itive types and collections in d

DSpace 7 - Creating High-Quality Software: Update to Development Practices

4Science

Presentation given at OR2019 in Hamburg DSpace 7 has offered the opportunity to enforce and improve practices introduced in previous years in the DSpace development process [1] moving forward to a Test-Driven Development (TDD) process. The presentation will provide an overview of the current practices and processes used from DSpace 7 on with regard to the test, development and documentation of the software: concrete examples about how to report a bug, solve a bug, propose and develop a new feature will be presented. The use of the git branch and github PRs [2] will be shown to illustrate how automatic testing helps to quickly validate changes, discover impact on unexpected points in the software and collaboratively improve the proposed solution. This will demonstrate the value of new requirements about code styling [3], code documentation, raising the test coverage and recommendation to provide automatic test to uncover found bugs. The introduction of community development sprints [4] provides community developers the opportunity to learn the new development processes in a hands-on fashion, with the help of fellow developers and coaches. The introduction of new DSpace docker images [5] (for each published branch) helps to simplify the development process by allowing developers to more easily test, validate and manage code changes against multiple versions of DSpace.. Finally, the REST contract [6] and the use of wireframes [7] will be presented as best practices to support early sharing of ideas and development proposals, and to drive uniformity in the implementation both on the REST and on the Angular side.

Design patterns for Event Sourcing in .NET

Dennis Doomen

Event Sourcing is becoming more mainstream these days, and a lot of conferences have demonstrated the pros and cons of this architecture style from multiple angles. I've done a few of these and publishes a lot of articles on best practices and solutions to common problems. But what nobody did was to show you how to build an event sourced systems in the .NET ecosystem. There are a lot of open-source projects that you can use, so you'll need to find a right mix and your own code to that. So let me show you how I would implement this in .NET with almost 10 years of Event Sourcing experience behind my belt.

The Power of Azure DevOps

Jeff Bramwell

The Power of Azure DevOps

Jeff Bramwell

"Different software evolutions from Start till Release in PHP product" Oleksa...

Fwdays

Ця розповідь розкриє підходи для вирішення багатьох проблем в PHP проєктах через: None-Breaking change development підхід, cross-stack контракти, Trunk Based development, еволюція з Polyrepo до Monorepo з компонентами на різних технологіях, Boilerplat’и компонентів, різні Architecture View, Continuous Testing & Quality, Infrastructure View, Infrastructure as a code як основний інструмент.

PHPFrameworkDay 2020 - Different software evolutions from Start till Release ...

Alexandr Savchenko

https://fwdays.com/en/event/php-fwdays-2020 All of us think about many questions when we start a project, when we already have a product and when we release it. Here are some of them: which architecture and infrastructure to choose? what should be the repository structure? how to make the right evolution from one application to 100 microservices with success product release? how to distribute cross-stack commands as a whole? what development practices to use? This story will expose approaches to solving these and many other problems in PHP projects through: None-Breaking change development approach, Cross-stack contacts, Trunk Based development, evolution from Polyrepo to Monorepo with components on different technologies, Boilerplates for components, different Architecture Views, Continuous Testing & Quality, Infrastructure View, Infrastructure as a code as the main tool. This topic will appeal to everyone - from Software Developer to Architect, as many Tips & Tricks will be revealed.

Large scale agile development practicesSkills Matter

Agile engineering environment 50 minutes or less

Vernon Stinebaker

Agile Engineering Environment – 2017

India Scrum Enthusiasts Community

In October 2009, I presented a well-received session entitled An Agile Engineering Environment (in 59 Minutes or Less) at an Agile conference in Chengdu, China. From 2009 – 2015 the environment presented in that session remained fundamentally unchanged as our primary internal development environment. By 2015, however, we began seeing the emergence of new tools which build upon the basic premises of that environment, but enable an even more robust environment to be established even more quickly and independently than the 59-minute environment realized in the 2009 session. In this session, we will briefly introduce the original configuration and see how modern tooling and techniques enable the improved environment to be established in a fraction of the time, enabling even greater agility in our engineering environment.

Agile Engineering Environment – 2017

India Scrum Enthusiasts Community

The Professional Programmer

Dave Cross

Behavior Driven Development—A Guide to Agile Practices by Josh Eastman

QA or the Highway

Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anyt...

Janusz Nowak

Azure dev ops

Swaminathan Vetri

The Power of Azure DevOps

Jeff Bramwell

Deploy multi-environment application with Azure DevOps

Andrea Tosato

Test-Driven Development in the Corporate Workplace

Ahmed Owian

What is TDD, and why is it giving traditional software development practices a run for their money? This presentation answers these questions, while focusing on a popular agile methodology, Extreme Programming (XP). It places a particular emphasis on the exploratory programming nature of XP and its testing practice, TDD. The paper also summarizes prior research on TDD and includes the results from a research survey conducted to compare TDD with traditional testing practices.

Test Driven Development - Overview and Adoption

Pyxis Technologies

TDD CrashCourse Part2: TDD

David Rodenas

Getting a grip on your code dependencies (2023-10)

Dennis Doomen

I'm sure every developer wants to be able to change code with confidence and without fear. Readable and self-explanatory code is one aspect of that. Too much coupling is another major source of problems that prevent you from changing one part of the system without causing side-effects. In this talk, I'd like you to show you common sources of unnecessary coupling and offer you options to help prevent and/or break those. I'll talk about how principles like Don't Repeat Yourself and Dependency Injection can be a double-edge sword, how to detect too unnecessary dependencies and how to use the Dependency Inversion Principle to unravel some of those. And yes, I will also talk about controlling dependencies on the package level. Challenge 1. How to prevent too much coupling? 2. We are tought to decrease coupling and increase cohesion 3. How do you increase cohesion? By applying DRY! 4. But DRY creates more coupling 5. And too much decoupling results in a forest of abstractions 6. The solution is… find a balance (or "it depends") On the architecture level 1. Use architecture style that embraces DIP (e.g. Onion, Hexagon, Clean Architecture) 2. Organize your code along functional boundaries -> this will make it easier to break off that boundary for rebuilding/strangler/microservices. 3. Apply DRY within those boundaries only, but allow shared services for complicated capabilities 4. Align your test scope with those internal boundaries… On the package level • Classes and interfaces that are almost always used together should be packaged together. Those that don’t meet that criteria don’t have a place in that package • Packages should not require changes (and thus a new release) for unrelated changes. • There must be no cycles in the dependency structure • A package should only depend upon packages that are more stable than it is or abstract packages On the code level • Avoid technical folders and organize them by functionalities or capabilities • Things in adjacent folders usually mean they are separate boundaries • Use the Tell, Don't Ask principle • Use the Law of Demeter to detect unnecessary coupling • Encapsulate primitive types and collections in specific types • Dependency injection is great, but try to avoid a global container • It's fine to inject concrete classes inside boundaries Strategy for legacy code 1. Ensure you have a safety net using characterisation tests 2. Find existing seams and decouple them better a. Identify modules or functional slices b. Identify groups of classes that are supposed to be used together and are designed to be reusable c. Identify interfaces or abstractions in DI registration code and see if they are truly designed for reusability d. Assume that code in adjacent folders is supposed to be independent e. Move code from different technical folders that belong together in their own (functionally named) folderPublic 3. Use that to define (and visualize) the target architecture

Getting a grip on your code dependencies

Dennis Doomen

Similar to What you can learn from an open-source project with 250 million downloads

Tools and practices to help you deal with legacy code

Dennis Doomen

DSpace 7 - Creating High-Quality Software: Update to Development Practices

4Science

Design patterns for Event Sourcing in .NET

Dennis Doomen

The Power of Azure DevOps

Jeff Bramwell

The Power of Azure DevOps

Jeff Bramwell

"Different software evolutions from Start till Release in PHP product" Oleksa...

Fwdays

PHPFrameworkDay 2020 - Different software evolutions from Start till Release ...

Alexandr Savchenko

Large scale agile development practicesSkills Matter

Agile engineering environment 50 minutes or less

Vernon Stinebaker

Agile Engineering Environment – 2017

India Scrum Enthusiasts Community

Agile Engineering Environment – 2017

India Scrum Enthusiasts Community

The Professional Programmer

Dave Cross

Behavior Driven Development—A Guide to Agile Practices by Josh Eastman

QA or the Highway

Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anyt...

Janusz Nowak

Azure dev ops

Swaminathan Vetri

The Power of Azure DevOps

Jeff Bramwell

Deploy multi-environment application with Azure DevOps

Andrea Tosato

Test-Driven Development in the Corporate Workplace

Ahmed Owian

Test Driven Development - Overview and Adoption

Pyxis Technologies

TDD CrashCourse Part2: TDD

David Rodenas

Similar to What you can learn from an open-source project with 250 million downloads (20)

Tools and practices to help you deal with legacy code

DSpace 7 - Creating High-Quality Software: Update to Development Practices

Design patterns for Event Sourcing in .NET

The Power of Azure DevOps

"Different software evolutions from Start till Release in PHP product" Oleksa...

PHPFrameworkDay 2020 - Different software evolutions from Start till Release ...

Large scale agile development practices

Agile engineering environment 50 minutes or less

Agile Engineering Environment – 2017

The Professional Programmer

Behavior Driven Development—A Guide to Agile Practices by Josh Eastman

Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anyt...

Azure dev ops

The Power of Azure DevOps

Deploy multi-environment application with Azure DevOps

Test-Driven Development in the Corporate Workplace

Test Driven Development - Overview and Adoption

TDD CrashCourse Part2: TDD

More from Dennis Doomen

Getting a grip on your code dependencies (2023-10)

Dennis Doomen

Getting a grip on your code dependencies

Dennis Doomen

My Laws of Test Driven Development (2023)

Dennis Doomen

About 15 years ago, I got inspired by a series of posts on Test Driven Development written by the Jeremy D. Miller. Now, with many years of great and not-so-great experiences practicing Test Driven Development, I thought it is the time to capture my own “laws”. The term "law" is obviously an exaggeration and "principles or heuristics" cover my intend much better. Either way, I want to talk about the scope of testing, using the observable behavior, naming conventions, state-based vs interaction-based testing, the impact of DRY, patterns to build useful test objects and some of the libraries and tools I use. In short, everything I try to follow every day I write, review or maintain code.

Automate Infrastructure with Pulumi and C#

Dennis Doomen

Who remembers the days were you had to manually setup a physical server somewhere in a 19 inch rack? Nowadays those physical racks have been replaced by virtual machines provided by Google, Microsoft and Amazon. But some people are still provisioning them manually. The more mature organizations will script most of the provisioning using the native CLI or HTTP API provided by the specific cloud platform, but quite often those are maintained separately from the code of the system that is being deployed. Terraform by Hashicorp is another attempt to support infrastructure-as-code by using a declarative syntex to define the desired infrastructure. But then again, Yaml isn't really suited for anything but simple single-file configuration settings. Yaml isn't code and doesn't provide real Intellisense, line-by-line debugging and most importantly, refactoring. But what if you could use C# and .NET to provision your infrastructure and treat that code as first-class citizens of your codebase, including all the capabilities that you would expect? Well, let me show you how Pulumi for .NET will allow you to evolve your infrastructure code with the rest of the code base without turning it in a big spaghetti of Yaml files.

What is the right unit in unit testing (UpdateConf 2022)

Dennis Doomen

Whether you're just writing your first unit test or have been practicing Test Driven Development for many years, I'm sure your biggest challenge is to find the right scope for testing. Unfortunately a lot of books and guidance seem to imply that every class or type should be tested separately. Well, I can tell you from 15 years of unit testing experience that that's the best way to shoot yourself in the foot. In this session, I'm going to show you some concrete examples and why I chose a certain boundary for the "unit" in unit testing. I will also share design heuristics I use myself to find those boundaries and why those are not guidelines. I'll also illustrate how principals like DRY and SOLID can be both a blessing and a curse that may lead to the wrong design choices

Slow Event Sourcing (re)projections - Just make them faster!

Dennis Doomen

I don't have to tell anybody how awesome Event Sourcing is as an architecture style. But those that have been using it in production must have experienced the pains of keeping the upgrades fast enough, especially if you use a more traditional relational database like SQL Server. I've once heard somebody say: "If it's slow, make it faster", but rebuilding a big projection is simply a very expensive operations and involves a lot of network traffic between the application and the database servers. Over the years since we adopted Event Sourcing, we've been experimenting a lot and have implemented various improvements to make those reprojections faster. And we haven't stopped. We're already working on some new ideas lately. So in this session, I'd like to share those techiques, their pros and cons and how we implemented them on a more detailed level.

50 things software teams should not do.pptx

Dennis Doomen

Enough books have been written, articles have been published and Youtube videos have been posted about how you should be behaving as a software developer, Scrum Master or team lead. To be original in this unoriginal world, I started thinking about the things you should NOT be doing. I came up with 50 tools, practices and principles covering topics like dealing with complexity, productivity, architecture, testability, traceability, maintainability, transparency and predictability that I believe hamper you as a professional. That sounds like a lot, but I promise you a fun and entertaining session that I'm sure will trigger a lot of recognition.

What is the right "unit" in unit testing and why it is not a class?

Dennis Doomen

A lab around the principles and practices for writing maintainable code

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I'd like to share my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

How to Practice TDD Without Shooting Yourself in the Foot

Dennis Doomen

It’s 2021, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, Dennis regularly talks to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session Dennis likes to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

Decomposing the Monolith using modern-day .NET and a touch of microservices

Dennis Doomen

If I have to name a single biggest hype in software architecture land then it would be "microservice". They are supposed to be small and focused, can be deployed independently, can work with any technology and will solve all your monolithical problems. But we all know that silver bullets don't exist, plus technology should never be a goal, but merely a means to an end. Nonetheless, following the path towards real microservices is a great strategy for decomposing a monolith without the deployment complexity of the first. So how do you do that? What technologies does the .NET realm offer for us? In this talk, I'll show you some of the pros and cons of micro-services and its ingredients to leverage modern-day .NET and Event Sourcing to move your monolith into a bright new future.

Event Sourcing from the Trenches (DDD Europe 2020)

Dennis Doomen

Over the years I've spoken many times about what Event Sourcing is and shared many of the good, the bad and the ugly parts of it in blog posts and various talks. However, I've never talked about how to actually build a system based on this architecture style. I keep getting the same questions over and over again. Like when to apply Event Sourcing and at what architectural level. How to deal with transactional boundaries within and outside the domain. How to build projections that are autonomous, reliable and self-supporting. How to deal with upgrades and blue-green deployments. But also on how to handle bugs, design mistakes and crashing projections. Having made a lot of these mistakes myself over these years, it's time to share my current thoughts and opinions about this. Since the .NET space has a pretty rich set of open-source projections to support this, the examples and code will be .NET. But the concepts are universal, so don't let that scare you off.

Practical introduction to DDD, CQRS and Event Sourcing

Dennis Doomen

After several in-depth talks about Event Sourcing, I realized that there's a large group of developers that may have heard about Domain-Driven Design, Command-Query Responsibility Segregation and Event Sourcing, but have not really connected the dots yet. So in this talk, I'd like to take a practical example of a simple domain and gradually introduce functional requirements to see how the principles behind DDD affect the way your entities are going to protect the business rules. After that, I'll introduce some real-world non-functional requirements and see if and how Event Sourcing and/or CQRS may or may not help to accomplish those.

How to practice TDD without shooting yourself in the foot

Dennis Doomen

It’s 2019, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks. And even if you believe you are well versed in the testing realm, join me anyway. Maybe we can learn some tips & tricks from the audience as well. Looking forward to it!

Decomposing the Monolith (Riga Dev Days 2019)

Dennis Doomen

A micro-service architecture is a great strategy for decomposing a monolith. In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future. If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Micro-services are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, micro-services are technology agnostic, but hey, we’re in the .NET space, aren’t we? And they are not a goal, but a means to an end. In fact, a micro-service architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a micro-service? What technologies does the .NET realm offer for us? And what if you don’t want to deploy them independently? In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future.

A lab around the principles and practices for writing maintainable code (2019)

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I like to share you my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

Lessons learned from two decades of professional software development

Dennis Doomen

I recently was asked what I would do differently if I had the experience I have now. This got me thinking about the mistakes I've made, the traps I fell for and the dogmatism I became part of over the last 22 years of professional software developer in the Microsoft realm. In this talk, I'll be going down memory lane with you and share everything I've learned on architecture, tools, technologies, agile software development, maintainable code, automated testing, documentation and anything else that I think you should know. Prepare yourself for an event of stories, both good and bad.

The Good, The Bad and The Ugly of Event Sourcing

Dennis Doomen

In 2009, I first learned about Event Sourcing and Command Query Responsibility Seggregation (CQRS) at a training Greg Young gave in Utrecht, The Netherlands. I remember being awed by the scalability and architectural simplicity those styles provided. However, I also remembered the technical complexity that comes with it. In 2012, I was in charge of transitioning a CQRS-based system to Event Sourcing. I knew it would be non-trivial, but boy was I in for a surprise. So, over the last four years, I've experienced first-hand how a large group of developers had to deal with the transition. It's a brilliant solution for high-performance or complex business systems, but you need to be aware that this also introduces challenges most people don't tell you about. In this talk, I'd like to share you some of the most powerful benefits of ES, but also show you the flipside of the coin and cover some of the smaller and bigger challenges you'll run into it. Again, I love it and would apply it again without any doubt, but I really want you to understand the trade-offs before you jump on the Event Sourcing train.

Event Sourcing from the Trenches (with examples from .NET)

Dennis Doomen

How To Practice TDD Without Shooting Yourself In The Foot

Dennis Doomen

It's 2018, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven't really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

More from Dennis Doomen (20)

Getting a grip on your code dependencies (2023-10)

Getting a grip on your code dependencies

My Laws of Test Driven Development (2023)

Automate Infrastructure with Pulumi and C#

What is the right unit in unit testing (UpdateConf 2022)

Slow Event Sourcing (re)projections - Just make them faster!

50 things software teams should not do.pptx

What is the right "unit" in unit testing and why it is not a class?

A lab around the principles and practices for writing maintainable code

How to Practice TDD Without Shooting Yourself in the Foot

Decomposing the Monolith using modern-day .NET and a touch of microservices

Event Sourcing from the Trenches (DDD Europe 2020)

Practical introduction to DDD, CQRS and Event Sourcing

How to practice TDD without shooting yourself in the foot

Decomposing the Monolith (Riga Dev Days 2019)

A lab around the principles and practices for writing maintainable code (2019)

Lessons learned from two decades of professional software development

The Good, The Bad and The Ugly of Event Sourcing

Event Sourcing from the Trenches (with examples from .NET)

How To Practice TDD Without Shooting Yourself In The Foot

Recently uploaded

Monitoring Java Application Security with JDK Tools and JFR Events

Ana-Maria Mihalceanu

Video Streaming: Then, Now, and in the Future

Alpen-Adria-Universität

In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.

LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...

DanBrown980551

Do you want to learn how to model and simulate an electrical network from scratch in under an hour? Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)! During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook. PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides: - A fully editable and extendable library for grid component modelling; - Visualization tools to display your network; - Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses; The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well. What you will learn during the webinar: - For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills; - For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.

Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...

James Anderson

Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management. The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM). Speakers: Bob Boule Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle. Gopinath Rebala Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.

Free Complete Python - A step towards Data Science

RinaMondal9

UiPath Test Automation using UiPath Test Suite series, part 5

DianaGray10

Essentials of Automations: The Art of Triggers and Actions in FME

Safe Software

In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation. We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios. Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!

A tale of scale & speed: How the US Navy is enabling software delivery from l...

sonjaschweigert1

Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved: - Reduction in onboarding time from 5 weeks to 1 day - Improved developer experience and productivity through actionable findings and reduction of false positives - Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO) Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production. We will cover: - How to remove silos in DevSecOps - How to build efficient development pipeline roles and component templates - How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence) - How to streamline operations with automated policy checks on container images

GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024

Neo4j

Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx

nkrafacyberclub

Epistemic Interaction - tuning interfaces to provide information for AI support

Alan Dix

Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024 https://alandix.com/academic/papers/synergy2024-epistemic/ As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.

Mind map of terminologies used in context of Generative AI

Kumud Singh

Securing your Kubernetes cluster_ a step-by-step guide to success !

KatiaHIMEUR1

Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster. However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks. In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.

20240607 QFM018 Elixir Reading List May 2024

Matthew Sinclair

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

Albert Hoitingh

GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024

Neo4j

Microsoft - Power Platform_G.Aspiotis.pdf

Uni Systems S.M.S.A.

Climate Impact of Software Testing at Nordic Testing Days

Kari Kakkonen

My slides at Nordic Testing Days 6.6.2024 Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.

zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs

Alex Pruden

This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second). Paper: https://eprint.iacr.org/2023/1886

20240605 QFM017 Machine Intelligence Reading List May 2024

Matthew Sinclair

Recently uploaded (20)

Monitoring Java Application Security with JDK Tools and JFR Events

Video Streaming: Then, Now, and in the Future

LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...

Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...

Free Complete Python - A step towards Data Science

UiPath Test Automation using UiPath Test Suite series, part 5

Essentials of Automations: The Art of Triggers and Actions in FME

A tale of scale & speed: How the US Navy is enabling software delivery from l...

GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024

Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx

Epistemic Interaction - tuning interfaces to provide information for AI support

Mind map of terminologies used in context of Generative AI

Securing your Kubernetes cluster_ a step-by-step guide to success !

20240607 QFM018 Elixir Reading List May 2024

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024

Microsoft - Power Platform_G.Aspiotis.pdf

Climate Impact of Software Testing at Nordic Testing Days

zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs

20240605 QFM017 Machine Intelligence Reading List May 2024

What you can learn from an open-source project with 250 million downloads

1. Tools, practices & principles you can apply in your day job What you can learn from an OSS project with 250 million downloads Dennis Doomen @ddoomen | Principal Consultant | The Continuous Improver | Aviva Solutions

2. About Me Hands-on architect in the .NET space with 26 years of experience on an everlasting quest for knowledge to build the right software the right way at the right time @ddoomen | The Continuous Improver

4. Win a 1-year license for Jetbrains Rider twitter: ddoomen mastodon: @ddoomen.mastodon.social bluesky: @ddoomen.bsky.social

5. About the project Dennis Doomen | @ddoomen | The Continuous Improver

6. What is it?

7. Is it successful? Tons of Pluralsight/YouTube videos #35 at nuget.org 600 depending packages 493 GH forks 3200 stars Used in 75K Github repositories 244 million downloads. Used in various Microsoft .NET projects

8. Why is that? It’s a library, not a framework Has Clean Code Designed using TDD Used in test code Works with all (testing) frameworks Improves readability Clear release strategy Designed for extensibility Documentation Great support Clear failure messages Catchy name.

9. Creating issues & having a discussion on it #avivasolutions

10. Organization

11. Issue Templates https://github.com/fluentassertions/fluentassertions/tree/develop/.github/ISSUE_TEMPLATE

12. Explicit API approval

13. Design Challenges 1. Core library vs extension 2. Breaking changes 3. Consistency like Should().AllSatisfy() 4. Behavior like records, tuples 5. Async postfix. https://fluentassertions.com/extensibility/

14. Exploring the repository Dennis Doomen | @ddoomen | The Continuous Improver

15. Proper read-me

16. Contribution Guidelines https://github.com/fluentassertions/fluentassertions/blob/develop/CONTRIBUTING.md

17. Release notes & documentation

18. Git CLI tools I work with

19. CLI and GUI: The best of both worlds

20. Technical patterns & guidelines Dennis Doomen | @ddoomen | The Continuous Improver

21. .editorconfig to allow auto- formatting (for VS, VS Code and Rider)

22. Roslyn Analyzers • XML comment formatting • LINQ performance improvements • Nested conditional statements • Long methods • Single type per file • Correct exception types • Proper async supports.

23. Naming & grouping of tests

24. Documenting exceptions

25. Directory.build.props

26. Faking time

27. BDD-style testing

28. Feeding data to tests

29. Getting the most out of newer C# and .NET versions

30. Using PolySharp to enable newer C# features on older frameworks

31. Main Package Application Shared Package Contract Contract Stable Package Auxiliary Package Optional Dependency Dependency Package Principles of successful package management

32. Refactor towards Design Patterns

33. Building and testing locally #avivasolutions

34. C# build script using Nuke

35. Approval tests to catch unexpected API changes

36. Benchmarking

37. Documentation

38. Automatic spell checking of our docs

39. Reviewing and merging pull requests Dennis Doomen | @ddoomen | The Continuous Improver

40. Saying NO

41. Clean source control history

42. GitHub Actions

43. Code coverage using coveralls.io

44. Four eyes review

45. Auto-merging

46. Releasing Dennis Doomen | @ddoomen | The Continuous Improver

47. Semantic Versioning, GitVersion and GitFlow

48. Releasing

49. NuGet reserved prefixes

50. Things still to do #avivasolutions

51. • Consistent naming and grouping • Extracting nice features (e.g. DataSets) • Capturing design guidelines • Extracting fluent date/time extensions • Structural Mutation Testing • Dependency management with ArchUnit • Piloting Jetbrains Qodana • Trying Docusarus.io

52. Q&A Also find me at twitter: ddoomen mastodon: @ddoomen.mastodon.social bluesky: @ddoomen.bsky.social email: dennis.doomen@avivasolutions.nl slack: fluentassertions.slack.com

What you can learn from an open-source project with 250 million downloads

Recommended

Recommended

More Related Content

Similar to What you can learn from an open-source project with 250 million downloads

Similar to What you can learn from an open-source project with 250 million downloads (20)

More from Dennis Doomen

More from Dennis Doomen (20)

Recently uploaded

Recently uploaded (20)

What you can learn from an open-source project with 250 million downloads