This is the reference point. All the other options are based off this.
|-- app
| |-- controllers
| | |-- admin
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 1000)
#Social Media Strategy
##About the Project
This was inspired by the Tiny Content Framework that focuses on “goals, messages, and branding.”
The Social Media Strategy collection is aimed at helping companies get started in planning their approach to social media. This is a bit of a template, and sprinkled with examples in each category. It should be a good starting point before a business dives head-first into whatever fancy social media outlet may be hot at the moment. (Tip: Find out what medium/outlet is best suited for your audiences before blindly signing up for accounts for whatever is the most popular at the moment. We used to think MySpace was going to rule the Earth for a while, until it faded into the background and gave way to Twitter, Facebook and the rest of the photo-sharing ones.)
##Contribute
##Setup your server (this would ideally be done with automated provisioning)
npm install -g forever
##Install flightplan
npm install -g flightplan
npm install flightplan --save-dev
While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.
Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.
lib/
is intended for code that can run as-issrc/
is intended for code that needs to be manipulated before it can be used// Random terminal tip #1 | |
//You'll see this message if you git commit without a message (-m) | |
// You can get out of it with two steps: | |
// 1.a. Type a multi-line message to move foward with the commit. | |
// 1.b. Leave blank to abort the commit. | |
// 2. Hit "esc" then type ":wq" and hit enter to save your choice. Viola! | |
# Please enter the commit message for your changes. Lines starting | |
# with '#' will be ignored, and an empty message aborts the commit. |
As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
Picking the right architecture = Picking the right battles + Managing trade-offs
rebase
vs merge
).rebase
vs merge
)reset
vs checkout
vs revert
)git rev-parse
)pull
vs fetch
)stash
vs branch
)reset
vs checkout
vs revert
)