I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb Yes! Notes to myself make me a much more efficient participant in lots of tasks.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
I just read a note I left for myself two months ago about a job I had to do today. It was so well worded and detailed I couldn't believe it.
It's such a good feeling to see the extra work you put in pay off.
-
I just read a note I left for myself two months ago about a job I had to do today. It was so well worded and detailed I couldn't believe it.
It's such a good feeling to see the extra work you put in pay off.
@eljorgeabides I think from now on when I make a new README I need to add an event two weeks later to check it and add more info if needed.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb Documentation has been one of my mantras to my team at my current job.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb amen. And use version control.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb Yes! I'll write documentation with a voice that assumes someone else will eventually read it, but is primarily for my own benefit.
Also, label makers: my house (and especially the old camper van I've been fixing up for the last 6 months or so) is filled with labels with the theme being "I don't use this often enough to remember this fact but want it to be quickly accessible when I do actually need it".
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb Senior Engineers write a lot of documentation, because they once found their three-line readme from when they were a Junior Engineer and the lack of information fucked them over in an epic way.
-
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb
This, 100%. I have a terrible memory so always make the effort to write good documentation, even if it's just for me. I also create aliases to run/stop/debug the project. -
I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.
I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.
Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.
@rasterweb Yes.
My reaction to my past notes is usually: I did that? -
J jwcph@helvede.net shared this topic
