Sharing some learnings I found, find, and will discover in the exciting world of formal languages, python, OSes, gnu/linux, ubuntu, webdev, and command-line interface.
I’ve been a computer scientist since 1996 and have been off and on (and full-fledged the past year) autodidactically learning about all the content of this blog/book/site and more.
Check the categories. I do a variety of posts on the designated categories, often more in one category for a certain time.
The categories are:
The purpose of this blog (sort of online how-to tutorial book in a sense) is:
- to be “out” with my geekiness. I’m “out” with my atheism and this is solidifying being “out” with my geekiness. The word “out” in this sense is usually reserved for sexual orientation (an exclusive limitation I find preposterous especially because the entire concept of sexual orientation is so ludicrous, banal, and irrelevant to my focus and life).
- to operate as a future reference for “how I did things” for myself
- to share learnings and help others as a highly abstract way of “giving back to the internet” after I’ve learned so much from others’ blogs, wiki pages, forums, and the like for free.
- to solidify and advance my learning (and others’ if they desire) in specific areas of tech, namely CLI, OSes, gnu/linux, python programming, and web development (all of which are separate readable categories on this blog-book-site).
I started linuxgeekoid (on a different blogging service) in 2007. Then and there I very joyfully posted some learnings and shared some breakthroughs with rudimentary/beginnger CLI on ubuntu. I had installed Feisty Fawn, was learning and loving learning CLI and wanted to share.
I realized that (mainly baby-boomers) some of my readership or people that would see linuxgeekoid likely wouldn’t have the slightest clue to what I was edifying. Fearing this, I mitigated my focus in linuxgeekoid.
However, only recently did I understand that my tech focus/investment/passion (whatever you watn to call it)in the past, present, and future has been more or less, unwavering, fulfilling, consistently joyful, helpful, and of perpetual interest. Additionally, I realized that most people that wouldn’t understand or have an interest in linuxgeekoid because of tech-unsavviness were people I wouldn’t even want to interact with nor would I want them reading my blog, in the first place! So what deterred me from writing in 2007 (fear that some people wouldn’t understand the more advanced tech learnings) is now precisely one of the most fundamental reasons fueling why I am full-fledged writing linuxgeekoid today (because it’s only for a readership with whom I actually would potentially like, tech-savvy and tech-interest people)! Granted, I dislike most people and am highly xenophobic (and have spent many long hard years discovering that the majority of people cause me pain, diminish my intelligence, and are distracting and discombobulating forces in my life), but on the rare occasion I do find a friend with like interests and such moments are AWESOME, but most friend-interactions usually involve the friend being tech-savvy (or felines)! So again, fearing being “too techy” in 2007 is precisely an implicit agenda to what I’m trying to do now, to attract the more likeable tech-savvy people and repel the un-tech-savvy folk. Jolly good.
Approach and Style
I’ve written over 28 books (5 of which are self-published and editted). I’ve written over 600 blog posts, some quite lengthy. I’m not trying to sound like an expert in writing and blogging (I am certainly not), but rather that I’ve had a lot of opportunity in the past to experiment with what I like and dislike. In the past I’ve had what I call very “bloated” blog interfaces. With a lot of flashy things, slow load times, and most annoyingly inconsistent text formatting (some posts would have headers 1 and 2 others bold, others a different font and it was rarely inconsistent). Those inconsistencies irked me greatly so I am doing away with them and writing every post in code without wysiwygs. With any special features to the blog/site, I plan to (and have begun) code myself. The result will be a much more accessible, slimmed down, elegant, faster, and more visually appealing blog-site-book.
One of the seemingly trivial (but decidely monumental) elements of writing that greatly vexed me at times was having hundreds and hundreds of font-size and font-styles from which to choose. Excessive options can often thwart productivity; one’s productivity and joy is optimized by limiting options so that only the best and optimal “choice” remains. 10 alone font-styles is a headache. That was always a barrier in productivity, choosing a font and then spending time dealing with convoluted, pre-written, excruciatingly messy CSS and html formatting generated by a horrendously sloppy html or wysiwyg app. So I’m hand-coding my posts all in the same delightful courier (and whatever template I have will make all the font-styles consistent). Having consistent and singular font-styles throughout my entire site may seem like a highly eccentrically nuanced joy, but it is a joy of simplification for me (and I eagerly aim to find those joys as a minimalist and coder).