DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • Top 7 Best Practices DevSecOps Team Must Implement in the CI/CD Process
  • Three Ways AI Is Reshaping DevSecOps
  • Why Software Development Leaders Should Invest in Continuous Learning and Growth Opportunities
  • The Rising Risks and Opportunities in API Security

Trending

  • Spring Authentication With MetaMask
  • Docker and Kubernetes Transforming Modern Deployment
  • Log Analysis Using grep
  • TDD With FastAPI Is Easy
  1. DZone
  2. Coding
  3. Tools
  4. Malicious Code Reviews: 11 Tips to Piss the Whole Team Off

Malicious Code Reviews: 11 Tips to Piss the Whole Team Off

Here are some wonderful suggestions for driving everyone crazy. That's the point of Agile, right?

Maria Khalusova user avatar by
Maria Khalusova
·
Sep. 11, 15 · Opinion
Like (16)
Save
Tweet
Share
15.63K Views

Join the DZone community and get the full member experience.

Join For Free

Disclaimer: Please do not take this post seriously.

Your team has decided to adopt code review practice, and your perfect code now will be judged by someone else. Well, how dare they think they can find any issues with your brilliant code? On top of that, you need to spend your valuable time reviewing someone else’s code? That does it! Fight back the tyranny by following these simple rules:
If your code is about to be reviewed

  1. Commit all the features and bug-fixes you’ve worked on this week in one go, and ask for a review. Let them see how much work you’ve done. 
  2. Invite the whole team to review your code. Everybody has to know how great your features are. 
  3. Be original. Do not use spell checker, do not use static code analysis. Do, however, use ReSharper or IntelliJ IDEA to reformat code to your style, ignoring the company’s standards.
  4. Introduce a tricky bug on purpose. See if they’re smart enough to find it. 
  5. If you are reviewing someone else’s code

  6. Take your time. Got a code review assigned to you? Take your time, it’s not important. No, really, have a cup of tea, answer all unanswered emails, tweet something, see what you friends have been up to on facebook, go home. Why should reading someone’s code be more important than what you want to do? Feel free to ignore notifications for a week or two: you are busy.
  7. Take your time doing review. They wanted you to find issues? Don’t close the review until you find at least a dozen, even if it takes months.
  8. See a bug? Perfect! First, question the author’s intelligence, then, when your superiority is well established, demand a fix.
  9. Found an elegant solution to a problem? Don’t tell anyone, especially the code author, that you’re impressed. Keep it cool, act like you’ve always knew how to do things best.
  10. Embrace your inner grammar nazi: Focus on the spelling, it’s the most important thing! How can we misspell things and call ourselves professionals?
  11. Count all the spaces. Point out every bad indentation.
  12. Never compromise. Even if another solution offered by your teammate is better than yours. Stand your ground. 

Good luck!

teams intellij

Published at DZone with permission of Maria Khalusova. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Top 7 Best Practices DevSecOps Team Must Implement in the CI/CD Process
  • Three Ways AI Is Reshaping DevSecOps
  • Why Software Development Leaders Should Invest in Continuous Learning and Growth Opportunities
  • The Rising Risks and Opportunities in API Security

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: