I Asked for a Portfolio but Got a Filing Cabinet

A developer spent nearly a week redesigning their portfolio site after feedback that it looked AI-generated. They used AI tools like Gemini and Claude to identify and fix 'AI tells,' ultimately shifting from a dashboard-like archive to an 'artsy page' that better reflects the human behind it. The developer's key insight was that describing the human element had to be done by themselves, not the AI.

🦄 I really am trying to get back to writing more and decided to write up a quick, fun post about my arguments with all of my AI friends. It took me nearly a week to redesign my portfolio site and most of that time was spent frustrated that nothing was working. So here's the quick read on what went wrong and how I finally fixed it. "Good enough," anyway. It was no secret my original portfolio site looked AI-generated: that's exactly what it was. So when that was the feedback I received, my response was mostly "yeah... and?" It's also no secret that I am not a UX person. I have no clue what most of these elements are even called, let alone what to do with them. My version of an animated page is literally "make it move". The good news is I don't need to know all that to build a page that doesn't completely suck. And yes — "not terrible" is the bar I'm aiming for here, because anything else would be me pretending to know what I'm doing. I pulled the metrics — something I rarely do — and ran across an anonymous input I wasn't looking for. Scary. I knew it wasn't great . But scary was a new low for me, even in the realm of design. So I sent Gemini out to crawl my site and generate a list of all the AI tells. The answer was really "the whole thing is terrible" — everything from the color to the index card implementation. The only human thing on the whole site was the about profile which was good seeing as how I actually wrote most of that . Alrighty then. Now is as good of a time as any to just rewrite the entire implementation. I had tried using Impeccable https://impeccable.style as a style guide along with Claude Design — neither one got rid of the AI generated look and feel. Claude and I ended up with more than 10 independent designs of my site, and I hated all of them more than the first. I didn't realize until later that every single one of these designs that I hated was describing an archive. Every one was a browsing interface — filters, counts, dropdown, search — and not one described me as the human behind it all. The problem is that I kept doing the same thing. I was sick of purple, my goto for awhile, so I tried a rainbow — which made things a million times worse. Blue, green, pink, red, orange, and finally yellow, the one I liked best, but nothing helped the overall look and feel. Then, in complete frustration, I told Claude I wanted an "artsy page" not a dashboard. That vibe clicked somewhere. I finally had options I didn't completely hate. Yellow looked fine in dark mode. Light mode had no pizazz and looked like a washed out attempt by somebody who didn't know what they were doing — which was no surprise, seeing as how that's exactly what it was. So I went back to quizzing the AI for potential ways to make that work. These rules are where I ended up after doing a ton of research and arguing with myself every time I actually had to make a decision: The highlighter was a combination of options squished together in a single ah-ha moment. You can also see the full page — with a functional agent — at https://anchildress1.dev . When I asked Gemini to review my previous website, I summarized the whole report as "this whole thing is terrible". I sent it out to rereview the updated version and got back "not completely terrible". I filed that as a win. It took me more than ten designs to work out why the about profile was the only thing that ever passed. Everything else was just a very well-organized way to look at my work. Describing the human was the part I had to do myself. While interviewing me about my own website, Claude invented a product I've never built and a redesign that never happened. I fixed that but let it write this footer.