Growing your career
Tooling and automation
Time spent learning your editor, shell, and a boring automation threshold compounds for years.
Time spent learning your environment compounds for years. An engineer who navigates a codebase at twice the speed does not work twice the hours. They explore more designs per day.
This is leverage applied to the tools you already live in.
Walking through what to invest in
Editor and navigation. Learn go-to-definition, find-references, multi-cursor, project-wide search, and debugger basics until they are muscle memory.
Shell and scripting. The ability to reshape logs, batch-rename, and wrap repetitive git or deploy steps is a force multiplier. MIT's Missing Semester exists because most CS degrees skip this.
Personal automation threshold. If you do a manual sequence more than twice a week, spend up to an hour automating it. If the sequence is shared, invest more and document it for the team — that is leverage with an ownership flavor.
AI coding tools. Use them to draft and explore, not to skip understanding. Shipping code you cannot explain is negative leverage when it pages at 2 a.m. Pair with working with AI tools.
Once a quarter, pick one tooling investment: a debugger workflow, a snippet library, a CI time cut, a better local seed script. Small, boring improvements beat a mythical "productivity system" rewrite.
Common mistakes
- Perfecting dotfiles in week one instead of shipping. Cap setup; then invest on a cadence.
- Letting an agent write code you cannot explain. Negative leverage at 2 a.m.
- Rebuilding your whole system instead of one boring improvement per quarter.
Check yourself
You run the same log-grep dance four times a week. What is the threshold?
Spend up to an hour automating it. If the team shares it, document the script.
A coding agent drafts a change you cannot walk through. Ship it?
No. Draft and explore with it. Do not skip understanding.
Key takeaways
- Editor, debugger, and shell skills compound for years.
- Automate a sequence you repeat more than twice a week.
- Use AI tools to draft, not to skip understanding.
- One boring tooling investment per quarter beats a system rewrite.
Further learning
MIT Missing Semester Lecture 1 (shell):
Next: saying no.
Related
Productivity, focus and sustainability
Leverage, deep work, saying no, and a pace you can still think clearly at in year five.
Engineering leverage
Impact divided by time. Ask what the next hour is worth, not whether you looked busy.
Working effectively with AI coding tools
Use autocomplete, chat, and coding agents to go faster without shipping code you do not understand — context, verify loops, and protecting your skill growth.