# How to Write a Technical Paper: Structure and Style of the Epitome of your Research

<https://pdfs.semanticscholar.org/441f/ac7c2020e1c8f0d32adffca697bbb8a198a1.pdf>

- Host: [pdfs.semanticscholar.org](https://links.thingelstad.xyz/hosts/pdfs.semanticscholar.org/)
- Saved: October 25, 2018 (2018-10-26T02:11:44Z)
- Record: https://links.thingelstad.xyz/links/d39b49b44b31/
- JSON: https://links.thingelstad.xyz/links/d39b49b44b31.json

## What Jamie wrote

This is a great example document.

> A major problem that young researchers face is their inability to write good research papers. This document serves as a guideline on how to write a good technical paper.

Technical papers and [white papers](https://en.wikipedia.org/wiki/White_paper) have been confused with marketing organizations taking over white papers as a form of advertising. It’s good to see a robust discussion of a straight technical paper.

## Facts

- Kind: [Paper](https://links.thingelstad.xyz/kinds/paper/)

## Appears in

- [WT77: Weekly Thing #77 / Oct 27, 2018](https://weekly.thingelstad.com/archive/77/), Notable Links 📌

## Saved the same week

- [Meow Hash](https://links.thingelstad.xyz/links/60c16e3418ed/) (mollyrocket.com, October 25, 2018)
- [How Minnesota Became the Land of 10,000 Startups - ReadWrite](https://links.thingelstad.xyz/links/9d304521886c/) (readwrite.com, October 25, 2018)
- [How Google Protected Andy Rubin, the ‘Father of Android’ - The New York Times](https://links.thingelstad.xyz/links/d1bcc1e969c1/) (nytimes.com, October 25, 2018)
- [The Google Pixel 3 Is A Very Good Phone. But Maybe Phones Have Gone Too Far.](https://links.thingelstad.xyz/links/561b30c45da7/) (buzzfeednews.com, October 25, 2018)
- [The next career step for Senior Software Engineers (that isn’t management)](https://links.thingelstad.xyz/links/d1848c5fba76/) (codewithoutrules.com, October 25, 2018)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://pdfs.semanticscholar.org/441f/ac7c2020e1c8f0d32adffca697bbb8a198a1.pdf