the_simian @5imian

I ❤️ @amandaharlin, Ada & Dorian And: Programming, Composing New Music, Synths Owner/Engineer @simiancraft Formerly/Cofounded: @techlahoma @okcjs @thunderplains jesseharlin.net Norman, OK Joined January 2011

Tweets

14K
Followers

1K
Following

1K
Likes

11K

the_simian @5imian

13 hours ago

@austinspires I see 2advanced I hit that like button.

0 0 1 24 0

View Details

Ewan Bristow @BristowEwan

a month ago

512 partial, full-spectrum instantaneous frequency additive resynthesis.

Ewan Bristow @BristowEwan

4 months ago

Real-time 512 voice "Instantaneous Frequency" re-construction, running smooth as butter :) Will be out as a native vst soon enough

13 30 390 92K 242

22 48 601 39K 297

View Details

the_simian @5imian

21 hours ago

@J_Longanecker @straceX I like how this is (possibly accidentally) implying nearly everyone should be using GraphQL

0 0 3 242 0

View Details

the_simian @5imian

21 hours ago

@joshmanders @jonaienq At scale doesn't mean important. If your favorite streaming service got deleted you'd be inconvenienced. We use scale as a benchmark of importance, when importance should be the bench. It might be a small codebase doing something critical for society. It may need to be 'correct'

1 0 0 34 0

View Details

the_simian @5imian

21 hours ago

@joshmanders The "illiteracy is actually good" camp is entirely fueled by cope. Everyone should ask themselves who you want building important software in 5 years. Not social media/entertainment. That being down doesn't matter actually. I mean the folks that keep the lights on.

0 0 0 75 0

View Details

the_simian @5imian

2 days ago

@DavidKPiano do you mean explicitly 'non' state-machine based flow?

0 1 2 442 0

View Details

the_simian @5imian

2 days ago

@kenwheeler This guy is permanently: 💪⬆️

0 0 0 43 0

View Details

the_simian @5imian

3 days ago

@tiri_220 Prog

0 0 0 11 0

View Details

the_simian @5imian

3 days ago

@AdamRackis Are you doing the "forbidden-in-2026-apparently" thing where you verify the code by actually being literate and reading it for like just a quick moment to make sure its not absolute slop? NGMI.

1 1 6 136 0

View Details

the_simian @5imian

3 days ago

@lookoutitsbbear Unrelated, but repeating that sample over and over sounds terrible to my ears, but beauty is in the eye of the beholder I guess.

0 0 1 22 0

View Details

the_simian @5imian

3 days ago

@lookoutitsbbear How can you tell the akai unit is not turned on? Blue light on the LCD? Could be the angle. They're likely under bright stage lights; these things can wash out at some viewing angles. Is there another clear tell?

2 0 0 260 0

View Details

the_simian @5imian

3 days ago

@thdxr that's a decision that's genuinely yours Now I'm off to go fail some captcha's that are effectively meaningless in 2026 and probably block humans more than frontier LLMs.

0 0 0 14 0

View Details

the_simian @5imian

3 days ago

@Kantorcodes @RhysSullivan The size is by design. Google's MCP toolsets stop short, so the suite covers the REST reference too; every operation annotated and cited. Complete control of an account is the point, which is exactly where per-tool policy earns its keep. It shouldn't be where it runs out.

0 0 1 23 0

View Details

the_simian @5imian

3 days ago

@Kantorcodes @RhysSullivan Snag. The suite is 1 npm package, 5 servers, 210 tools (33/31/35/35/76). Your entries match on package name, so that's one entry, and 79 names cover a third. The 69 destructive tools fit; the reads don't. Can an entry key on bin name? Then each server is its own kit and all fit.

2 0 0 34 0

View Details

the_simian @5imian

4 days ago

@Kantorcodes @RhysSullivan Interested, two blockers. Your MCP kits cap at 79 tools; Sheets is at 78 and growing. Also is byte-bound to tools/list in your repo, but we ship weekly. What happens on fingerprint mismatch? can a kit publish from our package? Our ops already carry annotations plus source links.

1 0 0 12 0

View Details

the_simian @5imian

5 days ago

@theo @maria_rcks Its a Very Serious tool for code, so "Very Serious Code"? Could shorten to VS.

0 0 0 17 0

View Details

the_simian @5imian

5 days ago

@weaverbeats I think I'm especially liking the guttural, yet glitch-like texture at the top, the ornamentation. Really good musical idea that plays against the syncopation. A strong passage, great work.