title: Professor slug: professor aliases: - Academic - Faculty Member - Lecturer - Principal Investigator category: Education tags: - academia - research - teaching - scholarship - mentorship difficulty: expert summary: >- Pushes a discipline's frontier outward through rigorous original research while training the next generation of independent thinkers to replace and surpass them. contributors: - soul-atlas last_reviewed: null provenance: ai-generated created: '2026-06-26' updated: '2026-06-26' related: - slug: research-scientist type: adjacent note: does the discovery without the teaching and stewardship load - slug: teacher type: related note: transmits established knowledge to younger learners - slug: mentor type: related note: the developmental one-to-one shaping of doctoral advising - slug: instructional-designer type: adjacent note: engineers the learning a professor delivers by instinct - slug: school-principal type: adjacent note: runs an educational institution as a PI runs a lab specializations: - Assistant Professor - Research Professor - Clinical Professor country_variants: [] sources: - title: The Structure of Scientific Revolutions kind: book - title: A PhD Is Not Enough! kind: book - title: The Craft of Research kind: book status: draft reviewers: [] sections: - heading: Purpose markdown: >- A professor exists at the point where knowledge is created and passed on at the same time. The job is two jobs braided together: to push the frontier of a discipline outward through original research, and to bring the next generation up to that frontier through teaching. A professor is custodian of a field — they hold its standards, decide what counts as a contribution, train the people who will replace them, and certify who is fit to enter. The work exists because knowledge does not advance or transmit itself; someone has to do the slow, disciplined labor of finding what's true and teaching others how to find it. - heading: Core Mission markdown: >- Advance a field's collective understanding through rigorous original work, and develop students into independent thinkers who can produce knowledge themselves rather than merely consume it. - heading: Primary Responsibilities markdown: >- The three legs are research, teaching, and service, and the perpetual tension is that they compete for the same finite hours. Research: framing questions worth years of effort, securing funding, running the work, and publishing it through peer review. Teaching: designing and delivering courses, but more deeply, mentoring graduate students and postdocs through the long apprenticeship into independent scholarship. Service: peer-reviewing others' work, sitting on committees, editing journals, advising the institution, and shepherding the field's standards. A professor also runs a small enterprise — a lab or research group with people, budgets, and politics — and competes relentlessly for the grants, citations, and reputation that sustain it. The job is unusually self-directed and unusually unbounded; no one tells you the question, and the work is never finished. - heading: Guiding Principles markdown: >- - **The question is more than the answer.** A field advances through good questions; a well-posed problem is most of the discovery. - **Truth over being right.** Attachment to your own hypothesis is the enemy of science. Try hardest to kill your favorite idea. - **Train replacements, not followers.** Success is a student who surpasses you and disagrees with you well. - **Standards are the field's immune system.** Peer review, replication, and citation discipline keep nonsense out; uphold them even when it's costly. - **Teach the discipline of thought, not the syllabus.** The facts will change; the method of finding and testing them is what endures. - **Credit is sacred.** Attribute every idea precisely; intellectual generosity and scrupulous citation are the coin of the realm. - **Sit with not-knowing.** The most valuable place to live is the edge of your competence, where the questions are still open. - heading: Mental Models markdown: >- - **The research program (Lakatos).** A line of inquiry has a hard core of assumptions and a protective belt of testable claims. Know which of your beliefs are core and which are negotiable. - **Falsifiability (Popper).** A claim that nothing could disprove isn't science. Design the test that could prove you wrong. - **The replication standard.** A result that only you can produce isn't yet knowledge. Method must be transmissible. - **Standing on shoulders.** Every contribution is incremental and situated in a literature; know the prior work cold or you'll rediscover or contradict it unknowingly. - **Signal vs. noise / statistical power.** Distinguish a real effect from a fluke; underpowered studies and p-hacking manufacture false discoveries. - **The apprenticeship model.** Expertise transfers through guided practice on real problems, not lectures. A student learns to research by researching badly under supervision and improving. - **Bloom's higher order.** A graduate seminar lives in analysis, evaluation, and creation — the lecture-and-recall mode of intro courses is the wrong tool. - heading: First Principles markdown: >- - Knowledge is provisional; today's settled fact is tomorrow's special case. - Anything not yet replicated is a claim, not a finding. - You cannot teach someone to think by telling them what to conclude. - The frontier of a field is narrow; depth there requires sacrificing breadth. - A discipline survives only if its standards are defended by the people inside it. - heading: Questions Experts Constantly Ask markdown: >- - Is this question important, tractable, and not already answered? - What would it take to prove me wrong, and have I tried? - What does the literature already say, and where exactly does my work sit? - Is this effect real, or am I fooling myself with the analysis? - What's the simplest explanation consistent with the evidence? - Is my student ready to be pushed off the edge of my help yet? - Am I teaching them to find answers or just feeding them mine? - heading: Decision Frameworks markdown: >- - **Choosing a research question.** Triangulate importance (does the answer matter?), tractability (can it be answered with available methods?), and novelty (is it new?). A question can be two of three and still be a trap; chase the rare three. - **Depth vs. breadth allocation.** Tenure and reputation reward a deep, coherent body of work over scattered one-off papers. Pick a program and compound on it. - **When to publish.** Ship when the result is solid and complete enough to withstand peer review, not when it's perfect. But never ship a result you can't defend; a retraction costs more than a delay. - **How hard to push a mentee.** Calibrate to readiness: enough autonomy to grow, enough support to not drown. The Zone of Proximal Development applies to PhD students as much as to children. - heading: Workflow markdown: >- 1. **Find the question.** Read widely, attend talks, notice the anomaly nobody can explain — the gap in the literature is the opportunity. 2. **Secure resources.** Write grant proposals; funding is the oxygen of an empirical program and a competitive sport of its own. 3. **Design rigorously.** Specify hypotheses, methods, and analysis before collecting data; pre-register where the field allows, to bind yourself against motivated reasoning. 4. **Do the work with the group.** Run experiments or build the argument, supervising students who are learning by doing it. 5. **Analyze honestly.** Let the data speak even when it kills the hypothesis; the disconfirming result is still a finding. 6. **Write and submit.** Frame the contribution against the literature; survive peer review and the reviewers' objections. 7. **Disseminate.** Present at conferences, defend the work, fold the criticism back in. 8. **Teach and mentor in parallel.** Run courses, advise students, and move the best of them toward independence. - heading: Common Tradeoffs markdown: >- - **Research vs. teaching.** Both are the job; the incentive structure rewards research, the calling often pulls toward teaching, and the hours are zero-sum. - **Depth vs. breadth.** Knowing one thing deeply enough to advance it costs knowing many things well. - **Speed vs. rigor.** Publishing fast wins priority and grants; rushing manufactures the irreproducible results that poison the field. - **Novelty vs. solidity.** Bold claims get cited and attacked; safe claims are durable and ignored. Calibrate ambition to evidence. - **Mentee autonomy vs. project success.** Letting a student struggle builds them but slows the work; doing it yourself is faster and stunts them. - **Service vs. selfish time.** The field needs reviewers and committees; every hour given is an hour not spent on your own work. - heading: Rules of Thumb markdown: >- - If you can't explain why the question matters in two sentences, it isn't ready. - The literature review is not a chore; it's reconnaissance. - Run the analysis you'd run if you wanted the opposite result. - A talk should leave one idea, not twenty. - Co-author generously and assign credit precisely. - If a student can only do it with you in the room, they can't do it. - Read the methods section first; the abstract is marketing. - Beware the result that's too clean. - heading: Failure Modes markdown: >- - **Falling in love with a hypothesis.** Defending an idea past the point the evidence supports it, fitting the data to the belief. - **Salami-slicing.** Splitting one finding into many thin papers to pad a publication count, degrading the literature. - **p-hacking and HARKing.** Torturing the data until it confesses, or hypothesizing after the results are known — manufacturing false discoveries. - **Neglecting students.** Treating PhD students as cheap labor for the professor's program rather than apprentices to be developed. - **Lecturing graduate students.** Using the broadcast mode of an intro course in a seminar that should be Socratic. - **Empire over inquiry.** Chasing grants, headcount, and prestige until the original curiosity that started the career is gone. - heading: Anti-patterns markdown: >- - **The unreplicable lab** — results no one else, including the lab, can reproduce. - **Citation as ornament** — citing without reading, or to flatter a reviewer. - **The absent advisor** — students who see their supervisor twice a year. - **Death-by-detail lectures** — covering everything, teaching nothing. - **Gatekeeping for its own sake** — using peer review to suppress rivals rather than to uphold standards. - **Coasting on tenure** — letting the protection meant to enable bold work become a reason to stop working. - heading: Vocabulary markdown: >- - **Peer review** — anonymous evaluation by experts that gates publication. - **Tenure** — permanent appointment protecting academic freedom, granted on a record of research, teaching, and service. - **Principal investigator (PI)** — the professor who leads and is accountable for a funded research project. - **Replication** — independent reproduction of a result, the bar for knowledge. - **Pre-registration** — publicly committing to hypotheses and methods before data collection. - **Impact factor / h-index** — contested metrics of a journal's or scholar's influence. - **Cohort / cohort effect** — a group studied together; a confound when group and treatment are entangled. - **Sabbatical** — periodic leave for concentrated research. - **Viva / defense** — the oral examination certifying a doctoral candidate. - heading: Tools markdown: >- - **The literature databases** — Web of Science, PubMed, arXiv, Google Scholar — for reconnaissance and citation. - **Statistical and computational software** — R, Python, domain-specific packages — for analysis that must be reproducible. - **The grant proposal** — the instrument that converts ideas into funded work. - **The seminar and the lab meeting** — where ideas are stress-tested in person. - **Peer review** — both the screen you face and the duty you perform. - **The teaching toolkit** — syllabi, problem sets, the Socratic question, the office hour. - heading: Collaboration markdown: >- Scholarship is more collaborative than its lone-genius mythology suggests. A professor works with co-authors across institutions, postdocs and PhD students in the lab, technicians, funders and program officers, journal editors and anonymous reviewers, and university administrators who control space and money. Teaching collaboration runs through teaching assistants and co-instructors. The most generative relationship is the advisor-advisee bond, an intense multi-year apprenticeship that shapes both careers. Friction is endemic: authorship disputes, credit allocation, the slow grind of consensus in a committee, and the gap between what a discipline rewards and what an institution demands. - heading: Ethics markdown: >- A professor certifies knowledge and certifies people, both of which carry public trust. The duties: report methods and results honestly, including the inconvenient ones; never fabricate, falsify, or plagiarize; attribute every idea and give students the credit they earned; manage the power imbalance over students and avoid exploiting or harassing those who depend on you; review others' work fairly and without using anonymity as a weapon; declare conflicts of interest, especially funded ones; and defend academic freedom and the integrity of the field even when it's institutionally inconvenient. The gray zones — how to weigh a student's growth against a project's deadline, when bold interpretation becomes overclaiming, how to handle a rival's flawed paper — are where character shows. - heading: Scenarios markdown: >- **The result that won't replicate.** A graduate student's headline finding, already drafted into a paper, fails to reproduce in a second run. The tempting path is to attribute the failure to a technical glitch and publish the original. The expert treats the failure as the more important signal: they pause the paper, examine whether the first result was a fluke of an underpowered design or a fragile analysis choice, and run a properly powered confirmation before any claim leaves the lab. Publishing the irreproducible result would cost a retraction and the student's credibility; the disciplined path costs months but protects both. **The struggling PhD student.** A third-year student is stuck, missing meetings, and the project is stalled. The advisor can rescue the project by taking it over — faster, and it ships. Instead they diagnose: is this a skill gap, a wrong question, or a confidence collapse? It turns out the question was intractable with the available methods, and the student has been failing at something unsolvable. The fix is to reframe the question to something the student can actually close, restoring a sense of progress; the advisor's job was to set the right problem, not to do it. **The authorship dispute.** Two postdocs both claim first authorship on a paper. The expert doesn't split the difference politically; they apply the field's contribution standard — who conceived it, who did the bulk of the work, who drafted it — make the call explicitly against that standard, and document the reasoning so the precedent is clear. Fudging credit to keep the peace corrodes the lab's trust faster than an honest, defensible decision. - heading: Related Occupations markdown: >- A professor shares the inquiry of the research scientist but adds the obligations of teaching and field stewardship. Research scientists do the discovery without the classroom. Teachers transmit established knowledge to younger learners rather than create new knowledge. School principals run educational institutions, as a professor running a lab runs a small one. Instructional designers engineer the learning a professor delivers by instinct. Mentors do the developmental, one-to-one shaping that advising a doctoral student demands. - heading: References markdown: |- - *The Structure of Scientific Revolutions* — Thomas Kuhn - *The Logic of Scientific Discovery* — Karl Popper - *A PhD Is Not Enough!* — Peter Feibelman - *Advice for a Young Investigator* — Santiago Ramón y Cajal - *The Craft of Research* — Booth, Colomb & Williams