the new "channels°hard word" system is complete. 🔥 the CSS°hard word is not°hard word; after wondering why several attempted fixes did nothing I found°hard word a syntax°hard word error in the CSS°hard word file°hard word. now they have all been applied°hard word and it looks bad 💡 the emphasis°hard word fix took 5 minutes
the new glasses ... i have decided°hard word on one pair°hard word. the second pair°hard word is 30% off, i am debating°hard word which (if any) I will get.
----
a project reaches a point where the "possible work" increases faster than the "valuable°hard word" work.
i could add more test files°hard word. but why? 🔥 tests are good! 💡 tests create friction against certain types of change. when those changes are bad, this is a good thing. but, if you know there will be changes, the tests simply mean you have to change more things.
----
the "quotes°hard word" system is too fragile°hard word. none of the metadata°hard word is getting populated°hard word by LLM°hard word. the metadata°hard word is also very rarely°hard word displayed°hard word.
is this worth°hard word my time?
----
💬 all computer systems expand until they are able to send email.
i still call them emails. Do I want "email to post"? Do I want "send emails to readers°hard word"? 🔥 it still seems like the wrong choice to try to convert°hard word this to a "newsletter°hard word" format°hard word
----
i could support "ISBN°hard word" tags. but that might need (or at least want) the "new parser°hard word" I talked about a few weeks ago, as°hard word an example of something the machine should be able to do, but can't°hard word.
----
those are questions for next week. and the answers will be (at least partly) based°hard word on "what other things do I have going on".