Having My Cake and Eating It Too, Roku Edition
Roku changed a policy that meant updating my screensaver app would mean tearing out its monetization and losing existing subscribers. I could have just left the old version running.
Roku changed a policy that meant updating my screensaver app would mean tearing out its monetization and losing existing subscribers. I could have just left the old version running.
There’s a workshop floating around that generates Amazon Connect contact flows and CloudFormation from a conversational UI powered by Claude Opus.
A colleague pointed me at a Claude Code skill that strips AI-isms out of generated text. I needed it.
A client called me out — users were overwriting each other’s contact flows, and the pipeline got blamed.
I keep seeing the same pattern in Amazon Connect implementations: Lambda functions that return HTTP-style status codes — 200 for success, 400 for validation errors, 404 for not found, 500 for unhandled exceptions.
Client docs shouldn’t look like a README.
I have a React App with a HubSpot contact form. The user must be logged into submit the form so I wanted to prefill their email address. Fortunately, HubSpot Forms API provides a onFormReady callback!
I was working a Google AdWords campaign for Mind-Wellness.net and I wanted to track when a user submitted the contact form. I generated the static site using Hugo, and I am relying on HubSpot for the
I am working on a Amazon Chime application that provides natural language and GenAI features to a legacy phone system. After deploying the app into a new account, I got the following error in my SMA Lambda Handler when trying to invoke the Amazon Lex bot:
I really like the declarative nature of CloudFormation - you describe an end-state, and it computes the diffs. CDK gives me even more flexibility in creating complex apps. Recently I built a CDK web a