Contact

The fastest way to get in contact with me is to use one of my services listed on /services. That gives the interaction a clearer surface for visibility, scope, and response. Otherwise, the best direct route right now is a DM on X, TikTok, or Instagram.

Course signups are currently once per season and include reasonable surfaces for visibility and discussion. Public surfaces like YouTube, software notes, and the blog are useful for context, but they are not the fastest path for outreach.

!["fastest_routes"]

Fastest Routes

⚡ @services Services The fastest and most structured way to get in contact. Best for serious inquiries, project context, and clearer response surfaces. ✉ ~x_dm X — @spwashi Very easy DM route. Preferred for quick outreach, direct questions, and current public context. ✦ @tiktok_dm TikTok — @spwashi Preferred DM path with strong public context around ongoing work, design, and engineering direction. ◌ >instagram_dm Instagram — @spwashi Preferred DM path for visual context, creative conversation, and lightweight contact.

^"contact_register"{

Contact Register

✉ ~x X @spwashi — currently one of the easiest DM routes. ✦ @tiktok TikTok @spwashi — direct messages plus short-form public context. ◌ >instagram Instagram @spwashi — direct messages and visual/public surface. ☁ ~bluesky BlueSky @spwashi.com — public surface and message-adjacent context. ▶ ^youtube YouTube @spwashi — public iteration around engineering, design, and long-arc direction. ⌘ #>github GitHub Current code, repositories, implementation depth, and active technical context.

*["course_signups"]

Courses and Seasonal Visibility

Once per season

Course signups currently happen once per season rather than continuously.

Reasonable surfaces

Those signups include reasonable surfaces for visibility, discussion, and sustained attention.

Best route for now

For immediate outreach, use services or send a DM on X, TikTok, or Instagram.

~"related_surfaces"

⚡ @services Services Fastest contact path, with clearer structure for collaboration and response. #>about_frame About Background on systems, public surfaces, domains, and current direction. #>software_surface Software Spw syntax, operator grammar, interactive codeblocks, and implementation context. #>blog_input_interpreter Blog Local interpretation for Spw fragments, wonder notes, and rough drafts.