Hey there! This is Nat Bennett, from Simpler Machines, a newsletter about software.
This week I launched a new zine, called How to Quit Vim. It's twenty pages, you can print it out, you'll probably learn something new even if you've used Vim for a long time, and it's free.
This one's version 0.3.0, and I'd appreciate any feedback you have. I've already made several updates based on comments readers and I'd love to make more. Questions, comments, corrections – whatever you've got, e-mail me at "nat at this website" or leave a comment or leave a comment here.
I'm also exploring how to make a hand-printed paper version with nice cover stock. This will probably be a signed & numbered limited print run, once I've got a nice 1.0.0 that I'm happy with. So keep your eyes peeled for that.
In the meantime – what do you need from me?
I'm expecting to have a little more time next week to spend writing. I've got a bunch of stuff in my notes and e-mails that I want to write up properly.
The list includes but is not limited to:
- Why & how Pivotal moved engineers between teams so damn much
- Why & how Pivotal did breakfast
- More about "how things were" at Pivotal
- More about "how things were" at Pivotal in general
- What happened when we started tracking test failures in Cloud Foundry's acceptance tests
- More about release engineering and scaling XP at Cloud Foundry
- Why does story size matter?
- My default approach to organizing code
- Advice to my younger self – the things I wish I'd known about programming before I learned how to do it
- Advice to my earlier-career self – problems I had in the 2-4 year zone and what I wish I'd known then
- What is "sustainable pace" really
- The mental side of programming – managing anxiety, energy, and attention during this demanding cognitive activity
- My personal maintenance practices – all the stuff I do to help keep myself relatively chill as an incredibly tightly wound person who got sick of being so mad all the time
- The spiritual side of programming – how do we get meaning from our work? Should we get meaning from our work? If we don't, where do we get meaning? How does a software job fit into, like, the 80 years of a human life?
- Does the god of your understanding care if you write code?
If any of that sounds especially interesting – or if there's another topic you'd like to hear about – let me know in the comments here or e-mail me at "nat at this website."