Suggestions

Hi Karim, Chen’s suggestions were:

• image for distributing Swift-WALA build
• emphasize C++ knowledge and experience
• emphasize compiler theory
• emphasize program analysis knowledge and experience
• de-emphasize Swift knowledge
• de-emphasize LLVM knowledge
• de-emphasize Java knowledge and experience
• biweekly plans for students

My augments to these suggestions:

• An image is tricky - too much virtualization overhead, streaming in codebase updates, etc. Having the build instructions and a set-up server instance is my suggestion as discussed
• Definitely emphasizing C++ knowledge/experience is a massive component, unless we’re looking for both people who can work at the compiler level and at the Swift level (e.g. different teams like we have now). I would suggest in terms of C++ having a piece of code or a few examples of complex code as baseline examples for things students should be able to explain in detail what it’s doing and why to consider themselves proficient
• Maybe instead of Java knowledge, we should put in a note about JNI, since that will be more useful than direct Java knowledge. Students probably don’t need to have experience using JNI but should familiarize themselves with it.
• Biweekly plans are also difficult because students will be at different levels/working on different things, I think. What could be good, though, is using the Github project board for progress tracking and task allocation.