Monday, July 8, 2019

Using Unit Tests for Communication

Expressing software requirements is hard. Software is abstract and intangible, you can't touch it see it or feel it, so talking about it can become very difficult.

There are plenty of tools and techniques that people use to make communicating about software easier like UML diagrams or software state diagrams. Today I'd like to talk about a software development technique my team has been using for communication: Test Driven Development.

Wednesday, June 5, 2019

I was featured on the AWS Blog!

Hello everyone,

Shameless self plug here, I was recently featured on the AWS blog:

https://aws.amazon.com/blogs/mt/how-docutap-automates-cloud-operations-using-aws-management-tools/

The post covers some of the techniques we use for configuration management at my company, many of which I helped design.

Thanks for giving it a read through!

Monday, May 13, 2019

Docker Windows container for Pester Tests

I recently wrote an intro to unit testing your powershell modules with Pester, and I wanted to give a walk through for our method of running these unit tests inside of a Docker for Windows container.


Wednesday, April 10, 2019

AWS S3 Lifecycle Policies - Prep for Deep Archive

AWS recently released a new S3 storage class called Deep Archive. It's an archival data service with pretty low cost for data you need to hold onto, but don't access very often.

Deep Archive is about half the cost of Glacier at $0.00099 per GB per month, but you sacrifice the option to get your data back in minutes, your only retrieval option is hours.


Sunday, March 10, 2019

Unit Testing PowerShell Modules with Pester

Pester is a unit testing framework for Powershell. There are some good tutorials for it on their github page, and a few other places, but I'd like to pull together some of the key motivating use cases I've found and a couple of the gotchas.

Saturday, February 16, 2019

Graph Your RI Commitment Over Time (subtitle: HOW LONG AM I PAYING FOR THIS?!?!?)

In my last post I talked about distributing your committed RI spend over time. The goal being to avoid buying too many 1 year RIs (front loading your spend), and missing out on the savings of committing to 3 years, but not buying too many 3 year RIs (back loading your spend) and risking having a bill you have to foot if your organization has major changes.

Friday, February 1, 2019

Our RI Purchase Guidelines

I've talked about it a couple of times, but AWS's recommendation engine is free and borderline magic.

It's a part of AWS Cost Explorer and ingests your AWS usage data, and spits back reserved instance recommendations