Skip to content

Your cart is empty

Continue shopping

Have an account?

Log in to check out faster.

Your cart

Loading...

Estimated total

€0,00 EUR

Tax included and shipping and discounts calculated at checkout

RF.Guru projects

  • VFO-Knob
  • SmartCW
  • OpenX6X00
  • TailChaser
  • SVXConnect
  • Apps
Listen to our SDRs↗ The Guru’s Lab→
  • New
  • Swag
  • HotSpot
  • Repeater
    • Build Your Own Repeater
    • ON0ORA
  • BalUn/UnUn
    • Balun/LineIsolator/Choke
    • Unun/Transformers
    • Lightning & Surge Protection
    • AC/DC Choke/LineIsolator
    • Grounding
    • Anti-Corrosion
  • Filters
    • VHF-UHF Filter
    • Line Filters
  • Antenna
    • HF Active RX Antenna
    • HF End Fed Wire Antenna
    • HF Verticals - V-Dipoles
    • HF Rigid Loops
    • HF Doublets - Inverted Vs
    • HF Stealth POTA/SOTA Antennas
    • UHF Antenna
    • VHF Antenna
    • Dualband VHF-UHF
    • Grounding
    • Masts
    • Guy Ropes & Accessories
    • GPS Antenna
    • Mobile Antenna
    • Handheld Antenna
    • ISM Antenna 433/868
    • Antenna Tools
    • Anti-Corrosion Lubricants
    • Dummy Load
  • Coax
    • Coaxial Seal
    • Coax Connectors
    • Panel Mount Connectors
    • Coax Adaptors
    • Coax Tools
    • Coax Cable
    • Coax Surge protection
    • Jumper - Patch cable
  • 19"
  • 13.8 V
    • DC-DC
    • AC-DC
    • Powerpole
    • 13.8 V Cable
  • PA
    • VHF Power Amplifiers
    • UHF Power Amplifiers
  • Parts
    • Ferrite
    • Pi
    • Routers
    • Enclosures
  • PCB
  • SDR
  • APRS
  • LAB|KB
Log in

Country/region

  • Belgium EUR €
  • Germany EUR €
  • Italy EUR €
  • Sweden EUR €
  • Australia EUR €
  • Austria EUR €
  • Belgium EUR €
  • Bulgaria EUR €
  • Canada EUR €
  • Croatia EUR €
  • Czechia EUR €
  • Denmark EUR €
  • Estonia EUR €
  • Finland EUR €
  • France EUR €
  • Germany EUR €
  • Greece EUR €
  • Hungary EUR €
  • Ireland EUR €
  • Italy EUR €
  • Japan EUR €
  • Latvia EUR €
  • Lithuania EUR €
  • Luxembourg EUR €
  • Netherlands EUR €
  • New Zealand EUR €
  • Norway EUR €
  • Poland EUR €
  • Portugal EUR €
  • Romania EUR €
  • Slovakia EUR €
  • Slovenia EUR €
  • South Africa EUR €
  • Spain EUR €
  • Sweden EUR €
  • Switzerland EUR €
  • United Kingdom EUR €
  • United States USD $
  • YouTube
RF.Guru Logo
  • New
  • Swag
  • HotSpot
  • Repeater
    • Build Your Own Repeater
    • ON0ORA
  • BalUn/UnUn
    • Balun/LineIsolator/Choke
    • Unun/Transformers
    • Lightning & Surge Protection
    • AC/DC Choke/LineIsolator
    • Grounding
    • Anti-Corrosion
  • Filters
    • VHF-UHF Filter
    • Line Filters
  • Antenna
    • HF Active RX Antenna
    • HF End Fed Wire Antenna
    • HF Verticals - V-Dipoles
    • HF Rigid Loops
    • HF Doublets - Inverted Vs
    • HF Stealth POTA/SOTA Antennas
    • UHF Antenna
    • VHF Antenna
    • Dualband VHF-UHF
    • Grounding
    • Masts
    • Guy Ropes & Accessories
    • GPS Antenna
    • Mobile Antenna
    • Handheld Antenna
    • ISM Antenna 433/868
    • Antenna Tools
    • Anti-Corrosion Lubricants
    • Dummy Load
  • Coax
    • Coaxial Seal
    • Coax Connectors
    • Panel Mount Connectors
    • Coax Adaptors
    • Coax Tools
    • Coax Cable
    • Coax Surge protection
    • Jumper - Patch cable
  • 19"
  • 13.8 V
    • DC-DC
    • AC-DC
    • Powerpole
    • 13.8 V Cable
  • PA
    • VHF Power Amplifiers
    • UHF Power Amplifiers
  • Parts
    • Ferrite
    • Pi
    • Routers
    • Enclosures
  • PCB
  • SDR
  • APRS
  • LAB|KB
