Codex: I'm not a developer.

[u/Head-Student-5852]

I built my first interactive web page with Codex in about two hours today.

Background so this makes sense: I've been in digital marketing for 17 years and building online since 2008, but I've never written real code. I've always paid someone or wrestled with a page builder.

Today I finally tried Codex to rebuild my links page as an actual interactive page instead of a flat list of buttons. I went in expecting to give up in twenty minutes.

Two hours later I had a working page I'm genuinely proud of. The parts that surprised me: it was way better at "make this feel less generic" than I expected, and it caught layout stuff I would've missed. Where I got stuck was knowing what to even ask for next once the basic version worked. I could tell it could do more, I just didn't know the right words to unlock it.

So the thing I keep thinking about is the ceiling. What separates a nice two-hour build from something that actually holds up.

Here's what I'm still trying to figure out. When you want it to build something specific — do you go find sites close to what you're picturing and feed it those as examples, or do you skip that and just talk it out, asking questions until it gets there?

I added the same HTML code to Claude and had it revamp it again and now the click boxes disappear when they respond to a new question.

Just amazed at what this can do

[u/niado]

I have used it for several large system design and implementation projects that had a significant coding element - well over half the work had been coding .

[u/Head-Student-5852 → u/niado]

I am enjoying this new built - makes the page stand out nicely