One of the biggest problems that software engineers and architects face during their day-to-day work is deciding when something is done. In the past, I’ve worked on both large and small-scale software systems that we would produce and then sell on to customers; but the questions that we’d get from customers, be they internal or external, were always of the same vein: “Can you just add x?” or “Can we change y?” Often, it’s cost prohibitive as a software vendor to make minor changes for individual customers; imagine a situation where you could contact Microsoft and ask them to ...
© Paul Michaels 2022
P. MichaelsSoftware Architecture by Examplehttps://doi.org/10.1007/978-1-4842-7990-8_55. The Admin Application Problem
Paul Michaels1
(1)
Derbyshire, UK
Get Software Architecture by Example: Using C# and .NET now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.