Berkhan Berkdemir BerkhanBerkdemir

GitHub Onboarding and Introduction

A guide for getting started and best practices for teams new to, or improving their interactions with, GitHub

GitHub's features and capabilities

This document is meant to help new teams to GitHub familiarize themselves with the features and platform, as well as start to explore some of the best practices. While not a complete exploration, it's meant as a introduction to the key tenets of using GitHub for your business. For teams and organizations that desire more one on one support, GitHub Professional Services has many different options available to customize tools, training, and process to best meet your needs. The GitHub offerings listed in the diagram above are just a sampling of the various capabilities and we'd love to create a customized offering to meet your specific organizational needs.

Overview and Intr

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

"Build tools for others that you want to be built for you." - Kenneth Reitz
"Simplicity is alway better than functionality." - Pieter Hintjens

Today I Learned

There's no doubt that everybody learns every single day. I like to keep track of what I've learned. I'll keep that as short as possible, so you can't get lost in the knowledge ocean.

I keep posted from here and my blog. If you like it, just give a ⭐

BB's One-Liners

I don't want to build yet-another bashoneliners. I just want to write documentation that I find one-liners own mine own. Maybe, I can search in a search engine and find the optimal solution, but I want to solve these problems.

Also, this guide is written for me. So, I will not include your extra one-liners; however, we can fix and improve the usage and documentation for them.

How to find man pages on online

There are a few thousand websites and tools, but I can recommend using www.man7.org.

My RegEx cheatsheet

About

This gist includes what I wrote for my self.

College email validation

/\A[a-z_]{3,}\@(student\.)?college\.edu\z/

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.

	# 1 "src/main.cpp"
	# 1 "/home/john/project//"
	# 1 "<built-in>"
	# 1 "<command-line>"
	# 1 "/usr/include/stdc-predef.h" 1 3 4
	# 1 "<command-line>" 2
	# 1 "src/main.cpp"
	# 1 "include/b.h" 1
	int foo_b(int x);
	# 2 "src/main.cpp" 2

	#!/bin/bash

	read -p "Domain: " domain
	read -p "DB name: " db_name
	read -p "DB pass: " db_password

	apt update
	echo "==================="
	echo "Nginx installing"
	echo "==================="

	<% flash.each do \|message_type, message\| %>
	<div class="alert alert-<%= message_type %> alert-dismissible fade show" role="alert">
	<%= message %>
	<button type="button" class="close" data-dismiss="alert" aria-label="Close">
	<span aria-hidden="true">×</span>
	</button>
	</div>
	<% end %>

	# This is a skeleton for testing models including examples of validations, callbacks,
	# scopes, instance & class methods, associations, and more.
	# Pick and choose what you want, as all models don't NEED to be tested at this depth.
	#
	# I'm always eager to hear new tips & suggestions as I'm still new to testing,
	# so if you have any, please share!
	#
	# @kyletcarlson
	#
	# This skeleton also assumes you're using the following gems: