I've rewrote the post to be "more pleasant" to read. Sorry for the unhinged original post.

This is my idea, pick something like the FreeBeeGee and make it for Card Games. This is the devlop with some high level concept.

Feedback is welcome. Playtest too. I'll be using this with my friends (reason for why I'm building this). I'll be fixing for the stuff that I need, but if there is some screaming bug, I would fix it.

Thanks for the reading, and any feedback.

all 4 comments

sorted by: hot top controversial new old
[–] 2 points 4 months ago (3 children)

thanks for your writeup. I didn't read the original but this one was fun to read through.

this looks like an awesome project, and I appreciate how you went over the ways AI helped and hindered your project at the end. its really hard to get honest feedback about AI from devs IRL right now, everyone keeps saying they have silver bullets in their workflows and I feel like the crazy one for not being able to figure it out.

looking forward to giving AC a shot!

  • source
  • hideshow 3 child comments
  • [–] [S] 2 points 4 months ago (2 children)

    Thanks for the reading, the original post was somewhat unhinged. It was a very long debugging session for the alpha thing, the AI tooling weren't helping. And I was losing my mind over my morning coffee. But I fixed the little details.

    I think the reality of the AI tooling for coding fall in the "middle", it isn't the 10x or 100x described by people, it's closer to a 10%~15% performance increase in my humble view. With some better harness (like the PI that I discovered) I think this can be sightly better, but far from the 50%. I would say that if the increase in productivity decays over time, the amount of code generated I had to refactor and clean for most of the week.

    But for sure the Claude was a huge disappointment, very bad quality for it's price, and super slow for the needs of a "start up mindset", let's put in this way.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 months ago (1 child)

    Claude is geared more towards enterprise companies, anyway. I think you went over pretty succinctly as to why: they can afford the extra resource burn.

    pretty much the way I use AI rght now is similar to how you see the near future of your use.

    • AI does first draft
    • I review draft, conclude 'this is shit'
    • redo most of it

    its pretty useful for getting through writers-block type scenarios sometimes because of that, but past the initial stages of the project the usefulness declines dramatically.

    I'm still not seeing any real ways of removing the human in the loop, especially for the review process.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 4 months ago

    Yet this is my problem, A tool that "waste" tokens, is slow (with some tasks taking 30~40 minutes) and generating a result, while a model running locally can do the 70% in 5min. It's a huge difference.

    And don't forget, at the end of the day, I would still need to look into the code and fix some stuff myself.

    And if compared with Deepseek (which had fit best on my use case), it's even faster like 1~3 minutes, to get on the 90% of the result, on a fraction of the cost. This is the points that I'm focused, and a enterprise should either understand that the market have changed, or pay the price. And looks like we will pay the price.

  • source
  • parent
  • 8 comments in c/programming@programming.dev view that post
    [–] 0 points 4 months ago (7 children)

    Wow, that was just.. an awful read.

  • source
  • hideshow 7 child comments
  • [–] [S] 4 points 4 months ago (6 children)

    Very sorry to hear that. Would you mind elaborating on the topic? What was the issue? The language? The tone? The way that I described? English isn't my mother language, and I want to improve how I do express myself in it.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 4 months ago* (5 children)

    I'll start with the unnecessarily combative tone with your reader. Then the self-contradicting absolutes (claude sucks, but my solution is x% as good as the lowest-end claude). Then the fact that it's really just an untargeted rant against "everything" that doesn't really justify the anger.

    And you hit my pet peeve about saying "containers aren't running on bare metal" when they run "on bare metal" exactly as much as non-containerized processes. That's the point of containers.

  • source
  • parent
  • hideshow 5 child comments
  • [–] [S] 4 points 4 months ago* (last edited 4 months ago) (4 children)

    Edit: I did rewrote the post. Once I calmed my mind down I think it's better now. At least my closed friends prefer this version of it.

    That was really insightful.

    And align with a close friend on the topic. So you know. I think I'll rewrite this post in a less "aggressive" tone.

    When two of my close friends don't like a post, there is a good chance that the post isn't good enough to leave the oven.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 4 months ago (3 children)

    That's a much nicer read! I'm interested in some of your Claude experiences though.

    I tested Claude heavily, and I have to be direct, it consistently fell below my quality bar. Even with strict, detailed guidelines, the code it produced was riddled with subtle issues, off-by-one errors, improper error handling, and a complete disregard for my idiomatic Go patterns.

    Which Claude model were you using? Opus 3.7 & 3.8 tend to do a very good job at things like that. It catches my off-by-one issues much better than I do... They are, however, a bit slower as you point out. But my local models on an NVidia 3070 with only 8Gig of VRAM are garbage...

    Single-letter variable names might be fine for tight loops, but when you’re generating thousands of lines of code via AI, i, j, and k become impossible to trace.

    I find that if I drop in a CLAUDE.MD some style guides that it does a good job of following them. In particular I hate the Python idiom of prepending "_" to "private" variables and functions. If I put a note in there it stops it from doing it.

    As an aside - i, j, and k for loop variables is a very old tradition going back to FORTRAN where i, j, and k were always integer variables. So i is the outer loop, j the inner loop, and k the inner-inner loop. If you have more nested loops than that you're doing it wrong...

    But if you don't like it the style hint should help.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 1 point 4 months ago (2 children)

    Most of my complains are on the func (f *thing) name(w *http.Writer...), this is ok for small functions, but when you have 20 lines, where 10 of then uses single letters around are unbearable.

    Regarding the CLAUDE.md, didn't work at all. I don't know if the training material is so small in the GoLang that makes the model go crazy on specific details, or maybe the single letter was preferred since it consumes less tokens, either way, didn't work at all. And I was using the Opus. I know that they released the Fable, but I can't use since it's coding related.

    The Qwen model I used a quantized version of it for a lot of the stuff, it's super fast, but a 8 vRAM won't hold it. On my Linux box I have 16vRAM and managed to hold it tight, but I notice that I was destroying the GPU for long running tasks, so I aborted.

    I do have a Blackwell in mind, with some luck I can manage to grab one and test a full precision DeepSeek V4 Flash in it. I already saw some people doing it in a single Blackwell, so should be a thing to have at home to play around, but this is a far future.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 months ago (1 child)

    Regarding the CLAUDE.md, didn’t work at all.

    Not at all? I do know that LLMs tend to have a "recency bias" and lose earlier context over time, especially when Claude summarizes a session to create a new one seamlessly. I've run into issues with it wanting to run git commands despite me explicitly telling it that it should never do so... Keeping sessions short seems to help.

  • source
  • parent
  • hideshow 1 child comment