We are a small team of developers working on a single multiplatform project (Web, Mobile and PC). One colleague in particular is in "charge" of the mobile application. I quoted that as he is not really in charge but simply the only one working on that project as per the higher ups choice. We have planning sessions at the start of each development cycle and for the sake of this post I will try to describe this as simple as possible.
My colleague starts spitting "facts" about how he can't do that, his dev env doesn't allow multi threaded work on mobile phones and other similar "fact" sounding stuff to our mostly code illiterate superiors. This in fact is just a cover up for the lack of knowledge about asynchronously running code.
This in the end results in us using the synchronous way and getting 10-15 seconds of startup time, which in turn gets the superiors attention and a meeting is scheduled to discuss this problem. He still adamantly states that he cannot do it because his tooling/dev env is limiting him and this really starts pissing the supes off. Eventually he actually starts learning about async code and finally implements it after like 6 months of development. All of a sudden it is a miracle, he basks in the glory of the async knowledge as he claims a new version of his IDE allowed for this to happen.
I mostly feel discredited and demotivated by this as it was originally my idea that I could actually implement and shorten the development of this application by a mile. He takes all the credit but based on fiction and deceit.
Should I just keep quiet and let it go or should try to document stuff like this and then point it out to my superiors?