PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Follow-up or Fail

hackerone.com | blog | #teamwork | #hackerone | #productivity | #prioritization | #engineering-culture | #project-management
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

HackerOne engineer Rafael de Carvalho discusses the pitfalls of over-committing at work and shares tips on under-committing, meeting follow-ups, and prioritization to keep projects from failing.
Published
Collected

Related coverage

blog · hackerone.com
Building Bridges: The Art of Effective Communication Across Teams
How do you run prime communication on a project that spans multiple teams? The 3 Ps: Purpose, People, Process.
blog · hackerone.com
On Writing Well as a Software Engineer
Charlie Kroon shares practical writing habits—starting small, reading good prose, and writing for the reader—that make software engineers more effective and impactful.
blog · hackerone.com
Product Management for Engineers
This HackerOne series post explains what product managers do, how they differ from project managers, and five traits of a good PM, from problem solving to leading by influence.
blog · hackerone.com
Measuring The Fix: How We Evaluate Frontier Models on Remediation Quality
HackerOne tested frontier models on security fix quality and found the judge mattered more than the model. See how CTEM remediation earns engineer trust.
blog · hackerone.com
Critical PHP Vulnerabilities: What Security Teams Need to Know
Learn about the critical PHP vulnerabilities, HackerOne’s response, and the rise in reports. Review patching guidance and coordinated disclosure practices.
blog · hackerone.com
Project Glasswing: What We Learned Running a Frontier Model on Our Own Codebase
HackerOne ran Anthropic's Mythos 5 model against its own production code; it surfaced a critical RCE spanning three safe-in-isolation commits, illustrating compositional risk that diff review misses.
Back