I don't think aimless journaling is necessarily the best thing for me; it will never be interesting to read except by my biographer. In time (= once I have more material to occupy the rest of this site) I will probably move journaling to a less visible place on the site. The nature of this digital journal is not meaningfully different than the stuff I used to write in paper journals, but I'm definitely more self-conscious about what I put up because it will be publicly viewable.
Not about the content, necessarily—I can't fathom there being anything here that's, let's say, incriminating—but the sheer inanity is just … intense. Where am I today? What am I doing? In the past, I would journal for the handwriting exercise, or as a spiritual house-clearing; this digital version is a lot more like just obligation. I can't tell if it's what I should be writing, if it's meaningful or whatever, but I know I have a long list of "more important" topics that I could reach for if I truly wanted to bust out something else.
I think there is a different kind of output I'm going to attempt: mini projects. The current one that's been on the tip of my tongue is "100 interview questions, and their answers." The concept would be more or less, find (or recollect) common interview questions, and answer them. These could then be collected on the site under an appropriate header, like my AppAcademy stuff. I've known that once I have two or more significant categories, I will be adding a navigation page to those items, and perhaps styling them to give readers a sense of locality; this is a definite example of a good one.
Another thing that I've been self-conscious about is the lack of clear technical content. Where I do talk about and allude to design, I feel that the kind of cursory reading this site will gather from (say) potential employers won't really show a that I know my shit, unless there's a clear corner for "here be code blocks." Case in point: there's a multi-line ruby code block, but it's only in maybe the second week of the AA posts? In the ensuing 80+ posts, there's no more than inline code. Does that make me a worse person? Or do I simply need to mark out a specific corner where that stuff can life now?
Regardless, writing about that stuff doesn't come naturally to me—I find that the same energies that drive my writing drive my coding, and so when I code I'm too drained/satisfied to write extensively about it, and vice versa. Furthermore, none of the stuff I "discover" while working on personal code seems particularly clever, but I know that I've benefitted from other coders' forehead slappers in the past, so I should probably get off my high horse and try to give back to the community, so to speak.
Finally, between Bear, Notes, and random and sundry other text sources, I have more than enough fodder to provide for all sort of Hot Takes™ for the indefinite future, but given how my last politics post went (mentally, not what's on the page necessarily) I worry that unless I find a way to set boundaries I'm going to get more constipated with ideas. There aren't that many truly new ideas I've had in some time, but if I don't find a way to get them out, they tend to build up in unproductive ways. One solution is wikifying, but I think I might start trying instead to view them as mini writing exercises: how can I explain the kernel of this thought in 100 (meaningful) words?
Writing long is easy; writing short and good is so hard.