Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

48h Before the Meeting

Don't show your work without understanding it.

Language

日本語 | English | 简体中文

The original is in Japanese. The English and Chinese versions are AI translations of the Japanese original.

When to use it (why 48h, not 24h?)

Run it 48 hours before your meeting. 24 hours at the very latest.

Why not just say 24h? Because then you'd do it 12h before. We all know how this goes. Aim for 48h and you'll probably land around 24h, which still leaves time to fix things. Aim for 24h and you'll land in the middle of the night before the meeting.

Doing it right before the meeting defeats the point. You need time to fix your code and slides, and to really understand what you find.

Why this exists

AI can write your slides and your code in minutes. It can't attend the meeting for you.

Progress reports look more polished than ever, but when we ask how the algorithm works, the author often can't say. That's the gap this fills. It's not an exam, and nobody is checking up on you. It's a way to make sure the understanding behind your work is yours.

So we turned the tool around. Instead of asking AI for answers, let it ask you questions, one at a time, starting with what you know best. A short sparring session, and you walk into the meeting ready to explain your own research.

Contribute

Advisors, add your own version! How to contribute and how to use Issues are in the guide for your language:

English | 日本語 | 简体中文

Contributors

License

This work is licensed under CC BY 4.0.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors