When I blog, I blog aspirationally. I previously wrote an article on my defunct Substack where I professed my love for Go, even though I wasn’t really coding in Go that much1.
And I have loads of other thoughts like that when I blog. Very much a top-down approach. And I think that’s dishonest of me. I am probably also doing myself a disservice. After all, New Year’s Resolutions don’t work and this is a lot similar similar.
Per chance I should leave aspiration to my Quest journal. | can say whatever non-sense I want over there. Here, I would like to be more helpful. Or maybe I should have a small widget as a window to my aspirations.
Anyway, writing aspirationally really bottlenecks my output and that’s no bueno. Sure, writing more about what I am doing is not that enjoyable as I am either in the middle of it, so it’s difficult to put into words, or beyond it, in which case it is boring to talk about.
It is indeed ironic to say that I will aspire not to write aspirationally but constraints are good.
- If I focus on what is, rather what could or should be, my loved languages are clearly Java and TypeScript. I rarely complain when using them and I generally find them acceptable to use. Yes, I wish Java and Node had a more Go/Bun-like tooling but it’s fine, bro, trust me, it’s fine. âŠī¸
Leave a Reply