What I've Learned
Practical insights from building products, scaling teams, and embracing AI
Prompt Engineering vs Prompt Guessing: When to Use Each
Prompt engineering vs prompt guessing: why prompts without context, guidelines and goals give random results, and when guessing is actually the right move.
Travis Sutphin
Principal engineer. 25+ years building software.
When to Use AI Thinking Mode (and When to Turn It Off)
When to use AI thinking mode: turn it on for strategy, tradeoffs and open questions, and off when you know exactly what you want built. A simple rule of thumb.
Travis Sutphin
Principal engineer. 25+ years building software.
AI Development Best Practices: Avoid the AI Speed Trap
AI doesn't fix chaos, it amplifies it. AI development best practices for moving fast with systems: documentation, tests, prompt templates and daily reviews.
Travis Sutphin
Principal engineer. 25+ years building software.
Weekly Priorities for Project Managers: The Big 3 Method
Set weekly priorities as a project manager with the Big 3: three outcomes that make the week a win, align your team and stop busywork stalling projects.
Travis Sutphin
Principal engineer. 25+ years building software.
File Naming Conventions: Best Practices to Stop File Chaos
File naming conventions best practices: a simple date, project, type and version format with examples, plus tips to roll it out so your team finds files fast.
Travis Sutphin
Principal engineer. 25+ years building software.
Recurring Tasks: Best Practices That Actually Work
Recurring tasks best practices: when to automate repeating work like standups and audits, when to skip it, and a one-sentence test for deciding.
Travis Sutphin
Principal engineer. 25+ years building software.
Monday Planning Framework: 30 Minutes in CEO Mode
A simple Monday planning framework: 30 minutes in CEO mode to brain dump your work, pick your top 3 priorities and block time before your calendar fills up.
Travis Sutphin
Principal engineer. 25+ years building software.
RACI Chart Guide: The 4 Roles, a Real Example and Tips
A RACI chart shows who is Responsible, Accountable, Consulted and Informed on each task. Learn the four roles, see a worked example and build your own.
Travis Sutphin
Principal engineer. 25+ years building software.