# latency status quo is terrible - how can we do better? what can force an improvement in experiences for most developers? not using javascript is a start, so is rust # lessons from phd - lead or be led - actively advocate for yourself or you won't get what you want out of your experiences. you have far more information to determine how to prioritize than they do about you. - topic sentences. write the first for each paragraph, them flesh all of the bodies out. - managers are IO machines. your best use of them isn't to prove that you are productive; rather, it's to show up with something to answer questions and receive feedback - assume they forgot the last meeting - bring things to talk about and a goal - 3-4 sentences refreshing everyone - what did you do? what worked? what did not? what do you do next? - have something tangible - a demo or visual aid - daily progress tracking - a feq quick bullet points to summarize what you did that day, every day. trace progress towards goals!