Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Do 11.07.2024 00:00:37 61.941 +12 3.533.951 57,1 Fosstodon 4.2.10 500 Mi 10.07.2024 00:00:53 61.929 +5 3.530.507 57,0 Fosstodon 4.2.10 500 Di 09.07.2024 00:00:08 61.924 +2 3.527.175 57,0 Fosstodon 4.2.10 500 Mo 08.07.2024 00:00:19 61.922 +5 3.524.369 56,9 Fosstodon 4.2.10 500 So 07.07.2024 00:00:04 61.917 0 3.522.885 56,9 Fosstodon 4.2.10 500 Sa 06.07.2024 00:00:07 61.917 -2 3.523.632 56,9 Fosstodon 4.2.10 500 Fr 05.07.2024 00:00:27 61.919 0 3.520.710 56,9 Fosstodon 4.2.10 500 Do 04.07.2024 00:00:52 61.919 +2 3.517.337 56,8 Fosstodon 4.2.9 500 Mi 03.07.2024 00:00:12 61.917 +2 3.513.906 56,8 Fosstodon 4.2.9 500 Di 02.07.2024 00:01:44 61.915 0 3.510.479 56,7 Fosstodon 4.2.9 500
ThomasAPowell (@thomasapowell) · 10/2022 · Tröts: 1.570 · Folger: 227
Do 11.07.2024 00:40
I’m reading some 1970s and 1980s #SWE books this summer. The cynical old dev in me keeps noticing how things seem eerily familiar. So, you hopefully can guess what I was thinking of when I noticed this diagram in Structured Design. Could it be something like, “Huh, this seems like a React component tree with a shared state store?”
All of this has happened before, and it will happen again and again…
A component or in case of Yourden Module call hierarchy with a shared environmental state which reveals that as much as everything is decoupled it really isn’t. Looks so familiar like a React tree with store abuse.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Ivory for Mac