Timeline for What is the "Fix Everything" design pattern?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6, 2019 at 12:33 | comment | added | candied_orange | @JohnWu it's simply a difference in scale. If more things had small "fix everything" functions maybe we'd need full reboots less often. It's a question of how you define "everything". | |
| Oct 6, 2019 at 8:55 | comment | added | John Wu | @candied_orange I'd say if you find yourself needing to reboot, it's more of an anti-pattern at that point :) But I see what you mean. Maybe an app pool recycle would make a better example. | |
| Oct 6, 2019 at 3:47 | comment | added | candied_orange | The "fix everything" pattern has a more common name for when you stop trusting things are good and just fix everything. It's called a reboot. Very idempotent. ; ) | |
| Apr 25, 2017 at 6:25 | comment | added | Dr. Hans-Peter Störr | It might be useful to point out that "fix everything" and idempotent are different things: "fix everything" is usually idempotent (but doesn't need to be), and idempotent operations don't need to fix everything or even have a performance penalty - just give the same result when executed twice. | |
| Apr 24, 2017 at 15:01 | vote | accept | Aaron Hall | ||
| Apr 20, 2017 at 20:01 | comment | added | Kevin | @Izkata Even more than React, this answer made me think of Redux. | |
| Apr 20, 2017 at 19:15 | comment | added | Matthieu M. | @Izkata: Yes, the important part is that the user-facing part is "total" so that from the point of view of the logic you do not have to wire all the dependencies, of course the framework is encouraged to be clever to limit the work actually performed. | |
| Apr 20, 2017 at 19:08 | comment | added | Izkata | @MatthieuM. React, which is quite popular on frontend development, is like that except it does virtual dom diffing so it only updates the real dom with the actual changes | |
| Apr 20, 2017 at 11:31 | comment | added | kojiro | This sounds essentially like the principle behind systems like Saltstack, Ansible, and Nix. Given a description of a configuration, you can theoretically bring several diverse systems into the same end state. | |
| Apr 20, 2017 at 11:18 | comment | added | Matthieu M. | It seems to me that MVC is typical of "Fix Everything": when you modify the model then redraw the view from scratch, the view is just fully redrawn, without attempting to divine what parts the action could potentially have affected. | |
| Apr 19, 2017 at 16:02 | history | edited | John Wu | CC BY-SA 3.0 |
added 484 characters in body
|
| Apr 19, 2017 at 15:56 | history | edited | John Wu | CC BY-SA 3.0 |
added 484 characters in body
|
| Apr 19, 2017 at 15:49 | history | answered | John Wu | CC BY-SA 3.0 |