Simplicity in Development

by Nov 16, 2022

Complexity kills the life of software projects and developers.

Complex solutions are hard to maintain. Hard to explain to your successor.

Complex code is hard to build and deploy. Hard to upgrade and to refactor.

Complex business requirements are difficult to build in software. Hard to explain and understand.

Complex Build and Release Pipeline are easy to break. Hard to fix and change by the team.

Complex project documentation is difficult to follow and use by the team. Hard to keep up to date.

Complex environments are hard to set up and to manage by the team. Hard to install and to configure.

Not keeping complexity under control, I have found that it is harder and harder to get work done and to keep quality high.

Keep It Stupid Simple

# Eliminate Friction
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more