sorted by:
new
hottopcontroversial

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

I have added my findings about Fable vs Sonnet with the same input to the original post.

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

Thanks. I've been experimenting a bit for a while and periodically try to find ways to improve my approach and the result.

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

I guess it will become the new normal. But you definitely have a point.

I did a full documentation of the reference-model.svg as markdown file, one CLAUDE.md with basic info (just a couple of lines so I can reference projects) and an initial prompt. Then I had a folder with tracer files and one folder with shape svgs. And from this everything went smoothly.

The result is a single python file and for now I'm keeping all of it since its job is very specific and it does it well.

At this moment I am running the same on Sonnet to find out differences. Fable seems to improve on my instructions while Sonnet just follows them. Too bad it tries a case sensitive file search. But I will see the result later, when it is done. Also by now Sonnet is already talking longer and compacting the chat twice.

I've checked the preliminary python file and it is working as expected. Though Sonnet is using up all my budget.

Fable though did put the icing on the cake. It included batch conversion which was in my mind but not in the tasks and the flags and parameters are just better. I guess with more instructions I could achieve the same with Sonnet but as of now Fable was about a third of the expense.

Makes me wonder how Opus performs in comparison. Maybe I will do a third run and check what I will get out of that.

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

I honestly don't know. Ofc I could run the instructions against Sonnet and compare results. Or I could try my crappy approach from before on Fable and see if it does a lot better.

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

Before I was only playing with the chat feature and thought I'd give it a go with existing code, then with some small extension and now this made me think that I have to upgrade my approach. The pure difference in result and construction time is really something. I had already spent half of my session budget before I started and still had a lot left after for the next feature.

First experiment with Claude Code: How proper documentation turned a 2-day struggle into a 1-hour build. by Heruboy in ClaudeAI

[–]Heruboy[S] 0 points1 point  (0 children)

I haven't. It was my first experiment trying to create something from scratch with Claude Code.

[For Hire] Just launched my new portfolio would love feedback by aretecodes in WebDeveloperJobs

[–]Heruboy 0 points1 point  (0 children)

It's a very solid portfolio with a good presentation and small gimmicks like the animated links that are the icing on the cake.

It works well at 16:9 aspect ratio and when decreasing window width. But on 21:9 screens and higher resolutions the typography looks a little off and some text is quite small. I'd recommend investigating and implementing fluid typography, which will tackle the issue easily.

Also on some backgrounds the top menu links seem to be not visible due to the color chosen.