The 10 habits of highly effective programmers

•

4 likes•2,273 views

A short introduction to various Agile and Lean practices such as Test Driven Development, Technical Debt, Pair Programming, and more.

The 10 Habits of Highly Effective Developers Dennis Doomen | Principal Consultant | Aviva Solutions

Dennis Doomen About Me ,[object Object]

C++ originsbut C# since 2001

Specialities

.NET Architecture

Silverlight

Scrum/XP

ALM

Occasional Speaker

Public initiatives

SilverlightCookbook

C# CodingGuidelines

FluentAssertions

Internet

www.dennisdoomen.net

DZone MVB

@ddoomen,[object Object]

Ubiquitous Language 1 concept = 1 name Verbs & nouns Refactor! Native language No ambiguity Business proposes Beware of conflictingrules

RequirementsChallenges Scoping Estimability Traceability Purpose Whichstakeholders? Documentationis ambiguous PromoteCommunication

User Stories Product Backlog Storyotypes Placeholder Project value Estimable Negotiable Who, what, why Global unit of work

MaintabilityChallenges Lot of coupling Inconsistent naming Bad cohesion Incorrect usageof .NET Intention obscuringcode Inconsistent layout Procedural Code Bad maintainability

Coding Standards Definesubset Ghostdoc ReSharper or CodeRush Static Code Analysis Distribute cheat sheet Go towww.csharpcodingguidelines.com

QualityChallenges Architecturalinconsistencies Design skills Communication skills Bad hair days Misinterpretations 10-50 bugs / 1000 lines

More Related Content

Similar to The 10 habits of highly effective programmers

Up to speed in domain driven design

Up to speed in domain driven design

Up to speed in domain driven design

Rick van der Arend

Double diamond-nodes

Double diamond-nodes

Double diamond-nodes

shahinaparveenm

Join Us and Enhance DeFi Development and step into the Emerging Financial Revolution Join hands with Optymize, the premier DeFi Development Company and utilize the open-source Decentralized Finance(DeFi) Protocol to develop ultra transparent, trustworthy, highly secure, unique and reliable financial apps for your company. Hire Top 5% Remote DeFi Developers: https://optymize.io/hire-defi-developers/

Hire Top 5% of Remote DeFi Developers | Optymize

Hire Top 5% of Remote DeFi Developers | Optymize

Hire Top 5% of Remote DeFi Developers | Optymize

OptymizeHireRemoteEn

GDSC NIET ORIENTATION ).pdf

GDSC NIET ORIENTATION ).pdf

GDSC NIET ORIENTATION ).pdf

YashiGupta410690

Nathan Caldwell Resume

Nathan Caldwell Resume

Nathan Caldwell Resume

Nathan Caldwell

Turing is a data-science-driven deep jobs platform helping companies spin up their engineering teams in the cloud at the push of a button. Based in Palo Alto, California, it is a fully remote company of 500+ people who help connect world-class remote software engineers with world-class companies. Turing makes the remote hiring journey easy and rewarding for both companies and developers. With Turing, companies can hire pre-vetted, Silicon Valley-caliber remote software talent across 100+ skills in 3-5 days. Also, Turing democratizes opportunities for remote developers from around the world by offering them high-quality software jobs with top US firms. Turing's Intelligent Talent Cloud uses AI to source, vet, match, and manage over a million developers worldwide. This, in turn, helps organizations save valuable time and resources as they build their dream engineering team in a matter of days. For more info, head over to: http://turing.com/s/yB8zZu

How to become a remote web developer

How to become a remote web developer

How to become a remote web developer

.NET Architecture for Enterprises

.NET Architecture for Enterprises

.NET Architecture for Enterprises

Code & Cannoli - Domain Driven Design

Code & Cannoli - Domain Driven Design

Code & Cannoli - Domain Driven Design

DDD In Agile

Event Storming #10 DDDGreece

Event Storming #10 DDDGreece

Event Storming #10 DDDGreece

Antonios Klimis

Distributed Agile

Distributed Agile

Distributed Agile

Tony O’Dowd presented at the Cloud On-Boarding Clinic in the Business School, Dublin City University, Ireland. The clinic, which was hosted by the Irish Centre for Cloud Computing and Commerce (IC4) aims to help companies leverage the benefits of using cloud computing in their businesses. Tony's presentation, ‘Cloud Computing It’s a world of complexity!’ draws upon Tony’s experience successfully launching a cloud based company, and addresses four of the greatest challenges facing companies wishing to implement a cloud infrastructure across their businesses. For more information about KantanMT contact; info@kantanmt.com.

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Agile Methodologies And Extreme Programming - Svetlin Nakov

Agile Methodologies And Extreme Programming - Svetlin Nakov

Agile Methodologies And Extreme Programming - Svetlin Nakov

dinubaby.pdf

FideliaCampbell_April2016_LinkedINResume2 Skills

FideliaCampbell_April2016_LinkedINResume2 Skills

FideliaCampbell_April2016_LinkedINResume2 Skills

Fidelia Campbell

JD_Java_Developer

JD_Java_Developer

JD_Java_Developer

Suthirtha Bhattacharjee

Le futur de .NET

Le futur de .NET

Le futur de .NET

Mdestypicalgoodbad

Mdestypicalgoodbad

Mdestypicalgoodbad

Lviv IT Arena is a conference specially designed for programmers, designers, developers, top managers, inverstors, entrepreneur and startuppers. Annually it takes place on 2-4 of October in Lviv at the Arena Lviv stadium. In 2015 conference gathered more than 1400 participants and over 100 speakers from companies like Facebook. FitBit, Mail.ru, HP, Epson and IBM. More details about conference at itarene.lviv.ua.

Domain-Driven Design (Artur Trosin Product Stream)

Domain-Driven Design (Artur Trosin Product Stream)

Domain-Driven Design (Artur Trosin Product Stream)

cisco_cv

Similar to The 10 habits of highly effective programmers (20)

Up to speed in domain driven design

Up to speed in domain driven design

Up to speed in domain driven design

Double diamond-nodes

Double diamond-nodes

Double diamond-nodes

Hire Top 5% of Remote DeFi Developers | Optymize

Hire Top 5% of Remote DeFi Developers | Optymize

Hire Top 5% of Remote DeFi Developers | Optymize

GDSC NIET ORIENTATION ).pdf

GDSC NIET ORIENTATION ).pdf

GDSC NIET ORIENTATION ).pdf

Nathan Caldwell Resume

Nathan Caldwell Resume

Nathan Caldwell Resume

How to become a remote web developer

How to become a remote web developer

How to become a remote web developer

.NET Architecture for Enterprises

.NET Architecture for Enterprises

.NET Architecture for Enterprises

Code & Cannoli - Domain Driven Design

Code & Cannoli - Domain Driven Design

Code & Cannoli - Domain Driven Design

DDD In Agile

Event Storming #10 DDDGreece

Event Storming #10 DDDGreece

Event Storming #10 DDDGreece

Distributed Agile

Distributed Agile

Distributed Agile

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Cloud Computing: IC4 Cloud On-Boarding Clinic, DCU

Agile Methodologies And Extreme Programming - Svetlin Nakov

Agile Methodologies And Extreme Programming - Svetlin Nakov

Agile Methodologies And Extreme Programming - Svetlin Nakov

dinubaby.pdf

FideliaCampbell_April2016_LinkedINResume2 Skills

FideliaCampbell_April2016_LinkedINResume2 Skills

FideliaCampbell_April2016_LinkedINResume2 Skills

JD_Java_Developer

JD_Java_Developer

JD_Java_Developer

Le futur de .NET

Le futur de .NET

Le futur de .NET

Mdestypicalgoodbad

Mdestypicalgoodbad

Mdestypicalgoodbad

Domain-Driven Design (Artur Trosin Product Stream)

Domain-Driven Design (Artur Trosin Product Stream)

Domain-Driven Design (Artur Trosin Product Stream)

