Why We Write the Way We Do at RF.Guru

A friendly conversation with a fellow radio amateur made me stop and think about our publications. Were some becoming too technical? How many readers are comfortable with technical English, equations or the mathematics behind an antenna? Those are fair questions. An explanation succeeds when it helps someone understand, not simply when its author can defend the mathematics.

My answer starts with why I write at all. I want people to understand what happens in their stations, make better decisions and feel able to investigate a question for themselves. Most of our articles are intended to offer a useful explanation without requiring an engineering degree. That explanation can still go deeply into the physics. Mathematics and scientific evidence belong alongside it, with a route into them for readers who want to learn.

The writing comes from the same place as the hardware

In Why We Started RF.Guru, I describe the frustration that led us to build equipment ourselves: avoidable failures, vague specifications and too little explanation of why a design should work in an actual installation. A failed active loop was part of that story. Wanting better answers was another part.

I was also fed up with half-truths, oversimplifications and folklore repeated as if repetition made them complete explanations. Often there was a useful observation underneath. The trouble began when advice from one installation became a rule for every antenna, every frequency and every location.

Writing became a way to address that frustration constructively. If I challenge an explanation, I owe the reader a better one: what happens, why it happens, when it matters and how we might check it.

That connects directly to our Modern Mission Statement for Amateur Radio. Amateur radio gives us room to ask questions, build, measure, operate and share what we learn. The publications are part of that activity. Their purpose is to help more people participate.

A simple explanation still needs its boundaries

Simplification is essential to teaching. We choose what to explain first and leave some detail for later. The responsibility is to keep the first explanation true within the conditions we give it.

Consider a familiar example: a low standing wave ratio, or SWR. This reading tells us about the electrical match where the meter is connected. By itself, it does not tell us how much power the antenna radiates. A suitable dummy load, a test device designed to absorb transmitter power, can give an excellent match while turning almost all the supplied power into heat.

A newcomer can understand that distinction without studying transmission-line equations. It is already useful when deciding what a meter reading proves. A reader who wants to investigate further can move on to feed-line losses, measurement location and the relationship between voltage, current and power.

The misleading shortcut would be to turn “a good match is useful” into “a good match proves the antenna is efficient.” The missing qualification changes the advice. Our article on SWR, reflected power and return paths explores those separate questions in more detail.

Experience remains valuable. An operator’s report that something worked can be the beginning of an investigation. To turn that observation into advice for somebody else, we need to understand which parts of the installation made the result possible.

A syllabus should be a beginning we can build on

My frustration with parts of the UBA and ARRL study material I have encountered is that I often want more of the underlying explanation: why a rule works, which assumptions it makes and what happens when the circumstances change. An exam answer can be correct within its intended scope and still leave those questions unanswered.

Licence courses have a defined syllabus, limited time and an important job to do. UBA describes its handbook as support for the examination syllabus. ARRL also provides further technical references and teaching resources; its General Class manual support page explicitly offers additional background. My concern is the gap that remains when a learner encounters the short rule and never reaches the explanation behind it.

When an introductory explanation leaves out a difficult step, we should still show readers how to reach it. Otherwise, a shortcut can lose its original qualifications as it is passed from person to person. Eventually it becomes folklore: a confident rule whose physical explanation has disappeared.

That is the gap I want these publications to help close. Begin with an explanation that is accurate enough to build on. Add the missing steps. Introduce the mathematics when it helps. A beginner should be able to extend an earlier understanding rather than discover that the first explanation has to be unlearned.

The question determines the depth

A practical installation question, a measurement problem and a disputed claim about electromagnetic theory need different kinds of answers. Treating every subject at the same depth would serve all three badly.

If someone asks what wavelength means, the place to start is the physical idea, familiar dimensions and a simple antenna example. That is the approach behind It All Starts With Lambda. If the question is why two measurements disagree, the test setup, settings and assumptions may become central to the explanation.

If a reader asks whether Heaviside removed something important from Maxwell’s theory after encountering that claim elsewhere, a reassuring opinion is not enough. At some point we need to examine the original argument and the equations. That is why Did Heaviside Delete Maxwell? goes further. The question calls for that evidence.

Even then, the opening should explain what the dispute is about and why it matters. Mathematical symbols need an introduction before the argument depends on them. Several of our specialist publications exist because readers specifically asked for that level of analysis. Technical depth is justified by the question and the work it does for the reader.

One article can offer several depths of explanation

This is a familiar writing approach, usually described as layered content or writing for a mixed audience. MIT’s technical-writing guidance recommends clear summaries, sections for different audiences and explanations of technical terms.

For RF.Guru, that means building an article around a few reader needs:

• Understand the question. What are we trying to explain or decide?
• Get a useful first answer. What does it mean in a station, at an antenna or on the bench?
• Follow the reasoning. What mechanism, evidence or measurement supports that answer?
• Explore further. Which calculations, original sources and limitations matter if you want to go deeper?

