I’m in my third rewrite of chat-cli. The first version was really, really wonky. I was just getting started with writing a CLI in Go, and I took a number of twists and turns before I got a working project together that did mostly what I was thinking it
I've been "going live" every Friday for the past six weeks. It's been pretty fun! Each week I spend an hour and a half talking through how I would build something on AWS. It's been heavily focused on building with Go and
A blog post, written by AI, inspired by my words is still a blog post. Right?
This week, we will go over deploying our generative service to AWS, adding the ability to pass unique identifiers as parameters.
For my next show, coming up this Friday at 3pm ET, you can expect to hang out with me as I wind my way through building a simple generative service using Go and AWS Lambda.
I'm gonna be doing a live-stream this Friday on Twitch. It will be just myself, sitting at the desk you see in the photo above, talking about building stuff on AWS for about 90 minutes. I've been thinking of doing something like this for a while.
Today I figured out how to embed the tracking code for Fathom Analytics into an Obsidian Publish website. It's easy. 1. Create a file in the root of your Obsidian Vault called publish.js - You'll need to use an editor like VS Code for this
I'm building a thing. I'll write more about that thing in the near future. But, in the meantime, I thought I'd write a little about one small other thing I learned along the way. The thing I am building has two main components. 1.
I had an interesting conversation at work today around package size limits for AWS Lambda and it got me thinking about a number of strategies for dealing with these limits. The limits First, here are the limits. As per the documentation, your Lambda function, including all its source code, layers,
Wow, that title is a mouthful. Here's what it means: * You can use AWS SAM to easily construct at Serverless Application on AWS where the AWS Lambda code is written in Go * You can deploy your app to AWS from the CLI with sam deploy which is nice
A while back I created a repo on GitHub that was simply the output of doing sam init and choosing the AWS Quick Start Template for a Hello World Example. From there, I simplified the SAM template.yml file a little, restructured the folder where all my Go code lives,
While working on my chat-cli program, I realized that waiting for a response from Amazon Bedrock could take some time, depending on the nature of your prompt. To offer a better user experience, I looked into the InvokeModelWithResponseStream API method, which allows you to receive the response from Bedrock in