Note, however, that this kind of reasoning does not include any estimate of the likely impact of a "bad decision". The implication is that all bad decisions are equivalent, but in practice some bad decisions are far worse than others.
Ultimately you wind up making your decisions on the best information available to you and on your own priorities, but you sort of have to take responsibility for your own limitations, also. So... for example... how do you address issues where your development environment stalls or prevents your problem solving? (There are multiple viable answers here...) Thanks, -- Raul On Fri, Nov 17, 2017 at 6:47 AM, Erling Hellenäs <[email protected]> wrote: > The more decisions you have to take, the greater the risk of taking a bad > decision. In a tailored development environment more decisions are taken for > you, thereby eliminating possibilities of taking bad decisions. /Erling > Hellenäs > > > Den 2017-11-17 kl. 12:28, skrev Raul Miller: >> >> I do not like to rely on "NSA touched it" reasoning - that's too broad >> of a brush. That said, I have problems with SELinux - its fine-grained >> failure modes make understanding what the computer is doing difficult >> for me to understand. That said, given how little effort most people >> place into understanding how malware propagates, and solving those >> problems, it's also difficult to identify better alternatives. (Which >> leads me back to my original post in this thread.) >> >> So... I think we have to assume that all software is not completely >> reliable. People are flawed, and the things we make are flawed. The >> trick is building resilience into your part of the system and then >> coping with the things you cannot control. >> >> But, yeah, we all make bad choices sometimes, and that's difficult to >> face. >> >> However, I strongly disagree with "only one way to __ it" reasoning. >> That inevitably turns out to be incorrect. It's often just an excuse >> for laziness. When you get into heavily optimized contexts, that does >> limit options, but there's always another way even if it's not the >> best way. >> >> Thanks, >> > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
