9 ms·
A Deep Logo Study
- WillAdams 2mo agoWas a bit bummed that this wasn't Logo (the programming language), but the content was well-written, and engaging, and the honesty about AI usage was refreshing and for once felt appropriate. To come full circle, a bit curious if programming this in Logo (or some other vector graphics programming system) would be an interesting/useful exercise.
- nate 2mo agoYeah, the AI percentage usage thing is even a badge on the article which was a neat design touch too.
- Karma1532 2mo agoThanks, and thanks for putting it here in the first place!
- Karma1532 2mo agoTempted to try it as a follow-up now. And sorry for the naming collision.
- WillAdams 2mo agoI'd love to see that! That said, this is a powerful argument for _not_ capitalizing all words in a title and: >A deep logo study (dannyspina.com) would have been clearer.
- albert_e 2mo agohttps://dannyspina.com/ai https://dannyspina.com/ai I like this disclosure and approach. I had a very similar idea to use a label or tag to show on blog posts that I refine with help of AI. Havent gitten around ti implementing it yet. will take some inspiration from this.
- Karma1532 2mo agoGo for it! Mine is just a hand-set percentage per post.
- vanagandr 2mo agoOne thing AI will reveal is a lack of prose in people’s writing. The way most of this post is written is, well, kind of stilted. I don’t have a better word for it. Some people read it and equate to an LLM output. The way it ends is all over the place: “I have a name in my head for the repair side, and two cameras on the desk, and no idea yet whether any of it becomes a real thing. A mute mark does not force me to decide. It works as the logo of a freelance developer today, it would work on a box tomorrow, and it does not look silly either way. Which is roughly what the component does. It holds because it is not closed.”
- Karma1532 2mo ago[flagged]