Skip to content

Instantly share code, notes, and snippets.

View gryte's full-sized avatar

Adam Linkous gryte

  • CapitalOne
  • Texas
View GitHub Profile
@gryte
gryte / recruiter_response.md
Last active April 1, 2016 16:47 — forked from dougireton/recruiter_response.md
I've started responding to recruiters with this list of requirements

Company Requirements

I'm definitely not looking for work. However to provide some helpful guidance for hiring like-minded engineers, I would only consider working for a company if it met these requirements:

  1. Concrete, measurable plan to increase the number of women and minorities in engineering roles.
  • Commitment to using and contributing to open source.
  • Collaborative, friendly atmosphere where pair programming is encouraged.
  • Meaningful work with clear linkage between work and company goals.
  • Demonstrated commitment to ethical business practices, e.g. B corp certification.
  • Commitment to career development including yearly conferences.
@gryte
gryte / doc_workinstruction_scope.md
Created March 9, 2016 21:50
Define the scope of any work instruction (what does 'done' look like when creating one)

Goal as it pertains to writing a work instruction

Your peers should be able to recreate your steps and achieve the same results everytime.

@gryte
gryte / logging_notes.md
Last active January 4, 2016 16:00
logging_notes

DESIGNING FOR AUDITABILITY [1]

  • Every tool or script you run should create a log event.
  • The log event should include as much meta-data as possible, but start with who, what and when.
  • These log events should be centralized into something like Logstash.
  • Adopt JSON as your logging format.
  • Incrementally improve things over time. This is not a big project to take on.
Citations
@gryte
gryte / git_commit_tmpl.txt
Created December 31, 2015 16:26
Commit Guidelines
Short (50 chars or less) summary of changes
More detailed explanatory text, if necessary. Wrap it to
about 72 characters or so. In some contexts, the first
line is treated as the subject of an email and the rest of
the text as the body. The blank line separating the
summary from the body is critical (unless you omit the body
entirely); tools like rebase can get confused if you run
the two together.
@gryte
gryte / pesterCommon.ps1
Created August 25, 2015 17:17
pester_common
# Create test scaffolding
New-Fixture -Path HelloWorldExample -Name Get-HelloWorld
@gryte
gryte / slack_remind
Created August 11, 2015 14:43
Reminder
/remind me at 8:30 tomorrow to remember you are happiest when you're creating, building, or taking things apart so that you learn more about how they work
@gryte
gryte / powershell_nano.ps1
Last active September 29, 2015 20:56
Microsoft Nano Server - Misc Commands
<#
This is a hodge-podge of various but useful commands that I've discovered
while exploring what nano has to offer. I expected these commands to change and
often.
#>
# Enable powershell remoting if it is not already enabled
Enable-PSRemoting -Force
# You may change "*" to the name or IP of the machine you want to connect to
@gryte
gryte / storyTemplate_jira.txt
Last active January 2, 2020 04:44
Story Template - Various Markup Syntax
*AS A:* user of some sort
*I WANT:* accomplish something here
*SO THAT:* justify here
*WE'LL KNOW WE ARE DONE WHEN:*
* goal 1
* goal 2
* goal next
@gryte
gryte / vagrant_cmdList.txt
Last active August 29, 2015 14:23
Common Vagrant Commands
# List vagrant box files downloaded
vagrant box list
# Remove vagrant box files
vagrant box remove <name from list>
# Get global status of vagrant environments to find any outliers
vagrant global-status
# Destroy vagrant box instance
@gryte
gryte / devWrkstnConfig.ps1
Last active September 15, 2015 10:42 — forked from ncerny/gist:8d4aa3696e460668518f
Windows Workstation Config for Dev Environment for Chef Cookbooks
# launch powershell with admin privileges
# run:
# install chocolately
iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
# update to WMF 5 & powershell version 5
choco upgrade powershell -pre
# reboot machine
# launch powershell with admin privileges