Zero to Hero - draft

Development Environment Setup Quickstart Reference

2025-12-03T00:00:00+00:00

Here are some bookmarks that I visit frequently when deploying a new system, or setting up a new development environment, or just trying to look something up, along with some snippets that I use frequently.</p>

Build Essentials</h2>

sudo</span> apt update</span></span>
sudo</span> apt upgrade</span></span>
sudo</span> apt install build-essential</span></span></code></pre>~/.zshrc</code></h2>
export</span> ZSH</span>=</span>"</span>$HOME</span>/.oh-my-zsh</span>"</span></span>
</span>
ZSH_THEME</span>=</span>"</span>powerlevel10k/powerlevel10k</span>"</span></span>
</span>
source</span> $ZSH</span>/oh-my-zsh.sh</span></span>
</span>
export</span> MANPATH</span>=</span>"</span>/usr/local/man:</span>$MANPATH</span>"</span></span>
export</span> PATH</span>=</span>"</span>$PATH</span>:/usr/local/go/bin</span>"</span></span>
export</span> GPG_TTY</span>=</span>$(</span>tty</span>)</span></span>
export</span> WORKSPACE</span>=</span>"</span>$HOME</span>/WORKSPACE</span>"</span></span>
export</span> PATH</span>=</span>"</span>$PATH</span>:</span>$WORKSPACE</span>/spire/bin</span>"</span></span>
export</span> PATH</span>=</span>"</span>$PATH</span>:</span>$WORKSPACE</span>/spike</span>"</span></span>
export</span> PATH</span>=</span>"</span>$PATH</span>:</span>$HOME</span>/.local/bin</span>"</span></span>
source</span> "</span>$WORKSPACE</span>/spike/hack/lib/env.sh</span>"</span></span></code></pre>Distro Information</h2>
cat</span> /etc/</span>*</span>release</span></span>
</span>
# Or:</span></span>
lsb_release</span> -a</span></span>
</span>
## Or:</span></span>
export</span> ARCH</span>=</span>$(</span>case</span> $(</span>uname</span> -m</span>)</span> in</span> x86_64</span>)</span> \</span></span>
  echo</span> -n</span> amd64</span> ;;</span> aarch64</span>)</span> echo</span> -n</span> arm64</span> ;;</span> *)</span> \</span></span>
  echo</span> -n</span> $(</span>uname</span> -m</span>) ;;</span> esac</span>)</span></span>
export</span> OS</span>=</span>$(</span>uname</span> |</span> awk</span> '</span>{print tolower($0)}</span>')</span></span></code></pre>NPM and Node</h2>

Node.js</a></li>
</ul>
Claude Code</h2>

Claude Code</a></li>
</ul>
Grammarly</h2>

Grammarly</a></li>
</ul>
GitHub</h2>

Generating a new SSH Key</a></li>
Adding a new SSH Key to Your GitHub Account</a></li>
Generating a new GPG Key</a></li>
Adding a GPG Key to Your GitHub Account</a></li>
</ul>
Docker</h2>

Installing Docker Engine to Ubuntu</a></li>
Linux Post-Installation Steps for Docker</a></li>
</ul>
Windows Subsystem for Linux</h2>

Installing WSL</a></li>
</ul>
Minikube</h2>

Installing Minikube</a></li>
</ul>
Copying SSH Keys to Remote Hosts</h2>
ssh-copy-id</span> -i</span> ~/.ssh/id_rsa.pub user@host</span></span></code></pre>zsh and PowerLevel10k</h2>
sudo</span> apt update</span></span>
sudo</span> apt install zsh</span></span>
chsh</span> -s</span> /usr/bin/zsh</span></span></code></pre>

Oh My ZSH</a></li>
Powerlevel10k</a></li>
</ul>
JetBrains</h2>

JetBrains Toolbox</a></li>
</ul>
Fonts</h2>

MonoLisa</a></li>
PragmataPro Mono</a></li>
Berkeley Mono</a></li>
Operator Mono</a></li>
</ul>
Themes</h2>

Gerry Themes</a></li>
Dracula Pro</a></li>
Monokai Pro</a></li>
</ul>
Vim Setup</h2>

