the beginning
so begins the diary of a gnome. there's not much to write here yet; but i thought it would be nice to kick-off this blog with a small introduction, to say why i decided to set up this blog, and what my intentions are with it.
one of the inspirations for this blog is the old new thing, a publication by microsoft engineer raymond chen. it's a great blog, whose content i don't often care about, as i try avoiding touching windows development and windows machines; but it has very useful developer information written by a very experienced engineer and i remember it showing up repeatedly in various stackoverflow answers, blog posts, and other locations. sometimes not even relating to windows specifically.
gno, as an ecosystem, is just starting out. there's lots of things which currently don't have proper documentation. but writing good documentation is hard; and things are still changing so often that trying to be a perfectionist in the content is likely to eventually be wasted effort, eventually. the idea is not to use this as a way to have "documentation"; but to have a place to tell you about the questions, concepts and problems i encounter on a daily basis while doing my job as a core team engineer. a good place to publicly document them, and my answer/thoughts related to them. i decided to do it on a ghost blog because i read a bunch of blogs using newsletters; and ghost offers it out of the box. (at the time of writing, mailgun has disabled my account; but hopefully it should be ready to roll pretty soon.)
this blog post is meant to be heavily informal. what i mean by that is that: you should have low expectations on the "refinedness" of the content. think of it as me and you having a conversation, and i'm giving you a braindump about what i know about topic x. this is why i'm writing everything in lowercase. yeah, there are no capitals and i made a typo there. also that sentence doesn't make sense. tough luck. maybe i'll fix it. i've enabled comments for members, so maybe sign up if you want to be pedantic. also see the "descriptivist punctuation reform" by jan misali.
so the hope is to make information in quantity, rather than quality. our in-code and official documentation, are likely to be eventual locations for quality over quantity. but i think for today, and for another while, quantity is good. then maybe we can find a way to dump all this quantity and summarise it in a useful way.
oh yeah. and should go without saying. but opinions are my own. i don't represent the core team or my employer with what i write here. i hope that what is written here may be useful to you; but take it with a grain of salt as always, and don't take it as the Gospel of the Core Team.
by the way, this would make sense a lot to be published a gno.land realm. it'll likely be one at some point. but in the meantime i wanted to get started publishing; and besides, this'll likely serve the hub for the newsletter anyway.