I created a writer page on Facebook because I wanted to be omnipresent on all services, but the value of this hasn’t been clear… while it meanwhile enabled Facebook to abuse the power of being the place everyone was.
Starting today, all my content will be on my two websites alone: technical/geek content and tech writing here, non-technical opinion and fiction writing over at http://www.jorhett.com/.
I’ll be posting a lot more content here, as I wind down my empowerment of these social networks.
One of the reasons I don’t update this site as often as I should is that I’m not sure just how useful it is to others. I want to find a way to make useful information more available. I’d really like to hear your feedback if there are channels I haven’t outlined below:
- Putting information on your own website is easy and effective, but it feels like to a branch falling deep in the forest. Only those very near will ever hear it.
- Past history has been to utilize major social media (Twitter, Facebook, etc). Unfortunately, it has been shown that centralization in the hands of commercial entities is not in the publisher or reader’s best interest.
- Most tech-oriented publications have found that FUD or shock value articles are much more effective from a profit standpoint than actual technical content.
Is there a place where I can provide value in written format to others? I’m not looking for money, just want it to be available/found. I would likely be able to send a minimum of 2 submissions a month.
Puppet Best Practices: Design Patterns for Maintainable Code
This collaboration between Chris Barbour and myself is now available for online reading at Safari Books Online
Offline versions can be found at:
I came here to let people know there will be a Puppet v5-specific update to the Learning Puppet book coming out soon. Then I realized I’d forgotten to post the last update. Oops! Well, there have been and will be quite a few updates… Read More
One problem I see often with local builds are Makefiles that use modern GNU features in common commands like
tar. If the product only runs on Linux, writing backwards compatible versions for the older BSD-based commands on Macs may not be an effective use of time.
A simple fix is to
libexec/gnubin directory to your path as documented here: Install and Use GNU Command Line Tools on macOS. However this changes your active environment, which might break scripts expecting to run on macOS. Further, this isn’t a repeatable configuration that can be safely used by others.
A better way is to explicitly configure the GNU versions to ensure they are used during the build. Read More