[Theory and practice] I value the combination of theory and practice. Even though you may be a theoretical computer scientist, I hope you will also appreciate the view if you aim to work with me. If you think you are only hands-on, kindly notice that I would like to know why things work, which may lead to fundamental discussions on theory. When reflecting on scientific writing, I would like to have precision when possible.
[Friendliness & Integrity] All members (Chih-Hong included) should communicate in a friendly, open, and constructive manner. Everyone has his/her own strengths, and your strength should not be a reason to disregard others. Please be patient when discussing research with me, especially as I will be busy with many other things and won't have time to go into deep detail every time (although this is what I love to do). I care so much about integrity, so don't fake things up.
[Collaboration] Balancing collaboration and independent work among PhD students is crucial for fostering both a productive research environment and ensuring individual academic growth.
As the thesis supervisor, I ensure each student has a research direction that aligns with the thesis goals. This project should be your primary focus and a significant portion of your PhD work.
Meanwhile, I will define collaborative projects as supplementary to the main thesis work. These projects can allow you to explore new ideas, learn different methodologies, and gain a broader perspective on the overall field.
Finally, I encourage sharing ideas, peer feedback, and joint problem-solving sessions within the group. These new ideas may lead to a novel line of attack for your thesis.
[Mathematics] You don't need to be super strong in mathematics. Still, you need to be comfortable catching up on some knowledge when needed, as this is crucial for CS in machine learning (ML), artificial intelligence (AI), and formal methods. In addition, you need to demonstrate some aptitude for analytical thinking.
[Work time] In principle, we shall try not to bother others on weekends. Relaxing holidays can fuel energy. There may be cases where you want to work hard before the submission deadline (your choice). You may trigger me, but I can't promise to be reactive. The draft should be ready 2 to 3 days before the deadline, as rushing things won't work.
[Your success & exit criterion] I hope you can be successful in your Ph.D. or postdoc journey, as that's how I define my success. You are not a component in building my success. However, depending on your career goals and capabilities, there are different criteria.
For Ph.D. students, you need to demonstrate the ability to drive some topics that interest me, with hints that you may continuously produce good results without my huge intervention (e.g., kicking in crucial ideas or rewriting). This might be interpreted as three to four conference papers, where I find the conference decent.
For a postdoc aiming for an academic position, I hope you can be independent in driving research directions and take responsibility for co-supervising Ph.D. students. You can write a grant yourself, and I will be your strong support. I expect that we will work together for at least one year.
For a postdoc aiming at industry, I hope you can take serious responsibility in leading projects (EU, national, industrial) I have acquired. I will ensure that you can transition smoothly. I also expect that we will work together for at least one year.
For master's or internship students, I hope you can experience a solid round of research-related training. This may be interpreted as working on a paper as a contributing author. My past students are high performers, and almost all of them end up having a paper. I hope this good phenomenon continues.
[Publication] Due to my past roles in government and industrial research, publishing in top CS venues was never a requirement. As I have returned to academia, I have set myself different expectations, and I encourage the team members to aim their work at premiere CS venues.