The important conditions belong with the practical advice. A safety requirement or a limitation that changes the recommendation cannot be hidden at the end and called optional detail.

A reader may stop after the practical explanation. Another may study the measurements. Someone else may check the derivation. The article should make those choices easy. An engineer also benefits from a clear introduction; a newcomer may eventually want the deeper sections.

The mathematical section should itself be teachable. Explain what each quantity represents, show the units, work through an example and connect the result back to the physical behaviour. Science and mathematics are part of what we want to bring to everyone. They become more accessible when we provide the steps needed to reach them.

Everyone, Basic and Expert describe where to start

The reading labels and filters in The Guru’s Incredible Lab help readers choose an entry point. Most of our published articles are classified as Everyone. There is also a growing Basic collection and a small group of Expert articles.

Label	What the reader should expect
Everyone	An approachable explanation of the question, with further technical depth where it helps.
Basic	A guided introduction that builds the vocabulary and physical ideas, as in our 101 series.
Expert	A specialist discussion that assumes relevant RF knowledge, measurement experience or mathematics from the start.

These labels describe the knowledge an article assumes. They do not rank readers, and they do not set a ceiling on what anyone may learn. An Everyone label is also a commitment I have to fulfil in the writing. If the opening depends on unexplained jargon, the label alone has achieved nothing.

There is more than one way to learn

Sometimes text helps most; sometimes a drawing, a demonstration or a repeatable experiment makes the idea clearer. The Ham Radio 101 collection provides a foundation, while Mark’s Ham Florida Man videos offer practical demonstrations and another way into the discussion. A video and an article can answer different parts of the same question.

Analogies can help too. A water-pipe comparison may introduce an electrical idea, provided we explain where the comparison stops working. A helpful first picture should leave room for the fuller explanation.

You do not have to become an RF engineer to enjoy amateur radio. If the engineering interests you, there should be a clear path into it. I want the publications to support that curiosity at whatever point it begins. My longer-term intention is to develop the 101 material into a book that builds that foundation progressively.

English lets us share one reference with an international audience

RF.Guru is based in Belgium, but our readers and customers are international. English gives people in many countries a common version to read, discuss and link to. That choice also creates a language barrier for some readers, and technical English can make it higher.

Over the years I have received hundreds of messages from readers who say an article helped something finally make sense. Some are in their seventies or older and use translation software to read the publications. Those replies are encouraging. They do not prove that every article works equally well for every reader.

I also write for Dutch-speaking audiences and prepare Dutch and French versions for UBA publications. Checking those translations can take me longer than writing the English original. Terminology, qualifications and the strength of a claim all have to survive the translation. AI can help with that work, but fluent wording still needs technical checking.

Broader multilingual publication remains something I would like to make more practical. Meanwhile, clear sentences, defined terms and consistent vocabulary help both direct readers and people using translation tools.

Useful publications belong in a business that sells engineering

RF.Guru is a business, and these publications are part of it. They let readers examine how we think, what questions we ask and what evidence we consider useful. That can build trust before someone buys equipment and help a customer choose something suitable for the job.

It should also help someone recognise when they already have the right equipment, when an installation needs attention or when buying another component will not answer the question. Advice that leads to no purchase can still be good advice.

I see this body of knowledge as an asset worth developing. A useful explanation can help readers for years, including after a particular product has changed. The business has grown while we have continued publishing, but growth alone does not tell us how much the publications contributed. Products, recommendations, demonstrations, service and many other factors contribute. Sales figures cannot prove an RF explanation correct, either.

The engineering standard must apply to our own claims as well as anyone else’s. Readers should be able to trace a conclusion to its sources, distinguish a calculation from a measurement, and see where the available evidence stops. That remains useful whether they buy from us, build something themselves or simply want to understand their station.

If something is unclear, please tell us

After six years of publishing, there is a substantial range of subjects and styles in the library. Some articles will need clearer openings, better definitions or a missing step between the practical explanation and the mathematics. A writing method is an intention; each article still has to deliver on it.

A general comment about difficulty is a useful signal. A title and a passage make it much easier to act on. Tell me where you lost the thread, which term needed explaining or which conclusion did not follow from the example. You do not need to diagnose the writing problem or propose the correction yourself.

Sometimes the answer will be a simpler sentence or a diagram. Sometimes a separate introductory article will help. Sometimes the technical section needs to stay, with a clearer route into it. The aim is to make the explanation easier to follow while keeping the evidence and qualifications that make it reliable.

I want readers to leave with a useful answer and a way to investigate the next question. That is why RF.Guru publishes: to turn curiosity and frustration into understanding that people can use, test and share.

Questions, antenna-factor records or height trials to share? Contact RF.Guru.