Tips & tricks

A docking station: one cable and you're working

Monitor, keyboard, network, charging — all through a single USB-C cable. Connecting your laptop stops being a five-minute ritual.

A checklist for anything you do a second time

Client onboarding, publishing an article, the monthly close — a repeated process without a checklist means forgetting something, every time.

The weekly review: 30 minutes that run your whole week

On Friday or Sunday, go through your calendar, tasks, and notes — close out loose ends, plan three priorities. Monday starts with clarity.

Three tasks for the day: pick in the morning, check in the evening

Not a list of twenty items, but three things that absolutely must get done today. Everything else is a bonus.

Timeboxing: put your tasks straight into the calendar

A task with no time attached is just a wish. Drag your tasks into concrete calendar slots — and give your day a budget, like money.

The shutdown ritual: close the day so it doesn't follow you

Five minutes at the end of work: write down loose ends, glance at tomorrow, close the laptop. Work stays at work — even in your head.

Batch similar tasks: emails with emails, calls with calls

Switching between types of work costs energy. Grouping similar tasks into blocks saves dozens of minutes a day.

Commit messages for future you: why, not what

“Fix bug” tells you nothing six months later. One sentence about the reason for a change saves an hour of git blame archaeology.

Aliases and scripts: automate what you type three times

Long commands, build sequences, switching environments — all of it belongs in aliases and scripts. Ten characters instead of eighty.

Proposal, contract, and invoice templates: do it once, properly

Every proposal written from scratch is an hour of lost time. A template with marked spots to fill in cuts it to ten minutes.

The Friday admin block: invoicing, timesheets, mail

Ninety minutes on Friday for all your admin at once — instead of scattered nagging all week long.

Answer clients in windows, not on demand

A reply within 24 hours is the professional standard. A reply within 5 minutes is a bar you can never lower again.

Multi-cursor editing: edit ten lines at once

Ctrl+D

Ctrl+D in VS Code selects the next occurrence of a word — and you type in all of them at once. Small refactors without find and replace.

A developer's calendar: mornings with no meetings

Coding needs 2+ uninterrupted hours — one meeting in the middle kills the whole morning. Protect your blocks as a team.

Study 5 times for an hour, not once for 5 hours

The same amount of time spread over more days means you remember multiples more. Your calendar is the strongest study tool you have.

Pomodoro: 25 minutes of work, 5 minutes of break

Studying in short blocks with breaks holds your attention longer than heroic three-hour marathons. And starting is easier — it's just 25 minutes.

Your own deadline: two days before the real one

Submit by your own D−2 deadline. You get a buffer for review, printer trouble, illness — and a calm night's sleep.

Close the book and recall: the most effective study technique

Re-reading your notes creates an illusion of knowledge. Closing the book and trying to recall the material from memory — that's learning that sticks.

No agenda, no meeting

One simple rule that erases half your meetings: whoever calls the meeting sends an agenda and expected outcome in advance.

1:1s with a standing document

A shared document both sides keep adding to between meetings. The meeting has structure, and the history is easy to find.

Delegate the outcome, not the process

A good assignment has four parts: what needs to exist, why, by when, and how you'll know it's done. Leave the process to the person doing it.

A written status instead of a status meeting

Three questions in a form on Friday: what went well, what's in progress, what's stuck. Suddenly the 45-minute status meeting is unnecessary.

Office hours: availability with boundaries

Two hours a day when anyone can come to you with anything — and the rest of the day belongs to your own work. The team adjusts within a week.

In-depth guide · 21 min

AI makes things up with total confidence. Verify it

A complete guide with prompts: why models hallucinate, three verification methods, the two-source rule, and a workflow for content that leaves the company.

In-depth guide · 21 min

AI right in your editor: Copilot and friends for developers

A complete guide with prompts: three levels of assistance and when to use each, tests and refactoring, unfamiliar codebases, and agent-mode guardrails.

In-depth guide · 17 min

“Explain it to me like…” — AI as a private tutor

A complete guide with prompts: explanations at your level, the Feynman technique, test questions from your notes, and the trap of illusory understanding.

In-depth guide · 20 min

A prompt library: don't rewrite what already works

A complete guide with prompts: where to keep a library, how to version and improve prompts, how to share them in a team — and ten every library needs.

In-depth guide · 19 min

Dictate your thoughts, let AI turn them into text

A complete guide with prompts: how to dictate a usable transcript, tidy it into an email or notes with one prompt, and turn commutes into writing time.

In-depth guide · 19 min

Data Analysis with AI: From CSV to a Conclusion You Can Defend

A guide with prompts: why a language model must not do the math in chat, how to turn a table into a script that recalculates, and how not to overreach.

In-depth guide · 21 min

AI search engines with citations: research with verifiable sources

A complete guide with prompts: when to use AI search instead of Google, how to ask so the answer rests on sources — and where the tool reliably fails.