Integralist

• Install
• Shell exports
• Directory explanations
• Automatic Imports
• Private repo access
• Guard (automatic go run)
• Godo
• Spurious
• AWS SDK with Go (inc. some old possibly broken examples)
• Build and Compilation

Integralist

# pylint: disable-all
# flake8: noqa

import sys
import socket
import getopt
import threading
import subprocess

listen = command = upload = False

Integralist

There are two 'types' to be aware of with a quickfix window:

1. entry: the actual line content (e.g. :grep foo will show a specific line that matched within a file).
2. file: the actual file itself (e.g. the path to the file that contained the match).

To replace content using vim (via the quickfix window) you need to choose whether you want to apply the change via the quickfix 'entry' or via the 'file' as a whole.

If you use cdo, then your 'action' (i.e. how you're going to replace content) will be applied to every entry in the quickfix window.

If you use cfdo, then your action will be applied to each file in the quickfix window.

Integralist

name: Update Dependencies and Run Tests

on:
  # Schedule to run at 9am UTC every day
  schedule:
    - cron: '0 9 * * *'

  # Allow manual trigger via GitHub UI
  workflow_dispatch:

Integralist

Here is an example that demonstrates how groups work and how they can be nested! https://play.golang.com/p/F3lBGUhfVkM

package main

import (
	"context"
	"log/slog"
	"os"

Integralist

Two of my favour features in Go are:

1. io.TeeReader(r, w)
2. pr, pw := io.Pipe()

TeeReader will write to w every time there is a read from r.

Pipe will read from pr every time there is a write to pw.

To consume from a single reader twice:

Integralist

curl --header 'Authorization: token INSERTACCESSTOKENHERE' \
     --header 'Accept: application/vnd.github.v3.raw' \
     --remote-name \
     --location https://api.github.com/repos/owner/repo/contents/path

# Example...

TOKEN="INSERTACCESSTOKENHERE"
OWNER="BBC-News"
REPO="responsive-news"

Integralist

SKU stands for stock-keeping unit.

It is mostly the unit used by Salesforce, and all other business systems to 'sell' and invoice for products/features we sell

It can take up to a quarter or more to get a SKU.

You can't sell something for $$ without a SKU.

Monetization engineering often won't get started on any work without a SKU/product description in Salesforce.

Integralist

We had a bug where a line [manifest_version] was being added by accident.

Integralist

Rules for good testing

Look at the following image...

...it shows an object being tested.

You can't see inside the object. All you can do is send it messages. This is an important point to make because we should be "testing the interface, and NOT the implementation" - doing so will allow us to change the implementation without causing our tests to break.