Happy reader question Friday, everyone. Today, I’ll field a question about the Developer Hegemony book. For any newer readers, I wrote this book over the last couple of years and published it to Amazon in early May. For a briefer synopsis of its purpose and message, you can check out this announcement post.
The question was a lot longer than this (and contained some much appreciated kind words). But I’ll leave out any personal details and the backstory and leave just the question (paraphrased).
Aside from joining the Facebook group on the “What Now” page and spreading the word via social media, is there anything else I could do to help you get these ideas to more developers?
For some quick housekeeping, here’s the page in question and the Facebook group, too (feel free to join!). I appreciate the question, and I also understand it. I mean, of course I literally understand the English language. But I mean that I understand the necessity of the asking.
The book release coincided with my “retirement” from IT management consulting. I went home, published a book, and dedicated my time to three simultaneous pursuits: a dev tools content marketing business, a specialized codebase analysis practice, and selling my primary residence in favor of what I think of as “cosmopolitan homelessness” (and moving). I offer this not as an excuse, but as an explanation. I’ve been distracted.
The Developer Hegemony Book’s Promise and the What Now
The upshot of my flurry of activity has included not doing a lot to pursue or facilitate the book’s vision. I’ve made occasional posts to the Facebook group and I’ve added some content to my Youtube channel about how to get a Tax ID and start a corporation. But I haven’t exactly kept the pedal to the floor and started a movement in earnest.
So I’ll take on this question and the rest of the post from the perspective of “what would I do to advance the cause if days were 32 hours long and I had more time?” After all, no one has more interest in advancing the cause than me.
I should also mention that the book contains my thoughts on how individuals and organizations can move toward Developer Hegemony. I won’t rehash that here, opting instead to address the specifics of how to spread the ideas.