Future home of insightful discussion about software architecture at least I hope so…
For example, Conway’s Law: Let’s assume you have a web app. You also have enough developers to split them into three teams. You can either split according to the parts (Frontend team, Backend team, Batch team) or you could use some other method, like split by function (Chat team, Video team, Account Management). You could also split them by skills (Dev team, Ops team, Designer team).
You can now pick your poison, where you want the app to be more consistent according to Conway’s Law. If you split by parts, then there will be a well defined API between front- and backend and changing it takes some discussion. If you split by function, the API will be fluid but the different functions will not feel as consistent to the users. If you split by skill, new features will take longer but the servers are more reliable and the logos are very consistent.
The effects will be weak if the three teams are in the same open floor. They will be extreme if each team is on a different continent and timezone.
I use the hosted version because the point of monitoring is that it alerts me when the rest of my stuff is down. You can self host it though.
Mars becomes the second planet that has more computers running Linux than Windows. https://twitter.com/mikko/status/1362763793042972673
Naturally, they go for conCATenative programming languages. 😉
“Official sock puppet account of the weirder.earth admin team.” https://weirder.earth/@WeirderAdmin
Google developers use Linux, probably something derived from Ubuntu.