4 ms·
Any experiences with intentionally hostile software architecture? Curious how for example code project structure or inter-process messaging constraints can pro
by sandij 7y ago
Any experiences with intentionally hostile software architecture?
Curious how for example code project structure or inter-process messaging constraints can prohibit mixing concerns or breaking the domain model. Also curious how such a forceful environment is experienced and whether it has the intended effect.
- batoure 7y agoI came to the comments to talk about this, was totally hoping to scroll down and find a section about software in the wikipedia article. I would argue that almost every project I have every worked on where the software was initially maintained by a single individual would be classified as "hostile architecture"
- unhammer 7y agoWell, there are hostile user interfaces at least: https://userinyerface.com/ https://userinyerface.com/ https://www.darkpatterns.org/ https://www.darkpatterns.org/ and in programming you have defensive/deterrent features like prefixing unsafe function names with "unsafe"
- twic 7y agoMicroservices advocates claim that the pain of implementing features across microservices encourages modularity.
- Thiez 7y agoPerhaps GCC qualifies? https://lwn.net/Articles/583140/ https://lwn.net/Articles/583140/
- nukeop 7y agoMicrosoft Office is built on such model, where the document specification is intentionally vague, contradictory, and the implementation is full of constantly changing details that make 100% accurate re-implementation by competition impossible, thus maintaining its hegemony in the office software niche.