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

On Writing Well as a Software Engineer

hackerone.com | blog | #documentation | #communication | #career | #productivity | #software-engineering | #soft-skills | #engineering-culture | #writing
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Charlie Kroon shares practical writing habits—starting small, reading good prose, and writing for the reader—that make software engineers more effective and impactful.
Published
Collected

Related coverage

blog · hackerone.com
On Listening
HackerOne engineer Charlie Kroon explains how empathetic listening makes you a better engineer, sharing a framework: check your intentions, be fully present, and ask questions like a journalist.
blog · hackerone.com
A Guide to Get the Most Out of Your One-on-ones
HackerOne's Charlie Kroon shares golden rules and agenda ideas for productive one-on-ones with managers, peers, and product managers, from career planning to feedback.
blog · hackerone.com
Respectfully Reviewing Your Coworker's Code Changes
Guidance for respectful code reviews: understand the change's context first, lead with positive feedback, give specific actionable suggestions, and critique the code rather than the coder.
blog · hackerone.com
Using Code Challenges for Interviews
PullRequest CTO Tyler Mann reviews coding challenge formats for interviews, from whiteboard exercises and automated online tests to take-home assignments, and what each shows about candidate skills.
blog · hackerone.com
Handling Code Reviews with Empathy
Explores handling code reviews with empathy, addressing how pull request conversations turn sour and how reviewers can give feedback that improves code without damaging working relationships.
blog · hackerone.com
Getting the Certification to Review Code at Google
A PullRequest reviewer recounts earning Google's JavaScript readability certification required to approve code, describing the exacting review process and how it made him a better engineer.
Back