The Daily Friction

A daily newsletter about automation and eliminating friction.

Standup meetings

Standup meetings Why have a Teams channel where everyone can post what they are struggling with, so anyone can respond to help and start a 1-on-1 call. If we can have 15-min meetings informing everyone once a day.

read more

Complexity <> Sophisticated

Complexity <> Sophisticated It can be just overly complex, because the person who created it didn't understand it well enough. Teachers face the challenge of breaking down complex subjects for their students. The ability to simplify abstract ideas without losing...

read more

I can’t read it anymore!

I can't read it anymore! You know those old guys with MASSIVE text on their phone or laptop. I have joined the club. I am 47 now and I started to pinch my eyes more and more. Today I increased my font size on my phone and laptop. I increased my text-size to 110% and...

read more

The Scrum ticket system

The Scrum ticket system You're churning out tickets, classified as 'features', that strongly resemble clean-up tasks. Are all team members solely focused on their own individual ticket? This surely isn't the Agile methodology that was initially pitched to you....

read more

5 reasons NOT to automate.

5 reasons NOT to automate. This might sound odd coming from me, a staunch advocate of automation. However, beware! If you're handling a process for the first, second or third time, don't rush to automate it immediately. Patience is key. Why? 1️⃣ Automation works best...

read more

Justifying marketing is hard.

Justifying marketing is hard. Generating awareness and traffic is hard to quantify. What is the ROI for marketing? The reason is the distance to the sale transaction. How further away how harder it is to quantify. Conversion is the closest to a sales transaction. They...

read more

Be a T-shape developer

Be a T-shape developer I always advocate developers to specialize when they are becoming senior. But don't lose track of the rest of the playfield. So be broad, know a lot of technologies and areas, but also go deep into one or more. That is a T-shaped developer. Why...

read more

OpenTelemetry for Dataverse ServiceClient?

OpenTelemetry for Dataverse ServiceClient? I love OpenTelemetry. It's so easy to plug in instrumentation and have a clear view of your distributed system. But Dataverse ServiceClient doesn't have it yet... Its logging is sparse. Fixing a bug using the Dataverse logs...

read more

Nobody cares about bad code if it works.

Nobody cares about bad code if it works. Besides you and your team, others don't care about the bad code that exists in your codebase. Management will not give you time to make the code better. So don't put it as a task on the board for the Product Owner to...

read more

Locality of Behavior principle (LoB):

Locality of Behavior principle (LoB): "The behavior of a unit of code should be as obvious as possible by looking only at that unit of code." This principle is starting to get more and more traction. I like it. You see it in components like React/Vue/Svelte. One file...

read more

‘Functions need to do one thing’-mantra is wrong.

'Functions need to do one thing'-mantra is wrong. Since Robert C. Marting wrote the book Clean Code, developers try to implement the guidelines from that book. One of them is to write Small focused functions. Please stop doing that! Don't let me go through multiple...

read more

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction