OM Copy and the Perfect Attribution Filter
OM Copy and the Perfect Attribution Filter
The advice passes with almost no loss. The acknowledgement never reaches the output.
A fictional club-room satire about credit and collaboration. OM is the traditional amateur-radio shorthand for “old man”; OM Copy is our imaginary presenter.
OM Copy has developed an extraordinary filter. It passes advice, explanations, sketches and useful corrections with remarkably little loss. Names, references and the words “with help from” disappear completely.
No expensive components. No alignment procedure. Performance improves automatically as the date of the next presentation approaches.
Other amateurs spend years trying to suppress unwanted signals. OM Copy has achieved a beautifully deep null in the direction of his sources.
Excellent reception at the workbench
Before the presentation, OM Copy is a model of collaborative enthusiasm. He asks questions. He shares a sketch. He wants to understand why connecting the next stage changes the circuit, whether another amplifier will actually help, and what a measurement really establishes.
Those are good questions. Asking them is how people learn. The colleague who answers usually enjoys the discussion too: a problem to investigate, an idea to test, another person building something instead of merely arguing about it.
Advice goes back and forth. A suggestion fails. Another leads somewhere useful. The builder makes decisions, changes the prototype and does the practical work.
So far, this is amateur radio doing exactly what it should.
Then someone connects a projector.
The pronoun conversion stage
The projector activates a little-known process. Discussions become discoveries. Suggestions become insights. The person who helped explain a problem becomes a faint disturbance somewhere below the noise floor.
The prototype required several conversations. The presentation requires only one pronoun.
I.
OM Copy explains how he identified the difficulty, considered the alternatives and arrived at his solution. The slides are beautifully uncluttered. Removing the acknowledgements has freed enough space for a larger photograph of the finished enclosure.
This is elegant engineering. Every unnecessary connection has been removed, especially the connection between the explanation and the person who supplied it.
A remarkably selective memory
OM Copy remembers the useful explanation with impressive precision. He remembers why the first approach failed. He remembers the suggested test. Sometimes he even remembers the analogy that made the whole thing click.
The name attached to that explanation proves much harder to retain.
Perhaps names require a different memory technology. Perhaps the firmware has a limitation. We should investigate before jumping to conclusions.
In the meantime, the technical content survives the journey perfectly. Only its history experiences severe attenuation.
Building something still counts
Here is where the joke needs a fair boundary. Someone who asks for advice and then builds, tests and improves a device has done real work. A useful answer does not automatically make its author the designer of the entire project. Explaining a standard principle does not give anyone ownership of that principle.
Equally, there is a difference between building an established circuit, adapting someone else's approach, receiving help with a particular problem and developing a new design. All can be worthwhile achievements. Describing them accurately gives each contribution its proper place.
Acknowledgements can be precise:
- “I built and tested this version from the published design by…”
- “A discussion with… helped me understand the loading problem.”
- “The measurements were made by…; these changes are mine.”
- “The original project is here. This is what I changed and why.”
None of those sentences takes the soldering iron out of the builder's hand. They give the audience a more useful account of what happened.
OM Copy remains concerned that an acknowledgement might reduce his gain. We await the measurements.
Freely shared knowledge has a history
I publish explanations because I want people to use them: read them, question them, try the ideas and build something better. A useful conversation can do the same job. Helping someone understand a circuit is one of the pleasures of this hobby.
That generosity works best when the trail survives. A source lets the next reader find the full explanation, its assumptions and its limitations. An acknowledgement shows which part came from a discussion and which part the builder established independently.
Credit also tells the next newcomer something valuable: competent people ask questions. Good projects can grow through collaboration. The person at the front of the room did not necessarily emerge from the workshop knowing everything.
Erase that process and we teach the audience the wrong lesson about how engineering happens.
Whatever licence applies to a particular document or project, the courtesy I am describing is straightforward: tell an honest story about the work and the help behind it.
The repair costs one sentence
We should leave room for ordinary mistakes. A forgotten acknowledgement can be corrected. A short event announcement is rarely a complete list of contributors. One missing name does not establish a whole history of deliberate omission.
The useful response is to put the missing contribution back where readers or listeners can find it. Add the source link. Correct the article. Thank the person when presenting the part they helped with. Describe the help accurately, without implying they designed or endorse everything else.
No committee is needed. No commemorative plaque. “That discussion helped me get this part right” will do nicely.
For OM Copy, this presents a serious technical challenge: an extra line on a slide.
Fortunately, modern projectors can handle it.
Leave the names connected
The real cost of disappearing credit arrives at the next conversation. If helping repeatedly means becoming invisible once the work reaches an audience, people may become less willing to spend their evenings explaining, checking and encouraging.
A hobby built on shared knowledge has good reason to look after that willingness.
Keep asking questions. Keep experimenting. Give yourself proper credit for the work you did, and give others proper credit for the contribution they made.
OM Copy's attribution filter has had a good run. It is time to bypass it.
Keep sharing the circuit. Just leave the names connected.
Mini-FAQ
- Is asking for technical help the problem? No. Questions, discussion and shared experiments are valuable parts of amateur radio. The satire concerns giving a misleading account of where useful contributions came from.
- Does every helpful answer make someone a co-designer? No. Describe the actual contribution: an explanation, a suggested test, a published design, measurements or joint design work.
- Does an acknowledgement imply endorsement? It should not. Explain what the person contributed and avoid implying that they approve the complete project.
- What if I forgot to acknowledge someone? Correct the publication or slides and add the missing contribution. A clear, proportionate acknowledgement is usually a straightforward repair.
Found this useful? Support my writing and experiments: Buy me a coffee.