Previously VPE at GRAX, engineering at Segment, co-founder and CTO of Convox (S15) and platform architect at Heroku.
https://github.com/nzoschke
- Another happy DBOS user here. It slides right into our existing Postgres usage and has a simple Go SDK.
- I recently started using this DBOS in Go and it’s been good.
https://github.com/dbos-inc/dbos-transact-golang
I have River on my list to try someday too
- Having the coding agent make screenshots is a big power up.
I’m experimenting with how to get these into a PR, and the “gh” CLI tool is helpful.
Does anyone have a recipe to get a coding agent to record video of webflows?
- A central service. Hosted, secure, frontier model is fine. I’m thinking this through it’s probably something GitHub or an addon should provide.
But maybe it starts local with an app like yours anyway. I do a lot of solo hacking I don’t want to share with the team too. Then there is some sort of way to push up subsets of data.
- Looks awesome for solo / indie devs.
For my small software shop I'd like a team version of this:
- collect all prompts/chats from all devs for our repos - store them somewhere in the cloud - summarize them into a feed / digest
- A digital assistant for your Gmail, Google Workspace, Notion and Slack.
Opinionated workflows and automations for less technical teams where no code, low code or vibe code tools are beyond reach.
- I’m doing agentic coding on a bunch of web apps and server side rendering HTML is so much easier than building APIs and React components.
Full page reloads are fine for most CRUD cases. Then layering DOM morphing can be even better UX almost for free
- I just want to say thanks to you and the team and community. Bun is a treat to use.
- Fun. I love the UI style.
See also the Endless Acid Banger:
https://www.vitling.xyz/toys/acid-banger/
And happy Acid August!
Every year we celebrate the 303 with a club night in SF.
- Looks neat!
As humans augmented with agents write more code, solutions that require less context shifting to get stuff done will win.
A common web stack may include API handlers, OpenAPI spec, generated TypeScript definitions, generated TypeScript client, React logic and effects code, TSX code, HTML, and CSS.
This generally needs filesystem watchers, code generators, transpilers, compilers to get stuff done.
Something that can go from a backend handlers straight to terse markup for reactive UI would be a massive simplification to all this, and a big productivity boost.
- I don’t know about the browser but I’ve been playing with a WASM build through this Go wrapper. Nice to not need CGO.
- Love it!
I made an open source jukebox too. Mine models an old-school jukebox, where you set up a tablet so all your friends can browse and queue up music at a party.
https://github.com/nzoschke/jukelab https://nzoschke.github.io/jukelab/spotify/desktop
I see you're in the Bay Area. I do occasional Jukebox Happy Hour in SoMa we could meet up at...
- I built my own audio player too.
https://github.com/nzoschke/jukelab
It's a web app with the Spotify Web Playback SDK or a good old MP3 HTTP server and API like Internet Archive.
It works crazy well on a ChromeBook, and reasonably well on an iPhone, iPad or Android both through a native app with a webview component or the browser.
I have a theory the pendulum is swinging back and there is a demand for controlling our own music and music interface, and web technology is sufficiently good for implementing players.
- GraalVM is neat.
I used it to make a program that logs all activity happening on the Pioneer CDJs. The best reverse engineering of the Pioneer protocols is a Java project, but I wanted to write the rest of my application in Go.
GraalVM plus a GitHub action spits out native binaries that I can exec and interact with over stdio from Go.
If/when the WASM backend supports UDP networking and threads I'd love to run it as WASM instead of a binary.
- https://github.com/nzoschke/vizlink
- https://github.com/nzoschke/vizlink/blob/main/.github/workfl...
- I’ll second Partiful.
Their use of good old fashioned www links and SMS messages makes it easy for everyone to share and join events. No app and no Partiful account necessary.
They also have simple and good event privacy model, group scheduling, reminders, Venmo based ticket system, and group chat.
It’s taken over almost completely in my social circles and I’m all for it.
- An export db with title, artist, album and rough BPM could be useful to interoperate with the native browse and search menus on a CDJ.
Without beat grids have to best match by ear but that’s par for the course for many DJ scenarios.
- Haven’t tried it myself but CDJ-3000s have been rooted.
- Starred!
I’ve been playing with hooking up a MIDI controller to my OBSBot Tail Air PTZ camera and OBS.
The config and filters and triggers looks similar to my prototypes.
I’ve been wondering if there’s any sort of prior art or standards here from other domains like lighting consoles or workflow systems.
- The hostility towards users and developers continues.
I have a fun Spotify web app that gives you an old school jukebox experience. I recently open sourced it as a final act of giving myself and all our users freedom to control our music and music playing experience.
https://github.com/nzoschke/jukelab
But I’m laying foundations to move off from Spotify.
Their playback SDKs are buggy and by default always give up control to the recommendation algorithm. APIs get shut down. Developers bugs and questions go unanswered. Trying to control Sonos + Spotify is some sort of cruel prank. Albums and tracks in your collection go dark.
For me I’ve switched to Tidal for streaming which at least for now is does well at the raw basics of playing high quality music. Tunemymusic is good for copying playlists.
Then to Bandcamp for buying dance music to DJ.
I’m very close to buying and ripping CDs again to truly have control.
That ~1000 drivers on the road are all better trained on what to do in the next power outage is incredible.
There will always be unexpected events and mistakes made on the roads. Continual improvement that is locked in algorithmically across the entire fleet is way better than any individual driver's learning / training / behaviorior changes.