cisco_cv

More from 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 (2023-10)

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

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

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

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

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. 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. 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.

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

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

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

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.

Getting a grip on your code dependencies

Getting a grip on your code dependencies

Getting a grip on your code dependencies

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.

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

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.

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

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.

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

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

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

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

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

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.

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

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

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

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.

50 things software teams should not do.pptx

50 things software teams should not do.pptx

50 things software teams should not do.pptx

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.

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

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

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

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.

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

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.

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

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.

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

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

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

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.

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

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.

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

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!

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

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.

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

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.

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

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

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

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.

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

More from Dennis Doomen (20)

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

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

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

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

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

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

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

Getting a grip on your code dependencies

Getting a grip on your code dependencies

Getting a grip on your code dependencies

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

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

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

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

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

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

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

50 things software teams should not do.pptx

50 things software teams should not do.pptx

50 things software teams should not do.pptx

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

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

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

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

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

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

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

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

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

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

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

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Recently uploaded

GenAI Risks & Security Meetup 01052024.pdf

GenAI Risks & Security Meetup 01052024.pdf

GenAI Risks & Security Meetup 01052024.pdf

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Artificial Intelligence Chap.5 : Uncertainty

Artificial Intelligence Chap.5 : Uncertainty

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

ICT role in 21st century education and its challenges

ICT role in 21st century education and its challenges

ICT role in 21st century education and its challenges

rafiqahmad00786416

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

Why Teams call analytics are critical to your entire business

Why Teams call analytics are critical to your entire business

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

A Year of the Servo Reboot: Where Are We Now?

A Year of the Servo Reboot: Where Are We Now?

MINDCTI Revenue Release Quarter One 2024

MINDCTI Revenue Release Quarter One 2024

MINDCTI Revenue Release Quarter One 2024

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

Strategies for Landing an Oracle DBA Job as a Fresher

Strategies for Landing an Oracle DBA Job as a Fresher

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Manulife - Insurer Transformation Award 2024

Manulife - Insurer Transformation Award 2024

Manulife - Insurer Transformation Award 2024

The Digital Insurer

Axa Assurance Maroc - Insurer Innovation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

Whatsapp Number Escorts Call girls 8617370543 Available 24x7 Navi Mumbai Call Girls Service Offer Genuine VIP Model Escorts Call Girls in Your Budget. Navi Mumbai Call Girls Service Provide Real Call Girls Number. Make Your Sexual Pleasure Memorable with Our Navi Mumbai Call Girls at Affordable Price. Top VIP Escorts Call Girls, High Profile Independent Escorts Call Girls, Housewife Women Escorts Call Girl, College Girls Escorts Call Girls, Russian Escorts Call girls Service in Your Budget.

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

Powerful Google developer tools for immediate impact! (2023-24 C)

Powerful Google developer tools for immediate impact! (2023-24 C)

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

Apidays New York 2024 - The value of a flexible API Management solution for O...

Apidays New York 2024 - The value of a flexible API Management solution for O...

Recently uploaded (20)

GenAI Risks & Security Meetup 01052024.pdf

GenAI Risks & Security Meetup 01052024.pdf

GenAI Risks & Security Meetup 01052024.pdf

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Artificial Intelligence Chap.5 : Uncertainty

Artificial Intelligence Chap.5 : Uncertainty

Artificial Intelligence Chap.5 : Uncertainty

ICT role in 21st century education and its challenges

ICT role in 21st century education and its challenges

ICT role in 21st century education and its challenges

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Why Teams call analytics are critical to your entire business

Why Teams call analytics are critical to your entire business

Why Teams call analytics are critical to your entire business

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

A Year of the Servo Reboot: Where Are We Now?

A Year of the Servo Reboot: Where Are We Now?

A Year of the Servo Reboot: Where Are We Now?

MINDCTI Revenue Release Quarter One 2024

MINDCTI Revenue Release Quarter One 2024

MINDCTI Revenue Release Quarter One 2024

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

