Skip to main content

How to read a paper?

Understanding papers fast and completely is an essential skill of mine. This is a living document of my strategy:

  1. Skim the intro. Seems it relevant?
  2. Skim the abstract without understanding. Seems it relevant? 
  3. Print the paper
  4. Skim the headlines. Do they and the order make sense? 
  5. Read the introduction
  6. Read it again
  7. What is the paper about? 
  8. I sketch out some possible solutions that come to my mind
  9. Work through the related work: Check at least the title of every reference here. Normally the paper builds only one or two main-references. Skim them.
  10. Extend your own solutions
  11. Read the paper without understanding to get a feeling for the context
  12. Read the sections of the paper
  13. Write an abstract
  14. Compare your abstract to the abstract of the paper that you read for the first time. Check why it is different.

Comments

Post a Comment

Popular posts from this blog

Futureproof Software

From here:  https://dzone.com/articles/the-secrets-of-futureproof-software Self-healing Self-patching, or more broadly, self-updating Backward compatibility Dynamic adaptation/ability to evolve over time Intent-based Made up of reusable futureproof components
Post a Comment
Read more

Choose Projects you do NOT do!

Inspiration from FluentC++ Choose which project NOT to work on. Be clear what you want and which projects are toxic. Keep the Hedgehog-concept in mind. Be sure that you are a) deeply passionate about the project b) the project can be the best in the world quality c) you can earn money with it If one of the three points is not met and not realistic soon don't do the project. Play around with it privately. Maybe you can pivot there so that it meets the criteria.
Post a Comment
Read more