<commit_before>Next steps
==========


Apply what you have learnt
--------------------------

The only way to learn is to keep practising. Try to think about how to apply
what you have been learning. You will run into problems, working your way
through these problems is the only way to solidify your knowledge.

Think about your day-to-day work and your research. How could they be improved
by scripting and computing? Try to solve problems that are outside of your
comfort zone. This is how you will extend your expertise.


Be social
---------

Find friends and colleges that are in the same boat as you and talk to them
about your computing experiences and the problems that you are trying to solve.
It is much more fun to learn together and you will keep each other motivated.

Find someone more experienced than you and learn from them. Having a mentor
to point you in the right direction can be a great time saver.

Connect with me on twitter `@tjelvar_olsson
<https://twitter.com/tjelvar_olsson>`_ or send me an email. Let me know what
you think of this booklet. I would really value your feedback.


Recommended reading
-------------------

<NAME>'s essay
`Teach Yourself Programming in Ten Years <http://norvig.com/21-days.html>`_
is really interesting. Norvig is the director of research at Google and really
knows what he is talking about. The essay should help you put your learning
into perspective and motivate you when things get tough.

<NAME>eman's
`Linux Phrasebook <http://www.granneman.com/writing/books/linux-phrasebook/>`_
provides a concise reference for learning the foundations of the most important
Unix command line tools.

<NAME> and <NAME>'s
`Pro Git <https://git-scm.com/book/en/v2>`_ book provides a comprehensive guide
to Git. I would recommend that you read chapter two of this book to solidify
your understanding of Git. Many of the other chapters in this book are also
really valuable, in particular chapters three and five.<commit_msg>Added 'Tidy Data' to recommended reading<commit_after>Next steps
==========


Apply what you have learnt
--------------------------

The only way to learn is to keep practising. Try to think about how to apply
what you have been learning. You will run into problems, working your way
through these problems is the only way to solidify your knowledge.

Think about your day-to-day work and your research. How could they be improved
by scripting and computing? Try to solve problems that are outside of your
comfort zone. This is how you will extend your expertise.


Be social
---------

Find friends and colleges that are in the same boat as you and talk to them
about your computing experiences and the problems that you are trying to solve.
It is much more fun to learn together and you will keep each other motivated.

Find someone more experienced than you and learn from them. Having a mentor
to point you in the right direction can be a great time saver.

Connect with me on twitter `@tjelvar_olsson
<https://twitter.com/tjelvar_olsson>`_ or send me an email. Let me know what
you think of this booklet. I would really value your feedback.


Recommended reading
-------------------

<NAME>'s essay
`Teach Yourself Programming in Ten Years <http://norvig.com/21-days.html>`_
is really interesting. Norvig is the director of research at Google and really
knows what he is talking about. The essay should help you put your learning
into perspective and motivate you when things get tough.

<NAME>'s
`Linux Phrasebook <http://www.granneman.com/writing/books/linux-phrasebook/>`_
provides a concise reference for learning the foundations of the most important
Unix command line tools.

<NAME>'s article
`Tidy Data <http://vita.had.co.nz/papers/tidy-data.pdf>`_
describes the concept of "Tidy Data" in detail along with background,
motivation and case studies. It is an accessible read and will give you the
tools required to structure your data so that it can be visualised directly
by ggplot2.

<NAME> and <NAME>'s
`Pro Git <https://git-scm.com/book/en/v2>`_ book provides a comprehensive guide
to Git. I would recommend that you read chapter two of this book to solidify
your understanding of Git. Many of the other chapters in this book are also
really valuable, in particular chapters three and five.
{'fraction_non_alphanumeric': 0.07575403320084172, 'fraction_numerical': 0.0016366612111292963, 'mean_word_length': 3.7798882681564248, 'pattern_counts': {'":': 0, '<': 21, '<?xml version=': 0, '>': 21, 'https://': 4, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7182265', 'n_tokens_mistral': 1115, 'n_tokens_neox': 1071, 'n_words': 643}