Skip to content

Instantly share code, notes, and snippets.


Ian Gilkes YenHub

View GitHub Profile
YenHub / websql-example.html
Created Jul 3, 2020 — forked from benpoole/websql-example.html
Javascript & Web SQL example
View websql-example.html
@author Ben Poole,
Example HTML5 code for playing with the local WebKit (Opera too?) SQL database.
<meta charset="UTF-8" />
<title>Winkles Of The World Unite!</title>
YenHub / hyper-v.bat
Last active Feb 12, 2020
Toggle Hyper-V
View hyper-v.bat
@Echo off
setlocal EnableDelayedExpansion
set 1=auto
set 2=off
set 3=exit
echo " __ __ __ __ ";
echo " / | / | / | / | ";
echo " $$ | $$ | __ __ ______ ______ ______ $$ | $$ | ";
echo " $$ |__$$ |/ | / | / \ / \ / \ ______ $$ | $$ | ";
YenHub /
Created Sep 27, 2019 — forked from mdang/
Lesson: SDLC

The Software Development Life Cycle

Learning Objectives


  • Explain what SDLC is and why we use it
  • Provide a general overview of what "Agile" means and compare it to Waterfall
  • Explain what SCRUM is, and how it relates to agile.
  • Describe the process of requirements gathering.
  • Explain what a user story is, and what specific points it should include.
YenHub /
Created Sep 27, 2019 — forked from blackfalcon/
Git basics - a general workflow

There are many Git workflows out there, I heavily suggest also reading the [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

YenHub / .git-commit-template
Created Mar 28, 2019 — forked from zakkak/.git-commit-template
This commit message template that helps you write great commit messages and enforce it across your team.
View .git-commit-template
# [<tag>] (If applied, this commit will...) <subject> (Max 72 char)
# |<---- Preferably using up to 50 chars --->|<------------------->|
# Example:
# [feat] Implement automated commit messages
# (Optional) Explain why this change is being made
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->|
# (Optional) Provide links or keys to any relevant tickets, articles or other resources
# Example: Github issue #23
You can’t perform that action at this time.