From: Lucian Mogosanu Date: Thu, 1 Aug 2019 13:33:32 +0000 (+0300) Subject: Add tmsr-work-iv draft X-Git-Tag: v0.11~19 X-Git-Url: https://git.mogosanu.ro/?a=commitdiff_plain;h=2513a0d09a65bca27217d94adb20c7caba268e1c;p=thetarpit.git Add tmsr-work-iv draft --- diff --git a/drafts/000-tmsr-work-iv.markdown b/drafts/000-tmsr-work-iv.markdown new file mode 100644 index 0000000..3cd11fc --- /dev/null +++ b/drafts/000-tmsr-work-iv.markdown @@ -0,0 +1,105 @@ +--- +postid: 000 +title: TMSR work: plan for 2019 M8 +date: August 4, 2019 +author: Lucian Mogoșanu +tags: tmsr +--- + +July started with a committment to [a plan][tmsr-2019-m7] and +continued with work on [CL WWWism][cl-www]: a [CL-WHO +demo][cl-who-demo], an overview of Hunchentoot's +[architecture][hunchentoot-ii], a schema and a [demo][hunchentoot-iii] +of the same and a [review][hunchentoot-iv] of one of its main +components. Not that bad[^1], is it? + +An observation would be that I've been completely neglecting +documenting [other][maramures] (more or less important) things in +favour of my technical work; and as that string of events I've +experienced and places I've seen goes further into the past, my mind +keeps [distorting and forgetting][btcbase-1925098]. Which means that +if I don't do this ASAP, I might as well screw it... which I won't, +because I'm stubborn like that. + +Thus, August is set to look along the lines of: + +* Week **32**: I will document[^2] my July travels and, if time + permits, I will wipe the dust off some of my other draft posts. +* Week **33**: I will review Hunchentoot taskmasters. +* Week **34**: I will review Hunchentoot requests and replies. +* Week **35**: I will review and demo some (hopefully really cool) + Hunchentoot request dispatchers. + +This covers about all of Hunchentoot, with the exception of: +headers.lisp, compat.lisp, specials.lisp, util.lisp, set-timeouts.lisp +and mime-types.lisp; some of these I've already covered as appendixes +of the main text, some *might* need special treatment, I'm not sure +yet. + +Otherwise my estimates are hopefully decent and this work won't spill +into September; on the other hand, if I knew exactly how long this was +going to take, it means that I would have known the code well enough +to just document it without putting all the hours into (re)reading, +which is the main time-eater at the moment. Also, *ideally* each of +these reviews should also come with a demo, but as +[acceptors][hunchentoot-iv] demonstrate, sometimes the triteness is +inherent in this type of documentation. + +For the lack of a better place, I'm going to leave here a discussion +regarding medium and long term work: + +* Since Hunchentoot will eventually [have to][mp-on-geneses] encompass + *all* of its dependencies, this puts into light the problem of + upstream requirements, firstly and foremostly a [Common Lisp + implementation][btcbase-1925448]. Since this is new territory to me, + it's hard to say how long it's going to take, but either way, the + "no CL without working CLtron" point sticks. +* Ave1 [remarks][ave1] the lack of Common Lisp learning + material. Jurov [recommends][btcbase-1925632] [CLTL2][cltl2], while + Stan [mentions][ave1-alf] one of Graham's older books. The way I see + it, the problem's not *Common* Lisp per se, but the fact that + there's very little text out there explaining Lisp (in general) from + first principles, which makes me seriously think that I should take + the first Lisp texts and transcribe and annotate them. This would + probably take at least a month, but I don't think it's a waste of my + time to take McCarthy's Lisp 1.5 Programmer's Manual[^3] and arrange + it in blog format. + +And then there's all that filling [the list][tmsr-work-ii], guess I'll +get back to it in September or so. + +[^1]: Just for the record, writing one of those large posts takes me + anywhere between one and five days of full-time work. I shudder + thinking at how this planning's going to hold when saeculum + decides to hit me out of nowhere. + + We'll cross that bridge when we get to it, I guess. + +[^2]: Sifting through the photos should take about an hour; processing + them another one to three, depending on the photos -- working on + DSLR raws is not a mechanical process, mkay? Then writing the + whole thing up and proofreading will take me another circa two + hours, which brings this to 4-6 hours total. + + This then should give me some time at the end of the week to + reload some Hunchentoot in my head and carry on with what comes + next. + +[^3]: No, I won't link the fucking pdf, it wholly beats the purpose of + what I'm discussing. + +[tmsr-2019-m7]: /posts/y05/094-tmsr-work-iii.html +[cl-www]: /posts/y06/097-hunchentoot-iii.html +[cl-who-demo]: /posts/y05/095-cl-who-ii.html +[hunchentoot-ii]: /posts/y05/096-hunchentoot-ii.html +[hunchentoot-iii]: /posts/y06/097-hunchentoot-iii.html +[hunchentoot-iv]: TODO +[maramures]: /posts/y05/094-tmsr-work-iii.html#selection-139.37-139.70 +[btcbase-1925098]: http://btcbase.org/log/2019-07-27#1925098 +[mp-on-geneses]: /posts/y06/097-hunchentoot-iii.html#comment2 +[btcbase-1925448]: http://btcbase.org/log/2019-07-29#1925448 +[ave1]: http://ave1.org/2019/lisp-documenting-my-encounter-with-step-2/#comment-238 +[btcbase-1925632]: http://btcbase.org/log/2019-07-30#1925632 +[cltl2]: https://www.cs.cmu.edu/Groups/AI/html/cltl/cltl2.html +[ave1-alf]: http://ave1.org/2019/lisp-documenting-my-encounter-with-step-2/#comment-244 +[tmsr-work-ii]: /posts/y05/090-tmsr-work-ii.html