DEV Community

PPPing
PPPing

Posted on

Ping64|What I Learned When a Summer Intern Shadowed Me for a Week and Wrote Down Every Question

A couple of months ago our team got a summer intern, and since I was the only one without back-to-back meetings, she got assigned to shadow me for a week. I expected to spend five days narrating ticket queues and explaining where we keep the documentation. What actually happened was stranger and more useful.

By Wednesday she had filled a notebook with questions I couldn’t answer quickly, and none of them were deep technical ones. She wanted to know why we have three different tools that all send alerts, and why resetting a single account involves four systems. Her outsider eyes saw friction I had stopped noticing years ago. I found myself apologizing for things I had never chosen, which was a slightly uncomfortable feeling.

The things she wrote down

One page of her notebook was titled things that seem weird, and it was brutal in the gentlest possible way. Why does the password reset flow email a temporary password instead of using the self-service portal? Why do we check two dashboards to confirm one alert? Why is the asset list a spreadsheet that stopped being updated in March? Each question had an answer, and each answer was basically history rather than logic.

I laughed at a few of those, then realized I had asked the very same questions in my first year. Somewhere along the way I stopped asking and started working around things instead. That’s the part that got my attention. The workarounds had become so normal that I forgot they were workarounds. They had quietly turned into the actual process, documented nowhere and understood by everyone.

Why the weirdness becomes invisible

Nobody designs a messy process on purpose. Each odd step exists because someone once had an urgent problem, patched it quickly, and moved on with their week. A tool bought during one bad quarter, a script written by someone who has since left, a checklist copied from a previous job. Individually, each of them is defensible.

The trouble is that veterans absorb the friction and stop seeing it, while new people see it clearly but lack the authority to change anything. An intern asking why is not a criticism of anyone on the team. It’s usually the cheapest audit you’ll ever get, and it walks out the door in eight weeks if nobody captures it. Most teams lose that window and never know they had it.

Some teams try consolidated platforms like Ping64 to reduce the daily busywork of multi-tool security stacks. I mention that as an observation about where the industry has drifted, not a pitch. When routine work spreads across too many tools, every handoff becomes a place where confused questions pile up.

What we changed after the week

  • We turned her notebook into a real backlog. Half the entries were fixed in a day; the rest became honest tickets with named owners.
  • I added a standing item to our onboarding checklist: write down everything that seems odd during your first month, with no filtering.
  • We killed one redundant alerting path entirely, something nobody had dared to touch for two years. It turned out nothing had depended on it since the migration.
  • The self-service password portal finally got fixed, which had been sitting in a pending state so long that everyone forgot it existed.
  • She also got a small deliverable out of it: a one-page map of which tool does what, written from a newcomer’s view. We still keep it pinned in the team channel.

What surprised me most

The intern wasn’t smarter than the rest of us, and I want to be clear about that. She just had fresh eyes and no history, which is a resource most teams waste completely. If your onboarding process mostly teaches people the workarounds, you’re spending that resource badly.

I noticed my own habits shifting afterward, too. When I hit a clunky step now, I try to ask whether I’m working around a problem or actually fixing it. It’s a small mental shift, but it catches a surprising number of quiet issues before they harden into permanent fixtures that nobody questions anymore. If nothing else, it makes my own tickets more honest about the real cause.

Closing thoughts

I went into that week expecting to teach a student some basics of the job. I came out with a list of process debt I’d been carrying for years without noticing it. Not a bad return on one week of coffee runs and screen sharing. The most valuable part was that the list came with fresh explanations attached, not just complaints.

If you get an intern, a new hire, or even a colleague visiting from another team, treat their confused questions as free consulting. Write them down before the freshness wears off. Future you will be quietly grateful, and so will the next person who joins.

References
https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
https://attack.mitre.org/techniques/T1078/
https://www.cisa.gov/secure-our-world
https://www.enisa.europa.eu/topics/cybersecurity-education

Top comments (0)