✨
Public Notes
  • Personal running notes using Forem
  • Setting up a local test env without docker
  • Setting gitbook to use "main" branch by default
  • User Moderation
    • User Moderation is really just scoring
  • Flaky Specs
    • GithubReadmeTag
    • JS Testing
    • Setup not completed
    • userData is sometimes not loaded
    • Tracking down spec failures
    • Flaky Specs #1
  • Travis CI Segfaults
  • Bookmarks
  • User Setup in development
  • Testing in Docker locally
    • Reapproach quay containers
    • Webdriver and chrome headless
      • Using Selenium standalone
      • Chrome in docker
    • Setting up a local test env with docker
    • Traditional CI container setup
  • Peer Review
  • Rails runaway process in initialize!
    • Don't fix it
    • fix it?
  • Zeitwerk
  • Parallelize Cypress
  • Reading List
  • Sidekiq Memory Use
  • Buildkite configuration
  • Dumping heap
  • Tricking KnapsackPro
  • Debugging Ruby
  • Docker development revisited
  • gitpod development test
  • Embedding HTML in Markdown
Powered by GitBook
On this page

Was this helpful?

Peer Review

PreviousTraditional CI container setupNextRails runaway process in initialize!

Last updated 4 years ago

Was this helpful?

A lot of buzz on twitter and blogs recently about peer-review/code-review and why it's hard, what it's for, whether it's bringing into a high trust, high cohesion team patterns that were designed for low trust distributed projects and more overhead than it's worth.

interesting format that probably helps to control tone and make the feedback process smoother. It also make (blocking)/(non-blocking) standardized and pretty non-confrontational and that feels like a smooth set of conventions to adopt. Nick talked about it here

https://conventionalcomments.org/
https://www.iamdeveloper.com/pages/talks/#heading-words-matter:-conventional-comments