go test -bench=. -benchmem
BenchmarkTypeof-4 10000000 153 ns/op 16 B/op 1 allocs/op
BenchmarkReflectTypeOf-4 50000000 27.4 ns/op 0 B/op 0 allocs/op
PASS
ok github.com/mrap/bench/typeof 3.099s
| require 'benchmark' | |
| class RubyQuicksort | |
| def self.prepare(number_of_items) | |
| time_taken = Benchmark.realtime{ generate_random_array number_of_items } | |
| puts "Took #{time_taken}s to generate an array of #{number_of_items} random items" | |
| end | |
| def self.generate_random_array(number_of_items) |
| #include <iostream> | |
| #include <algorithm> | |
| typedef int pillar_t; | |
| pillar_t* read_pillars(int); | |
| int get_volume(pillar_t *, int); | |
| int main() { |
| " Settings | |
| set noautofocus | |
| set cncpcompletion | |
| set linkanimations | |
| set showtabindices | |
| set smoothscroll | |
| set hud | |
| let searchlimit = 20 |
go test -bench=. -benchmem
BenchmarkTypeof-4 10000000 153 ns/op 16 B/op 1 allocs/op
BenchmarkReflectTypeOf-4 50000000 27.4 ns/op 0 B/op 0 allocs/op
PASS
ok github.com/mrap/bench/typeof 3.099s
| /* Copy this into your [[roam/css]] page */ | |
| /* IMPORT CORE THEME */ | |
| @import url('https://azlen.github.io/roam-themes/core.css'); | |
| /* GOOGLE FONTS */ | |
| @import url('https://fonts.googleapis.com/css2?family=Source+Sans+Pro:ital,wght@0,400;0,700;1,400;1,700&display=swap'); | |
| :root { | |
| --page-width: 616px; |
| /* | |
| * Roam template PoC by @ViktorTabori | |
| * 0.1alpha | |
| * | |
| * forked by @everruler12 | |
| * v1 2020-08-07 | |
| * include moment.js and replace ::current_time:: and ::today:: variables in template | |
| * | |
| * forked by @mrap | |
| * 2020-10-26 |
For: Lucy From: Mike (with a little help from his AI agent) Date: April 29, 2026
Hey Lucy! Huge congrats on the Honeystack launch — the site looks great and the build choices are really solid. As a friendly favor, I ran a security pass on honeystack.agency since you guys are about to be handling nonprofit data and email lists. Most of what I found is "you're already doing the right thing" — but there's one urgent fix in the newsletter API that's worth doing before this thing gets shared more widely.
This document is written so you can hand each section directly to Claude Code in the Honeystack repo and have it do the work. No security background needed.
name: repo-audit description: > Use when asked to audit a repository, assess codebase health, find what's wrong with a codebase, identify technical debt, or produce a prioritized improvement plan for an existing project. Also use when a repo feels untrustworthy — red CI, stale docs, mystery failures — and the user wants a grounded picture before investing, or says "upgrade this project", "what should we fix here", "how bad is this code". tags: audit, code-quality, repo, technical-debt, improvement-plan, verification