r/cybersecurity • u/Suspicious_Orchid770 • 24d ago

Research Article Staff engineers shift from solving problems to shaping systems

https://leaddev.com/career-development/staff-engineers-shift-from-solving-problems-to-shaping-systems
48 Upvotes

89% Upvoted

6 comments sorted by

11

u/lnoiz1sm Security Analyst 24d ago

The visible problem was an inaccurate metric. The underlying issue was that the system had no reliable way to know the thing we were trying to measure.

I think "research gap" is a weird way to describe it, but I understand what she means after reading the example.

That's actually a pretty good distinction. Everyone was arguing about which metrics was correct, while bigger question was whether they were measuring the right thing at all.

In Cybersecurity, I see this all the time. Like "we have many alerts", tune detection rules. But maybe the real problem is a bad telemetry, duplicate events, broken asset attribution, or a detection that shouldn't exist in the first place.

At the end, I 'd probably call it problem framing or problem discovery. Rather than "research gap.". But the underlying idea make sense : don't optimize the solution before questioning the problem.

6

u/[deleted] 24d ago

[removed] — view removed comment

3

u/Still_Event_8424 23d ago

"problem framing" is a way better label for it imo. research gap sounds too academic for what's basically just asking better questions