<commit_before>---
layout: essay
type: essay
title: I Have Standards
date: 2016-09-22
labels:
  - Standards and Practices
  - Coding Standards
  - CSS
---

<img class="ui medium right floated rounded image" src="../images/keep_off_the_grass.jpg">
<commit_msg>added coding standards essay body text<commit_after>---
layout: essay
type: essay
title: I Have Standards
date: 2016-09-22
labels:
  - Standards and Practices
  - Coding Standards
  - CSS
---

<img class="ui medium right floated rounded image" src="../images/keep_off_the_grass.jpg">

For a while, I’ve been curious about coding standards in different organizations. How do successful tech companies like google organize their code? I’ve used their standards in previous website projects, but it seems like many times good standards are unclear or hard to find.

I see great value in coding standards; they provide order and improve collaboration and compatibility between different systems.

I like the way code standard checking is automated in an IDE like IntelliJ IDEA. The way an IDE streamlines and automates so many aspects of programming is very helpful.

Some of the standards in the .eslintrc files contrast with my style, but also make me rethink how I should code. Sometimes I like to add spaces between parentheses nested in other parentheses, and the eslint file flags uses of that practice. If I can figure out my own standard, I could probably create my own eslint file.
{'fraction_non_alphanumeric': 0.05674740484429066, 'fraction_numerical': 0.011072664359861591, 'mean_word_length': 4.2773722627737225, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, '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': '2102530', 'n_tokens_mistral': 386, 'n_tokens_neox': 354, 'n_words': 207}