Skip to content

Instantly share code, notes, and snippets.

@aviflax
aviflax / 1 - Resources for Learning Stream Data Processing.md
Last active April 21, 2024 21:29
Resources for Learning Stream Data Processing

Introduction

This gist started with a collection of resources I was maintaining on stream data processing — also known as distributed logs, data pipelines, event sourcing, CQRS, and other names.

Over time the set of resources grew quite large and I received some interest in a more guided, opinionated path for learning about stream data processing. So I added the reading list.

Please send me feedback!

[
// // Evaluate
{"keys": ["ctrl+enter"],
"command": "clojure_sublimed_eval",
"context": [{"key": "selector", "operator": "equal", "operand": "source.clojure"}]},
// // Evaluate Buffer
{"keys": ["ctrl+b"],
"command": "clojure_sublimed_eval_buffer",
"context": [{"key": "selector", "operator": "equal", "operand": "source.clojure"}]},
@aviflax
aviflax / homebrew formulae and casks.md
Last active November 8, 2023 23:08
My Homebrew Formulae & Casks

Leaves

$ brew leaves --installed-on-request
actionlint
aws-iam-authenticator
babashka/brew/obb
bat
borkdude/brew/babashka
borkdude/brew/carve
{
"Africa/Abidjan": "+00:00",
"Africa/Accra": "+00:00",
"Africa/Addis_Ababa": "+03:00",
"Africa/Algiers": "+01:00",
"Africa/Asmara": "+03:00",
"Africa/Asmera": "+03:00",
"Africa/Bamako": "+00:00",
"Africa/Bangui": "+01:00",
"Africa/Banjul": "+00:00",

I’ve noticed that there seems to be a new crop of “modern” knowledge sharing apps for teams and I just wanted to start keeping a list. I have not tried all of these.

Apps that combine spreadsheets, databases, and/or documents

I’ve noticed a lot of these cropping up lately and just want to start keeping track of them:

@aviflax
aviflax / Dockerfile
Last active January 7, 2022 22:33
A Docker setup for building and using a multi-architecture image with the Confluent Platform (community edition)
# We could use a smaller/simpler image to download the package, but this is the same base image as
# our ultimate image that we’re building, so we get to reuse the same cached layers.
FROM debian:buster-slim AS builder
WORKDIR /tmp/install
RUN apt-get update && apt-get install -yq wget
RUN wget --quiet \
-O confluent-community.tar.gz \
@aviflax
aviflax / cleanup_svg.py
Created December 9, 2021 15:25
Structurizr scripts
#!/usr/bin/env python3
import fileinput
def cleanup(line: str) -> str:
return line.replace(" ", " ").replace('xml:space="preserve"', "")
def __main__():
curl -v https://gitpod.com/
* Trying 45.79.154.83...
* TCP_NODELAY set
* Connected to gitpod.com (45.79.154.83) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
@aviflax
aviflax / push.yaml
Last active July 1, 2021 17:27
An example of a GitHub Actions job that builds a Docker container image and then pushes it to to the GitHub Packages container registry associated with the same repo, using regular `docker` commands
# An example of a GitHub Actions job that builds a Docker container image and then pushes
# it to to the GitHub Packages container registry associated with the same repo, using
# regular `docker` commands.
# Change these to whatever you want, of course. For example, you might want to only run this workflow for
# PRs. Personally I like to check the build on every push. That said, it’s probably not necessary to publish
# an artifact (container image) for every single push; I’m personally planning to add an `if` to the push
# step that skips the `docker push` if the GitHub event is `push`.
name: Push
on: