Je cherche à vous aider à atteindre vos objectifs #code en #français . My goal is to help you work faster by sharing what I know about #SQL, #Python, and #Salesforce in #English and #French
The "Programming 101" notes are each in their own week-by-week Word document under a "101" folder under "grad school," same for OS, etc. I didn't really need to study them beyond the midterms, and later, I just need to remember where to find them when the subject comes up.
I suppose that's part of why I blog -- like the "git brain dump" I wrote last week.
I was just walking around the house thinking I should edit that post -- I thought of a new definition to add.
(If "git" is spyware that spies on folders you tell it to and calls them "repositories," then a "repository" is a folder you've told "git" software to spy on. Although "git" doesn't necessarily keep a big log of everything you've ever asked it to spy on -- it does it more "on demand" as long as the folder has certain types of "Hey, git, come spy on me!" folders & files in it -- so I suppose a folder can be a "repository" even if Git has been uninstalled from a computer? But then ... if a tree falls in the woods and no one hears it, does it make a sound? If no Git can possibly spy on a folder, is it still a repository?) :-)
Anyway, I feel like they work better segmented in their own contexts, the same way each book on a topic might have its own glossary that works best for that book's audience (vs. an encyclopedia entry, which tries to cover every possible question someone could have about something but then gets really long-winded).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You know, I don't!
The "Programming 101" notes are each in their own week-by-week Word document under a "101" folder under "grad school," same for OS, etc. I didn't really need to study them beyond the midterms, and later, I just need to remember where to find them when the subject comes up.
I suppose that's part of why I blog -- like the "git brain dump" I wrote last week.
I was just walking around the house thinking I should edit that post -- I thought of a new definition to add.
(If "git" is spyware that spies on folders you tell it to and calls them "repositories," then a "repository" is a folder you've told "git" software to spy on. Although "git" doesn't necessarily keep a big log of everything you've ever asked it to spy on -- it does it more "on demand" as long as the folder has certain types of "Hey, git, come spy on me!" folders & files in it -- so I suppose a folder can be a "repository" even if Git has been uninstalled from a computer? But then ... if a tree falls in the woods and no one hears it, does it make a sound? If no Git can possibly spy on a folder, is it still a repository?) :-)
Anyway, I feel like they work better segmented in their own contexts, the same way each book on a topic might have its own glossary that works best for that book's audience (vs. an encyclopedia entry, which tries to cover every possible question someone could have about something but then gets really long-winded).