Skip to content

Instantly share code, notes, and snippets.

View chriseaton's full-sized avatar
🐢
Soup

Christopher Eaton chriseaton

🐢
Soup
View GitHub Profile

Programmatic Naming Convention Cheat Sheet

This cheatsheet is, shockingly, for programmers using programming languages to program.
Below are examples of the best naming conventions used in the programming world.

Note

You may have different thoughts on this, but they are wrong.

It's time to get with the program... ☜(⌒▽⌒)☞
These are the naming conventions that have bubbled-up through the decades as the most proficient and ideal, which is why they are some common today.

# use grep to search the output of the file for specific terms.
# the `-n` flag will output line numbers to the left of matches.
cat some.log | grep -n "Looking for..."
# you can then use the line number to find the entries on and around the entry.
# Note the line-number is used, as well as a count to includes a number of lines after.
# In this example, we're looking at lines starting at 3176101 and the +10 lines after.
sed -n '3176101,+10p' app.log
#on the server
sudo dnf install git gettext-devel openssl-devel perl-CPAN perl-devel zlib-devel -yy
sudo useradd git -mr
sudo su -c "git config --global init.defaultBranch master" git
sudo su -c "chmod 700 ~/.ssh && touch ~/.ssh/authorized_keys && chmod 644 ~/.ssh/authorized_keys" git
# MANUAL STEP
# add your pub key to /home/git/.ssh/authorized_keys
# if you want to explicitly allow certain users over SSH, you can use "AllowUsers".