Thingies

A web-based tool for calculating project estimates using a Monte Carlo simulation was recently made publicly available. The results of a Monte Carlo simulation can help manage expectations with stakeholders.

Every year at InfoQ we update our topic graph to show where we think different topics are in the technology adoption curve. When we do so we look at the state of practice, emerging ideas and information we hear on the various grapevines the editorial team is tapped into.

@BernerDominik @bastacon

The Order Management System (OMS) at Jet is responsible for a number of business functions and was originally developed using a collection of microservices orchestrating tasks.

Copying other successful companies opens up risks that may tank your product — which is exactly what happened to YouTube Premium.

Almost two decades ago, Joel Spolsky excoriated Netscape for rewriting their codebase in his landmark essay Things You Should Never Do. He concluded that a functioning application should never, ever be rewritten from the ground up. His argument turned on two points:

The #1 Challenge with Agile is culture – Industry Research has consistently reported for years. Adaptation of a new way of working often doesn’t blend into “business as usual”. To succeed with Agile we need to understand culture and how to navigate it.

This report is a case study on upgrading a C# 7 class library to C# 8 with nullable reference types. The project used in this case study, Tortuga Anchor, is a collection of MVVM style base classes, reflection code, and various utility functions.

Scrum is founded in the belief that self-organizing teams can figure out what they need. When true, this is sometimes not sufficient. And sometimes, particularly in software development, it seems not to be true. Ken demonstrated this repeatedly in the class.

For global businesses to meet today’s architectural challenges with constant change and extreme scale, we need to go back to the basic principles of system design.

Here’s a little something I offered on Twitter a day or so ago. I wrote it in response to some tweets from a very smart and creative member of our community, whose ideas are usually quite good.

Titel müssen zwar ein bisschen provozieren, damit sie angeklickt werden, aber dieser hier entspricht auch tatsächlich dem was ich denke.

Going fast without control could be the biggest enemy of software development. The three main areas where you should slow down in are people, process, and product. Before digging into details, let me start with a story. I guess it was 2011.

The biennial Conference on Innovative Data Systems Research has come round again.

Agility is a unique and continuously evolving state that is typical to a specific organization with its people and its history. A traditional (industrial) approach to becoming more Agile commonly creates no more than an illusion of agility.

In many situations, there is only one possible type allowed in a given place. And yet C# still requires you to explicitly list the type. If the Target-typed `new` expression proposal is adopted, such boilerplate code will no longer be necessary.

Wie die Kenntnis über die Bedeutung von Kompliziertheit und Komplexität helfen kann komplexen Problemstellungen klug zu begegnen. Problemstellungen bestehen oftmals aus einer Mischung von zwei Bestandteilen.