My #opensource history has a lot connection to where the water spins in the other direction, and #golang.
Chris Mazur dared to host my first talk on #webassembly a couple years ago, in Wellington. This was on #wazero.. pure go runtime (against the odds in a rust ecosystem). This year, Katie Fry dares to host my first talk on #genai in go (against the odds in a python ecosystem), in Sydney.
To write a first talk for me is a mammoth task. I get really nervous and do tons of research, ask my friends, look at a million demos. I have 300 browser tabs, tons of example code locally, several rambling text editor windows.
Co-located with an Elastic meetup, my presentation at Katie's is all about Go, and I feel good about it. I had a quite decent plan together, even if later versions go farther. Yesterday, I had some initial scratches towards a real outline.
This morning, Philippe Charrière pointed me to his 3 month old baby, https://lnkd.in/eTCRpNPr. This is one of his finest works: it is another improvement on his developer empathetic approach to #opensource. His examples are simple, tiered and top-notch. As GenAI is such a vast and drifty space, this is even more important for noobs.
Of course, I was unsurprised this integrates with #webassembly functions via Extism. So, when you ask a question in a way the LLM understands a tool is relevant, those functions can be in any language, not just #tinygo, but anything that works in wasm, like rust. I chuckled stumbling on this, unsurprised as I worked with Phillipe earlier with his capsule FaaS project.
TL;DR; I basically threw out my examples and will start over and use parakeet. This doesn't imply you will end with parakeet, but frankly there are far worse ways to start in Go. Who knows where you will end, but starting is the most important part.
I'm hoping folks in Sydney enjoy this as much as I do, and also hope this turns into another successful way to relate a new tech, yet again starting where the water spins in the other direction.
https://lnkd.in/ebZfF9Va