Log in Cart

My Phone Is on Do Not Disturb. The Projects Aren’t.

Reading level: everyone — Technical depth when you want it
From the RF.Guru bench · How I work

My Phone Is on Do Not Disturb. The Projects Aren’t.

People often ask how I keep so many projects moving. They asked long before AI arrived. My answer is fairly ordinary: I protect my attention, think through what I am building, and regularly check where my time actually goes. The interesting part is doing those things consistently.

FocusDesign rationaleShared knowledgeOriginal products

Related Reading

The Guru’s Incredible Lab — the growing publication library

The work starts before I start building

When I begin a development project, I write the rationale first. Why are we building this? Whose problem does it solve? Why this approach? What would make the result useful enough for someone to choose it?

I enjoy that part enormously. Thinking through the problem, finding the weak assumptions and choosing an architecture are often the most interesting work in the entire project. Once the important choices are clear, implementation becomes much more focused. There are still surprises, but fewer hours disappear into decisions that should have been made before the first line of code or the first PCB layout.

A rationale does not need to become a fifty-page document. A page that explains the problem, the constraints, the proposed solution and the main uncertainty can be much more useful. Add what success would look like and what the first version deliberately leaves out. Now there is something concrete to build and something concrete to test.

It is also a working document. If a measurement disproves an assumption, change the approach. Thinking first does not mean pretending that thinking can replace experiments. Sometimes the most useful next step is a small prototype that answers one awkward question before the rest of the design depends on it.

Give the project a reason to exist before giving it a parts list. A clear purpose makes later decisions easier: does this change help solve the original problem, or are we simply adding another feature?

Several projects, one piece of work at a time

Having several projects underway does not mean trying to think about all of them at once. I divide my day into sprints: blocks in which one piece of work gets my attention. During that block, a different project may have a perfectly interesting idea attached to it. The idea can wait.

My phone stays on Do Not Disturb. Notifications and pop-ups are off, apart from things directly relevant to the project I am working on. I check email, tickets and chats three times a day. Leaving them open all day would give every incoming message a vote on what I should do next.

That is a poor way to design anything complicated. You come back to a circuit or a section of software and spend time reconstructing the reasoning you had in your head a few minutes earlier. The interruption may have lasted thirty seconds; recovering the thread can take longer.

There is an important distinction here: protecting attention does not cancel commitments. People still deserve answers. A predictable response routine is useful; disappearing behind “I am focusing” while someone is blocked is not. Where a role genuinely requires urgent cover, arrange that explicitly rather than treating the entire inbox as an emergency channel.

Nor does every project deserve to be active today. A useful idea can live in a backlog. Too much work in progress creates a collection of nearly finished things, each carrying its own mental overhead. The question is not only “What can I start?” It is also “What can I finish, test and put into use?”

A break does not have to look like another screen

Between sprints, I often do something that asks less of the same kind of concentration. I solder something, tidy up, or simply do nothing for a while. Changing the kind of work helps me return with a clearer head.

Of course, soldering a familiar assembly is different from debugging a delicate new circuit. The second one is another demanding task, whatever tool happens to be in my hand. The point is to recover attention, not disguise more intense work as a break.

I get more out of that rhythm than out of forcing eight continuous hours at the same problem after my concentration has already gone. A calendar full of activity is not proof of useful output. Some of the best decisions arrive after stepping away long enough to see what I had stopped noticing.

If I keep repeating it, I ask whether it needs a tool

When I notice myself performing the same operation repeatedly, I often build a little tool for it. Over time, I have accumulated quite a few that make my daily work easier.

That might mean turning a manual check into a script or making a small interface for a task that otherwise involves too many steps. The value is not that the tool is impressive. The value is that a recurring job becomes simpler, more consistent and less dependent on remembering every detail.

There is a trap, though: you can spend a whole afternoon automating something you will do twice. The useful calculation includes the time to build the tool, check it and maintain it. Automate a process you understand and expect to repeat. Otherwise you may simply manufacture a second project around the first one.

Good tools should reduce future obligations. A clever shortcut that requires constant repair has a habit of becoming another item in the inbox.

