Pinned Tweet
Legacy Archipelago: a series of systems built one after another, each aimed to replace the previous one. For each step the new system only covered ~80% of the original functionality so the previous one was never decommissioned. All versions in use.
[v1]->[v2]->[v3]->[v4]->[v5]
Gus Power retweeted
We talk endlessly about modularity in application code, then connect to a database where everything can depend on everything else. Why does modularity stop at the database?
businesssoftwareishard.com/e…
Gus Power retweeted
A chance encounter leads to an unexpected conversation about software, its history, and the questions that have been troubling us for decades.
What if some of the answers we've been looking for were there all along?
My new book, The Parnas Suite.
leanpub.com/theparnassuite
Gus Power retweeted
Why does it only fail in production?
Because production may be the first place where the (concurrent) program we wrote actually runs concurrently.
businesssoftwareishard.com/e…
Gus Power retweeted
New essay: Fifteen Hundred Classes and No Visible Shape
businesssoftwareishard.com/e…
We can expect the same system will continue to produce similar outcomes as long as the same heuristics are in use. Separate "thinkers" from "doers", silo people by function, pay bottom dollar for suppliers and staff: all of these heuristics have predictable and measurable effect.




