Two unrelated experiments made it challenging for us to reproduce the issue at first: an internal-only server-side experiment related to message queuing; and an orthogonal change in how we display thinking suppressed this bug in most CLI sessions
大多数人认为复杂的系统测试流程应该能够发现大多数关键缺陷，但作者展示了即使有多重测试机制，两个看似无关的实验如何协同掩盖了一个严重bug。这挑战了'全面测试能保证产品质量'的传统认知，揭示了系统复杂性带来的意外风险。
system reflexivity
for - definition - system reflexivity (Moore et al., 2018) - the capacity to see the complexity and mobilize the agency in a system, while deeply engaging with diversity across multiple scales - SOURCE - paper - Reflexivity as a transformative capacity for sustainability science: introducing a critical systems approach - Lazurko et al. - 2025, Jan 10
I often noticed that most Candidates inExaminations used to begin to write their Essays atonce. They never realised that their minds were there-by being distracted and divided among many differentprocesses, each of which is particularly hard even whentaken alone. For all at once their minds are being-called upon to Collect Ideas, to Select and decide whichare important, etc., to Arrange the Selected Ideas, andto Express them. To try all this as a single action is" most extraordinarily unscientific, even if a few brilliantgeniuses here and there have succeeded in the attempt.
One of the major affordances of using a zettelkasten or card index for writing is that it forces the writer to break things down into their constituent parts, thereby making the entire process of writing far easier and less complex. One can separately focus their attention on the smaller steps of collecting, selecting, and arranging the material before beginning to actually write.
Centre for the Evaluation of Complexity Across the Nexus
for - complexity - evaluation - from - paper - Building a system-based Theory of Change using Participatory Systems Mapping
But then life went on and nothing really happened.
This essay seems to be more about shiny object syndrome. The writer doesn't seem to realize any problems they've created. Way too much digging into tools and processes. Note the switching and trying out dozens of applications. (Dear god, why??!!) Also looks like a lot of collecting digitally for no clear goal. As a result of this sort of process it appears that many of the usual affordances were completely blocked, unrealized, and thus useless.
No clear goal in mind for anything other than a nebulous being "better".
One goal was to "retain what I read", but nothing was actively used toward this stated goal. Notes can help a little, but one would need mnemonic methods and possibly spaced repetition neither of which was mentioned.
A list of specific building blocks within the methods and expected outcomes would have helped this person (and likely others), but to my knowledge this doesn't exist as a thing yet though bits and pieces are obviously floating around.<br /> TK: building blocks of note taking
Evidence here for what we'll call the "perfect system fallacy", an illness which often goes hand in hand with "shiny object syndrome".
Too many systems bound together will create so much immediate complexity that there isn't any chance for future complexity or emergence as the proximal system is doomed to failure. One should instead strive for immediate and excessive simplicity which might then build with time, use, and practice into something more rich and complex. This idea seems to be either completely missed or lost in the online literature and especially the blogosphere and social media.
people had come up with solutions Sadly, despite thousands of variations on some patterns, people don't seem to be able to settle on either "one solution" or their "own solution" and in trying to do everything all at once they become lost, set adrift, and lose focus on any particular thing they've got as their own goal.
In this particular instance, "retaining what they read" was totally ignored. Worse, they didn't seem to ever review over their notes of what they read.
I was pondering about different note types, fleeting, permanent, different organisational systems, hierarchical, non-hierarchical, you know the deal.
Why worry about all the types of notes?! This is the problem with these multi-various definitions and types. They end up confusing people without giving them clear cut use cases and methods by which to use them. They get lost in definitional overload and aren't connecting the names with actual use cases and affordances.
I often felt lost about what to takes notes on and what not to take notes on.
Why? Most sources seem to have reasonable guidance on this. Make notes on things that interest you, things which surprise you.
They seem to have gotten lost in all the other moving pieces. Perhaps advice on this should come first, again in the middle, and a third time at the end of these processes.
I'm curious how deeply they read sources and which sources they read to come to these conclusions? Did they read a lot of one page blog posts with summarizations or did they read book length works by Ahrens, Forte, Allosso, Scheper, et al? Or did they read all of these and watch lots of crazy videos as well. Doing it "all" will likely lead into the shiny object syndrome as well.
This seems to outline a list of specifically what not to do and how not to approach these systems and "popular" blog posts that are an inch deep and a mile wide rather than some which have more depth.
Worst of all, I spent so much time taking notes and figuring out a personal knowledge management system that I neglected the things I actually wanted to learn about. And even though I kind of always knew this, I kept falling into the same trap.
Definitely a symptom of shiny object syndrome!
Trends of Emerging System Properties
One of the primary tasks of engineers is to minimize complexity. JSX changes such a fundamental part (syntax and semantics of the language) that the complexity bubbles up to everything it touches. Pretty much every pipeline tool I've had to work with has become far more complex than necessary because of JSX. It affects AST parsers, it affects linters, it affects code coverage, it affects build systems. That tons and tons of additional code that I now need to wade through and mentally parse and ignore whenever I need to debug or want to contribute to a library that adds JSX support.
Méndez, P. F. (2020). Blue uncertainty: Warding off systemic risks in the Anthropocene – Lessons from COVID-19 [Preprint]. SocArXiv. https://doi.org/10.31235/osf.io/z2br5
Murphy, C., Laurence, E., & Allard, A. (2020). Deep learning of stochastic contagion dynamics on complex networks. ArXiv:2006.05410 [Cond-Mat, Physics:Physics, Stat]. http://arxiv.org/abs/2006.05410
Torres, L., Blevins, A. S., Bassett, D. S., & Eliassi-Rad, T. (2020). The why, how, and when of representations for complex systems. ArXiv:2006.02870 [Cs, q-Bio]. http://arxiv.org/abs/2006.02870
Olthof, M., Hasselman, F., & Lichtwarck-Aschoff, A. (2020, May 1). Complexity In Psychological Self-Ratings: Implications for research and practice. Retrieved from psyarxiv.com/fbta8