The publication library is part of the method

The mailing list and the large number of RF.Guru publications are a good example. I receive questions continually. Many are variations on subjects that have already come up. I can write a fresh explanation in every reply, or I can take the time to explain the subject properly and make that explanation publicly available.

That is why I build a library. A useful answer should be able to help more than the person who happened to ask first.

This gives the work two benefits. First, a public library creates reach: people can discover an explanation through search, a shared link or the mailing list, even if they have never contacted us. Second, it becomes something we can offer directly to someone asking a question. The next reply can begin with a relevant article and then address the details specific to that person’s situation.

The mailing list helps people find new additions. The library gives those publications a lasting home. One distributes the work; the other keeps it useful after the announcement has disappeared down an inbox.

There is an important condition: a link is not a substitute for listening. If someone describes a particular installation or a failure, I still need to understand what makes that case different. The article handles the shared explanation. The reply handles the application, the missing information and any exceptions.

Nor is publishing once the end of the job. A library needs understandable titles, working links, useful related reading and updates when something changes. If readers cannot find an answer, or the answer is obsolete, the same questions come back. The savings depend on keeping the knowledge usable.

A repeated question can become a lasting resource. Answer the immediate question, identify what others can reuse, publish that explanation, and improve it when the next question reveals something you missed.

That is the purpose of The Guru’s Incredible Lab: knowledge people can read, share and return to without a paywall. It supports the community and makes our own work more efficient. Those two purposes fit together quite well.

Build from a problem, not from someone else’s feature list

The same reasoning applies to software and physical products. I want a clear USP: a unique selling proposition, or in ordinary language, a concrete reason why someone should choose this particular solution.

“Another version of what already exists” is not much of a starting point for me. I prefer to begin with the problem and work out the approach from scratch. If you start by copying someone else’s layout, feature list and assumptions, you can spend the entire project refining answers to questions you never asked.

Start instead with the user. What is unnecessarily difficult? Which jobs require several awkward steps? What fails in the conditions where the equipment is actually used? What could become easier to install, understand, repair or maintain?

Uniqueness only matters if it creates useful value. An unfamiliar connector is certainly different; it may also be a nuisance. A simpler workflow, better behavior under clearly defined conditions, or an interface that removes a recurring mistake gives someone a reason to care.

A useful test is to finish this sentence without vague adjectives: “For this person, doing this job, our approach improves this specific thing.” If I cannot do that, I probably need more thinking before I need more features.

Original thinking does not require collective amnesia

There is an apparent contradiction worth clearing up. I say “start from scratch,” and I also say there is little value in repeatedly reinventing the wheel. Both make sense when applied to the right part of the job.

Start the reasoning from the actual problem. Do not start the entire body of engineering knowledge from zero. Established physics, standards, well-understood circuit techniques, mature software libraries and other people’s published lessons are useful foundations.

I do not want someone else’s finished product to dictate my design. That does not mean refusing to learn what already exists. Understanding prior work can expose a false assumption, avoid a known failure and show that a supposedly new idea is not new at all. When using someone else’s work, respect its license and give the appropriate credit.

The worthwhile originality lies in the problem you choose, the decisions you make and the value of the result. There is no prize for rebuilding a dependable standard component badly just so you can say every part was your own.

Meetings need a purpose too

I apply the same discipline to meetings. I participate when they are prepared and there is something concrete to discuss.

I send my report fourteen days before the meeting. If there is no response, I generally assume there is nothing to add concerning my report and do not join. That occasionally drives people a little crazy. 😉

The wider principle is to put information in writing early enough for people to read it, then use the meeting for questions, decisions and disagreements that benefit from an actual conversation. Reading a report aloud to people who could already have read it is an expensive distribution method.

That approach does need shared expectations. Silence is not automatically agreement, and a meeting may require someone’s presence for a decision unrelated to their report. Make the purpose and responsibilities clear. The aim is to remove unnecessary attendance, not to make collaboration harder.

Every quarter, I look at where the time went

A routine that worked three months ago may no longer fit the work in front of me. Every quarter, I review where my time is going. Which projects receive how much attention? What takes more time than it gives back? Which habits still help, and which have quietly become overhead?

“Gives back” does not have to mean immediate revenue. Learning, community work, a useful public explanation and a tool that saves future effort can all be worthwhile returns. The point is to choose those investments consciously.

