Luke Winikates LukeWinikates

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

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

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'

Lacquer

A Pen by Luke Winikates on CodePen.

License.

Keybase proof

I hereby claim:

I am lukewinikates on github.
I am lwinikates (https://keybase.io/lwinikates) on keybase.
I have a public key whose fingerprint is AC5F 7444 8560 9905 7128 38E9 AE14 2850 289E 14F4

To claim this, I am signing this object:

	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.

	#! /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

	# See http://help.github.com/ignore-files/ for more about ignoring files.
	#
	# If you find yourself ignoring temporary files generated by your text editor
	# or operating system, you probably want to add a global ignore instead:
	# git config --global core.excludesfile ~/.gitignore_global

	# Ignore bundler config
	/.bundle

	# Ignore the default SQLite database.

	# See http://help.github.com/ignore-files/ for more about ignoring files.
	#
	# If you find yourself ignoring temporary files generated by your text editor
	# or operating system, you probably want to add a global ignore instead:
	# git config --global core.excludesfile ~/.gitignore_global

	# Ignore bundler config
	/.bundle

	# Ignore the default SQLite database.