Post History

We can't go and shamelessly promote Codidact in SO comments etc just for the sake of it - that's regarded as spamming and might get you banned, plus it will give Codidact a nasty rep. Similarly, SE and many other sites frown upon using "signatures" in your posts.

What you can do - and what I've been doing myself - is to refer to Codidact posts as a link to an on-topic source, resource or duplicate. I've been writing some self-answered Q&A here to get the site going and I refer to those posts from my SO activity. 

This requires some good "canonical dupe"/FAQ-like technical content here on this site though, preferably better than the present "canonical dupe" on SO. Which might sound intimidating at first - how do we make something better than SO posts that have been up-voted and peer reviewed by hundreds of users? But it's actually not that hard, given that you know the topic.

To take a practical example, then #1 all-time most common C programming FAQ has this canonical dupe on SO: [Why are these constructs using pre and post-increment undefined behavior?](https://stackoverflow.com/questions/949433/why-are-these-constructs-using-pre-and-post-increment-undefined-behavior)

The question is good with lots of examples, but the each individual answer is actually not that good at all. They are individually incomplete and lack detail - in order to truly understand the problem, you have to go through multiple answers, each containing various pieces of the puzzle that makes a complete answer. And the 500+ top-voted answers is basically just "this is undefined behavior, don't worry your pretty head about it". It's actually quite bad, likely it gets massively up-voted because people always refer to the above link out of habit.

So I made a more complete self-answered Q&A here on Codidact:  
[Why can't we mix increment operators like i++ with other operators?](https://software.codidact.com/questions/278384)  
This goes into all the dirty details of _why_ the code doesn't work, explains the various rules and terms of the language, mentions common misconceptions etc. I personally believe that it holds higher technical quality than the SO post, since it is a single answer containing everything that's scattered over multiple answers in the SO post. It's also up to date, some answers on the SO post became slightly outdated in 2011 when there was a major language revision.

If we can keep referring to higher technical content on Codidact than on SO, then we will win over domain experts from there. Who in turn can make more high quality posts: it becomes a "positive circle".