7 ms·

HN needs an AI flag or something. Not sure how well it would work, but worth an experiment.

bobowski 25d ago
Ai generate with human in the loop, so hard to say it’s not while also saying it’s terrible. Definitely the fact that I have ai makes it more fesable for me to actually publish something rather than spednign years on copy I can spend time on code and outsource copy
- alsanan 25d ago
  Agree. AI generated is not bad if it's well directed and audited in a loop by a human in good detail. I won't discard a project because a tool has been used. That's extremism. I'll take a look at the project first.
  - bobowski 25d ago
    Hope you’ll like it. At least concepts, I know htmx live or datastar are more mature so there’s no discussion about it. Would you have any hints what to avoid for „next time”? Should I just make this absurdly small and make much less polished approach even for this kind of project? Honest question. Will try to work on anything you suggest <3
- stanmancan 25d ago
  The only way to get better at writing is by writing. I’d rather read a less polished but clearly human written article than something clearly written by AI. If I can’t tell I can’t tell. Use it for editing or as a review but the weird hyperbolic AI stuff makes me instantly close an article. I barely got past the intro: ONE ATTRIBUTE. EXACT BEHAVIOR. The markup says what happens. Start with local behavior. Add the server only when the interaction needs to cross the wire. The attribute is moo= — in case you were wondering what the ox says.
  - bobowski 25d ago
    „You’re absolutely right” ;) Your onto something here, thanks - the title and the section where the things I’ve spent more time on than the rest I mean this „ Behavior, right where it happens. moo= for reactive signals and ordinary JavaScript on the element itself. Datastar SSE when the interaction has to cross the wire and patch HTML and state.” Still feels bad but I know I went trhu it couple of times. Not so much with the new sample you give here. Gotta work on that. Thanks!
    - stanmancan 25d ago
      I only shared because it might very well be cool stuff but if people are tired of AI writing and close it like me then it’s a lost opportunity. Not publishing at all is a bigger loss though, so it’s a tricky balance.
      - bobowski 25d ago
        Exactly my thoughts. Decided to publish and iterate. Deslopifying over time could verywell be a viable approach.

Ai generate with human in the loop, so hard to say it’s not while also saying it’s terrible. Definitely the fact that I have ai makes it more fesable for me to actually publish something rather than spednign years on copy I can spend time on code and outsource copy

alsanan 25d ago
Agree. AI generated is not bad if it's well directed and audited in a loop by a human in good detail. I won't discard a project because a tool has been used. That's extremism. I'll take a look at the project first.
- bobowski 25d ago
  Hope you’ll like it. At least concepts, I know htmx live or datastar are more mature so there’s no discussion about it. Would you have any hints what to avoid for „next time”? Should I just make this absurdly small and make much less polished approach even for this kind of project? Honest question. Will try to work on anything you suggest <3
stanmancan 25d ago
The only way to get better at writing is by writing. I’d rather read a less polished but clearly human written article than something clearly written by AI. If I can’t tell I can’t tell. Use it for editing or as a review but the weird hyperbolic AI stuff makes me instantly close an article. I barely got past the intro: ONE ATTRIBUTE. EXACT BEHAVIOR. The markup says what happens. Start with local behavior. Add the server only when the interaction needs to cross the wire. The attribute is moo= — in case you were wondering what the ox says.
- bobowski 25d ago
  „You’re absolutely right” ;) Your onto something here, thanks - the title and the section where the things I’ve spent more time on than the rest I mean this „ Behavior, right where it happens. moo= for reactive signals and ordinary JavaScript on the element itself. Datastar SSE when the interaction has to cross the wire and patch HTML and state.” Still feels bad but I know I went trhu it couple of times. Not so much with the new sample you give here. Gotta work on that. Thanks!
  - stanmancan 25d ago
    I only shared because it might very well be cool stuff but if people are tired of AI writing and close it like me then it’s a lost opportunity. Not publishing at all is a bigger loss though, so it’s a tricky balance.
    - bobowski 25d ago
      Exactly my thoughts. Decided to publish and iterate. Deslopifying over time could verywell be a viable approach.