codereviews   283

« earlier    

Automated code reviews & code analytics | Codacy
Automatically identify issues through static code review analysis. Get notified on security issues, code coverage, code duplication, and code complexity in every commit and pull request, directly from your current workflow. High-security standards. Identify OWASP Top 10 vulnerabilities and prevent critical issues from affecting your product. Code standardization. Make sure your code quality is standardized across all teams and projects by applying code patterns and getting notified on new issues. Tailored to your needs. Save time by knowing which set standards are being broken and getting insights on how to tackle them. Integrated in your workflow. Get notified where it matters to you. Speed up the process by receiving notifications as pull request comments or on Slack.
programming  analysis  automation  code  codereviews  staticanalysis  codequality  quality  security  software  softwareengineering 
9 weeks ago by dlkinney
How to do a code review
Google’s Engineering Practices documentation
engineering  google  programming  code  codereviews 
10 weeks ago by phubbard
10 tips for reviewing code you don't like - Red Hat Developer Blog
Avoid hyperbolic or bombastic assertions, avoid argument strategies, avoid elitist or demeaning language, and avoid constructs like “obviously” and “why don’t you just…”. Use clear, factual statements and supportive language, ask questions, and move things forward. Remember that coworkers and contributors are human people, and their time is worthy of the same respect as yours.
CodeReviews  Tutorial  2019  blog  DavidLloyd 
july 2019 by dlb

« earlier    

related tags

2018  2019  acm  advice  agile  analysis  arnemertz  article  automation  bestpractices  better  blog  branches  bwg-links  c++  career  checklist  clean  cleancode  code-reviews  code  codeconventions  codequality  codereview  codesmells  codingwithempathy  collaboration  communication  community  compassion  compassionate  compsci  css  culture  cybersecurity  davidlloyd  dev  development  devtools  engineering  essay  feedback  feedly  fridayfrontend  frontenddev  fun  gergelyorosz  git  github  go  golang  google  guidelines  guides  handbook  howto  important  improve  improvements  incidentresponse  instapaper  intro  language  lead  leadership  linting  management  mentor  metrics  michaelsorens  microsoft  mobiledevelopment  mobiletesting  mobprogramming  opensource  pairprogramming  papers  politeness  postmortem  practices  presentation  processes  programming  pullrequest  pullrequests  quality  refactoring  research  review  reviews  russia  security  software-development  software  softwaredevelopment  softwareengineering  softwarepractices  softwaretesting  solid  squash  srdev  stackoverflow  staticanalysis  styleguide  tasks  tdd  team  teams  tech  testing  tips  tools  top  toread  toxic  tumblr  tutorial  validation  video  walkthroughs  webdev  whitepaper 

Copy this bookmark: