veyepar: PhD not required: a layperson's guide to reading journal articles

Author(s):	Julia Duimovich
Location	Mystic Theatre
Date	nov Sun 03	Days Raw Files
Start	13:30	First Raw Start	13:03
Duration	0:30:0	Offset	0:26:46
End	14:00	Last Raw End	14:03
Chapters	00:00 0:01:23
Total cuts_time	22 min.

https://2019.northbaypython.org/schedule/presentation/11/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf PhD_not_required_a_laypersons_guide_to_reading_journal_articles.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Despite having "learned" how to read a journal article in school, the skill stopped at reading - I didn't really know how to apply what I'd learned to my professional practice. I could read an article on byte code optimization and then go back to work without gaining any practical takeaways.  I felt so discouraged because I wasn't really getting anywhere. Once you've read something, you need to be able to use it in some way, or else it becomes trivia. And it takes time to build this skill. 
Developing it has huge benefits, however - building your base knowledge of the field,  discerning what is bragging and what has technical value, engaging with proposals that are out of your area of expertise, designing experiments, and improving your technical writing. 
Specifically, I'll be reviewing a paper on reverse debugging to demonstrate some techniques. You can follow along here if you'd like, although it is not recommended that you read the paper in advance. https://www.usenix.org/system/files/osdi18-cui.pdf

The gap between industry & academics is wide and tough to bridge.  Not only are journal articles intimidating, they aren't always topical to software engineers. However, there are a ton of benefits to reading journal articles if you know what and how to read them. You'll leave this talk wanting to find yourself a journal article or two, a beverage, and a quiet space so you can learn something new!

Comment:

production notes