This is an examination of conscience (of sorts). I have rejected the idea that people can be busy (much as it is a badge of honor to claim as much), but more of stressed/surprised/over-scheduled/etc. I question if there is a linear limit to an individual’s output and if there are ways that this can be increased. I touch on strategies that can virtually make this limitless and even reduce the human toll.
In this recording is a review of my current web hosting architecture as I see it after several months of active use. Specifically, I cover the shortcomings of the current setup, ways around each one and advantages of each alternative. This post mainly sets the stage for future updates or posts…
- What are the core needs?
- Review of my current setup and available alternatives
- Discussion of the advantages and disadvantages of each option
- Next steps
Membership in any one of the social media platforms has its benefits; that are seldom longterm. By definition, these platforms come and go. In the next 17 minutes of audio, I will cover the following points as I set context for my decision to leave social media (not that I was that invested). I am instead focusing on establishing and maintaining a robust internet presence.
NB: The audio-levels are much higher/better in this post.
- Briefly explain the Internet of past and the built-in autonomy of publishing
- Contrast with the walled-garden idea that characterizes: BBS, AOL, FB, LinkedIn, Twitter, etc using the controlled model
- Tying your fate to that of the walled-garden that you live in VS
- Leaving an alias that enables others to find you regardless of what garden or personal island you move to
- Walled safety AND house-rules that stifle unique authenticity (sandboxes have rules/censorship)
I like having machines (and any system) that has a predictable input and output. Dishwashers are the machines that have thus far not given me dependable results. I know that a laundry machine will not scrub collars; and it lives to that performance standard every time. I am working researching how to get consistent value from my dishwasher – this is a review of the process.
Please note that the audio level is lower – I am working on a way to standardize it going forward.
- Effectiveness as defined by the ISO-9000 (extent to which planed activities/results are achieved to the planned level)
- Baseline of a dishwasher as an energy inefficient rinsing machine
- Inconsistent washing of dishes based on positioning and level of soaking
- Inability to keep dishes stacked for the whole day
– Consistent quality and results that presents MVP value to justify the wait and cost
– Disruption caused by fluctuations and unplanned cost of corrections to meet minimum expectations
– Establishment/standardization of pre-work that can get the inputs to a level that can assure the desired outputs and justify the costs (delay, value-add, time savings)
This topic is way bigger than any few-minutes could cover – in fact, human beings have spent a good part of the known past trying to do more and better.
My focus here is about the appearance of productivity, really getting important things done, and doing so with minimal mental weight (stress).
Beginning with a pedestrian item (a loaf of bread), I examine the process that is necessary to produce consistent results and eliminate variability by understanding the inputs for predictable output. I then touch on how this is echoed in GTD, iProcrastinate (Tim Pychyl), and Agile project management. The common theme across all the above is the definition of the desired result, and the break-down of the seemingly complex result into constituent steps that in themselves have little variability. It is a combination of a production-line and a chemistry experiment to produce tasty stuff.
Being that it is repeatable and can be progressively improved upon, it allows for limited experimentation by tweaking selective variables and measuring the output.
1000 hour goal! What is it, and what am I doing?
This should have been the very first post, but it makes more sense to first get the activity going in order to have some retrospect. I am providing context on what I am doing by creating these daily posts on various topics. The activity itself is a lesson and a meta-goal and a building-block for a bigger project. The above is a relatively short post that explains my motivation and purpose for these posts.
In this post, I talk about my review and optimization of the ironing process (or chore). The connotation of the word chore says it all: it is an oft unlikable process that is done just because it has to be, not out of pleasure. Similar to many other processes, I enjoy ironing if the process is efficient and optimized.
- Core requirements for the task of ironing (why do we even need to iron – clarify that)
- Previous experience
- Requirements for the new iron
- Current experience
- Generalizing the principle of process improvement