--- /dev/null
+---
+postid: 000
+title: TMSR work: interlude and plan for July
+date: July 1, 2019
+author: Lucian Mogoșanu
+tags: tmsr, cogitatio
+---
+
+Following recent discussion in [the forum][btcbase], as well as my own
+recent (spectacular) failure to report, let alone deliver, on [yet
+ongoing work][ii], in this post I'm reflecting on what's going on in
+spykedlands and proposing to take the bull by its horns from a
+different angle and in a different way, with the aim of doing stuff
+more efficiently.
+
+Long story short: on June the 22nd, Mircea Popescu observes a [marked
+silence][btcbase-1919157] among the Lordship, including yours
+truly. This is followed by [short reports][btcbase-1919195] and
+[further discussion][btcbase-1919627] on the matter, including the
+problem of [allocation priority][btcbase-1919411] for existing things
+on the to-do list. This is when it first becomes clear to me that my
+[previous][ii] reporting style hasn't quite been working[^1] and that
+I need to change something, although I'm not yet sure what or how.
+
+Then the latest [S.NSA report][snsa-q2-2019] comes,
+and... [well][btcbase-1920853], read the whole discussion and draw
+your own comments, thoughts and conclusions from it.
+
+As for my own thoughts: I happen to be in a situation somewhat similar
+to Stan's, so I understand the man's trouble. In theory it's easy to
+say "next week I'll allocate X hours out of a total of Y [of which Y-X
+are already allocated to work putting bread on the table] for
+completing item I", until in practice, occasionally, surprisingly and
+in the last moment, your favourite saeculum overlord decides to
+sabotage you and drive Y up so that X becomes close to zero. What's
+more, having both X and Y time there leads to context switching
+overhead and the reporting component on X is itself costly[^2], which
+then spills into personal life and leads to lack of sleep, leading the
+untrained minds among them to a nasty burnout. But sure, complaining
+about it won't be of any help and getting into [that fucking
+hustle][btcbase-1921027] is not an option, da' viața-i grea și nu toți
+poate, or how did the saying go.
+
+So since I suppose properly managing my time is but the first
+[necessary][btcbase-1921168] step in the great process of growing my
+own legs, let's see how to tackle this issue. For one, it's worth
+stating upfront that my [to-do list][ii] as well as my priorities are
+consultative and not set in stone, and no, I'm not in a marriage with
+Hunchentoot [and whatnot][btcbase-1919411] and I can move up and down
+the stream as the more pressing needs dictate. For now, as per
+previous discussion, I'll assume people still need a working CL-based
+WWW stack and work on that.
+
+As for the other, my previous reporting style of giving approximate
+time intervals for large tasks is an utter failure, so I'll need to
+spend more time breaking everything into small pieces and report as
+often as possible on what I've found. More concretely, I'm aiming for
+monthly planning reports such as this one (minus the lengthy intro),
+plus weekly or at worst bi-monthly reports on the things that I'm
+working on. For now I'm resolving to do a planning report at the
+beginning of each month (though this may change depending on whether
+planning itself becomes a lengthy task, such as in the case of
+Hunchentoot this June) while the weekly reports are set out to be:
+
+* Week **27**: I will publish a [cross-referenced][btcbase-1919634]
+ version of the Hunchentoot coad, for subsequent use.
+* Week **28**: I will be away from the workbench, but will be following
+ the logs closely and I'll be available for emergency situations,
+ e.g. Feedbot maintenance.
+* Week **29**: I will publish an architecture of Hunchentoot, with
+ comments of each component and the interworking between the parts.
+* Weeks **30**, **31** and onwards: I will publish detailed write-ups
+ on Hunchentoot components, to be further discussed in week 29.
+
+[^1]: Although I'll say, it has been quite a useful exercise in
+ putting in perspective the gigantic amount of work to be
+ done. Sure, some of the items are of lower priority while others
+ (e.g. studying FFA) won't necessarily yield any immediate
+ products; even so, they're all immensely important in the medium
+ to long term and there's absolutely no way around doing them.
+
+[^2]: Yeah, I know, my posts are too damn long, but I'm afraid that
+ the ongoing exercise of being more succint brings that X further
+ up.
+
+ I could have just said "here, I'm changing my planning schedule
+ from this to that" to be done with it, but then the reader would
+ have had little to no context of where I'm coming from, my thought
+ process and so on. Heck, I had no context of it until yesterday,
+ and it's only becoming clearer as I'm writing it.
+
+[btcbase]: http://btcbase.org/log/
+[ii]: /posts/y05/090-tmsr-work-ii.html
+[btcbase-1919157]: http://btcbase.org/log/2019-06-22#1919157
+[btcbase-1919195]: http://btcbase.org/log/2019-06-22#1919195
+[btcbase-1919627]: http://btcbase.org/log/2019-06-23#1919627
+[btcbase-1919411]: http://btcbase.org/log/2019-06-22#1919411
+[hunchentoot-i]: /posts/y05/093-hunchentoot-i.html#selection-183.0-191.93
+[snsa-q2-2019]: http://trilema.com/2019/no-such-labs-snsa-statement-on-q2-2019/
+[btcbase-1920853]: http://btcbase.org/log/2019-06-30#1920853
+[btcbase-1921027]: http://btcbase.org/log/2019-06-30#1921027
+[btcbase-1921168]: http://btcbase.org/log/2019-07-01#1921168
+[btcbase-1919634]: http://btcbase.org/log/2019-06-23#1919634
projects / thetarpit.git / commitdiff