<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, May 25, 2017 at 1:25 PM, DJ-Pfulio <span dir="ltr"><<a href="mailto:DJPfulio@jdpfu.com" target="_blank">DJPfulio@jdpfu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/25/2017 01:08 PM, Joey Kelly wrote:<br>
>> In fact, my initial code is usually a page of comments describing what<br>
>> needs to happen, in order. Then each of those comments usually becomes a<br>
>> function. If a function gets too long, more comments are written and<br>
>> more sub-functions are made, about 5-20 lines at a time.<br>
><br>
> A lot of my code is exactly like that... document first, code later.<br>
<br>
</span>For non-trivial programs, each comment might be an entire class, if<br>
doing OO.<br>
<br>
I actually do it to help remember where I left off the next day or the<br>
following week after being interrupted. Sleeping helps wipe memories.<br>
This isn't something new caused by age. When I coded in my 20s, it was<br>
good to have reminders too. ;)<br></blockquote><div><br></div><div> </div><div>My comments tend to be something like "this broke stuff" and "get rid of this". I try to avoid things that would be embarassing after a "git push". :)</div></div><br></div></div>