Skip to main content

Innocuous scraps

Nécessité fait loi. i was about to mangle Hamlet's soliloquy (slings and arrows of micromanagement?) when i found this :-)

with so many ostensibly peaceable people at war, it's easy to imagine being in a situation where killing someone might be the best option. after all, sometimes there are no good choices. whether you are willing is one question. which is better is another.

i'm sure i've been characterized as results-oriented at some point, and i certainly have broken rules. now i self identify as process-oriented, partly because i think it's possible to be both, mostly because a mindful focus on processes can lead to better results.

metrics are situational, i.e. better is in the eye of the beholder. in my kitchen, using less water is important because i wasted so much. this shift toward conservation probably began when i stopped washing my skillet; i just remove its contents as completely as i can. during the brief period when i made French toast, the trace of curry from the previous night's dinner complemented the egg (as always) and dark maple syrup.

i own several small saucepans, because buying one is a good way to evaluate a brand. unlike the Europeans, my cheap Chinese saucepan pours without dribbling, so i always boil water in it. after steeping Sideritis scardica and Helichrysum italicum in this saucepan, i leave the spent herbs to dry overnight. the innocuous scraps that remain after i lazily wipe it clean will not be noticed when i boil water for coffee the following morning. their flavor is insignificant, and the paper filter neatly captures them.

some cooking processes are more constructive. long ago, i would make split pea soup with a bone salvaged from pork cooked earlier. a bone like this can flavor a lot of soup and pea soup gradually becomes porridge, so the next step in the process was making a bastardized version of Purée Mongole by adding canned Italian tomatoes. like my French toast, i made this soup without cream or milk. my French toast was better :-)

Comments

Popular posts from this blog

Improper english

Before retirement ended my last spell of unemployment, i wondered if the timing of that dismissal was ideal. one month earlier or later might have been better? improving a server log was my last assignment. like many other companies, their senior management believed in their culture, technology, and tools. like other well-funded companies, they used Splunk and wanted to use JSON format. nobody reviewed the pull request that would have established a baseline for my work. their Splunk dashboard code was not versioned. Overcommunicating JSON can be ideal, and creating a data structure to discover if a log entry describes an error is easy and reasonably fast, but computers find strings very quickly. a faster algorithm uses less electricity; computer activity is human activity. ...

Deliberate logging

While diagnosing an error, it's not unusual to discover that the application log does not contain relevant information while also being overly verbose. DEBUG-level entries can be cryptic, and maintainers often insist that their applications emit them in production environments. the universal acceptance of low quality logs is a management failure. Holistic development a software development protocol should synergize best practices, but we should run away whenever someone claims that success depends on a protocol's complete implementation. incremental development of software is common, as is reusing large frameworks. the development process can mature similarly. Holistic Development is a protocol i should describe someday, but piecemeal presentation makes sense because partial implementation is help...

Sphinx supplement

Once upon a time, i was in a team led by a developer who was devoted to introducing modern standards. he didn't have much experience, so i think this devotion was essentially a cloaking device. though we didn't generate documentation, most pull requests elicited a request for a docstring change. my first post about Holistic Development focused on logging . this one is about generated documentation. though software developers habitually read code, generated documentation can become their primary source of information because it's easier to read. it also assures product owners that features are addressed, and that the design is orderly. Documentation review a docstring is just a comment until documentation is generated. at that point, evaluation of docstring quality should be based on the generate...