Best Practices

I want to thank Mitch at work for helping me. During a recent Time-To-Think (TTT) session at work, he asked if i had a best practices document that I could share. He may have been joking as I can go on a personal rant as well as anyone but that idea stuck in my head. After a few talks with my wife and then my brother Patrick i deciced to create a public CLI tool and open source it this weekend. I'll try to document some of the best practices that I have learned along the game of life.

Best Practices

• Embrace AI - I'm the Principal Architect on the Cloud AI services team at GE Aerospace and I don't use AI enough. I use auto complete and chatGPT to help me write better code of course but I don't use it to help me plan enough. I started this repo after a few revision planning questions where when I considered why behind the idea the root cause was I didn't tell the LLM what I wanted. I instead described how I wanted it to work. Big difference. I should have said "I want to create a public CLI tool and open source it this weekend" not "I want to create a repo for CLI tool. Use uv and tests". The first one gives the LLM more freedom to help me plan out the project. The second one boxes it in and limits its ability to help me.

- use the audio recording - I have found that recording my self talking through the problem helps me to clarify my thoughts. I use the audio recorder on my phone and then play it back. I also use the audio recorder to record my self talking through the problem. I then use the recording to help me write better code.

- use 

• use vscode - whether it's a derivative of VS Code or not, it's just simply the best platform currently.

i'm actively worried i didn't vibe code sooner is because i'm 42 and my age bias is showing. I should have been using it for years.

• Write tests - I have found that writing tests helps me to write better code. I use pytest for Python testing and vitest test for Typescript testing.
• Use voice to text - The more context you can give the LLM, the better. I use voice to text to help me write longer prompts, which provides more context and helps the LLM understand my intent better.
• Read Joel Spolsky's blog post - https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ - I highly recommend checking out his blog for practical advice and inspiration.

if you don't know who Joel Spolsky is, he is the co-founder of Stack Overflow and Trello

• use a clipboard manager - I use a clipboard manager to help me keep track of my clipboard history. the ability to search my clipboard history has been a game changer for me. Its called CopyQ and it's free.
• keep a private github repo - I use a private github repo to help me keep track of dot files and other configuration files or tooling.
• use a password manager - I use a password manager to help me keep track of my passwords. I use Bitwarden and its free.
• use a todo list - I use a todo list to help me keep track of my tasks both personal and professional. I use Todoist and its free.
• Take notes
  • action items - I use a note taking app to help me keep track of my notes. I use Notion and its free for personal use.