This message was deleted.
# feed
s
This message was deleted.
not kotlin but kotlin colored 2
🚫 1
y
Please try to include a link about this feature. #C0BJ0GTE2 is explicitly meant for sharing links about interesting kotlin-related things. Thus the link aspect is crucial
k
yes good idea
one sec
this is the website: https://firebender.com plugin: https://plugins.jetbrains.com/plugin/25224-firebender/ and the plugin does in 60 seconds so you have a good overall understanding
a
Yet again, this seems to be unrelated to Kotlin.
☝️ 1
💯 1
s
@Kevin #C0BJ0GTE2 is not meant for content like this. As said before, if you made an app or library with Firebender, you may share that. Thus your chess app you live built in Dave Leeds podcast shared as a GitHub repo together with the video would have been a great post. You may want to consider adding such a link to your previous post to improve it and make it a better fit for this place. For updates to Firebender you should stick to #C09DG7J8LDS and maybe consider #C0CMKCL87 - that said I don’t know how they feel about these posts. You will find out. Feed is not the place.
1
🫡 1
y
I'd appreciate it if at the very, very least there was a link to a blogpost or something with more info about this specific feature launch. I think the community clearly doesn't like ads in their #C0BJ0GTE2, and rightfully so, but at least making it a more useful ad would maybe help the reception a little bit. We're already in tangential-to-Kotlin territory because this is an IntelliJ plugin. Showing off specific creations made by firebender, or Kotlin-specific tips for it, would likely be the play here. Just my $0.02
💯 1
k
okay this makes a lot of sense, so kotlin creations with firebender is fair play, not feature launches but things actually built and written in kotlin
💯 1
y
Perfect! Again, feel free to post the feature launches in #C09DG7J8LDS since those users likely care.
🫡 1
s
maybe like this
@Kevin Depends, this specific article is a stretch in my eyes. The thing I personally like to see in #C0BJ0GTE2 the most are posts about helpful Kotlin libraries. That's why I'm here. Sharing sample apps (GitHub repos) written in Kotlin is also a helpful learning resource - that's why I ask for your chess game. Articles are a mixed bag. Some are really great and helpful, others (like that one) questionable. The link you shared doesn't explain something about Kotlin, it's just a tutorial on how to use Firebender. Therefore: a stretch. If you want to make a helpful article, maybe share the chess app you built on GitHub and release alongside with that an article about your finding how to prompt AI and how to not. You should be the expert here. Just make sure it stays on the Kotlin topic and you'd be fine. For example I don't understand how I'd use MCP with kotlin-wrappers - that's a great topic for an article.
But the article you you mentioned is something you should share in #C09DG7J8LDS.