Denver-based full-stack technologist and lifelong maker who has spent decades building software, exploring data, tinkering with hardware, and helping developers succeed. My work spans UX/UI, web standards, application development, data analytics, AI/ML, and practical problem-solving — and I still love learning something new every day.
Documentation, samples, developer tooling, education, and DX strategy.
Modern UI/UX, Web Components, and standards-based client architecture.
APIs, backend services, automation tools, and production-ready systems.
Database design, real-time telemetry, data pipelines, and insight generation.
Model training, computer vision, inference pipelines, and applied ML tooling.
Sensor design, device integration, and real-time data flows.
A Raspberry Pi camera and custom-trained Watson model detect whether a garage door is open or closed. Combines ML, image processing, and IoT.
Every once in a while you need to roll your own. With a splash of SVG and helping hand from Stencil, you can create a custom chart as a web component.
Upload an audio file to S3, manage the details of an AWS Transcribe job, and download the results. Include code to clean up after yourself if you are so inclined.
In this post, we put aside the charting libraries, dive into some circle math, and discover that building lightweight custom charts is easier than you think.
A real-time telemetry demo using a drone, sensors, wireless links, and satellite uplink to stream flight-style data to the cloud, illustrating a modern "black box."
A reflection on how the classic Project Triangle applies to developer relations, exploring the trade-offs when building authentic developer communities.
I recently had a client whose project required putting a basic REST API in place to handle data-oriented requests. The target language was PHP for a LAMP deployment. Here is a basic PHP "Hello, World" REST API endpoint example that includes CORS with an allowed list.
Honey pot fields can and should also be checked on the server. This is in case the bot is going to the server directly, and bypassing the form. The honey pot value from the form is submitted to the server. It should be null when it arrives. If there is content, there is a bot.
A honey pot is a means to prevent bots from submitting forms. A seemingly valid input field is hidden by CSS. Bots will read the code, and put content into the field - humans will not. Validation checks for content in the field. If there is content, then a bot is using the form.
This assistant is trained on my public work and resume.
This tool is helpful, but not perfect. For nuance or a real conversation, contact me.
Professional software development
Working remote as a technologist
Speaking/workshop engagements
Managed for DevRel programs
Supported via internal AI tooling
Directly mentored across career
Developed for people with a mouth. Assists with palate development for people looking to improve their understanding of the foods they consume. From hobbyist to connoisseur. Robust data visualization, AI recommendations, and custom form controls.
A comprehensive year-at-a-glance calendar. Built with Web Components, embracing a MacOS look and feel. Supports multiple calendars and limited sharing via cloud object storage and serverless integration.
Built for a pharmacuetical company to digitally track and manage controlled substances. Replaced a paper-based workflow to mitigate risk and improve accountability and efficiency. Roles-based features.
Have a project, collaboration, or opportunity you would like to discuss? I am especially interested in work involving web architecture, data, IoT, and developer experience.
Prefer email? You can reach me at kevin@ketnerlake.com.