A while back, @Zvi set up a Schelling point for mentorship. I, personally, had some pretty good experiences from that thread, and wanted to continue the tradition, now that the old thread's been inactive for some time.
To see some of my thoughts on mentorship, check out this dialogue between Elizabeth and I.
I'll be copying Zvi's formatting for comments:
Replies to this post should take the form of any of the following:
- [MENTOR]: A non-binding indication of potential interest in mentorship. Mention that you might, at some point, be interested in taking on an apprentice. This commits you to nothing. Make sure to indicate what you’d be teaching them and what project would likely be involved, and open with [MENTOR]. You are free to include contact info, or not include it and monitor replies.
- Replies to this comment to indicate potential interest in being the apprentice, marked [APPRENTICE], which should include a method of further contact.
- [APPRENTICE]: A non-binding indication of potential interest in being an apprentice. Mention that you might, at some point, be interested in being an apprentice. This commits you to nothing. Make sure to indicate what you’re interested in being an apprentice in and learning, and an indication of what’s motivating you.
- Replies to this comment to indicate potential interest in being the mentor, marked with [MENTOR], which should include a method of further contact.
- [NORMAL] You’re free to comment as per normal, but start with [NORMAL] in the top-level for clarity.
[APPRENTICE]:
For a bunch of these, the minimum viable product for mentoring me is a combination of pointing me to books/textbooks and checking in on me to make sure I actually do it.
Some things I'd like mentorship on:
Hm. My background is computer science at university, about 20 years of Java, plus some Python in my free time. Chances are, you know more about Python than I do, so the useful advice I could provide would be in the "programming in general" area, which of course also applies to Python code. Either something theoretical (e.g. finite-state machines), or something from practice (e.g. test-driven development); actually those are the only two examples that come to my mind right now, but maybe if I think longer about it, I will find something more. Also, you coul... (read more)