What if I started using a part numbering scheme for all the silly things I make, so that I can track them using tags and stuff. A company I worked for used the scheme: xxx-yyyyy-zz Where xxx was the "kind" of thing, e.g. an assembly, or a certain kind of document, or a full product; yyyyy is the "project id"; and zz is a major revision/iteration document id of that thing. Overengineering? Probably, you really only need this if you have/want/are required to maintain a document control system. But maybe I do?

Euclidean Rhythms [https://dbkaplun.github.io/euclidean-rhythm/] are a cool way to generate beat patterns, originally shown to me by @jjbbllkk. There's a paper (pdf) [http://cgm.cs.mcgill.ca/~godfried/publications/banff.pdf] that describes a way to calculate it, by shuffling the beats and rests to make sure they are well spaced. There IS a rust crate that does this, but it follows the paper's methods fairly directly, which requires a bunch of SmallVecs, and I don't love it: https://github.com/padenot/euclidian-rythms/blob/3c72f37ff8a6c1b7897fdc783e52fabe8eb45dc8/src/lib.rs#L5-L72 [https://github.com/padenot/euclidian-rythms/blob/3c72f37ff8a6c1b7897fdc783e52fabe8eb45dc8/src/lib.rs#L5-L72] Instead, I have hit the problem with loops and bit math, which allows me to handle the problem much more comfortably on embedded systems: pub struct Euc32 { interval: u32, data: u32, } impl Euc32 { pub fn new(hits: u32, interval: u32) -> Option<Euc32> { if hits == 0 { return Some(Euc32 { interval, data: 0 }); } if (hits > 32) || (interval > 32) || (hits > interval) { return None; } let mut ctr = 0u32; // TODO: There's probaby a *math* way to do this without // a loop, but whatever while ctr < interval { ctr += hits; } let mut data = 0; for i in 0..interval { if ctr >= interval { data |= 1 << i; ctr -= interval; } ctr += hits; } Some(Euc32 { interval, data }) } } This gives me the results I expect: test euc::test::sevens ... 0: [.......] 1: [x......] 2: [x..x...] 3: [x.x.x..] 4: [x.x.xx.] 5: [xx.xxx.] 6: [xxxxxx.] 7: [xxxxxxx] ok test euc::test::thirteens ... 00: [.............] 01: [x............] 02: [x.....x......] 03: [x...x...x....] 04: [x..x..x..x...] 05: [x..x.x..x.x..] 06: [x.x.x.x.x.x..] 07: [x.x.x.x.x.xx.] 08: [x.xx.x.xx.xx.] 09: [xx.xx.xx.xxx.] 10: [xxx.xxx.xxxx.] 11: [xxxxx.xxxxxx.] 12: [xxxxxxxxxxxx.] 13: [xxxxxxxxxxxxx] ok

A RISC-V emulator for the 8051 (MCS-51) microcontroller. - cyrozap/rv51