I'm writing a guidebook for new tenure-track profs here:
https://vijay03.github.io/asstprofbook/

Two updates!
- A new chapter on teaching is available: https://vijay03.github.io/asstprofbook/chapters/teaching.pdf
- If you would like a version of the book to read on your kindle/tablet, you can now pre-order the book from Amazon: https://www.amazon.com/dp/B0BPLYLKQK

Chapters already up:
- Chapter 1: The Assistant Prof Job
(covers what the job is, responsibilities, perks, salaries, consulting..)
- Chapter 2: Students
(covers how to evaluate students, how to attract students, how to manage students)
- Chapter 3: Funding
(covers different types of funding, grants, etc)
- The "Networking At Conferences" sub-chapter of the Outreach chapter

Hoping to finish the book soon!

The CS Assistant Professor Handbook

Essential know-how for new and aspiring professors in computer science

The CS Assistant Professor Handbook
Please give me your comments and feedback as you read the book! One of the nice things about this format is that I can make corrections and changes

@vijay Nice book! I've been following along with every new chapter.

While reading this latest chapter on teaching, I was curious to see if you would discuss the distribution of responsibilities between TAs and professors. Specifically, I'm curious about what work a professor can or is expected to offload to their TAs, and whether there's a pattern to this based on university type or course size.

In my personal experience from the TA side, there don't seem to be any guidelines. Consequently, professors seem to have very different teaching workloads, and sometimes I wonder if they're aware of the disparity between courses.

For example, some professors are actively involved in the running of their course (e.g., setting homework, designing projects, regular meetings with the TAs, easily multiple days of effort per week), and I can't imagine the course running without them. But on the other extreme, some professors may not even be in their course development Slack or student Piazza, having delegated everything except showing up to give lecture and setting exam questions.

I don't think it is possible to make a statement that applies to all the different universities, but I think it may be helpful to suggest some templates for responsibility distribution, e.g., consider appointing a head TA to handle course logistics, you may want to be involved in high-level project design but you probably shouldn't be writing any code, and so on.

(Minor nitpick: I'm not sure if you defined "TA" before use. I think it first appeared in chapter 2 where the reader can figure it out from context.)

@capybara thats a good point. You are right in that its hard to say anything general about this, because it varies a lot! But I'll add some content about handling TAs to the chapter