Contents 1 Overview 2 Reasons for failure 2.1 Overconfidence and complacency 2.1.1 Natural tendency 2.1.2 The illusion of control 2.1.3 Anchoring 2.1.4 Competitor neglect 2.1.5 Organisational pressure 2.1.6 Machiavelli factor 2.2 Dogma, ritual and specialisation 2.2.1 Frames become blinders 2.2.2 Processes become routines 2.2.3 Resources become millstones 2.2.4 Relationships become shackles 2.2.5 Values becomes dogmas 3 The paradox of information systems 3.1 The irrationality of rationality 3.2 How computers can be destructive 3.3 Recommendations for practice 4 Case studies 4.1 Fresh & Easy 4.2 Firestone Tire and Rubber Company 4.3 Laura Ashley 4.4 Xerox 5 See also 6 References

Inevitably, I read and highlight more articles than I have time to fully process in Obsidian. There are currently 483 files in the Readwise/Articles folder and 527 files marked as needing to be processed. I have, depending on how you count, between 3 and 5 jobs right now. I am not going to neatly format all of those files. I am going to focus on the important ones, when I have time.

The second situation would be zombie reaping. If the process spawns child processes and does not properly reap them it will lead to a full process table

Unfortunately most init systems don't do this correctly within Docker since they're built for hardware shutdowns instead. This causes processes to be hard killed with SIGKILL, which doesn't give them a chance to correctly deinitialize things.

According to the Unix process model, the init process -- PID 1 -- inherits all orphaned child processes and must reap them. Most Docker containers do not have an init process that does this correctly. As a result, their containers become filled with zombie processes over time.

When a process loses its parent, init becomes its new parent. init periodically executes the wait system call to reap any zombies with init as parent.

Zombie processes should not be confused with orphan processes: an orphan process is a process that is still executing, but whose parent has died. When the parent dies, the orphaned child process is adopted by init (process ID 1). When orphan processes die, they do not remain as zombie processes; instead, they are waited on by init.

The result is that a process that is both a zombie and an orphan will be reaped automatically.

The term zombie process derives from the common definition of zombie — an undead person. In the term's metaphor, the child process has "died" but has not yet been "reaped". Also, unlike normal processes, the kill command has no effect on a zombie process.

This occurs for the child processes, where the entry is still needed to allow the parent process to read its child's exit status: once the exit status is read via the wait system call, the zombie's entry is removed from the process table and it is said to be "reaped".

When a zombie is created (i.e. which happens when its parent exits, and therefore all chances of it ever being waited by it are gone), it is reparent to init, which is expected to reap it (which means calling wait on it).

In other words, someone has to clean up after "irresponsible" parents that leave their children un-wait'ed, and that's PID 1's job.

Have lost their parent (i.e. their parent exited as well), which means they'll never be waited on by their parent.

Now, unlike other processes, PID 1 has a unique responsibility, which is to reap zombie processes.

A low-level approach is to fork twice, running the desired process in the grandchild, and immediately terminating the child. The grandchild process is now orphaned, and is not adopted by its grandparent, but rather by init.

The process group mechanism in most Unix-like operating systems can be used to help protect against accidental orphaning, where in coordination with the user's shell will try to terminate all the child processes with the "hangup" signal (SIGHUP), rather than letting them continue to run as orphans.

In a Unix-like operating system any orphaned process will be immediately adopted by an implementation-defined system process: the kernel sets the parent to this process

Even though technically the process has a system process as its parent, it is still called an orphan process since the process that originally created it no longer exists.

Let's look at a concrete example. Suppose that your container contains a web server that runs a CGI script that's written in bash. The CGI script calls grep. Then the web server decides that the CGI script is taking too long and kills the script, but grep is not affected and keeps running. When grep finishes, it becomes a zombie and is adopted by the PID 1 (the web server). The web server doesn't know about grep, so it doesn't reap it, and the grep zombie stays in the system.

In fact, every timeone combines and recordsfacts in accordance withestablished logical process-es, the creative aspect ofthinking is concerned onlywith the selection of thedata and the process to beemployed, and the manip-ulation thereafter is repeti-tive in nature and hence afit matter to be relegatedto the machines

We’ve been taught that it’s important to work “with the end inmind.” We are told that it is our responsibility to deliver outcomes,whether that is a finished product on store shelves, a speechdelivered at an event, or a published technical document.

“This technique alsoexplains why I don’t think at all linearly and have trouble finding the right sequence ofchapters when writing a book, because indeed every chapter must reappear in everyother.”22

To produce meaningful work, and then forget about it, so you can move on to another and hopefully greater act of linear will.

in reality pretty much everyone out there has some messiness in their graph and that's okay

nicholas lerman is a sample of one 01:09:54 and if the zerocarton is a tool for thinking there are all these other thinkers out there who are thinking um and do we know how they're thinking how their 01:10:07 how you know what note systems are they using i'd like to i'd like to be able to place lerman yeah amongst all these others and and sort of in the zerocast and 01:10:23 see what others are doing as well and yeah i mean if there was one project i would have loved to do is going around 01:10:36 asking everyone i whose work i admire how do you do it how do you do it exactly what do you do in the morning how do you sit down how do you digest the books you're reading 01:10:48 um i was obsessed with the idea and it's just because i'm too shy to follow up on that

I used to use Roam for lots of things: a daily diary, book notes, keeping track of lists like my todo list, and taking meeting notes.Today, this is my stack:Daily Diary / paper notebookBook Notes / split between Roam and MuseTo-do List / ThingsMeeting Notes / Apple Notes

After some time though, reality started to sink in. ‘I am not really going back through all of these notes as often as I thought I would.’

There is one reliable sign if you managedto structure your workflow according to the fact that writing is not alinear process, but a circular one: the problem of finding a topic isreplaced by the problem of having too many topics to write about.

Informal observations include direct observations of our own and others’ behavior as well as secondhand observations from non-scientific sources such as newspapers, books, blogs, and so on. For example, you might notice that you always seem to be in the slowest moving line at the grocery store. Could it be that most people think the same thing? Or you might read in a local newspaper about people donating money and food to a local family whose house has burned down and begin to wonder about who makes such donations and why. Some of the most famous research in psychology has been inspired by informal observations.

A Mental Squeeze Point is when your unsorted knowledge becomes so messy it overwhelms and discourages you. Either you are equipped with frameworks to overcome the squeeze point, or you are discouraged and possibly abandon your project.

ot its deepestlevelW whatever the mediumW note taking involves variations on and comXbinations of a few basic maneuversW which w propose to identify as the fourSsh storingW sortingW summarizingW and selectin

Run the Rails server (bin/rails s) and the Webpack Dev Server (bin/webpack-dev-server) via your preferred method. Two terminal tabs will work or create a Procfile and run via overmind or foreman.

There is no inactive learning, just as there is no inactive reading.

Ralph Waldo Emerson, the man who encouraged his friend Thoreau to start a journal and the man who had the most success with the journal > lecture > essay > book method, kept elaborate notebooks just for indexing his other notebooks.

There is one very important reason for enabling job control to be useful inside scripts: the side-effect it has of placing background processes in their own process groups. This makes it much, much easier to send signels to them and their children with one simple command: kill -<signal> -$pgid. All other ways of dealing with signaling entire trees of processes either involve elaborate (sometimes even recursive) functions, which are often bugnests, or risk killing the parent in the process (no pun intended).

Process based parallelisation is simpler than thread based due to well, the GIL on MRI rubies and lack of 100% thread safety within the other gems. (I'm fairly certain for example that there are threaded bugs lurking within the mocks code).

Parallel testing in this implementation utilizes forking processes over threads. The reason we (tenderlove and eileencodes) chose forking processes over threads is forking will be faster with single databases, which most applications will use locally. Using threads is beneficial when tests are IO bound but the majority of tests are not IO bound.

man ps has all the answers, under the "PROCESS STATE CODES" heading:

The rsync and sleep commands (the sleep is just an example) are run through exec to prevent the creation of zombie processes if I kill the parent script while they're running, and each potentially-long-running command is wrapped in its own subshell so that when exec finishes, it won't terminate the whole script.

It’s not that Slack is too distracting and killing individual productivity. It’s that your company’s processes are so dysfunctional you need Slack to be distracting and killing individual productivity.

Brown, M., & Sacco, D. F. (2020, May 6). Testing the Motivational Tradeoffs in Pathogen Avoidance and Status Acquisition. https://doi.org/10.31234/osf.io/y8ct6

If any Firefox engineers are reading this, please don't try to subvert the above workaround, it requires multiple steps and administrator rights to set up, and we must all agree that it is of little sense for Firefox to try defending against unwanted programs or malware that has root access on the device.

The prokaryotic CRISPR-Cas system of defense against mobile elements seems to function via a bona fide Lamarckian mechanism

scientists are uncovering and debating an increasing array of other evolutionary processes at work in bacteria, some of which are suspiciously Lamarckian in character4–6

A composite process, remember, is organized from both human processes and computer processes

osthumanism as an attempt to engage humans asdistributed processes rather than as discrete entities. In

conditional distribution for individual components can be constructed

calculation once again involves inverting a NxN matrix as in the kernel space representation of regression

in equation B for the marginal of a gaussian, only the covariance of the block of the matrix involving the unmarginalized dimensions matters! Thus “if you ask only for the properties of the function (you are fitting to the data) at a finite number of points, then inference in the Gaussian process will give you the same answer if you ignore the infinitely many other points, as if you would have taken them all into account!”(Rasmunnsen)

The better a designer understands his or her audience and the unique needs of that particular audience, the more efficiently and effectively he or she will be able to develop, design, implement, and evaluate instructional materials in a rapid format. 

The frequent assessment of the use of standardized leading practices and processes