Could it just be that people with views at each end of spectrum see posts this like as part of a battleground, and everyone else stays clear of battlegrounds?
I think this
"* The software is pretty specific to my requirements."
is the biggest part for me. I built something with Antigravity over the holidays that I can use for myself and it solves my use case.
I tried thinking about if this can be helpful for others and pushed it a bit further into a version that could be hosted. Which does not make that much sense because it is a computationally intense numerical solver for thermal bridges and just awfully slow on a free hosted platform.
But the project was a couple of evenings and would otherwise haven taken me half a year to complete (and thus never been done).
> Antigravity did the vast amount of work, it feels unworthy
I think this is true for me as well. I have two types of projects that I’ve been working on - small ones with a mix of code I wrote and AI. I have posted these, as I spent a lot of time guiding the AI, cleaning up the AI’s output, and I think the overall project has value that others can learn from and built on.
But I also have some that are almost 100% vibe-coded. First, those would take a lot of time to clean up and write documentation for to make them publishable/useful.
But also, I do think they feel “unworthy”. Even though I think they can be helpful, and I was looking for open-source versions of those things. But how valuable can it really be if I was able to vibe-code it in a few prompts? The next person looking for it will probably do the same thing I did and vibe-code their own version after a few minutes.
Access to the audiobooks published for Yoto. Yoto daily (daily podcast for kids that my kids absolutely love). A button that plays relaxing music to help them go to sleep. The display (they love this a surprising amount). General polish (I imagine it's pretty janky if it took 2 evenings).
One difference is that if I submit an issue, and it requires some back and forth to figure out the actionable improvement, then suddenly the issue is very noisy.
Whereas if it goes via a Discussion first, the back and forth happens elsewhere.
Arguably an separate issue could still do this, but it being a discussion sets the expectation better.
This kind of thing happens in Jira or any company's internal bug tracker, and GitHub Issues is not any different. If you want a certain kind of "hygiene", you can always do that in the existing system instead of inventing a whole different solution.
> Arguably an separate issue could still do this, but it being a discussion sets the expectation better.
As someone wearing the post-sales support hat for a non-OSS product, I appreciate use of "ready" tags in Jira. Unlike OSS, our engineers prioritize KPIs to be compensated for their work, and so we must find a way to track the triage discussions within Jira. In a significant way, Jira is solid proof that work happened, even if no actual code was pushed into the repo. If the support team has an unconfirmed bug that requires a technical deep dive, then the "non-ready" Jiras seem like a good fit. I'm open to a better way of doing this and would like to learn more about alternatives, but for now, this is how the teams engage.
I had periscapular pain when sitting/standing for years: no pain in the morning, but it would grow during the day.
My backpod mobilises some stiff thoracic ribs, allowing me to then do exercises through that normal range of motion to strengthen it.