Notes/personal/input/whitepapers.md

Author: dvogt23

Notes/personal/input/whitepapers.md

@@ -1,9 +1,42 @@
+---
+id: whitepapers
+aliases: []
+tags: []
+---
+
+## Links
+
 - [Google Scholar - Suche](https://scholar.google.de)
 - [dblp](https://dblp.org/)
 - [Springer nature - open science](https://www.springernature.com/de/open-research/about/whitepapers)
 - [Uni Trier](https://irdt.uni-trier.de/aktuelles/)
 - [Papers we Love](https://github.com/papers-we-love/papers-we-love)
-- [2 Minute Papers - Youtube]()
+- [2 Minute Papers - Youtube](https://www.youtube.com/channel/UCbfYPyITQ-7l4upoX8nvctg)
 - [SIG Conferences](https://www2.sigsoft.org/) / [Conference ranking](https://people.engr.tamu.edu/guofei/sec_conf_stat.htm)
 - [Elicit](https://elicit.com/)
-- [SciSpace](https://typeset.io/)
+- [SciSpace](https://typeset.io/)
+
+## A Software Engineer’s Guide to Reading Research Papers
+
+**Reading research is now essential for engineers**: Staying current with technical progress means engaging directly with academic papers.
+
+**Don’t expect instant understanding**: Papers are dense by nature; the frustration is normal, and a structured reading method helps.
+
+**First pass = bird’s eye view**: Focus on Abstract, Intro, Results, and Conclusion to see if the paper is relevant and valuable.
+
+**Second pass = detailed scan**: Read the rest without stressing about full comprehension. Note unknown terms and important references.
+
+**Investigate unknowns**: Look up definitions and cited works. This research builds the base knowledge needed for deeper understanding.
+
+**Third pass = connect the dots**: Revisit technical sections with your new knowledge to grasp the deeper mechanisms and reasoning.
+
+**Test your understanding**: Reproduce results, simulate algorithms, or even implement techniques from the paper.
+
+**Teach others to cement your grasp**: Explaining the paper helps clarify your thinking and exposes remaining gaps.
+
+**Carefully integrate AI tools**: Don’t rely solely on them—AI can hallucinate. Use them to challenge and refine your reasoning.
+
+**Build your own reading framework**: Adapt this method to your needs, but the key is to stay consistent and keep reading.
+
+Source: [codingconfessions](https://blog.codingconfessions.com/p/a-software-engineers-guide-to-reading-papers)
+