<commit_before>---
layout: essay
type: essay
title: Why your code isn't working.
date: 2017-09-21
labels:
  - Engineering
  - Reflection
  - Coding Standards
---

<img class="ui centered middle image" src="../images/clean.png">

  We've all had the experience of reading somebody else's code and think "how does this possibly work", and that's reality, everyone adapts a different coding standard. For those who are not familiar with coding standards (which I hope you are), they are just specified guidelines and rules that are used in formating source code, pulled from <a href="http://www.valid-computing.com/benefits-of-coding-standards.html">http://www.valid-computing.com/benefits-of-coding-standards.html</a>. Coding standards are really effective in making source code look "clean" which is really important for anyone learning a new programming language, or for team developments.

  Learning a new language is already hard as it is, but the difficulty factor increases drastically by reading a poorly written source code. This does not only apply to programming languages but for anything else you learn for a first time. Seeing something performed a sloppy way, can easily hinder your growth in that field. Reading poorly written code will lead to confusion while trying to analyze code, and it will take a longer time period in order to process the new material. Then, once you finally understand the code, you will eventually adapt that exact same coding standard. This will ultimately lead to poor coding standards produced by you which you will carry out through your coding career,  just like "monkey see monkey do". This will not be the case if you practice reading good coding standards and change your style as soon as possible. 

    
  Having "clean" looking code has never been so important than when you're working on a team project / development. How do you expect someone to add to your code when they don't even understand it? It's almost impossible. With good coding standards, your team members will benefit because, they'll be able to spend more time adding and improving your code, than constantly asking you what each line means and becoming frustrated.  This will lead to more productivity and ultimately nicer looking code for anyone else that decides to read it. Adding onto the first claim, with less confusion in your code, your team members will have a much less stressful time finding bugs in your code. Isn't that great, you'll have more helping hands and people won't be discouraged to get a crack at your problem. 

  As to wrap it up, I believe that having good coding standards will help others out, whether it's for beginners or even for people that you work with. It's always best to remind yourself whether someone else will be able to read your code as well as you'<commit_msg>Update whyyourisntcodeworking.md<commit_after>---
layout: essay
type: essay
title: Why your code isn't working.
date: 2017-09-21
labels:
  - Engineering
  - Reflection
  - Coding Standards
---

<img class="ui centered middle image" src="../images/clean.png">

  We've all had the experience of reading somebody else's code and think "how does this possibly work", and that's reality, everyone adapts a different coding standard. For those who are not familiar with coding standards (which I hope you are), they are just specified guidelines and rules that are used in formating source code, pulled from. Coding standards are really effective in making source code look "clean" which is really important for anyone learning a new programming language, or for team developments.

  Learning a new language is already hard as it is, but the difficulty factor increases drastically by reading a poorly written source code. This does not only apply to programming languages but for anything else you learn for a first time. Seeing something performed a sloppy way, can easily hinder your growth in that field. Reading poorly written code will lead to confusion while trying to analyze code, and it will take a longer time period in order to process the new material. Then, once you finally understand the code, you will eventually adapt that exact same coding standard. This will ultimately lead to poor coding standards produced by you which you will carry out through your coding career,  just like "monkey see monkey do". This will not be the case if you practice reading good coding standards and change your style as soon as possible. 

    
  Having "clean" looking code has never been so important than when you're working on a team project / development. How do you expect someone to add to your code when they don't even understand it? It's almost impossible. With good coding standards, your team members will benefit because, they'll be able to spend more time adding and improving your code, than constantly asking you what each line means and becoming frustrated.  This will lead to more productivity and ultimately nicer looking code for anyone else that decides to read it. Adding onto the first claim, with less confusion in your code, your team members will have a much less stressful time finding bugs in your code. Isn't that great, you'll have more helping hands and people won't be discouraged to get a crack at your problem. 

  As to wrap it up, I believe that having good coding standards will help others out, whether it's for beginners or even for people that you work with. It's always best to remind yourself whether someone else will be able to read your code as well as you'
{'fraction_non_alphanumeric': 0.040014484881405035, 'fraction_numerical': 0.002896976281006699, 'mean_word_length': 4.363106796116504, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, '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': '3929767', 'n_tokens_mistral': 1258, 'n_tokens_neox': 1181, 'n_words': 872}