Post History

Thank you for raising this. It's particularly useful to get a new user's perspective, because it's easy to forget how things were after getting used to them. I encourage you to continue raising anything that could be improved, even if you don't wish to participate in the Q&A yet.

For me personally, the difference that stands out is that Codidact is open to feedback and makes improvements. I've raised many bugs and feature requests because the first few I raised were fixed, which made me feel it was worth raising more. Over time I've started fixing some myself, made possible thanks to the very welcoming and supportive team.

You can filter the questions on Meta by tags to see how many bugs and feature requests have been raised, and how many have been completed (figures effective at time of posting):

Meta posts tagged with | Number of posts
---|---
["bug"][Meta posts tagged with "bug"] | [517][Meta posts tagged with "bug"]
["bug" and "status-completed"][Meta posts tagged with "bug" and "status-completed"] | [265][Meta posts tagged with "bug" and "status-completed"]
["feature-request"][Meta posts tagged with "feature-request"] | [558][Meta posts tagged with "feature-request"]
["feature-request" and "status-completed"][Meta posts tagged with "feature-request" and "status-completed"] | [170][Meta posts tagged with "feature-request" and "status-completed"]

The figures will include occasional duplicates so this is just a rough estimate, but it gives an idea of how much improvement is happening. There's also a post summarising the improvements that have been made: [Recent feature changes to the Codidact software](https://meta.codidact.com/posts/39539).

Any other suggestions for improvements are very welcome - on [Codidact Meta](https://meta.codidact.com/) for general improvements or here on Software Development Meta for things more specific to this community. Since Codidact is for the community, rather than for profit, decisions come from the community, and that can lead to customisations that are not supported elsewhere. For example, Code Golf Codidact has an automated leaderboard. This didn't need to wait for a company to decide to allocate resources to it. [Someone in the community made it, and it was added to the open source codebase](https://github.com/codidact/qpixel/pull/523).

There's plenty more to improve, but the fact that the improvement is happening is what keeps me here.

For Codidact overall (rather than Software Development Codidact in particular) there have also been some previous discussions that might be relevant:
- [What should I know when coming here from Stack Exchange?](https://meta.codidact.com/posts/277998)
- [Why prefer Codidact to Stack Exchange?](https://meta.codidact.com/posts/278006)


  [Meta posts tagged with "bug"]: https://meta.codidact.com/categories/3?predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags%5B%5D=394

  [Meta posts tagged with "bug" and "status-completed"]: https://meta.codidact.com/categories/3?predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags%5B%5D=394&include_tags%5B%5D=377

  [Meta posts tagged with "feature-request"]: https://meta.codidact.com/categories/3?predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags%5B%5D=961

  [Meta posts tagged with "feature-request" and "status-completed"]: https://meta.codidact.com/categories/3?predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags%5B%5D=377&include_tags%5B%5D=961