dougireton

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. Fewer than 250 employees.
2. Concrete, measurable plan to increase the number of women and minorities in engineering roles.
3. Commitment to using and contributing to open source.
4. Collaborative, friendly atmosphere where pair programming is encouraged.
5. Meaningful work with clear linkage between work and company goals.
6. Demonstrated commitment to ethical business practices, e.g. B corp certification.

dougireton

#!/usr/bin/env ruby

# check for whitespace errors
git_ws_check = `git diff-index --check --cached HEAD --`
unless $?.success?
  puts git_ws_check
  exit 1
end

COOKBOOK_PATH = File.split `git rev-parse --show-toplevel`

dougireton

# Copyright 2015 Nordstrom, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,

dougireton

# Description: Boxstarter Script
# Author: Jess Frazelle <jess@linux.com>
# Last Updated: 2017-09-11
#
# Install boxstarter:
# 	. { iwr -useb http://boxstarter.org/bootstrapper.ps1 } | iex; get-boxstarter -Force
#
# You might need to set: Set-ExecutionPolicy RemoteSigned
#
# Run this boxstarter by calling the following from an **elevated** command-prompt:

dougireton

---
AWSTemplateFormatVersion: '2010-09-09'
Description: 'Cloudformation stack to manage permission to deploy a serverless service'

Parameters:
  ServiceName:
    Description: Name of the Service you want to deploy
    Type: String

Resources:

dougireton

Per our discussion today we have the following recommendations:

1. Pick a single easy server “role” to automate, e.g. my_web_server.
Get that cookbook installing a single package a single Windows Feature, across all of your environments, including Prod. 

2. Then rapidly iterate on that cookbook adding features and deploying through all environments, including Prod. 
Build a regular habit of code review. Every change should be reviewed by another engineer.
Feel free to include Chef team engineers on Pull Requests.

3. Ideally you start writing simple tests with the cookbook, which our Cookbook Pipeline will execute on every Git push and merge.

dougireton

{
  "chefdk_bootstrap" : {
    "package" : {
      "atom" : false,
      "git" : false,
      "iterm2" : false,
      "vagrant" : false,
      "chefdk_julia" : false
    }
  }

dougireton

# https://github.com/opscode-cookbooks/windows

# create a printer
windows_printer 'HP LaserJet 5th Floor' do
  driver_name 'HP LaserJet 4100 Series PCL6'
  ipv4_address '10.4.64.38'
end

dougireton

# include Windows::Helper from Opscode Windows Cookbook
::Chef::Recipe.send(:include, Windows::Helper)

# now you can call helper methods like win_friendly_path directly
my_batch_file = win_friendly_path(
                     ::File.join( node['cookbook']['batch_dir'],'foo.bat'))

execute "My batch file" do
  command my_batch_file
  creates "e:/logs/my_batch_file.log"

dougireton

locate_sysnative_cmd("dism.exe")