Well, @lobsters decided to slap a vibecoding tag on a story about a project I worked on, which was not vive coded, because someone trolled in the comments.
-
Well, @lobsters decided to slap a vibecoding tag on a story about a project I worked on, which was not vive coded, because someone trolled in the comments. Which meant the story was hidden for me.
If anyone is wondering why I don’t post there as much as I used to.
-
Well, @lobsters decided to slap a vibecoding tag on a story about a project I worked on, which was not vive coded, because someone trolled in the comments. Which meant the story was hidden for me.
If anyone is wondering why I don’t post there as much as I used to.
@david_chisnall I have a feeling that people who are butthurt about the tag slap it on everything to make it useless. But that may be just paranoia.
I still check the tag for that reason but it‘s nice to have the LLM boosting out of the standard timeline.
-
Well, @lobsters decided to slap a vibecoding tag on a story about a project I worked on, which was not vive coded, because someone trolled in the comments. Which meant the story was hidden for me.
If anyone is wondering why I don’t post there as much as I used to.
@david_chisnall @lobsters The reason given is the existence of this folder: https://github.com/microsoft/bocpy/tree/main/.github
That doesn't seem like trolling to me? But I am not up to date on what various LLM-related files actually imply concretely.
-
@david_chisnall @lobsters The reason given is the existence of this folder: https://github.com/microsoft/bocpy/tree/main/.github
That doesn't seem like trolling to me? But I am not up to date on what various LLM-related files actually imply concretely.
@krig @david_chisnall @lobsters in particular the copilot instructions file in that folder. I don't know whether Copilot has already been used by that project or not, but the presence of that file indicates the intention to use it, so I actually find the vibecoding tag useful. I agree that the link title seems like trolling (anything from MS is vibe-coded), but it seems to be correct for this project.
-
@krig @david_chisnall @lobsters in particular the copilot instructions file in that folder. I don't know whether Copilot has already been used by that project or not, but the presence of that file indicates the intention to use it, so I actually find the vibecoding tag useful. I agree that the link title seems like trolling (anything from MS is vibe-coded), but it seems to be correct for this project.
@edwintorok @david_chisnall @lobsters Given that Microsoft apparently has made AI usage mandatory for employees, even the title doesn't seem over the top. https://www.forbes.com/sites/bernardmarr/2025/07/08/microsoft-makes-ai-mandatory-for-employees-what-it-means-for-your-career/
-
@david_chisnall @lobsters The reason given is the existence of this folder: https://github.com/microsoft/bocpy/tree/main/.github
That doesn't seem like trolling to me? But I am not up to date on what various LLM-related files actually imply concretely.
It has a file that enables people to use Copilot. Microsoft employees are actively pushed to use it, but that doesn't mean that the project is vibe coded (it was not - I reviewed some of the code and it was quite painstakingly written by a human who spent a long time understanding the subtleties of the CPython implementation, which is something LLMs would be really bad at).
If you're saying 'any project that accepts any LLM contributions deserves the vibecoding tag', that's a policy choice. I'm not entirely opposed to that, but it means that, for example, any story about Linux should have the vibecoding tag. As should a huge number of other F/OSS projects. And that's fine as a self-consistent policy, but that's when I stop bothering to read the site.
-
R relay@relay.infosec.exchange shared this topic
