As a software developer, there will be times you are given a task to create the

As a software developer, there will be times you are given a task to create the code behind a set of requirements.  Once you finish that work, you move to another.  Your original code goes into production.  If it turns out you have a bug in the code you wrote, you might get it back or an Operations & Maintenance (O&M) will fix it.  Our code will more than likely contain many functions.  Regardless of who gets the code to fix, there is a good chance you won’t remember what you did.  This is where the dreaded comments come into play.  Engineers and developers really don’t like to write documentation as they think the code is self-explanatory.  Many times this is true and we don’t want to documentation code JUST to document.  Research online the best practices for code documentation.  I would expect at least 2-3 paragraph