Adobe ColdFusion Summit 2026 Schedule
In a few days, I'll be attending the Adobe ColdFusion Summit (CFSummit) for the 3rd time. In previous years, I've tried — and struggled — to use the online agenda for the event. This year, I'm taking matters into my own hands! I went to the event site, downloaded the .json data files, and then asked Claude Code to stitch them together and help me bootstrap a simple, one-page site that would suit my personal needs.
View my CFSummit 2026 Event Schedule →
View my CFSummit 2026 repository on GitHub →
I'm old enough that I remember going to conferences and, at registration, receiving a print out of the agenda. And I loved it! This personalized rendering of the CFSummit 2026 schedule is my attempt to recreate that grid-based, track-by-time look-and-feel.
It's not perfect; but I've gotten it to a point where I think it cleanly separates the agenda UX from the details. And then links back-and-forth between the sections using native page anchors.
It works on my iPhone as well. In portrait mode, I get a simplified stack view; and in landscape mode, I get the grid view.
Reader Comments
Just taking a moment to reflect on working Claude Code. At first, it was kind of amazing! I went from random idea to MVP (minimum viable product) in like 20-minutes. That was exhilarating.
But then I thought about putting the code in a public GitHub repo (which I did); and suddenly, it all looked terrible. It wasn't "my code". And the stylistic and technical choices in the code were very questionable. So once the MVP was done, I then spent several hours over the last few days rewriting much of it and refactoring the logic and the files.
And now, I have this Frankenstein concoction of an app. Some of it is the Claude output; and much of it is my output. And together they kind of mostly work if you don't think too deeply about why certain decisions were made here or there.
The huge value-add of Claude in this was getting me over the hurdle of putting in the effort in the first place. I went from "this isn't worth my time" to "eh, let's see if Claude can do it". And once I got over that bump, I really should have just taken over. But instead, I tried to have Claude keep tweaking it; and then I would take turns tweaking it; and really, I should have just taken over full control much earlier in the process.
Even now, the repo still had a Python script that downloads the latest
.jsonfiles. But really, I should have rewritten that usingCFHttponce the concept was proven. Now I have tightly-coupled logic that is spread across the static build and the live data massaging and it loses its coherence.But hey, this only needs to work for a few days! 😜 which is really the bread-and-butter of the Claude Code one-shot world.
Post A Comment — ❤️ I'd Love To Hear From You! ❤️
Post a Comment →