Join

Well begun is half done.

Application

  • There are nothing blocking you from contacting Jeehoon (e.g., GPA, experience, …). You can also contact Jeehoon via comments!

  • Send an application to Jeehoon (jeehoon.kang@kaist.ac.kr). The application should at least contain:
    • The most interesting experience on computing. It can be about course projects, research or industry experience, or anything related to computing. Please prepare for a Google Docs document that clearly describes the experience, and give the document’s comment access to jeehoon.kang@cp.kaist.ac.kr.
    • What you want to do in the lab. Please read the lab’s research page; see what’s going on in this lab; write down your plan as a Google Docs document; and give the document’s comment access to jeehoon.kang@cp.kaist.ac.kr.
    • The time you’re available for an online meeting for 30 minutes. Please look at Jeehoon’s calendar for his schedule.
  • Finish reading this document and do all the action items.

Discussion

  • Don’t pretend to know something if you don’t. If you do that, then you’re losing an opportunity to (1) learn the knowledge; and (2) go deeper into the problem that leads to a great research topic. Cherish (and even foster) your ignorance. Don’t assume the others will look down on you if you don’t know something. I know people often do it, but it’s their bad.

    • Don’t say yes (or no) if you’re not sure about it.
    • Don’t say you understood something if you don’t.
    • You’re encouraged to say “I don’t get it” and “I don’t know that.”
  • Be faithful to the discussion. If you disagree, say so; if you don’t like it, say so; if you’re happy with it, say so! But don’t try to win the argument. Research is not about winning and losing (especially within the same group). Try to summarize what you want to say (e.g., “Your idea doesn’t work in general”) and then substantiate your argument with evidences (e.g., “for instance, let’s look at this code: …”).

  • Don’t be angry or grumpy when the discussion is getting hotter. Research and any other creative works require different opinions clashing with each other, or in other words, hot discussions. But they don’t need to be involved with emotions clashing with each other. I know it’s difficult to separate them out, but let’s try to do that.

  • Right after every discussion, write down and share a summary note in the corresponding project stream in Zulip. For instance:

      ## discussions
      def function():
        x = 10
        return "Hello"
    

    action items

    • jeehoon: contact D’s authors
    • kyeongmin: investigate if B really matters, and document why A won’t work in gitlab.
    • seungmin: implement C, make a schedule for the next meeting

    Please faithfully summarize discussions. Especially, be fair to the ideas you don’t agree with.

Requirments

  • All new graduate students are required to finish at least two of the followings before joining the lab. So please start working on one of them ASAP.

    You’re also strongly encouraged to join the lab as an undergraduate intern to see what’s actually going on in the lab.

  • Undergraduate interns don’t have any requirements.

    We are widely open to all undergraduate students! If you want to join this lab as an intern, you’re going to do so. You are first going to do at least one of the above assignments, and then starting on research projects.

Markdown-Test Section

h1 Heading

h2 Heading

h3 Heading

h4 Heading

h5 Heading
h6 Heading

Horizontal Rules


Emphasis & Checkbox

This is bold text

This is italic text

Strikethrough

  • chekc
  • ckckck

Blockquotes

Normal Blockquotes

Lorem Ipsum is simply dummy text of the printing and typesetting industry.

Lorem Ipsum has been the industry’s standard dummy text ever since the 1500s

when an unknown printer took a galley of type and scrambled it to make a type specimen book.

It has survived not only five centuries,

but also the leap into electronic typesetting, remaining essentially unchanged.

Lists

Unordered

  • Create a list by starting a line with +, -, or *
  • Sub-lists are made by indenting 2 spaces:
    • Marker character change forces new list start:
      • Ac tristique libero volutpat at
      • Facilisis in pretium nisl aliquet
      • Nulla volutpat aliquam velit
  • Very easy!

Ordered

  1. Lorem ipsum dolor sit amet
  2. Consectetur adipiscing elit
  3. Integer molestie lorem at massa

Code

Inline code

Syntax highlighting

var foo = function (bar) {
  return bar++;
};

console.log(foo(5));

Tables

Option Description
data path to data files to supply the data that will be passed into templates.
engine engine to be used for processing templates. Handlebars is the default.
ext extension to be used for dest files.

Right aligned columns

Option Description
data path to data files to supply the data that will be passed into templates.
engine engine to be used for processing templates. Handlebars is the default.
ext extension to be used for dest files.

link text link with title

Images

Minion ![Alt text][id] With a reference later in the document defining the URL location: [id]: https://octodex.github.com/images/dojocat.jpg “The Dojocat”

Footnotes

Footnote 1 link1. Footnote 2 link2. Duplicated footnote reference2.

Definition lists

Term 1
Definition 1

with lazy continuation.

Term 2 with inline markup
Definition 2
{ some code, part of Definition 2 }

Third paragraph of definition 2.


  1. Footnote can have markup 

  2. Footnote text.  2