>instead of being frustrated at the statement that my TypeScript and the other team's C needs to use the same headers, I focused on how to communicate, in an ec

>instead of being frustrated at the statement that my TypeScript and the other team's C needs to use the same headers, I focused on how to communicate, in an economy of words, why this API deviation may be a process problem, not a technical one. The statement actually makes a lot of sense if you don't take it literally. If you programmatically generate both C and TS part from the same common definition (protobuf?) as a part of the build process, API deviation will become an easy-to-see compile-time error instead of a runtime surprise.