Did you know that researchers spend about half of their professional lives doing academic and technical writing? For example, research students spend at least a third of their studies writing their theses, without counting papers, and bids for grants.
Technical writing includes a lot of different types of texts, such as scientific papers, technical reports, manuals, tutorials, and so on.
Things I have done
I have some experience in writing technical reports and tutorials, and my refereed publications are evidence that I can write at an academic level. Here are some examples.
- Series of “Learn to code” posts on my personal blog (in Italian)
- Series on Drupal for the Italian magazine Linux&C, in issues 73, 74, 75
- Series on Inkscape for the Italian magazine Linux&C, in issues 64, 67
Other (more or less) technical writing
- The #VIZcoin revolution (hackernoon.com)
- Kotlin is cheating on me… (hackernoon.com)
- Android is hard (hackernoon.com)
- How I messed up my artsy app’s launch (hackernoon.com)
- How I made an artsy app based on science (medium.com)
- A. Franceschini, R. Laney, C. Dobbyn (2016) “Sketching music: making music through exploring art”. In Proceedings of Sempre: Music, Education, Technology (MET2016), London, UK.
- Franceschini, Andrea, Robin Laney, and Chris Dobbyn. (2014). “Learning musical contour on a tabletop”. Joint ICMC/SMC 2014, Athens, Greece.
- Franceschini, Andrea. (2010). “Towards a practical approach to music theory on the Reactable”. SMC 2010, Barcelona, Spain.
Other academic works
Need something written? Get in touch!