NerdTree</a></li>
Gruvbox Theme</a></li>
Vim Airline</a></li>
</ul>
.vimrc</code></h3>
set nocompatible</span></span>
filetype off</span></span>
</span>
syntax enable</span></span>
colorscheme darcula</span></span>
set nu</span></span>
set rnu</span></span>
set cursorline</span></span>
</span>
# Right Margin</span></span>
set colorcolumn=80</span></span>
highlight colorcolumn guibg=#444444</span></span>
</span>
# Tab Settings</span></span>
set tabstop=2</span></span>
set shiftwidth=2</span></span>
set softtabstop=2</span></span>
set smarttab</span></span>
set expandtab</span></span>
</span>
# Remove Scrollbars</span></span>
set guioptions-=r</span></span>
set guioptions-=R</span></span>
set guioptions-=L</span></span>
set guioptions-=l</span></span>
</span>
set laststatus=2</span></span>
set hlsearch</span></span>
</span>
# IndentGuidesEnable</span></span>
autocmd! GUIEnter * set vb t_vb=</span></span></code></pre>Windows</h2>

Windows Terminal</a></li>
Power Toys</a></li>
</ul>
Windows Shortcuts</h2>

Next/Previous Desktop: Win + Ctrl + (right or left arrow key)</code></li>
Shift+Drag to move a window to a fancy zone.</li>
</ul>
JetBrains Shortcuts</h2>

Search Everywhere: Shift + Shift</code></li>
Search in file: Alt + F3</code></li>
Find in files: Ctrl + Shift + F</code></li>
Select in…: Alt + F1</code></li>
Toggle terminal: Alt + F12</code></li>
Various views: Alt 1--9</code></li>
Commit view: Alt + 0</code></li>
</ul>



Code and Documentation Audit Prompt for Claude Code
2025-12-03T00:00:00+00:00
Here is the prompt that I used to verify that the code and documentation of
SPIKE</strong></a> and
SPIKE Go SDK</strong></a> is aligned.</p>
Later down the line, I am planning to streamline this process even further.</p>
But I still think, you need a human in the loop, as some of the documentation
may turn out to be misplaced or inaccurate.</p>
 I need a comprehensive audit of Go documentation vs implementation across the </span></span>
 codebase.</span></span>
</span>
Scope: /home/volkan/WORKSPACE/spike-sdk-go</span></span>
</span>
For each exported function, check:</span></span>
1. Return type mismatches (e.g., doc says "error" but returns </span></span>
   "*sdkErrors.SDKError")</span></span>
2. Parameter type mismatches (e.g., doc says "string" but uses custom type)</span></span>
3. Missing godoc comments</span></span>
4. Outdated behavior descriptions</span></span>
5. Missing parameter documentation</span></span>
6. Missing return value documentation</span></span>
7. Inconsistent example code</span></span>
</span>
Focus on:</span></span>
- All packages under api/</span></span>
- crypto/ package</span></span>
- kv/ package</span></span>
- log/ package</span></span>
- retry/ package</span></span>
- security/ package</span></span>
- strings/ package</span></span>
- system/ package</span></span>
- validation/ package</span></span>
- net/ package</span></span>
- errors/ package</span></span>
- spiffe/ package</span></span>
</span>
Return:</span></span>
- A structured markdown report grouped by issue type</span></span>
- File paths with line numbers</span></span>
- Current vs expected documentation</span></span>
- Severity rating (critical/moderate/minor)</span></span>
</span>
Do NOT make any changes - only analyze and report.</span></span>
</span>
Based on this report, we will create a phased plan and incrementally fix things.</span></span>
</span>
Alternative: Iterative Approach</span></span>
</span>
If you want changes made incrementally:</span></span>
</span>
Audit and FIX documentation issues in these files:</span></span>
- /home/volkan/WORKSPACE/spike-sdk-go/api/internal/impl/secret/*.go</span></span>
</span>
Check and fix:</span></span>
1. Return types: Update "error" to "*sdkErrors.SDKError" where applicable</span></span>
2. Add missing godoc for exported functions</span></span>
3. Ensure parameter types match function signatures</span></span>
4. Verify return value lists are complete</span></span>
</span>
After each file, report:</span></span>
- What was found</span></span>
- What was fixed</span></span>
- Line numbers changed</span></span></code></pre>

Zero to Hero - draft

Development Environment Setup Quickstart Reference

JetBrains Shortcuts</h2> Search Everywhere: Shift + Shift</code></li> Search in file: Alt + F3</code></li> Find in files: Ctrl + Shift + F</code></li> Select in…: Alt + F1</code></li> Toggle terminal: Alt + F12</code></li> Various views: Alt 1--9</code></li> Commit view: Alt + 0</code></li> </ul>

Code and Documentation Audit Prompt for Claude Code