Code Review Pins and Buttons

Profanity is a language all programmers speak fluently. The amount of cursing and swearing can get excessive when doing a code review, especially if you are the BDFL of a project like Linux, so better warn your co-workers if you can't hold back. This design shows a yellow caution sign with the warning "I CURSE WHEN I REVIEW CODE". Suitable for work, code sprints and conferences and it makes for a not-so-subtle gift for your cursing coding peers.

Programmers' humor? You betcha!

Join Mark and Simon's quest to create cinema-based behavioural equilibrium via municipal swimming pool-style commandments. Sales of this design will almost undoubtedly benefit Kermode and Mayo financially in some way possibly.

Debugging code with rubber duckies? Sounds like something only a bored programmer could come up with! It's a conversation that goes nowhere, but at least you end up with fewer bugs and it also calls for a celebration of the weird and wonderful world of software development where your only friends are rubber ducks. This design is featuring three rubber ducks who want to review your code.

This is a cool and funny design to certify that the code is free of any possible injection threats following the best practices like OWASP or CWE.

A design about the the common weakness enumeration 20 also known as improper input validation. If user input is not properly escaped, sanitised and validated then the attackers can perform DoS, RCE or even tamper the information.

IT code.

A shield design of the input validation steps that developers should do in the methods or functions that manipulates untrusted data. This is one of the best practice of OWASP for secure coding.

Never forget to handle a potential exception thrower code to avoid any undesired web application status. Run the code within a try and process the error on the catch section.

A funny design to concern developers that the usage of eval() to process or parse untrusted data could let attackers to inject code to run.

This is a reminder for developers to replace any print used for debugging purposes with logger to write them in files.

This should be the input validation steps that the code must do to avoid processing harmful untrusted data.

Whether you’re a coder, programmer, or developer, wear it proudly during hackathons, code reviews, or casual meetups.

One of the recommendations of secure coding is to practice pair programming, because 4 eyes catches more than 2 and it is a good way to share context and knowledge between coworkers.

Fuzzing is an important testing to be done on running applications because it can catch flaws that static analysis can't like buffer overflows or memory corruption. This is a black background with white letters design version.

Insecure deserialisation could lead to remote code execution if no proper validation is done previously.

Developers are under great pressure with aggressive delivering dates but, one of the most important things that they shouldn't overlook, is to applying input validation in the functions or methods. This is a black background with white letters design version.

Another secure coding design about the sensitive information disclosure caused by pushing code with secrets to the git repository. One of the ways to avoid this is by introducing the file names of the project with secrets into the .gitignore file. This is a black background version with white letters.

A funny design of a samoyed reminding the importance of doing input validation before processing any user provided data.