The project that still opens in six months

Two problems, one lesson

The first is speed: most beginners edit with a mouse, dragging clip edges by hand, and are three to five times slower than they need to be. The second is survival: a client emails in March about a video you made in September, and you cannot open it, or you can open it and half the clips are offline.

Both are solved by habits that cost nothing and take an afternoon to adopt.

Learn five keys, not fifty

Shortcut lists are useless because you cannot absorb forty at once. These are the ones that change how the work feels, and they are close to identical across Resolve, Premiere, Avid, Kdenlive and Shotcut.

J, K, L. L plays forward, J plays backward, K stops. Tap L twice for double speed, three times for faster. Hold K and tap L to step forward one frame. Your left hand lives here and you never touch the playhead with the mouse again.

I and O. Mark in, mark out. This is how you select a piece of a clip without dragging anything.

The split key. Cuts the clip at the playhead. In Resolve it is Ctrl/Cmd+B; in Premiere it is Ctrl/Cmd+K. Learn the one for your editor and stop reaching for the blade tool.

That is five. Use only those for a week and your speed roughly doubles.

Three-point editing, which is the real unlock

This is how professional editors actually work and almost no self-taught editor discovers it.

1. 1In the source viewer, mark in and out on the piece of the clip you want.
2. 2In the timeline, mark in where it should land.
3. 3Press insert (which pushes everything downstream later) or overwrite (which replaces what is there).

Three points define the fourth. You never drag a clip to the timeline and then trim it, which is two operations and a guess. In Resolve, insert and overwrite default to F9 and F10 on the edit page.

Once this is in your hands, an assembly of a one-hour interview takes twenty minutes instead of two hours.

A folder structure that survives

Decide this before you import anything, because moving files afterwards breaks every link in the project.

2026-03-12_Sharma_ClinicFilm/
  01_footage/
  02_audio/
  03_graphics/
  04_project/
  05_exports/
  06_docs/
  proxies/

Date first, in year-month-day, so folders sort chronologically without any effort. Numbered subfolders so they stay in a sensible order rather than alphabetical. Exports named ClinicFilm_v01.mp4, v02, v03 — never final, never final_final, never FINAL_USE_THIS. A version number tells you which is newest six months from now; the word "final" tells you nothing and is always a lie.

Put a plain text file in 06_docs holding the music licence log from the earlier lesson, the client's brief, the delivery specifications, and the passwords-free notes about who said what. That file is what makes a revision request in March survivable.

The Resolve trap that eats projects

Worth stating plainly because it catches people who thought they had backups.

DaVinci Resolve stores projects in an internal database, not as a loose file in your project folder. Copying the whole footage folder to an external drive therefore backs up none of your edit. You have to explicitly export the project — File, Export Project, producing a .drp — or export the whole database.

Do it at the end of every session. The .drp is a few megabytes. Also open Preferences and confirm project backups and auto-save are on, and note where they are being written.

Premiere, Kdenlive and Shotcut do store a project file in the folder, but the same discipline applies: the project file is small, the footage is large, and they need different backup strategies for exactly that reason.

Backups, cheaply

The standard is 3-2-1: three copies of the data, on two different kinds of media, one of them somewhere else physically. That sounds like a corporate policy. Here is the student version, and it costs the price of one external drive:

• Copy one: your working drive.
• Copy two: an external hard disk you plug in at the end of each week. External drives are cheap per terabyte and irreplaceable footage is not.
• Copy three, off-site: the project file, the licence log and the exported master in any free cloud storage. Those are megabytes, not terabytes. You cannot afford to sync 500 GB of footage to the cloud, and you do not need to — footage from a shoot can often be reshot or is already backed up on the camera cards, while the edit represents forty hours of decisions that exist nowhere else.

Keep camera cards unformatted until the edit is delivered, if you can afford the cards. It is the cheapest insurance in this list.

Two speed habits worth the effort

Render cache. When playback stutters on a section with effects, render that region in the background so the timeline plays smoothly and you can judge the timing. It is called render cache or smart cache in Resolve, and preview rendering elsewhere.

Make a template project. Bins already created, timeline at your usual resolution and frame rate, title styles and caption styles saved, export presets set. Duplicate it at the start of each job. Twenty minutes of setup, once, that you never do again.

Today

Export your current project file to the folder next to your footage, then write your file structure down and use it on the next thing you shoot. And spend a week on JKL. Nothing else in this course pays back faster.

Next, if you want to go further: Motion and Audio for titles that move and mixes that hold together, Visual Storytelling for what to point the camera at, and AI Video for what generative tools can and cannot yet do in a real edit.