Story time for the young kids in the room: Once upon a time, in my role as a technical consultant for hire at a large multinational corporation, I found myself tasked with a management board presentation. I was filling in for several project managers who were otherwise engaged due to urgent commitments.<p>My responsibility was to elucidate the difficulties stemming from the company's current internal systems integration architecture. I was to outline immediate measures for mitigating existing issues and offer a comprehensive plan for long-term resolution. With only a few days' notice, I prepared the required technical material, knowing well that the management board I was to address had a decidedly technical inclination.<p>As I delved into the presentation, I began to perceive an escalating sense of discomfort in the room. I quickly sought to discern whether the material was perhaps too tedious or excessively technical. Although the management board was known for its technical expertise, I couldn't immediately pinpoint the cause of the unrest. However, clarity struck in a sudden flash when a senior member of management hesitantly inquired, "Why are you using Mark's materials?" Mark, a pseudonym in this story, was the absent CTO who should have been present at the meeting.<p>After an instant of cognitive dissonance, the truth become clear...The CTO, who had engaged my services as a technical consultant, had been presenting my work to the management board for months, all the while assuming full authorship of the technical reports and presentations...