I also want to see the maintenance cost behind new work. A product needs documentation and support. Software needs updates. An article needs corrections when the evidence changes. Starting something creates obligations beyond launch day; those belong in the decision.

A good review should change something. Stop an activity that no longer makes sense. Simplify a process. Finish a neglected piece of work before opening another. Leave room for the unexpected instead of planning every available hour and calling the resulting overload a surprise.

Without that adjustment, an agenda gradually fills with yesterday’s decisions. Eventually there is no space left for the work you would choose today.

AI makes parts of this faster

AI now accelerates part of my work. It can help turn a clear intention into a draft, code or a first implementation more quickly. But people were already asking how I managed several projects before those tools were available.

The rationale still matters. So do the acceptance criteria, testing and judgment. Producing something quickly is only useful if I can establish that it solves the problem and that I understand what I am putting into use.

A vague request can generate a lot of plausible-looking work that still needs to be untangled. A clear problem, sensible boundaries and a way to check the result make the assistance much more valuable. Faster execution makes choosing the right work more important.

Yes, there are bad days

Do I have ups and downs? Of course. Some days a difficult problem suddenly becomes clear. Other days I reread the same thing and get nowhere. Structure does not make a person immune to fatigue, frustration or life happening.

What it gives me is something to return to. The rationale reminds me why the project exists. Notes preserve decisions. A defined next step makes restarting easier. A familiar rhythm gives the day a shape when motivation does not provide one.

That is also why I would not turn this into a rule that everyone must follow exactly. Different jobs, family responsibilities and support commitments leave people different amounts of control. Three message checks a day fit my method; they are not a universal measure of discipline. Use the control you have, and make realistic arrangements for the rest.

A system that only works when you are enthusiastic, rested and uninterrupted is missing an important operating condition.

Keep ownership of your time

I often recommend this way of working. I see it applied consistently much less often. The individual habits are not particularly exotic. Their value comes from keeping them in place, checking whether they still work and adjusting them when they do not.

Think before building. Give focused work a protected place in the day. Turn repeated operations into sensible tools and repeated explanations into shared knowledge. Build products around a real reason to exist. Finish things. Review what all of it costs to maintain.

I want time for the interesting thinking, the experiments and the work that makes a difference. That requires making choices about what gets my attention and what can wait.

My phone can stay on Do Not Disturb. There is plenty happening at the bench.

Follow the Current Path, Not the Folklore

Explore more RF.Guru technical deep dives on transmission lines, common-mode current, baluns, chokes and antenna measurement—and subscribe for new engineering articles and laboratory notes.

Join the notification list →

Quick Questions

  • Does working on several projects mean multitasking all day? No. Several projects can progress over a week while each work block has one clear focus. Limit the number actively competing for attention.
  • How much rationale should I write? Enough to explain the problem, intended user, constraints, approach, main uncertainty and a useful definition of success. Keep it proportionate and revise it when evidence changes.
  • When is a recurring question worth an article? When a substantial part of the answer will help others. Publish that common explanation, then keep individual replies specific to the person asking.
  • Does an original product require every component to be new? No. Use sound foundations and respect attribution and licenses. Originality should create a meaningful benefit for the user.
  • Should everyone check messages only three times a day? No. That is my routine. Agree on response expectations and any urgent coverage that your responsibilities require.
  • What does the structure do on a difficult day? It preserves the purpose, decisions and next steps so restarting takes less effort. It does not remove the need for rest or realistic commitments.

Questions or working methods to share? Contact RF.Guru.

Joeri Van Dooren, ON6URE — RF engineer, antenna designer and founder of RF.Guru, specialising in practical HF/VHF receiving systems and RF components.

Found this useful? Support my writing and experiments: Buy me a coffee.

Subscribe here to receive updates on our latest product launches

  • YouTube
Payment methods
  • Bancontact
  • Bizum
  • iDEAL Wero
  • Klarna
  • Maestro
  • Mastercard
  • MB WAY
  • MobilePay
  • PayPal
  • Satispay
  • Visa
© 2026, RF Guru Powered by Shopify
  • Refund policy
  • Privacy policy
  • Terms of service
  • Contact information
  • News
  • Guru's Lab
  • Press
  • DXpeditions
  • Fairs & Exhibitions
  • Order Withdrawal
  • Choosing a selection results in a full page refresh.
  • Opens in a new window.
Purchase options
Select a purchase option to pre order this product
Countdown header
Countdown message


DAYS
:
HRS
:
MINS
:
SECS