HackerOne Blog

Code Security

Return on Mitigation

Code Security

H1 Code

The Cost Savings of Fixing Security Flaws in Development

February 25, 2025

There’s no debate that catching and fixing security flaws in development saves time, money, and stress.

Read Now

All

CTEM

Engineering

Cloud Security

Code Security

Crowdsourced Security

Culture & Talent

Defense in Depth

From the CEO

HackerOne News

Offensive Security

Public Policy

Return on Mitigation

Security Compliance

Security Research

Exposure Management

Code Security

Setting Goals for Onboarding Outsourced Devs

September 23, 2018

Want to get the most from your outsourced developer? Focus on getting them completely onboarded...

Code Security

Why You Need To Focus on Improving Your API Docs

September 21, 2018

Whether they realize it or not, these days every company is a technology company. Companies...

Code Security

5 Steps to Create an Effective Code Review Culture

September 20, 2018

Anyone on a development team who contributes to a software project expects some sort of...

Code Security

How to Create a Programming Style Guide

September 20, 2018

A programming style guide is an opinionated guide of programming conventions, style, and best practices...

Code Security

Programming Style Guides, the Blueprint of Clean Code

September 14, 2018

Programming style debates are too often focused on unimportant formatting choices at the cost of...

Code Security

Read Me First: An Intro to Internal READMEs

September 5, 2018

The most successful open source projects have informative and entertaining READMEs. There are badges, screenshots...

Code Security

Marketing for Engineers

August 30, 2018

Marketing is "the exchange of goods and services aimed at satisfying the needs and wants...

Code Security

PR (Public Relations) for Engineers

August 24, 2018

PR (public relations) can be an effective way to drive a lot of awareness around...

Code Security

Seven Habits for a More Toxic Code Review Culture

August 17, 2018

Please don't practice any of the following "advice." From junior developer to CTO of a...