Chapin Bryce chapinb

name	intentional-design
description	Use when starting a feature or facing a decision with meaningful tradeoffs -- researches options, clarifies intent, proposes approaches, and decides before any code is written. Skip for small or obviously clear changes.

Intentional Design

Overview

Think before building. Understand the problem, surface tradeoffs, pick the right approach. The output is a decision and a direction -- not a document. Hand off to intentional-development immediately after.

name	intentional-development
description	Use when starting a new feature, approaching an unfamiliar problem, or deciding how to structure code -- guides the full workflow from uncertain start to clean implementation

Intentional Development

Overview

Code with purpose. Know why every line is there. Understand the end-to-end path before filling in details. Prove behavior with tests. Design modules so their interface is simpler than their implementation.

Here are some free resources to improve your software development skills, in no particular order.

Programming

roadmap.sh
- Free learning paths across multiple domains. The "Start Here" on the top menu bar is a great place to start.
Git Internals
- Learn how git works under the hood. Not only is it the most common version control system, it has a well thought out interface and backend.
Practical Python Course
David Beazley's popular python course, setting a foundation in using Python for a variety of tasks.

	#!/bin/bash

	## Please insert the appropriate User and IP address values
	## You may also need to edit the path to where your PCAPs
	## exist on the remote system
	echo ===== Pulling remote pcap data
	rsync -a <USER>@<IP>:/data/rdp..pcap /data/pcap/
	echo rsync exit code: $?

	## This script is available at:

	FROM adoptopenjdk/openjdk11:slim

	RUN apt update &&\
	apt install -y curl nginx

	# SETUP NGINX PROXY

	COPY default.nginx.conf /etc/nginx/sites-available/default

	# SETUP ELASTIC 7.5.1

	#!/usr/bin/env bash

	# Tested on Debian 10 (Buster)

	# Make a report folder
	outdir=bro-`date +%FT%H-%M-%S`
	mkdir $outdir

	# Generate our reports with bro in the report folder
	cd $outdir

	# Homebrew, install at brew.sh
	alias binfo='brew info'
	alias bupdate='brew update'
	alias bupgrade='brew upgrade'
	alias bsearch='brew search'

	# Git
	alias gitu='git add -u'
	alias gitc='git commit'
	alias gits='git status -uno'

	# -- coding: utf-8 --
	"""Script to check the TrustRecords key for documents with enabled macros

	Prior research/tools:
	- http://az4n6.blogspot.com/2016/02/more-on-trust-records-macros-and.html
	- http://windowsir.blogspot.com/2012/07/links-and-updates.

	Other tools support parsing this key (ie RegRipper plugin TrustRecords) though
	it's always useful to have more options to parse an artifact. This is just
	another take on extracting value from this registry key with the hope of

	{
	"query_seconds": 0.114051,
	"records": {
	"13.52.4.25": {
	"message": "",
	"results": [
	{
	"cidr": "13.52.0.0/16",
	"first_collected": "2017-09-08T16:27:01",
	"last_collected": "2019-01-13T08:00:01",

	$ fgrep Invalid\ user auth.log \| head -n 5 \| awk '{ print $10 }' \| ursort
	3 180.211.137.8
	2 188.165.201.89