From 883e31b6a20e08b0299d93b66c15d0e628cdfe6a Mon Sep 17 00:00:00 2001 From: Lucian Mogosanu Date: Mon, 5 Aug 2019 21:58:16 +0300 Subject: [PATCH] posts: 099 --- drafts/000-tmsr-work-iv.markdown | 105 ------------------------ posts/y06/099-tmsr-work-iv.markdown | 151 +++++++++++++++++++++++++++++++++++ 2 files changed, 151 insertions(+), 105 deletions(-) delete mode 100644 drafts/000-tmsr-work-iv.markdown create mode 100644 posts/y06/099-tmsr-work-iv.markdown diff --git a/drafts/000-tmsr-work-iv.markdown b/drafts/000-tmsr-work-iv.markdown deleted file mode 100644 index 3cd11fc..0000000 --- a/drafts/000-tmsr-work-iv.markdown +++ /dev/null @@ -1,105 +0,0 @@ ---- -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 diff --git a/posts/y06/099-tmsr-work-iv.markdown b/posts/y06/099-tmsr-work-iv.markdown new file mode 100644 index 0000000..ba4799a --- /dev/null +++ b/posts/y06/099-tmsr-work-iv.markdown @@ -0,0 +1,151 @@ +--- +postid: 099 +title: TMSR work: plan for 2019 M8 +date: August 5, 2019 +author: Lucian Mogoșanu +tags: tmsr +--- + +For teh posterilulz: this post was published one day late. + +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? + +August started with: [comments][ht-iv-alf-ttp-comm] on the lack of a +comment box on this here Tar Pit; [comments][ht-iv-comm2] on the +[quality][ht-iv-comm3] of Hunchentoot code; and an emergency +[halt][trilema-dark] to discussions on #trilema, caused by +[btcbase][btcbase] logbot downtime and the lack of an immediate +replacement. + +Another 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. + +All these given, the plan for the next two months (or so) will have to +suffer a few minor adjustments in priorities. In particular 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. *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. + +Before wrapping this up, let's take a look at the medium term: + +* The next Hunchentoot demo will [have to][t-g-d-130488] materialize + into a minimally-working WWW-facing logotron. As I see it, writing a + piece of software that turns database entries into HTML shouldn't be + that big of a deal, and since I'm going to maintain Lisp code, I + might as well put it to some useful work. Said logotron will run + 24/7 logging the contents of #spyked and #trilema; although to be + honest, I'm doing this with some reluctance, since I'm already going + through some of the [inherent pains][t-g-d-130541] of operating an + IRC bot with [Feedbot][feedbot]. +* I need to add a commenttron to The Tar Pit, which faces me with the + prospect of undertaking a large project, which would require + implementing e.g. a proper [anti-spam][trilema-antispam]. On the + other hand I can cut this commenttron into smaller pieces and then + implement -- and specify/document, which in my opinion makes the + exercise immensely useful -- an item that provides the full + functionality (or very close to that) on the client's side, while + automating some of my current manual comment-adding work. Eventually + this other CL-WWW demo will materialize into a genesis for The Tar + Pit, what else. + +As for the long term: + +* 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. IMHO 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. +* That [pastebin][pastebin] project might turn out to be an important + piece of Republican infrastructure, especially in light of recent + downtimes. At the very least I should replicate + [Ben][cascadianhacker]'s [paste service][p-bvulpes] and genesize the + blueprints if he isn't available to do this himself. + +And then there's that [huge list][tmsr-work-ii] that I'll have to get +back to later. For now discussion goes into [#spyked][contact] and +will be posted at [^4]. + +[^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. Yes, when, not if. + + 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. + +[^4]: No comments here yet. + +[tmsr-2019-m7]: /posts/y05/094-tmsr-work-iii.html +[cl-www]: /posts/y05/090-tmsr-work-ii.html#selection-108.0-108.17 +[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]: /posts/y06/098-hunchentoot-iv.html +[ht-iv-alf-ttp-comm]: /posts/y06/098-hunchentoot-iv.html#comment1 +[ht-iv-comm2]: /posts/y06/098-hunchentoot-iv.html#comment2 +[ht-iv-comm3]: /posts/y06/098-hunchentoot-iv.html#comment3 +[trilema-dark]: http://trilema.com/2019/trilema-goes-dark +[btcbase]: http://btcbase.org/log/ +[maramures]: /posts/y05/094-tmsr-work-iii.html#selection-139.37-139.70 +[btcbase-1925098]: http://btcbase.org/log/2019-07-27#1925098 +[t-g-d-130488]: http://trilema.com/2019/trilema-goes-dark/#comment-130488 +[t-g-d-130541]: http://trilema.com/2019/trilema-goes-dark/#comment-130541 +[feedbot]: /posts/y05/08c-feedbot-iii.html +[trilema-antispam]: http://trilema.com/2009/trilema-anti-spam/ +[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 +[pastebin]: /posts/y05/090-tmsr-work-ii.html#selection-144.0-144.5 +[cascadianhacker]: http://cascadianhacker.com/ +[p-bvulpes]: http://p.bvulpes.com/ +[tmsr-work-ii]: /posts/y05/090-tmsr-work-ii.html +[contact]: http://webchat.freenode.net/?channels=#spyked&nick=from_thetarpit -- 1.7.10.4