And so on, and so forth. Please, guys, if you write a blog post, add some context!
And so on, and so forth. Please, guys, if you write a blog post, add some context!
README files are very, very old. As old as packaging software. To give you an idea of just how old they are, the file name is in all-capitals because when they were first used there were no lowercase letters in file names.
The file would be called README and it would be referred to as a 'README' in docs. We just kept it as all-uppercase with modern operating systems with lower-case characters because being uppercase kept them at the top of directory listings.
GitHub picked it up as the default description page because these files became standards in code packages, definitely didn't happen the other way around - with README becoming more popular with GitHub!
There's only one "kind" of repository generally referred to in programming topics.
> Surely, the repositories at my company don't have readmes
Good lord, why not?! Mine do!
> When you join a team, the rest of the team is the readme.
What nonsense. That is a horrible, inefficient use of resources. Stop it now, you're wasting time and, hence, money. There is no reason to keep walking new developers through the same steps and answering the same questions over and over again. Write a README! And a HACKING!