
I'm a father and husband, a software developer, a computer geek, a board game collector, and a heart transplant recipient living in Sun Prairie, Wisconsin.
Search for a command to run...

I'm a father and husband, a software developer, a computer geek, a board game collector, and a heart transplant recipient living in Sun Prairie, Wisconsin.
No comments yet. Be the first to comment.
This series of articles covers details related to building TrendWeight.
Create React App, Vite, Next.js, Remix...
If you use TrendWeight with a Fitbit account, there's a change coming that you should know about. tldr: Google is retiring the API that TrendWeight uses to read weight data from Fitbit, and once it's

Well, it’s been just shy of a week since the launch of the new version of TrendWeight. Early feedback was mostly positive and many small bugs were squashed in the first few days. There were also a couple larger improvements that just went live that a...

After more than a decade sitting mostly unchanged, TrendWeight has gotten a fresh update. While the app looks and works mostly the same way you're used to, everything under the hood has been modernized. What You Need to Know Logging In You'll need to...

Last night at the gaming table… They ascended cautiously, weapons ready. In a chamber on the upper floor, they found her - an emaciated figure kneeling within a circle of power. On either side stood skeletal guardians, each bearing six arms laden wi...

// Ewal
12 posts
I'm a father and husband, a software developer, and a general geek. I ramble about web development, ai, homelabs, and smart home tech.
More about me.
A while ago, I shared that I was going to rewrite TrendWeight from scratch (see Why Rebuild?). And then there was three years of radio silence on the project. The rewrite stalled at 70%—most of the interesting architecture was done, leaving authentication flows and other tedious tasks.
What unstuck this project? AI coding tools, specifically Claude Code.
AI coding tools make tedious tasks easier. Plus, playing with new AI coding assistants is genuinely fun—they're like new toys. Sure, they're not perfect and sometimes generate questionable code, but they transform grunt work into something more engaging. The project stopped feeling like a chore.
I decided to not just finish the in-progress Next.js rewrite as is, and instead I decided to adjust the tech stack (again). My 2021 perspective on Next.js was overly optimistic. It's solid for content sites, but for interactive applications like TrendWeight, the server-side complexity adds up quickly. I also fell out of love with Chakra UI, and I wanted to move to Supabase instead of Firebase.
Current stack:
Frontend: Vite (stable, fast, minimal configuration)
Backend: ASP.NET Core (Vite SPAs need a backend, and I know C#/.NET well)
Styling: Tailwind (utility classes over opinionated components)
Authentication/Database: Supabase (self-hostable, Postgres compatible)
Claude Code handled the implementation well, particularly in dealing with grunt work:
The entire authentication stack (social logins, email magic link)
Migrating from Next.js to Vite + C#
Migrating from Chakra UI to Tailwind
Of course, AI coding tools still make a bunch of mistakes, and TrendWeight is complicated enough that you can’t really vibe code and get away with it. I definitely had to pay close attention to what Claude was doing (and in not a few places had to go back and clean up questionable choices after the fact), but I still enjoyed the process.
The rewrite is almost done. Just testing and polish remain, primarily around user migration UX. If things go smoothly, you can expect a follow-up post in the next couple weeks announcing the launch of the new site, so stay tuned!