Strategies for Landing an Oracle DBA Job as a Fresher

Strategies for Landing an Oracle DBA Job as a Fresher

Strategies for Landing an Oracle DBA Job as a Fresher

Manulife - Insurer Transformation Award 2024

Manulife - Insurer Transformation Award 2024

Manulife - Insurer Transformation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Powerful Google developer tools for immediate impact! (2023-24 C)

Powerful Google developer tools for immediate impact! (2023-24 C)

Powerful Google developer tools for immediate impact! (2023-24 C)

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Apidays New York 2024 - The value of a flexible API Management solution for O...

Apidays New York 2024 - The value of a flexible API Management solution for O...

Apidays New York 2024 - The value of a flexible API Management solution for O...

The 10 habits of highly effective programmers

1. The 10 Habits of Highly Effective Developers Dennis Doomen | Principal Consultant | Aviva Solutions

2.

3. C++ originsbut C# since 2001

4. Specialities

5. .NET Architecture

9. Occasional Speaker

10. Public initiatives

11. SilverlightCookbook

12. C# CodingGuidelines

13. FluentAssertions

15. www.dennisdoomen.net

17.

18. Ubiquitous Language 1 concept = 1 name Verbs & nouns Refactor! Native language No ambiguity Business proposes Beware of conflictingrules

19. RequirementsChallenges Scoping Estimability Traceability Purpose Whichstakeholders? Documentationis ambiguous PromoteCommunication

20. User Stories Product Backlog Storyotypes Placeholder Project value Estimable Negotiable Who, what, why Global unit of work

21. MaintabilityChallenges Lot of coupling Inconsistent naming Bad cohesion Incorrect usageof .NET Intention obscuringcode Inconsistent layout Procedural Code Bad maintainability

22. Coding Standards Definesubset Ghostdoc ReSharper or CodeRush Static Code Analysis Distribute cheat sheet Go towww.csharpcodingguidelines.com

23. QualityChallenges Architecturalinconsistencies Design skills Communication skills Bad hair days Misinterpretations 10-50 bugs / 1000 lines

24. Peer Reviews Always! Ad-Hoc TFS vNext! ByPeers Chooseyour tool FormalProcess Record Comments

25. Team Challenges Compliancy Too manythings toremember Common mistakes Juniors UI choices Annoyingreviews Design choices

26. Checklists Short Concise Open Unambiguous Design choices Sign-off Online or offline CodingGuidelines Project-specific

27. Productivity Challenges Fixing the wrong problem Bugs Design flaws Building the wrong thing Late feedback Alternateinterpretations Lack of experience

28. Pair Programming Switchpairs Complexproblems Straightdesks Same level only Coaching Not the entireday Dual keyboard + mouse

29. ConsistencyChallenges KISS Requirements change YAGNI Oracles don’texist LDUF Utopianarchitectures don’texist Ubiquitous Language changes

30. Refactoring Single responsibility Small changes S.O.L.I.D Decrease coupling Continuous Increasecohesion Boyscout rule NOT Redesign ReSharper / CodeRush

31. Design Challenges Debugging hell Untestable Refactoring Too many responsibilities Regressions Insufficient design skills No cohesion Strong coupling

32. Test Driven Development Test-First Read, read, read > 90% Usefor peer reviews Design Process First-Class Citizens Includesrefactoring Avoid UI logic

33. Technical Debt Repetition causes repetition Repeatingfixes Qualityundefinable Suboptimal check-Ins Simple changes become complex Software rot

34. Wall of Pain Open PlanRedesigns Visible SmallSteps Wall of pain Regular Review Meetings PrioritizeByPain ConsiderCosts & Risks

35. Even More Challenges PainfulDeployment Code Analysis Unit Testing Testing on Real Server Code Coverage Redeployment

36. Automatic Builds Conflict Detection Code Analysis Unit Testing AutomaticDeployment ContinuousIntegration Team Responsibility

37. ? Emaildennis.doomen@avivasolutions.nl Twitter @ddoomen Blogwww.dennisdoomen.net