Fluid Thinking

Blogging again, after great delay

My last published post was on October 26, 2016. That’s forever ago. A lot has happened since.

I’ve learned tremendously in the intervening 2.5 years. From these formative lessons, I’ll be publishing more on this site soon.

Among those lessons, ironically, is that one should make a habit of writing about the things they learn, fairly promptly after they have learned them. Writing is an exercise in forming thought into (hopefully) concrete language, which forces one to ponder and remember. This reinforces the neurological patterns of that learning; it’s important to actively remember at times.

Unfortunately I had set a roadblock in my own path: I was rather tired of the visual layout of my site here, and had begun work (in several failed attempts) to develop a new theme. I’ve always found the clean look of publications on Medium, but I’ve always felt leary of some of their policies. Finally, after much recent effort, I’ve crafted a new, separate Jekyll theme, specifically designed to emulate some of the feel of Medium, while publishing via GitHub pages. (Note I’m still tuning the theme a bit, based on my observations on this site.)

Therefore this post serves two purposes

It’s also come to my attention, through this process, that some of my past blogging is absolutely terrible. :thinking:

Data Model Fluidity in Analytics

The world of data, intelligence and analytics perpetually evolves, so too will the data structures we work with. With the rising popularity of data lakes, there’s a steadily increasing need for developers, consultants, and vendors to work with all kinds of data, be it structured, unstructured, or semistructured.

Continue Reading

Writing Short Blog Posts is Difficult and That's OK.

How long should my blog posts be?

I’ve got several drafts in progress right now on various topics.

It turns out it’s really hard to write short blog posts, at least on relatively technical subjects. From some quick research though, maybe that’s OK.

Neil Patel suggests that writing 3000+ words in a blog post is OK, and while shorter posts may gain some immediate popularity, longer-form content also has longer-term value, provided it’s oriented to “evergreen” topics and formats.

Joe Bunting also remarks that content should have a purpose, the goals of which should dictate the resulting format.

As a quick guideline, based on your goals,

Neil’s remarks on “evergreen” content align nicely with the goal of organic search, highlighting longer formats based on:

  • How-to Guides
  • Resource Lists + Reviews
  • Unchanging stances on industry issues
  • Frequently-asked-questions collections
  • Industry definitions

So I think I’m OK: my content tends to be fairly technical in nature, and I naturally tend to longer-form, lending to more advantage in the organic search category. I’ll continue to train myself to the thresholds above, based on content goals, when needed.

Continuous Deployment with Python Packages

Streamline your Python development with GitLab CI; automate build, test, and publication of libraries to PyPI package repositories.

Continue Reading