Skip to content

Instantly share code, notes, and snippets.

View elovelan's full-sized avatar

Eric Loveland elovelan

View GitHub Profile

TODO.it Requirements

TODO.it is a simple command line application designed to capture and manage TODO tasks from the command-line. Designed as a beginner ruby challenge.

Any thing marked in (( double parenthasis )) are examples or ideas for the challenger to pick.

The app must

  • Accept input from the command ((an input prompt or command-line arguments))
  • Display active tasks
Function PrintDetails
{
Param (
$ComputerName,
$DriveLetter = "",
$VolumeName = "",
$Error = ""
)
$obj = New-Object PSObject
@elovelan
elovelan / 0_reuse_code.js
Created February 18, 2017 03:59
Here are some things you can do with Gists in GistBox.
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console
@elovelan
elovelan / Get-ParameterValues.ps1
Created October 10, 2018 19:05 — forked from Jaykul/Get-ParameterValues.ps1
Rather better than `$PSBoundParameters`
function Get-ParameterValues {
<#
.Synopsis
Get the actual values of parameters which have manually set (non-null) default values or values passed in the call
.Description
Unlike $PSBoundParameters, the hashtable returned from Get-ParameterValues includes non-empty default parameter values.
NOTE: Default values that are the same as the implied values are ignored (e.g.: empty strings, zero numbers, nulls).
.Link
https://gist.github.com/Jaykul/72f30dce2cca55e8cd73e97670db0b09/
.Link
@elovelan
elovelan / README.md
Created April 14, 2020 16:37 — forked from mbbx6spp/README.md
Gerrit vs Github for code review and codebase management

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

  • Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
  • Atomic/related changes all in one commit is something worth striving for. Having your dev