I invite you to upgrade to a paid subscription. Paid subscribers have told me they have appreciated my thoughts & ideas in the past & would like to see more of them in the future. In addition, paid subscribers form their own community of folks investing in improving software design—theirs, their colleagues, & their profession.
In product led organizations, you will usually gradually iterate design as new requirements surface. But how do we avoid letting business progression be too tied up to the inherent uncertainties of structural changes?
You’ve lost me on interruptible and parallels. Could you expand on that please again?
Do you think ideas like tik-tok releases (one more focused on features, one more focused on cleaning up) are a good way to hold the balance (without killing the relationships)?
Kent: How is the structure made visible for the feature focused people?
Which strategy would you suggest to cover all Social, Software and Economic concerns in requirements gathering meetings before starting to design a software solution?
You mentioned the value in options for upfront design, what about the problem of over engineering for options that do not get used, was this a waste of seconds? I am thinking about the principle "YAGNI" (you aint going to need it)
in a startup context, how do you reconcile the tidy first principle with the idea that earning earlier is earning more? tidying could easily slow time to market for a new feature.
How the Tidy First’s Social, Software and Economic imperatives could be aligned with the FinOps Iron Triangle: Costs, Quality and Time?
what are your suggestions to solve the outdated documentation issue? It’s not always possible to get rid of all kind of documentation, in software development, especially in large companies.
Is there any way to study coupling through percolation theory? With the goal of figuring out what’s the degree of coupling that cause the big crisis?
Can you design in avalanche protection? Something that stops avalanches in case they got started. Did you see something / maybe an pattern that help to prevent this?
What aspects, if any, of Extreme Programming do you find hold less true today than they did, when you published your book on the topic initially?
How Tidy First Idea-Structure-Feature concept live together with TDD considering that the refactoring is the last phase and not the second one?
Kent, did you want to write this book or felt that the field needs you to write this book?
You’re currently a free subscriber to Software Design: Tidy First?. Buying me more time to think & write means more thoughts & ideas for you. |