I am a bit confused and very curious what purpose this site is trying to serve. They seem to have many articles all talking about the same concept which I think could be summarized as: "code is fungible". That is to say, the tests, specifications, and other supporting documentation are the truly important pieces of a system. The code part is easily replaceable. Every article on the site is about that concept in some way.
Human language is imprecise and it seems to be a common thought on HN that it is impossible to clearly and completely define the requirements of a sufficiently complex system of software without, well... writing the software. I just don't see a scenario where The Phoenix Architecture would actually make sense.
> The deletion test is not a recommendation. It’s a diagnostic.
> That’s not robustness. It’s entanglement.
> This isn’t a tooling fad. It’s an economic shift.
I have a strong feeling this article would survive regeneration well.
Human language is imprecise and it seems to be a common thought on HN that it is impossible to clearly and completely define the requirements of a sufficiently complex system of software without, well... writing the software. I just don't see a scenario where The Phoenix Architecture would actually make sense.
> The deletion test is not a recommendation. It’s a diagnostic.
> That’s not robustness. It’s entanglement.
> This isn’t a tooling fad. It’s an economic shift.
I have a strong feeling this article would survive regeneration well.