I have very little original advice to offer to my advisees. The best I can do is pass along advice from others. After some notes on protocol, I link to resources that I have found helpful.

Meeting with me

• Attend our student working group. Felix Tintelnot, Rodrigo Adao, and I run a working group for students studying international trade and economic geography. You can learn a lot from other students' presentations and our comments on them.
• Bring an agenda to meetings. 30-minute meetings are sufficient to discuss about three substantive points in meaningful detail. Write up a page of notes beforehand to ensure that we discuss those points.
• Follow through after meetings. At the beginning of a meeting, tell me what you did to implement or address concrete suggestions I made at the previous meeting.

Presenting

• Present information coherently and efficiently. For background, please read Edward Tufte's The Visual Display of Quantitative Information.
• Budget at least two minutes per slide. A 60-minute talk should have about 25 slides.
• Your slidedeck is not a teleprompter. Don't put so many words on the slide that the audience has to choose between listening to you and reading your slides.
• At minimum, adhere to Jonathan Schwabish's An Economist's Guide to Visualizing Data (JEP 2014).
• Respect the principle of proportional ink
• I like slide titles to state conclusions, not topics. Instead of 'skill premia and city size', title the slide 'Skill premia are higher in larger cities'. Don't hide your message.
• Consider the assertion-evidence slide design. Watch Michael Alley's NSF talk. He reports a treatment effect of putting the assertion in the slide title.
• Make slides with a 16x9 aspect ratio: \documentclass[aspectratio=169]{beamer}
• Like 8% of males, I am red-green color blind. Please produce color-blind-friendly figures. (explainer, test, Stata module)
• The figures and tables that are optimal for your paper are rarely also optimal for your slides. Produce distinct versions.
• When presenting regression tables, it's a good idea to adhere to Keith Head's criteria.
• Read Jonathan Schwabish's Ten Guidelines for Better Tables.
• Please read Jesse Shapiro's slides on How to Give an Applied Micro Talk. Follow that advice when making your slides.
• Read Eric Zwick's A Graph is Worth a Thousand Citations.
• Check out Paul Goldsmith-Pinkham's beamer tips.
• Watch Patrick Winston's How To Speak.
• Look at Rachel Meager's Public Speaking for Academic Economists.
• There are some good sugggestions in Adam Guren's How to Give a Lunch Talk.
• Make sure your presentation answers the questions listed in Don Davis's What Makes for a Successful Paper and Seminar?
• As a discussant, do not waste your time repeating what the presenter said. See Chris Blattman's guidance.

Coding

• My workflow is described in my project template.
• Use a good text editor like SublimeText, Atom, or VS Code to write code, slides, and papers. A good text editor offers multi-select, autocompletion, and language-specific syntax highlighting.
• Use version control. Learn Git now.
• Use build automation tools. I use Make. R has targets. Stata has project.
• Read Kieran Healy's The Plain Person's Guide to Plain Text Social Science.
• Read Gentzkow and Shapiro's Code and Data.
• Look at Gentzkow and Shapiro's online infrastructure.
• Read Patrick Ball's The Task Is A Quantum Of Workflow.
• Watch Patrick Ball's Principled Data Processing.
• If you're using Matlab, consider using Julia.
• Beware of dumb Stata gotchas
• XKCD comics that apply: 208, 974, 1205, 1319, 2510

Working

• Read Paul Graham's Maker's Schedule, Manager's Schedule.
• Paul Niehaus on Doing Research.

Writing

• Use language carefully. Check out Phile Haile's Models, Measurement, and the Language of Empirical Economics.
• If you've got a complete project, write up an introduction according to Keith Head's formula.
• John Cochrane's Writing Tips for PhD Students.
• Claudia Goldin and Larry Katz's The Ten Most Important Rules of Writing Your Job Market Paper.
• Steven Pinker: "The main cause of incomprehensible prose is the difficulty of imagining what it's like for someone else not to know something that you know."
• Steven Pinker's Why Academics Stink at Writing.
• Varanya Chaubey's The Little Book of Research Writing.
• Don't write statements like 'higher (lower) values of X cause more (less) Y'. These parenthetical opposites add zero information. Delete them. This mistake is not uncommon. I bet Keith Head hates it.
• Go download 10 JMPs in your field, read all of them in under 5 hours, and rank them from best to worst. Now you know why recruiting committees value readability.
• Look at the experimental evidence on the value of editing an economics paper. Then hire an editor.

The job market

• At least one year before you'll be on the market, read John Cawley's very comprehensive Guide and Advice For Economists on the US Junior Academic Job Market. It outlines what you need to do by application time in November, interviews in January, flyouts in January-February, decisions in March, etc. The process will be much less intimidating if you see the big picture from the beginning rather than learning about the market at the last minute.
• You need to have your main research results in hand by June. You will spend the summer writing, not producing new results. The typical student underestimates the difficulty of writing clear prose for general-interest readers. Give a full draft of your paper to your advisors in June. Sharing something in September is too late.
• For your opening pitch in an interview (or for an entire elevator ride), Owen highlights good examples from Justin Wolfers.
• The European market differs in some ways. See David Schindler's Guide to the European Job Market for examples.