Question on the code machine archetype

Come hear from the very first Code Machine! Becoming A Legendary Meta Coder: The Story of the First E7 Code Machine

To have high coding velocity, the project matters a lot. You need to operate in an area where (1) there's a lot of code to be written and (2) there's not as much red tape/bureacracy from Product Managers or Designers. That means you likely need something that is engineering-driven -- IIRC, Michael wrote many internal tools used by other engineers.

The other thing that I've noticed with engineers with high coding output is that they are not shy about making minor improvements and bug fixes as they notice issues in their main flow.

• Found an unnecessary variable in this unit test? --> Let me make a PR for that
• Opportunity to refactor this method. --> Let me make a PR for that

Most people wouldn't be bothered to do these changes since it's a "distraction" from their primary work.

Code review is something that people will start to trust you over time. The more code you write, assuming you don't cause bugs or issues, the faster you'll get at code reviews.