<commit_before><commit_msg>Update file<commit_after><!DOCTYPE html>

<title>1.7 Technical Blog</title>

  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">


<main>
  <h1>Reflections</h1>
  <h2>An introduction to version control</h2>
  <h4>Jan 4th 2016</h4>
<article><h2>This is the heading's big bro</h2>
  <section>
<h3>This is the heading</h3>

      <header>What are the benefits of version control?</header>

      Version control allow software developers to have the ability to have
      a history of the changes made to a software project. This is beneficical
      in many ways, including the freedom to work on new features without
      having to worry about breaking the master copy of the software.

      The master copy, or 'master branch' is the latest working copy of the
      software. When working with a team, several developers can be working
      at the same time by using version control, and they can keep track
      of who makes what.


        How does git help you keep track of changes?

        Git helps you create new branches of your project, and there is a
        specific process one must go through in order to merge the new branch
        back into the master branch.

        With git, you create a copy of the project and then make changes to
        it. When you make changes to the project, it is best practice to
        summarize the details of the changes. This way, new developers can be
        caught up to speed when joining a project.

        You can check the git log to see all the changes that have been made
        in the project's history.

    <aside>
    25,000 engineers collaborating in one huge code repository sounds like a logistical nightmare. Could one sleep-deprived, grumpy developer make a single tiny mistake and take down the one thing (Google Hangouts) getting millions of Millennials through the workday? Is there a conference room large enough to house 25,000 developers working on the same project each day? Are thousands of man-hours wasted in duplicative work each day due to communication lapses across the 25,000 code maestros? Thankfully for us and for Google, there’s git.
    </aside>
    <p>
        Why use GitHub to store your code?

        Because GitHub is a social site used by developers all around the world,
        and is an implementation of git on the web. You can work on a software
        project from different machines, and developers who may not be in your
        network can do the same.

        GitHub features an easy to use interface and can be customized with a
        profile, allowing developers to showcase their own uniqueness.
    </p>
      <!-- copy and paste as many sections as you want to add paragraphs -->
  </section>
  </article>
</main>
<!-- this is my comment section -->
{'fraction_non_alphanumeric': 0.05130927105449398, 'fraction_numerical': 0.01132342533616419, 'mean_word_length': 3.0213371266002844, 'pattern_counts': {'":': 0, '<': 31, '<?xml version=': 0, '>': 31, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, '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': '201108', 'n_tokens_mistral': 731, 'n_tokens_neox': 684, 'n_words': 412}