Effective Technologist Book Club
Book clubs for professional development are not new, but nothing like this exists at my employer or in my city, so I guess I’ll start one.
What does “Effective” mean?
Borrowing from another group 1, I’ll say whatever it means to you. 2
And “Technologist”?
Someone who builds or wields technology as a career. It’s a big tent including software and systems engineers, hardware engineers, UX practitioners, project managers, researchers, students, data scientists and more.
What’s the format?
Other book clubs are intensely organized, but this one is simple. I suggest the following, very open to modification.
We can have monthly video meetups 3, scheduled via When2meet or equivalent, hosted on Jitsi Meet or equivalent. 4 We’ll do two things:
- Choose the next month’s book via ranked choice voting.
- Spend 1-2 hours 5 talking about the previous month’s book. What did we learn from it? How do we try to apply it in our work? Where is the book wrong?
Between meetings we can coordinate via email list, because the last thing we all need is more chat notifications.
What kind of books?
Primarily (but not exclusively?) non-fiction that might grow one’s effectiveness and wisdom as a technologist. Topics might include socio-technical systems, software engineering, productivity, leadership, communication, incentives in organizations, case studies, and biographies. 6
We can learn about successful projects, crashed planes, and how to work with the most complex systems of all: human minds, and the organizations and societies they create.
That’s vague, give me examples.
I’ve read only part of each of these, but I think they fit the theme.
- The Effective Engineer by Edmond Lau
- Nonviolent Communication by Marshall Rosenberg
- A World Without Email by Cal Newport
- The Soul of a New Machine by Tracy Kidder
- Kill it with Fire by Marianne Bellotti
I’m not a programmer, do I belong?
Yes!
On one hand, everyone’s work is adjacent to code in some way, and growing one’s code literacy is a way to become more effective. On the other hand, a lot of technologists don’t work with much code directly, and I want to include you.
I imagine some books will be code-adjacent, and a few might be code-focused, but many won’t be either of those. This is not a programming book club per se.
Does this book club scale?
It doesn’t, because I don’t want to spend much time organizing it, and a reasonable-length meetup allows maybe 12 people to hear each others’ perspectives. If it grows larger, maybe we splinter.
What’s next?
Send me a message: bookclub at cmart dot today. Tell me what you like and dislike about this idea. What variation of it would you most want to join?
I have about 3 people interested so far. Let’s find our alignment and grow something new.
If something like this already exists, and we should join that instead of re-inventing, please tell me that as well.
-
For me, it means things like setting ambitious-yet-achievable goals, making important contributions to the teams and projects I join, increasing my motivation, gaining better control of my attention, working and communicating well with others, exchanging mentorship, and building my career proactively. ↩︎
-
Yes, the DALL-E pic above shows an in-person group. But I’d like to include people who don’t live nearby, and hybrid meetups are kind of awkward. ↩︎
-
It’s kinda like Zoom, works great, but it’s non-proprietary software. ↩︎
-
I think we should try to give everyone a chance to share their perspective within an hour. After that, staying to talk longer is cool, and leaving early is also cool. ↩︎
-
I imagine that longer essays and blog posts are also fair game. As long as everyone can reliably get their hands on a copy. ↩︎