This is an adaptation of the Ten Bullets ruleset by Tom Sachs. The original ten rules were written for his modern art studio, but have been adapted and implemented by many other notable entities, including the Jet Propulsion Lab at NASA.
Here are the Ten Bullets:
I. Work To Code
II. Sacred Space
III. Be Thorough
IV. Be On Time
V. I Understand
VI. Sent Does Not Mean Received
VII. Always Be Knolling
VIII. Be On Time
IX. Leatherface
X. Persistence
The purpose of this blogpost is to readapt them to the world of software development, while also adding some extra considerations.
I. Work To Code
For Tom Sachs, creativity is the enemy. Adhere to the tried and tested working principles, unless there is a very good reason to change them. Inventions need to fall in place within the already existing ecosystem.
When working on projects, define precise rules for anything ranging from repository structure to pre-commit and commit format, all the way to merging pull requests and releasing software. Don't make a mess.
II. Sacred Space
The original rule was about respecting the shop as a sacred place - keeping it in order, managing access, using separate areas for separate tasks – yet it's easy to see how this may apply to any workspace. Even working from home, it's better to have a separate room (or a separate corner of a room) to dedicate to work only. It increases the mental separation between your work and private life.
III. Be Thorough
Always Be Closing is a phrase used by Alec Baldwin's character in the 1992 movie "Glengarry Glen Ross", to refer to the sales practice of going through with each lead. The concept was generalized and made popular by youtuber Casey Neistat, a former Sachs employee. Always close what you started, archive the result and put the tools back.
Thoroughness Counts: don't leave half-baked artifacts around. If you use the last item in stock, buy it back (or send a request to the resource owner, in a structured environment).
IV. Be On Time
Come prepared and commit yourself entirely. It is not only about being there punctually (Van Neistat, the author of the original video adaptation of Ten Bullets, made a video with rules about being on time, by the way). It also means being well prepared for work for the entirety of its duration.
Work at a reasonable, sustainable pace. Too many of us in the software world spread themselves out too thin – both on trying to deliver too much and with our personal energy – the result are burnout and delayed deliveries.
V. I Understand
This is about acknowledgement. If you understand the task you've been assigned, say it out loud. If you don't, ask questions immediately.
So much time is lost by doing things the wrong way, especially in start-ups, where sometimes individual members might subvertly misunderstand directives on purpose when they don't agree. Make sure everyone understands their tasks, otherwise chaos will reign.
VI. Sent Does Not Mean Received
Your work can't be marked as complete until it has been delivered, received and approved.
Delivered your product to the customer? Have them confirm the reception. Someone sent you something? Let them know you saw it. A simple "Received." message is enough. Don't leave the doubt lurking in your (or their) mind. Think of it as an ACK packet at the transport layer of a network.
VII. Keep A List
Keep (and carry with you) a list with the details of all the projects of what you're working on. Don't let details fall through.
This could be anything from your notes to a .txt file on your desktop, or even GitHub issues about your projects.
VIII. Always Be Knolling
The act of knolling is defined as constantly reorganizing your tools to keep them square to the surface you're working on. In Sachs's philosophy, the problem is not having may tools or parts around at once. You can handle complexity as long as the many moving parts are well organized and easy to see.
In the software development world, this is akin to refactoring. Keep your files, folders and classes in order.
IX. Leatherface
The Tom Sachs studio had an action figure of Leatherface, the character from the 1970s show "The Texas Chainsaw Massacre". In case any of the artists and artisans of the studio committed a violation to the code, like leaving some appliance on during the night, they were required to leave money by the Leatherface figure.
To be more careful and avoid repeating the same mistakes, set up a small expiation ritual. It will help to make the rule stick in your head.
X. Persistence
Persistence and determination beat talent, education and resources. Keep on trying.
Bruteforce is not the answer to everything – resources count and so does efficiency – but it will get you a long way. In a distracted world, full of half-baked software projects, being able to stack up hours of real undistracted work can make a David beat any Goliath.