taskforce

2024.03 - My Top Tools I Don't Want to Live Without

March 1, 2024 ยท 2 min read

Your game can be fine. And you still miss the deadline. Because the real time leak is the developer loop: searching code, repeating boilerplate, losing decisions in meetings, rebuilding the same scripts on every machine, and praying your files never disappear.

This module is my current "I refuse to work without this" stack. Not theory. Tools we actually use to move faster every week: AI-assisted research, instant code search, template-driven standard compliance, real backups, transcription + search, remote automations, and one "cheat code" for performance triage when profiling is not giving you usable signal.

My Top Professional Tools I Don't Want to Live Without (March 2024)

Free preview value (do this today): pick one of these and implement it in 30 minutes. You'll feel it tomorrow.

1) Stop wasting minutes on search. If you ever dig into Unity packages, unit tests, or any large codebase: use ripgrep instead of waiting on your IDE. It's multi-threaded, respects .gitignore, and supports context output so you can see the lines before/after the match (useful when you're hunting patterns like "public/protected bool fields" or "MonoBehaviour + what gets declared next").

2) Stop losing decisions in meetings. Record the call (ask for permission), transcribe it with WhisperX to SRT + TXT, then search your entire history with ripgrep. "Where did we discuss Switch port?" becomes a literal text search, and the SRT timestamps tell you where to jump in the recording.

whisperx "meeting.mp4" --model medium.en --language en --device cuda
# then:
rg -n "Switch|port" /path/to/transcripts

3) Stop trusting a single point of truth. For backups, Restic gives you snapshots, diffs between snapshots, and restores. Ruben's setup is even more paranoid: not just local backups, but a remote machine doing the job so your laptop being off doesn't kill your safety net.

And yes, the performance "cheat code" tool in this module is remote hierarchy debugging: connect to a running build (laptop, console, whatever), toggle GameObjects/components on and off, and do fast A/B tests to answer "what's eating the frame time?" when profiler data is incomplete or noisy.

HDG Remote Debug: remote hierarchy inspection, toggles, and live component value edits
Remote hierarchy toggles + live value edits: fast A/B signal when profiling is not enough.

CEO/Producer translation: this is how you increase throughput and reduce delivery risk without hiring. Less waiting. Less rework. Less "where the hell was that?"

Members-only below is the complete step-by-step module (all 7 lessons, plus the audio/resources/downloads). The free preview is just the opening move.

In this module:

Join to unlock the full module, audio, and resources.