Wilduck's post pretty much hits the nail on the head. Especially the first two points and the last paragraph. While the third point is important, it doesn't ha

Wilduck's post pretty much hits the nail on the head. Especially the first two points and the last paragraph. While the third point is important, it doesn't have to be a full presentation. Just have the person talk to everyone on the team for a moment or two[1] about what (s)he did in the previous week, and how (s)he thinks the next week will come along[2]. Maybe a quick demo, if anything big was done. For the fourth point, I can't really say. I was the only intern at the company this summer. I was told about a few programs to get interns from various startups together, but they mostly involved going from SF down to Mountain View. I made the trip once to visit somewhere and its too much of a hassle for me to have wanted to do on a semi-regular basis[3]. I spent the time around the city and met a bunch of other people instead. Still had a blast. 1. Just "Added this and that feature, fixed this and that bug that were assigned as well as a few others that I ran into," not anything that takes time to prepare. 2. Even if its just "Yup. Sounds like a good plan" or "I'm not sure. This feature/bug might take a bit longer to fix." 3. Off-topic, but, I don't know how people do this commute. I had to do something similar, from Long Island to NYC two summers ago, and hated doing it every morning and evening.