Luke Winikates LukeWinikates

Lacquer

Markdown DSL for drills

I partice a few skills on a weekly basis - certain workouts, guitar drills, and Japanese langauge drills. The concerns are broadly similar, and it got me wondering if there is a way to generalize "practice routine creation" in a format that is serializable, sharable, and "playable" in a variaty of formats.

Examples:

Define an 'atom'

Possibly a prometheus exporter, possibly just a CLI that returns metrics in prometheus format

Metrics for PR response time? Time since last release count of open issues dependency status number of branches, branch age

features I care about:

type-safety of route parameters
- avoid ginContext.Param etc
- inspired by Elm routing, which seems to be insipired by an OCaml example
  - https://package.elm-lang.org/packages/elm/url/latest/Url-Parser
  - http://rgrinberg.com/posts/primitive-type-safe-routing/
performance
- don't want to be a cute but unusable api
can provide an accounting of the routes on-demand

	#! /usr/bin/ruby

	lines = `git log --format=oneline`.lines.reverse
	result = lines.map { \|l\| ws = l.split(" ").drop(1) }.map do \|line\|
	line.join " "
	end.join(". ").send(:+, ".").gsub("\.\.", ".")

	puts result

	Resembling a cutaway diagram of a physical machine, or resembling a circuit diagram for an electronic system.

	shows the objects instantiated from the process entry point.

	a function allocates objects/data structures and owns them; you can see the fields of the object and their types.

	I'm curious if I can use OOTB tracing techniques from OTel or from eBPF-based tools to collect this information and apply it to increasingly sophisticated programs.