Sidebar Menu

Projects

  • Dashboard
  • Research Project
  • Milestones
  • Repository
  • Tasks
  • Time Tracking
  • Designs
  • Forum
  • Users
  • Activities

Login

  • Login
  • Webmail
  • Admin
  • Downloads
  • Research

Twitter

Posts by stumathews
Stuart Mathews
  • Home
  • Blog
  • Code
  • Running
  • Gaming
  • Research
  • About
    • Portfolio
    • Info

The fading importance of ego and the utility of the checklist

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
18.Apr
18 April 2022
Last Updated: 02 August 2025
Hits: 3399
  • Book revew

Since Fading importance and the utility of lists, I decided to re-read the Checklist Manifesto by Atwal Gawande, and while checklists are not exactly the same thing as jotting down various observations and happenings, they do both share a commonality, after all its in the name. 

I'm intrigued by the utility of lists mostly for their cognitive and psychological benefits, as I have previously described, and checklists help in this respect to, however, they also provide a rigorous means to enforce quality through consistency, particularly when following or responding to the need for a sequence of necessary actions to be taken.

What is clear is that the quality of simple solutions can be improved by reducing the flaws inherent in remembering the minimum necessary steps through this externalization, i.e by using checklists to combat the distractions that can lead to these flaws. By externalizing necessary information into checklists, the enforcement of thoroughness is also ensured. 

These flaws that we seem to have, appear to be centred around the difficulty in being always disciplined, always detailed and paying attention - forgetfulness, distractions and boredom are human nature. 

An interesting distinction made in the book is what constitutes types of complexity that cause us to have difficulty in maintaining the level of discipline and thoroughness required when interpreting them. 'Complicated' problems or solutions are deemed to be repeatable, i.e once they are defined, they do not fundamentally vary and are often built upon simpler well-defined problems. They may however manifest in varying circumstances however, but essentially they are based on well-defined principles. Complicated problems are complicated because they require the management of many well-defined ideas in new and novel ways. Building a robot that can skip or juggle, is complicated, and so are various math problems. They vary, but they are all well-defined never-the-less.

'Complex' problems or solutions however are unique and individualized and cannot be repeated verbatim and require improvisation and experience to deal with. The example given in the book is that of raising children, no one child is the same as another and the complexity of an individual scenario is specific to that individual. I guess some examples would include overcoming one's own fears or reasoning about the unknown, possibly even devising a strategy to run faster, despite having been involved in a running accident. Overcoming and devising a strategy that's variable and specific to you, is not likely repeatable and general enough for others. If it is, then it is likely more in the realm of being a 'complicated' problem. This was quite interesting.

The coordination of seemingly large complicated work, correctly applied can be found in the execution and coordination of checklists at the basis of such work, to provide the core discipline required to manage and verify that the work is carried out thoroughly and without missing vital components required for producing quality, consistent results.

It appears that when checklists are used to ensure consistency and rigour, they improve quality. 

In these complicated work scenarios, an approach that seems to yield success is the stacking up of checklists upon checklists that define the execution of a series of fields of disciplines or work, that are then used to bring together a final aggregate or composite result - much like the building industry is composed of structural engineering, safety, building, design, materials etc. Put all these fields together using checklists to ensure they are rigorous in their quality and execution appears to help produce a coherent outcome in the face of multiple fields of combined complexities. However, it also appears that there are usually occasions, perhaps inevitably, where conflicts result, despite each field being rigorous and producing quality isolated results.

Modelling these situations and testing can be useful in reviewing conflicts. More interesting is that communication about the conflicts is presented as the means by which problems that inevitably result, are resolved through expert collaboration of the various fields. The example in the book is that of a 'submittal schedule' which upon detecting conflicts (by modelling the combination of incoming fields of work), coordinates which experts from the various fields that are part of the resulting conflict need to discuss the reasons and the possible resolutions in order to move forward with the next piece of scheduled work.

This collaboration in the face of complexity is an essential idea because it allows problems to be offloaded to various minds that can come up with a resolution. In A software engineering process for delivering software, I spoke about the burden that individuals have to solve problems, which are relieved by the spreading out of the problem across experts. Indeed, it appears that this is how many complicated processes that is engineered today are being rationalized in the face of complexity. The construction industry is one case in point. Possibly there is the application of these ideas in both Medicine and Software Engineering. 

In summary, the humble checklist provides a means to:

  • simplify complicated situations by ensuring necessary but crucial and critical steps are not missed or not considered.
  • combat human cognitive flaws such as forgetfulness, distraction, boredom and lack of discipline
  • enforce rigour and thoroughness, thereby improving quality and consistency
  • allows seeing problems/conflicts as you design checklists to address them
  • ensure work is applied correctly

There are some other interesting ideas that pertain to the utility of checklists too. Spreading the complexity of discovered problems (when combining checklists with submittal schedules) reduces the burden that individual has to make correct judgements and avoids mistakes in any one individual judgement when coming up with new solutions. This shows that collaboration is key in dealing with complexity.

Another important message is that measuring progress is important and setting a unified goal among many and then allowing multiple individuals to act autonomously to bring about achieving this goal, spreads the cognitive load and empowers people to do what they feel they can, i.e bring their own individualized expertise to the problem. 

So while individual autonomy is important, having it within a group of like minded-goal-oriented experts, is likely to reduce the cognitive load on any one individual. Embracing a culture of teamwork and discipline is also likely to produce quality results including increased communication and it is vital to clear any confusion throughout the team, regardless of how long it takes. 

Furthermore, checklists can be seen as an instrument that makes reliable management of complexity a routine exercise.  The complexity that is routinely managed is arguably simplified. 

A useful and effective mechanism is a change-of-behaviour delivery vehicle. This was shown in the distribution of soap in India in combination with a checklist that describes the minimal necessary steps to wash effectively. Making people like the product such that they prefer to use it, can very much help your cause, particularly if it's related to your cause. This is vital perhaps in establishing effective and useful research outcomes, for example.

Anything that makes something systematic improves its rigour and quality. Checklists are an example of this idea, but they are also a useful means to make priorities clear and explicit.  

When constructing a checklist, it should be brief and focus only on the 'killer items' in such a way that if the item was removed, it might be as critical as potentially killing someone - in relation to the criticality of the subject matter that the checklist pertains to. In this way, is recommended that they be between 5 to 9 items and hold only the minimum necessary but critical items. Detail is not required, fundamental, broad, non-difficult but killer items are, and these are often obvious but deviously elusive at times - and this is what makes checklists difficult to construct or appreciate but these are what make checklists effective, not only in emergencies or under dire distractions but when human senses are dulled perhaps by boredom etc.

Equally important is that the difficult concepts aren't usually good candidates for inclusion in a checklist, but more often it is the simpler, fundamental ideas that cannot be skipped that are. The difficult or hard things, or indeed the detailed things are likely to be what is expected by the expert to deal with or improvise at the time it occurs. In this way, unlikely, variable or non-consistent items should be considered as likely adding more items that are strictly necessary for the checklist. 

Another interesting concept is that simulation provides the needed practical testing for checklists, as checklists are expected to evolve over time and require frequent revisits and tuning. In testing a checklist, the effectiveness needs to be measured, such as asking or determining what will constitute a failure, for which the checklist is trying to reduce/prevent. This can help tailor the checklist when evaluating its performance against this measure.

General or the genericity of checklist items are favoured over specific, variable and ambiguous items. 

Checklists are likely useful in situations where 'process' is largely inconsistent, likely due to routine improvisation by experts. This is arguable a burden to experts and can be what they might perceive as negative to experts who feel it diminishes their utility to assess and deal with circumstances as they arise - i.e it affects their ego.  

Equally, adding a checklist to facilitate one's own expertise and experience is likely to be useful, however, one needs to overcome the idea that checklists are uninteresting, obvious and boring and more importantly impinge on our sense of capability and ego to require them. However, checklists are a tool to enforce quality, consistence and discipline - they do not provide experience or improvisation as experts do.

 

 

 

 

 

 

 

Differential Calculus

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
14.Apr
14 April 2022
Last Updated: 16 April 2022
Hits: 3299
  • Math

I've been studying how exactly Differential Calculus works by reading Mathematics: Its Content, methods and meaning.

The derivative provides a comparative indication of the rate of change at a particular point on a function on a non-linear function/graph. I find it helpful to think of the derivative as a property of change, i.e it quantifies a change so it can be compared with change occurring at another point of the function/graph.

