Week 36, year 2024

• Tales from the .NET Migration Trenches - Turning Off the Lights - Posts in this series: Intro Cataloging Empty Proxy Shared Library Our First Controller Migrating Initial Business Logic Our First Views Session State Hangfire Authentication Middleware Turning Off the Lights In the last post, we looked at migrating our middleware, which we tackle in an as-needed basis. When a controller needs [Jimmy Bogard]
• Governing data products using fitness functions - Decentralized data management requires automation to scale governance effectively. Fitness functions are a powerful automated governance technique my colleagues have applied to data products within the context of a Data Mesh. Since data products serve as the foundational building blocks of a data strategy, ensuring robust governance around them significantly increases the chances of success. Kiran Prakash explains how to do this, starting with simple tests for key architectural characteristics and moving on to leveraging metadata and Large Language Models. [Martin Fowler]
• Bliki: Cycle Time - Cycle Time is a measure of how long it takes to get a new feature in a software system from idea to running in production. In Agile circles, we try to minimize cycle time. We do this by defining and implementing very small features and minimizing delays in the development process. Although the rough notion of cycle time, and the importance of reducing it, is common, there is a lot of variations on how cycle time is measured. A key characteristic of agile software development is a shift from a Waterfall Process, where work is decomposed based on activity (analysis, coding, testing) to an Iterative Process where work is based on a subset of functionality (simple pricing, bulk discount, valued-customer discount). Doing this generates a feedback loop where we can learn from putting small features in front of users. [Martin Fowler]

Permalink | From 02 September 2024 to 08 September 2024 | Last updated on: Wed, 11 Sep 2024 14:37:10 GMT