Blog on Uwe Friedrichsen

Quality - The unknown entity - Part 3 This is the third post of a blog series discussing quality.

Quality - The unknown entity - Part 2 This is the second post of a blog series discussing quality.

Quality - The unknown entity - Part 1 Quality is the subject of countless discussions, e.g., with unsatisfied clients. 1 I had the situation more than once that a client was not satisfied, that they felt their quality expectations for the software were not

The importance of comments - Part 3 This is the third and last post discussing the value of comments in code.

The importance of comments - Part 2 This is the second post discussing the value of comments in code.

The importance of comments - Part 1 I wrote about the importance of documentation a few weeks ago.

Don’t make me think!

The importance of documentation Documentation – not only since the rise of Agile a controversially discussed topic in IT.

The cloud-ready fallacy Lately, I had a discussion with an on-premises data center manager who claimed that public cloud does not leverage any cost advantages over on-premises computing.

The limits of the Saga pattern The Saga pattern has become quite popular in the context of microservices.

The microservices fallacy - Part 11 This post complements the discussion of the previous posts with a few general complementing recommendations and concludes this blog post series.

The microservices fallacy - Part 10 In this post we take a look at microliths as an alternative to microservices.

The microservices fallacy - Part 9 In this post we take a look at moduliths as an alternative to microservices.

The microservices fallacy - Part 8 In this post we start to make sense of what we have discussed so far – when we should use microservices, when not to use them and what to do instead.

The microservices fallacy - Part 7 This post discusses actual reasons that justify the use of microservices.

The microservices fallacy - Part 6 This post discusses the fallacy that microservices make technology changes easier.

The microservices fallacy - Part 5 This post discusses the widespread fallacy that microservices lead to better solution design.

The microservices fallacy - Part 4 This post discusses two widespread fallacies – that microservices improve reusability (and thus pay for themselves after a short while) and that microservices improve team autonomy.

The importance of resilience engineering There was a bigger outage at AWS this week, and of course media coverage was big again.

The microservices fallacy - Part 3 This post discusses the widespread fallacy that solutions become simpler with microservices.

The microservices fallacy - Part 2 This post discusses the widespread fallacy that microservices are needed to tackle scaling issues.

The microservices fallacy - Part 1 This is a blog series discussing the fallacies of microservices.

The value of speed The speed of the IT value chain often is a topic in discussions I have with decision makers.

The purpose of architecture Software architecture is one of the things in software development that is important.

Throwing things away This post sort of complements the “Simplify!”

Simplify!

Simplify!

The continuous amnesia issue In this post I want to discuss an issue that I, being for a longer time in IT meanwhile, observe over and over again.

Simplify!

Simplify!

Simplify!

Simplify!

Simplify!

The laws of architectural work After completing the short “OSS” blog series series and before returning to the “Simplify!”

Open Source Software – Part 3 In the previous post, I discussed the two most widespread misconceptions about OSS, that OSS is for free and that it does not create any lock-in.

Open Source Software – Part 2 In the previous post, I discussed the rise of OSS, the positive effects it had and how it changed software development.

Open Source Software – Part 1 When I started to discuss accidental complexity on the architectural level in my “Simplify!”

Simplify!

Simplify!

Worlds apart A few days ago, I saw the following job advertisement creating a lot of mockery in the Internet: While I perfectly understand why it received so many ironic comments, I think it goes deeper.

Simplify!

Simplify!

Simplify!

Dismiss maturity models I wanted to give you a short break from my “Simplify!”

Simplify!

Simplify!

Simplify!

Simplify!

Degrees of uncertainty After introducing the concept of uncertainty as the unifying main driver of rethinking IT, I discussed the basic approach how to act under uncertainty in the previous post.

Acting under uncertainty In the previous post, I introduced the concept of uncertainty as the unifying main driver of rethinking IT.