The derivative is normally classified as instantaneous velocity when the graph is of distance with respect to time, i.e velocity is the derivative of distance with respect to time (\(v = s'(t) \)). The wording is sometimes confusing here. If velocity is the derivative of distance with respect to time, this is indicating that the distance is the measurement that is changing over time, i.e with respect to time. I suspect that the where this idea becomes generic is when the derivative can be defined using other independent variables (related of course) to measure the change of a magnitude with respect to another independent variable, which need not be time, as required for the velocity.

The derivative is the ratio of the difference of a function values at both ends of its domain, and the length of the that domain, and tends towards a value as the length of the domain shortens.

The derivative can be used to determine the differential of a function, which in turn can be used to estimate the increment of a function. I suspect that the differential and the increment are actually the same, however, there is a question of whether the differential calculation includes the infinitive term or not. If it does, then it's truly equal to the increment, if not, then it's only an approximation.

For example, \(\Delta y \approx f'(x)\Delta x\) while the increment is \(\Delta y\) as the infinitive term is not included, but when included accurately describes the increment of the function, ie \(\Delta y = f'(x) \Delta x + \alpha \Delta x\). Either way, the function differential helps determine functions that can be used to describe/define a natural phenomenon based on observed measurements represented as a graph (Differential equations). This in my mind is probably the most important application of differential calculus, because the applications are so diverse - you can mathematically model a phenomenon based on observations. 

The definition of the diffirential (of a funtion) is a finite magnitude for each increment of \(\Delta x\) and is at the same time proportional to \(\Delta x\). 

\(\Delta y = f'(x) \Delta x + \alpha x \)

So this essentially means that "a small increment of the function is equal to the differential of the function", meaning proportionate change in the function for the proportional change in x is the differential. The derivative is used to approximate the increment of a function: \(f'(x) \Delta x\)

The increment of the function or approximation of it (given by the diffirential) is useful at it provides the next value of the function given the change in the independant variable.. 

Orders of derivatives can be used in a polynomial to estimate/approximate/emulate a function when the derivatives of the function are known (Taylors formula/series). This is interesting because putting a function's derivatives into a polynomial can simulate that function, most accurately around the derivative, i.e where the change in x is the smallest. As the change in x grows larger, the Taylor series produces less accurate or more variance of the function produced, which then starts to deviate from the original function, ie the emulation becomes less correct. It appears from the theory that the higher the order of derivatives the more accurate this emulation. What this essentially allows us to do is approximate a function by using a polynomial expression.

The laws of nature, as a rule, can be expressed with good approximation by functions that may be diffirentiated as often as we like and that in turn may be approximated by polynomials, the degree of which determines the greater the accuracy.

The derivative is defined as the limit approached by the ratio of the change (distance/delta) of y to the change (distance/delta) of x, specifically as the change in x moves towards zero. Specifically, \(\lim\limits_{x \to 0} \frac{\Delta y}{\Delta x}\). For a while, I confused the notion that the derivative is somehow related to the ratio of the output of the function at a specific point and the input at that point. This is not correct as the derivative is specifically a ratio of the distance between two values of a function/curve (not the values themselves), to the distance or variance of the corresponding input values, which when taken to their limits, in no way relate directly to the value of the function at the derivative point, the derivative is itself unique indication of change, not function value.  

The derivative is derived from the result of the tan of the angle of inclination, where the change in y (distance) is the opposite side of a right-angled triangle and the change in x is the adjacent side of that triangle. The hypotenuse is the secant line that joins two points on the same function/graph and which becomes the tangent line as the change in x tends towards 0. This is how the derivative is actually defined and calculated, it is the definition of the tan of an angle, or more specifically and simply, the \(\frac{opposite}{adjacent}\) and this value/derivative changes as the change in x or the adjacent side becomes vanishingly small, which produces a vanishingly small \(\Delta x\) and correspondingly vanishingly small \(\Delta y\) or \(opposite\) side of the triangle. This reaffirms that the distances between the y-values and x-values are being considered and not the actual y-values and x-values themselves.

The mean-value theorem of Lagrange's formula allows one to calculate the exact increment of the function (not an approximation). More specifically and usefully it allows the exact determination of the actual value of any limit expression (which is impressive). Here a limit such as \(\lim\limits_{x \to 0} \frac{\phi '(x)}{\varphi '(x)} \) can be exactly defined to be \( \frac{\phi '(\varepsilon)}{\varphi '(\varepsilon)}\), meaning there exists a specific derivative at \(\varepsilon\) (on the same graph of as the function describing the limit) which is equal to the increment of the function exactly. Specifically between the ends of the range of the function. i.e \(\phi(b) - \varphi(a) = \phi '(\varepsilon)\) where the domain is (a, b), such that \( \frac{\phi(b) - \phi(0)}{\varphi(b) - \varphi(0)} = \frac{\phi `(\varepsilon)}{\varphi '(\varepsilon)}\)

The derivative is a limit, which hasn't got a defined value as the change in x is always tending towards zero and can do so indefinitively. Only when the change in x is factored out, can the derivative have a defined value. Every time you reduce the \(\Delta x\) within the difference equation, (\(\lim\limits_{x \to 0} \frac{f(x_0+ \Delta x) - f(x_0)}{\Delta x}\)), the derivative gets a different value, in most cases this becomes larger as the \(\Delta x\) decreases. As \(\lim\limits_{\Delta x \to 0}\) cannot ever be defined(there is always an ever-decreasing \(\Delta\)), the result of this expression or derivative is ever-changing.

The derivative can be depicted as \(f', f'(x)\), \(f^n(x)\), \(\lim\limits_{x \to 0} \frac{\Delta x}{\Delta y}\), \(\frac{\delta y}{\delta x}\) and \(\lim\limits_{x \to 0} \frac{f(x_0+ \Delta x) - f(x_0)}{\Delta x}\) where \(x_0\) is the initial point of the domain of the curve/function in question, and \(x_0 + \Delta x\) is the subsequent point on the domain of the same function. The distance between these two points is the \(\Delta y\)

The value of the derivative can indicate that the change that is occurring at a particular point in a non-linear function is either a) increasing, b) decreasing c) not changing. This can be used to determine the minima and maxima of that function. This is helpful and can be used to determine when, ie what input value i.e x will result in the largest, smallest value of the function. This is useful.

In calculating the derivative, the tangent can be defined because the derivative and the tangent are actually the same things, one is geometric and one is algebraic. To calculate the derivative requires establishing the relationship between the two secant points on the graph and manipulating the calculated relationship (\(\tan \alpha = \lim\limits_{x \to 0} \frac{opposite}{adjacent} \) or exactly the same is \(\tan \alpha \frac{\Delta y}{\Delta x}\)) by reducing the distance between them to such an extent (limit), that the geometric secant becomes a tangent and that limiting manipulation calculation becomes the derivative.

While the derivative is defined as \(\frac{\delta y}{\delta x}\) which is a limit more easily identifiable in this representation: \(\lim\limits_{\delta x \to 0} \frac{\Delta y}{\Delta x}\), these deltas are always decreasing as \(x \to 0\) but often the change in x is factored out of the difference equation (\(\lim\limits_{x \to 0} \frac{f(x_0+ \Delta x) - f(x_0)}{\Delta x}\)) by assuming x=0, this allows a definite value to be calculated. This is usually done by when using calulus 'first principles', i.e substitute the function you want to differentiate into the difference equation, ie (\(\lim\limits_{x \to 0} \frac{f(x_0+ \Delta x) - f(x_0)}{\Delta x}\))) to determine the derivative of any particular function. Rules have emerged when certain functions that are differentiated this way, leading to shortcuts which means that first principle calculation can be forgone by using the rules which result in the same result. These include the chain rule, product rule, and quotient rule etc.

The derivative is also interpreted as the slope of a non-linear function, in the same way that the slope is defined in a linear function, i.e for a linear function, the slope is defined as \(m = \frac{\Delta y}{\Delta x}\) and this is very similar to how the slope is defined in a non-linear function, however it is defined as a limit of this expression: \(\lim\limits_{\Delta x \to 0} \frac{\Delta y}{\Delta x}\).  

I've found some quotes to be especially helpful when studying calculus:

Wikipedia says: 

The slope of the tangent line is equal to the derivative of the funtion at the point the tangent line touches the graph.

The derivative measures the sensitiveity of change of the function value (y) with respect to the change in its argument (x)

Another informative quote from Mathematics: Its Content, methods and meaning is:

The derivative of a function \(y = f(x)\) of a variable x is a measure of the rate at which the value y of the funtion changes with respect to the chane of the variable x.

It is called the derivative of \(f\) with respect to \(x\). The derivative is the slope of the graph at each point in the graph.

For a function \(y = f(x)\), a small chane in \(x\), i.e \(\Delta x\) causes a change in y, i.e \(\Delta y\),

where: \(\Delta y = f(x_0 + \Delta x) - f(x_0)\) and \(\frac {\Delta y}{\Delta x} = f(x_0 + \Delta x) - f(x_0) x \frac{1}{\Delta x}\)

 Of differentiation, this is succinctly put:

The process of obtaining the derivative of a function by considering small changes in the function and in the independant variable, and finding the limiting value of the ratio of such changes.

 

Fading importance and the utility of lists

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
29.Dec
29 December 2021
Last Updated: 29 December 2021
Hits: 3476
  • Random
  • Impressions

I've become increasingly comforted by writing lists down. This might not seem unusual, but it's not something I used to do, so it is unusual for me. 

Each working day, I write out a list that outlines what I've done in the day, not what I'm planning to do, but what I've done throughout the day, almost like a timesheet. It's not as granular as a timesheet as it's not an hour-by-hour account but merely a casual outline of what's been done in the day.

For example, I write down what progress I've made in some certain task, specifically for example, what its current status is, what's left to do and if there is anything of interesting about it, such as any observed obstacles etc.

Ultimately, I'm left with a trail of bullet points that outline my activities.

There are a few reasons why I do this, but the first is that I need to report on my progress back to my team on a daily basis. I tend to do a lot of research and investigation-type work, where outcomes and the rationale need to be documented so that I can accurately inform my team about what I've found. If I write it down, I won't forget. If I don't forget, I've got more to discuss, and ultimately having more useful information to discuss means the discussions are more meaningful when I have them. So that's the first reason. 

As a side note, I have found that people are very much interested in what happened during my activities, i.e why I did what I did, what the issues were etc. I think this is probably true of any team, but something I didn't realise until recently.

Interestingly, I am usually less interested in what happened and more interested and what the result is/was. I'm not embarrassed to say, that I've learnt that people like to know what happened along the way, they are actually interested in the nuances that otherwise I'm not. I think this is an important aspect of social communication, particularly within teams that share a common discipline such as Software Engineering. Making list allows easy recall of these types of nuances that occur during the day.

It also turns out to be a useful way to account for when things go wrong, but it's certainly not primarily used for that. For example, if I need to develop a feature within an estimated time frame, say of 3 days, then anything that occurs during this time which makes achieving that less possible, must be raised immediately. Having a trail of rationale is useful to remind others (and myself) that certain things cannot be done due to entirely reasonable but unforeseen circumstances, however, if these are not reported, it will appear to indicate that you've been unable to achieve the requirement of your work, i.e that you're lacking, which is not the case in these circumstances. So that's the second reason.

As another side note: me being able to discuss obstacles or significant events that occurred during an activity, which may impede my task delivery is important, not only because it provides feedback to my team and helps reset expectations, but most importantly, it informs them about empirical circumstances of the world around me, and this brings in new information. All this information is gold because it provides context and situational awareness. Sure, it justifies not only my position (I've documented the rationale and outcomes) but provides a wealth of circumstantial evidence of the actual world around me, information that was not known during planning. This is what my team finds so very interesting, and perhaps quite rightly, i.e having more information about things they did not know before. Obstacles and nuances are such sources of delightful information.

Typically, I find obstacles all the time and they never seem significant to me because I always have them. I am so used to obstacles that they are normal and my default reaction is to circumvent the obstacle and move on. I basically discount obstacles, they are not important to me. However, in light of what I've just said about what they bring in terms of informing the wider community about the actual world around you, they are indispensable. So, the trick with writing lists down, is I can use them to inform my team of the world as it's happening around me (or to me). So, that's the third reason.

The thing about obstacles is I know they will inevitably vanish as I deal with them, so remembering obstacles, reporting on the details and informing my team about them, for me, is challenging, but is increasingly insightful to the team and recently has become incredibly insightful to me too. This is not because I find obstacles interesting (I still don't), but because they remind me how far I've come in whatever it is that I was doing. This is an important psychological feedback mechanism and makes writing lists become more than reporting to the community but reporting to yourself. So, that's the fourth reason.

With a little bit of reflection, what I have found, is that generally for me, with time (even after a few minutes after completing an activity), the degree of perceived utility or usefulness of that activity diminishes significantly. What this means is, at the end of the day I feel less productive, as the sum of diminishing utility is well, diminished utility. From a personal and psychological standpoint, this realisation is significant. Using lists provides a feedback mechanism that helps assure me that I have made progress, and that my efforts have been significant and that they are useful and important. Otherwise, this seemingly fading sense of importance can leave me feeling... unaccomplished and annoyed with my progress.

So, it brings me great comfort in recalling what I've done. 

I also wonder about other aspects that might contribute to why making lists is so comforting to me. For example, it's well known that externalising thinking through note-taking relives the cognitive load on your memory, and I think that knowing that I don't have to remember something, but that there is still an artefact that represents that something, also comforts me. 

I think this is the fifth reason.

 

 

More Articles …

  1. Abstractions and Patterns
  2. Mind Maps
  3. ISO27001, Machine-Learning and Game dev
  4. Design Patterns: Representation, Transmission and Dependencies
  5. Sufficiently Complex
  6. Deadlocks and databases
  7. Enterprise System Integration
  8. In the meanwhile
  9. Try Monad, Progress and Lockdown Rules
  10. Agile and Model Driven Development
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

Page 15 of 182