How to Code Review
•
0 likes•444 views
The document contains links and references to various coding topics including OpenPlay 1.0, rating systems, ElasticSearch, Redis pubsub, admin statistics migration, Python, GitHub pull requests and issues, code review best practices, and references for further reading. It provides an overview of code, tools, and processes for development and code review.
Report
Share
Report
Share
Download to read offline
Recommended
Python, Keras, Hello world, Installation, Binary Classification
This document discusses getting started with Keras for binary classification. It covers installing Keras with different backends like TensorFlow, Theano, or CNTK. It also covers configuring Keras by editing the keras.json file to select a backend and set the image data format. The document then demonstrates building a basic binary classification model on the Breast Cancer dataset using Keras sequential API to add layers, compile, train, and predict with the model.
PostgreSQL Replication with Bucardo
Bucardo is an open source, asynchronous PostgreSQL replication system that allows for multi-master and multi-slave configurations. It was developed by Jon Jesen and Greg Sabino and is free to use under a BSD license. Bucardo supports master-master replication, conflict resolution, and custom code. It uses push delta, full copy, or swap replication methods and manages database objects in "herds" that are synced between databases.
My Computer
This system has an AMD Phenom II x4 810 processor, 8GB of RAM, and uses a ATI Radeon 3100 Graphics card with 1655MB of total graphics memory. It has a 32-bit operating system installed on an HP Compaq dc5850 Small Form Factor computer with 4 processor cores and 932GB of total hard drive space across several partitions. Network connectivity includes Broadcom Ethernet, Atheros wireless, and Bluetooth.
History
7-Zip is an open source file archiver that supports multiple compression formats. The document outlines the history of 7-Zip releases from 2009 to 2011, noting fixes and improvements made in each release such as support for additional file formats, encryption methods, and localization updates. Major additions include support for LZMA2 compression in 2009, PPMd compression in 2011, and speed optimizations for various file operations.
Understanding Eclipse Plug-in Test Suites @ The Eclipse Testing Day 2011
Testing plug-in based systems entails testing a complex net of multiple plug-ins
which not only interact with, but also enhance the functionality of each other by extension mechanisms.
In the Eclipse Testing Study, testing practices of successful Eclipse projects have been studied. Among others, Eclipsers stress integration testing as an important testing activity for plug-in systems, and explain that understanding complex plugin test suites can become a challenging task.
To remedy the problem of understanding plug-in test suites, we developed the
Eclipse Plug-in Test Suite Exploration (ETSE) tool. ETSE combines static and
dynamic information on plug-in dependencies, extension initialization, and
extension or service usage during a test run. This information is used to create five
architectural views of the system under test and its test suite, which developers
can use to understand how the integration of multiple plug-ins is tested.
In this presentation, we will talk about plug-in test suites and present the architectural views, which help answering questions like: “which plug-ins are tested by this test suite?”, “where are test harness and test utilities located?”, “which extensions influence the state of the test system?”, and many more.
We will end this session with a short demonstration of ETSE by visualizing the test suite of Mylyn.
ICSE 2012: Test Confessions - A study of testing practices for plug-in systems
1. The document summarizes a study on testing practices for plug-in systems. It examines how developers test plug-ins and the challenges of testing cross-plugin integration and different versions.
2. The study found that unit testing is widely used for plug-ins but other types of testing like integration and system testing are less common. Testing cross-plugin interactions and different versions is also limited.
3. Barriers to more rigorous plug-in testing include unclear responsibilities, lack of expertise, and long test times. Developers compensate by relying on community testing and involvement to identify issues.
Strategies to Avoid Test Fixture Smells durin Software Evolution
An important challenge in creating automated tests
is how to design test fixtures, i.e., the setup code that initializes the
system under test before actual automated testing can start. Test
designers have to choose between different approaches for the
setup, trading off maintenance overhead with slow test execution.
Over time, test code quality can erode and test smells can develop,
such as the occurrence of overly general fixtures, obscure inline
code and dead fields. In this paper, we investigate how
fixture-related test smells evolve over time by analyzing several
thousand revisions of five open source systems. Our findings
indicate that setup management strategies strongly influence the
types of test fixture smells that emerge in code, and that several
types of fixture smells often emerge at the same time. Based on
this information, we recommend important guidelines for setup
strategies, and suggest how tool support can be improved to help
in both avoiding the emergence of such smells as well as how to
refactor code when test smells do appear.
JDD Effective Code Review In Agile Teams
Presentation about effective code review for agile developers.
Slides were used during sessions at Agile2009 in Chicago and JDD09 in Krakow.
Recommended
Python, Keras, Hello world, Installation, Binary Classification
This document discusses getting started with Keras for binary classification. It covers installing Keras with different backends like TensorFlow, Theano, or CNTK. It also covers configuring Keras by editing the keras.json file to select a backend and set the image data format. The document then demonstrates building a basic binary classification model on the Breast Cancer dataset using Keras sequential API to add layers, compile, train, and predict with the model.
PostgreSQL Replication with Bucardo
Bucardo is an open source, asynchronous PostgreSQL replication system that allows for multi-master and multi-slave configurations. It was developed by Jon Jesen and Greg Sabino and is free to use under a BSD license. Bucardo supports master-master replication, conflict resolution, and custom code. It uses push delta, full copy, or swap replication methods and manages database objects in "herds" that are synced between databases.
My Computer
This system has an AMD Phenom II x4 810 processor, 8GB of RAM, and uses a ATI Radeon 3100 Graphics card with 1655MB of total graphics memory. It has a 32-bit operating system installed on an HP Compaq dc5850 Small Form Factor computer with 4 processor cores and 932GB of total hard drive space across several partitions. Network connectivity includes Broadcom Ethernet, Atheros wireless, and Bluetooth.
History
7-Zip is an open source file archiver that supports multiple compression formats. The document outlines the history of 7-Zip releases from 2009 to 2011, noting fixes and improvements made in each release such as support for additional file formats, encryption methods, and localization updates. Major additions include support for LZMA2 compression in 2009, PPMd compression in 2011, and speed optimizations for various file operations.
Understanding Eclipse Plug-in Test Suites @ The Eclipse Testing Day 2011
Testing plug-in based systems entails testing a complex net of multiple plug-ins
which not only interact with, but also enhance the functionality of each other by extension mechanisms.
In the Eclipse Testing Study, testing practices of successful Eclipse projects have been studied. Among others, Eclipsers stress integration testing as an important testing activity for plug-in systems, and explain that understanding complex plugin test suites can become a challenging task.
To remedy the problem of understanding plug-in test suites, we developed the
Eclipse Plug-in Test Suite Exploration (ETSE) tool. ETSE combines static and
dynamic information on plug-in dependencies, extension initialization, and
extension or service usage during a test run. This information is used to create five
architectural views of the system under test and its test suite, which developers
can use to understand how the integration of multiple plug-ins is tested.
In this presentation, we will talk about plug-in test suites and present the architectural views, which help answering questions like: “which plug-ins are tested by this test suite?”, “where are test harness and test utilities located?”, “which extensions influence the state of the test system?”, and many more.
We will end this session with a short demonstration of ETSE by visualizing the test suite of Mylyn.
ICSE 2012: Test Confessions - A study of testing practices for plug-in systems
1. The document summarizes a study on testing practices for plug-in systems. It examines how developers test plug-ins and the challenges of testing cross-plugin integration and different versions.
2. The study found that unit testing is widely used for plug-ins but other types of testing like integration and system testing are less common. Testing cross-plugin interactions and different versions is also limited.
3. Barriers to more rigorous plug-in testing include unclear responsibilities, lack of expertise, and long test times. Developers compensate by relying on community testing and involvement to identify issues.
Strategies to Avoid Test Fixture Smells durin Software Evolution
An important challenge in creating automated tests
is how to design test fixtures, i.e., the setup code that initializes the
system under test before actual automated testing can start. Test
designers have to choose between different approaches for the
setup, trading off maintenance overhead with slow test execution.
Over time, test code quality can erode and test smells can develop,
such as the occurrence of overly general fixtures, obscure inline
code and dead fields. In this paper, we investigate how
fixture-related test smells evolve over time by analyzing several
thousand revisions of five open source systems. Our findings
indicate that setup management strategies strongly influence the
types of test fixture smells that emerge in code, and that several
types of fixture smells often emerge at the same time. Based on
this information, we recommend important guidelines for setup
strategies, and suggest how tool support can be improved to help
in both avoiding the emergence of such smells as well as how to
refactor code when test smells do appear.
JDD Effective Code Review In Agile Teams
Presentation about effective code review for agile developers.
Slides were used during sessions at Agile2009 in Chicago and JDD09 in Krakow.
EclipseCon: Test Confessions - What Eclipsers think and do about testing
The document summarizes a study on testing practices within the Eclipse community. Interviews were conducted with 25 experienced developers and testers from various Eclipse projects. The goal was to understand testing culture and practices. Grounded theory was used to analyze interview transcripts, testing articles, and event participation. A test adoption model emerged to explain used and unused test practices based on technical prerequisites, integration into daily practice, application knowledge, and ownership factors. There is a focus on unit testing with minimal automated integration and system testing. User involvement is seen as important but challenging due to openness, communication, and support needs. Actionable items and an upcoming discussion are proposed to help build a stronger testing community.
Code review process checklist by VINTAGE
The document provides a code review checklist with rules for code organization, style, and installation of components. Key points include:
- Do not insert CSS/JS code anywhere other than predefined files and avoid string concatenation in links.
- If themes are used, views must be stored in theme folders and built-in scopes should replace Criteria.
- For large data processing, use data providers and batching.
- Use Composer for library installation and updates in production.
- PHPStorm code style can be set from PSR standards and code should be regularly inspected.
Code review in practice
This document provides an overview of code review practices. It discusses why code review is important to improve code quality, readability and maintainability. It describes different types of code review including over-the-shoulder, pair programming, automated and various time-based methods. Tools for facilitating code review are also presented, such as Review Board, Gerrit, Fisheye/Crucible and SmartBear CodeCollaborator. The goal of the document is to educate about best practices for conducting code reviews.
Code review drinking game
The document proposes a "Code Review Drinking Game" where certain common code review occurrences trigger sips of a drink, such as using "Random" instead of "secureRandom", TODO comments, or merge conflicts in committed code. It includes drinking game rules for both Java and JavaScript code reviews. The goal is to have an entertaining way to conduct code reviews by turning typical issues into opportunities to drink.
Code Review
The document discusses code review practices at the presenter's team. It covers basic concepts like broken window theory and technical debt. It then details the team's Git and Jira processes, coding standards using PHP CodeSniffer, and code review steps involving checking code, unit tests, and identifying inefficiencies and improvements. The concepts discussed will become obsolete when applications can self-improve by writing new code to meet business needs without human involvement.
Review your code like a Googler
Presentation about Code Review and Gerrit given at Confitura 2013 conference. Shows how to start with Gerrit, how configure Ecipse Mylyn Gerrit Connector plugin and how perform code reviews directly in the IDE
Code Review: Veni, ViDI, Vici (saner15)
!!! For the demo purposes of ViDI there was a set of videos in the presentation. You can see the full demo video here: http://youtu.be/EtdkcNBJAec
Modern software development sees code review as a crucial part of the process, because not only does it facilitate the sharing of knowledge about the system at hand, but it may also lead to the early detection of defects, ultimately improving the quality of the produced software. Although supported by numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of shortcomings in the state of the art. We present a critical analysis of the state of the art of code review tools and techniques, extracting a set of desired features that code review tools should possess. We then present our vision and initial implementation of a novel code review approach named Visual Design Inspection (ViDI), illustrated through a set of usage scenarios. ViDI is based on a combination of visualization techniques, design heuristics, and static code analysis techniques.
Code Review for Teams Too Busy to Review Code - Atlassian Summit 2010
This document provides a summary of code review for busy teams. It begins with an introduction to the author and topics to be covered. It then discusses making code review activity and code itself more visible and accessible through tools. It emphasizes the importance of encouraging discussion around code and providing feedback in a constructive manner. The document concludes with some tips for conducting more effective code reviews, such as focusing on problems rather than solutions and embracing feedback to improve.
Code Review: An apple a day
This document summarizes code review tools and processes. It discusses Flex Formatter and Google Code Reviews tools for facilitating code reviews. Flex Formatter ensures code style consistency while Google Code Reviews allows uploading code diffs for review and commenting. The Rietveld script uploads code diffs to Google Code Reviews to initiate reviews. Benefits of code reviews include distributing knowledge, catching bugs, encouraging tidiness, and saving time.
On to code review lessons learned at microsoft
Keynote for QUATIC 2016 - the 10th International Conference on the Quality of Information and Communication Technology
The Impact of Code Review Coverage and Participation on Software Quality
Software code review, i.e., the practice of having third-party team members critique changes to a software system, is a well-established best practice in both open source and proprietary software domains. Prior work has shown that the formal code inspections of the past tend to improve the quality of software delivered by students and small teams. However, the formal code inspection process mandates strict review criteria (e.g., in-person meetings and reviewer checklists) to ensure a base level of review quality, while the modern, lightweight code reviewing process does not. Although recent work explores the modern code review process qualitatively, little research quantitatively explores the relationship between properties of the modern code review process and software quality. Hence, in this paper, we study the relationship between software quality and: (1) code review coverage, i.e., the proportion of changes that have been code reviewed, and (2) code review participation, i.e., the degree of reviewer involvement in the code review process. Through a case study of the Qt, VTK, and ITK projects, we find that both code review coverage and participation share a significant link with software quality. Low code review coverage and participation are estimated to produce components with up to two and five additional post-release defects respectively. Our results empirically confirm the intuition that poorly reviewed code has a negative impact on software quality in large systems using modern reviewing tools.
Can we induce change with what we measure?
The document discusses data-driven approaches to optimizing software testing processes at Microsoft. It describes how historical test and code data can be analyzed to determine which tests are most valuable and cost-effective to run, in order to reduce total test execution time without negatively impacting code quality. Simulation results on Windows 8.1 data show the potential for significant test reduction (up to 60%) while maintaining bug finding ability. This could improve development processes by lowering machine costs and increasing developer satisfaction.
Simplified Security Code Review Process
This document summarizes a presentation about simplifying secure code reviews. It discusses defining an effective security code review process, including reconnaissance, threat modeling, automation, manual review, confirmation, and reporting. It also discusses using the OWASP Top 10 list to focus code reviews, and defining trust boundaries to identify areas of code to review for specific vulnerabilities. The goal is to introduce a simplified process that can help development teams integrate security code reviews into their workflow.
Code Review: How and When
You want to improve your software skills. That’s a given. You may be a mentor or a manager who needs to improve the knowledge sharing among your software developers across different projects. Code Reviews can do just that while improving code quality in your projects. Code Review not only builds developer team spirit but also offers new ways to improve a software solution. You’ll walk away from this session with in-depth understanding of Code Review to strengthen your team.
Code Review for iOS
Hi I’m Cris, iOS Developer in KLabCyscorpions. In this post, I want to share with you my presentation on Code Review guidelines for iOS.
But, what is Code Review?
According to Wikipedia:
“Code Review is systematic examination (often known as peer review) of computer source code. It is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers’ skills. Reviews are done in various forms such as pair programming, informal walkthroughs, and formal inspections.”
Want to review code? Then First things first! For you to review code effectively, you need the basic know-how of reviewing code as both the developer and the reviewer. These slides will give some guidelines on how to think in both these roles when reviewing code.
Improving Code Quality Through Effective Review Process
The document discusses improving code quality through effective code review processes. It outlines common coding mistakes like redundant code, long or deeply nested functions, large modules, poor comments, and hardcoding. It recommends following best practices like coding guidelines, centralized server communication, and the single responsibility principle. The document also discusses measuring and reducing code complexity, avoiding memory leaks, optimizing images, static code analysis, and profiling to improve code quality.
Peer Code Review An Agile Process
Peer code review is one of the most effective ways to find defects – but is it agile? Because agile teams loathe heavy process, code review practices can easily fail. However, lightweight peer code review aligns well with the central tenets of agile—keeping feedback close to the point of creation, increasing team velocity by finding defects faster, and improving collective code ownership through frequent collaboration. Gregg Sporar shares recent research on code review practices and describes an agile code review approach—how much time to spend, which code to review, how much code to review at a time, how to set goals, the value of annotation, and more. After comparing four styles of code review—pair programming, over-the-shoulder, email, and tool-assisted—Gregg gives specific advice for creating review checklists and dealing with the social effects of code review in an agile environment.
Code Review
Presentation from Agile Base Camp 2 conference (Kiev, May 2010) and AgileDays'11 (Moscow, March 2011) about one of the most useful engineering practices from XP world.
Voxxed days 2015-hakansaglam-codereview
At Peak Games, one of the most important development practices is Code Review. We believe that, with Code Review we have
* increased the code quality
* decreased the bugs
* encouraged collaboration
* kept the code maintainable
* created common language in the team
In this presentation I try to give some samples and practices about
* How we are doing Code Review.
* What are the findings to be able to make it more effective.
* What are we doing to make “Code Review” as a part of our development culture.
LogStash - Yes, logging can be awesome
Logging. Everyone does it. Many don't know why they do it. It is often considered a boring chore. A chore that is done by habit rather than for a purpose. But it doesn't have to be! Learn how to build a powerful, scalable open source logging environment with LogStash.
Network Security Testing Tools
The document discusses various security testing tools categorized by their functions - networking, operating systems, packet crafting, scanning, fuzzing, debugging, benchmarking and web. It provides descriptions and usage examples of tools like nmap, ngrep, hping, nikto, ethtool, ping, netstat, ab, netcat, metasploit, tcpdump and iperf. The document also covers related topics like SNMP, NTP, DoS attacks and references for further reading.
netwatch 2.0
This document discusses various tools and techniques for aggregating content from blogs and social networks including RSS, twitter, mixi, and others. It provides tips for using RSS readers like Bloglines, automation tools like AutoPagerize and LDRize, and APIs for interacting with services like twitter and mixi. Specific scripts and applications are also mentioned for following users, posting updates, and filtering content.
More Related Content
Viewers also liked
EclipseCon: Test Confessions - What Eclipsers think and do about testing
The document summarizes a study on testing practices within the Eclipse community. Interviews were conducted with 25 experienced developers and testers from various Eclipse projects. The goal was to understand testing culture and practices. Grounded theory was used to analyze interview transcripts, testing articles, and event participation. A test adoption model emerged to explain used and unused test practices based on technical prerequisites, integration into daily practice, application knowledge, and ownership factors. There is a focus on unit testing with minimal automated integration and system testing. User involvement is seen as important but challenging due to openness, communication, and support needs. Actionable items and an upcoming discussion are proposed to help build a stronger testing community.
Code review process checklist by VINTAGE
The document provides a code review checklist with rules for code organization, style, and installation of components. Key points include:
- Do not insert CSS/JS code anywhere other than predefined files and avoid string concatenation in links.
- If themes are used, views must be stored in theme folders and built-in scopes should replace Criteria.
- For large data processing, use data providers and batching.
- Use Composer for library installation and updates in production.
- PHPStorm code style can be set from PSR standards and code should be regularly inspected.
Code review in practice
This document provides an overview of code review practices. It discusses why code review is important to improve code quality, readability and maintainability. It describes different types of code review including over-the-shoulder, pair programming, automated and various time-based methods. Tools for facilitating code review are also presented, such as Review Board, Gerrit, Fisheye/Crucible and SmartBear CodeCollaborator. The goal of the document is to educate about best practices for conducting code reviews.
Code review drinking game
The document proposes a "Code Review Drinking Game" where certain common code review occurrences trigger sips of a drink, such as using "Random" instead of "secureRandom", TODO comments, or merge conflicts in committed code. It includes drinking game rules for both Java and JavaScript code reviews. The goal is to have an entertaining way to conduct code reviews by turning typical issues into opportunities to drink.
Code Review
The document discusses code review practices at the presenter's team. It covers basic concepts like broken window theory and technical debt. It then details the team's Git and Jira processes, coding standards using PHP CodeSniffer, and code review steps involving checking code, unit tests, and identifying inefficiencies and improvements. The concepts discussed will become obsolete when applications can self-improve by writing new code to meet business needs without human involvement.
Review your code like a Googler
Presentation about Code Review and Gerrit given at Confitura 2013 conference. Shows how to start with Gerrit, how configure Ecipse Mylyn Gerrit Connector plugin and how perform code reviews directly in the IDE
Code Review: Veni, ViDI, Vici (saner15)
!!! For the demo purposes of ViDI there was a set of videos in the presentation. You can see the full demo video here: http://youtu.be/EtdkcNBJAec
Modern software development sees code review as a crucial part of the process, because not only does it facilitate the sharing of knowledge about the system at hand, but it may also lead to the early detection of defects, ultimately improving the quality of the produced software. Although supported by numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of shortcomings in the state of the art. We present a critical analysis of the state of the art of code review tools and techniques, extracting a set of desired features that code review tools should possess. We then present our vision and initial implementation of a novel code review approach named Visual Design Inspection (ViDI), illustrated through a set of usage scenarios. ViDI is based on a combination of visualization techniques, design heuristics, and static code analysis techniques.
Code Review for Teams Too Busy to Review Code - Atlassian Summit 2010
This document provides a summary of code review for busy teams. It begins with an introduction to the author and topics to be covered. It then discusses making code review activity and code itself more visible and accessible through tools. It emphasizes the importance of encouraging discussion around code and providing feedback in a constructive manner. The document concludes with some tips for conducting more effective code reviews, such as focusing on problems rather than solutions and embracing feedback to improve.
Code Review: An apple a day
This document summarizes code review tools and processes. It discusses Flex Formatter and Google Code Reviews tools for facilitating code reviews. Flex Formatter ensures code style consistency while Google Code Reviews allows uploading code diffs for review and commenting. The Rietveld script uploads code diffs to Google Code Reviews to initiate reviews. Benefits of code reviews include distributing knowledge, catching bugs, encouraging tidiness, and saving time.
On to code review lessons learned at microsoft
Keynote for QUATIC 2016 - the 10th International Conference on the Quality of Information and Communication Technology
The Impact of Code Review Coverage and Participation on Software Quality
Software code review, i.e., the practice of having third-party team members critique changes to a software system, is a well-established best practice in both open source and proprietary software domains. Prior work has shown that the formal code inspections of the past tend to improve the quality of software delivered by students and small teams. However, the formal code inspection process mandates strict review criteria (e.g., in-person meetings and reviewer checklists) to ensure a base level of review quality, while the modern, lightweight code reviewing process does not. Although recent work explores the modern code review process qualitatively, little research quantitatively explores the relationship between properties of the modern code review process and software quality. Hence, in this paper, we study the relationship between software quality and: (1) code review coverage, i.e., the proportion of changes that have been code reviewed, and (2) code review participation, i.e., the degree of reviewer involvement in the code review process. Through a case study of the Qt, VTK, and ITK projects, we find that both code review coverage and participation share a significant link with software quality. Low code review coverage and participation are estimated to produce components with up to two and five additional post-release defects respectively. Our results empirically confirm the intuition that poorly reviewed code has a negative impact on software quality in large systems using modern reviewing tools.
Can we induce change with what we measure?
The document discusses data-driven approaches to optimizing software testing processes at Microsoft. It describes how historical test and code data can be analyzed to determine which tests are most valuable and cost-effective to run, in order to reduce total test execution time without negatively impacting code quality. Simulation results on Windows 8.1 data show the potential for significant test reduction (up to 60%) while maintaining bug finding ability. This could improve development processes by lowering machine costs and increasing developer satisfaction.
Simplified Security Code Review Process
This document summarizes a presentation about simplifying secure code reviews. It discusses defining an effective security code review process, including reconnaissance, threat modeling, automation, manual review, confirmation, and reporting. It also discusses using the OWASP Top 10 list to focus code reviews, and defining trust boundaries to identify areas of code to review for specific vulnerabilities. The goal is to introduce a simplified process that can help development teams integrate security code reviews into their workflow.
Code Review: How and When
You want to improve your software skills. That’s a given. You may be a mentor or a manager who needs to improve the knowledge sharing among your software developers across different projects. Code Reviews can do just that while improving code quality in your projects. Code Review not only builds developer team spirit but also offers new ways to improve a software solution. You’ll walk away from this session with in-depth understanding of Code Review to strengthen your team.
Code Review for iOS
Hi I’m Cris, iOS Developer in KLabCyscorpions. In this post, I want to share with you my presentation on Code Review guidelines for iOS.
But, what is Code Review?
According to Wikipedia:
“Code Review is systematic examination (often known as peer review) of computer source code. It is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers’ skills. Reviews are done in various forms such as pair programming, informal walkthroughs, and formal inspections.”
Want to review code? Then First things first! For you to review code effectively, you need the basic know-how of reviewing code as both the developer and the reviewer. These slides will give some guidelines on how to think in both these roles when reviewing code.
Improving Code Quality Through Effective Review Process
The document discusses improving code quality through effective code review processes. It outlines common coding mistakes like redundant code, long or deeply nested functions, large modules, poor comments, and hardcoding. It recommends following best practices like coding guidelines, centralized server communication, and the single responsibility principle. The document also discusses measuring and reducing code complexity, avoiding memory leaks, optimizing images, static code analysis, and profiling to improve code quality.
Peer Code Review An Agile Process
Peer code review is one of the most effective ways to find defects – but is it agile? Because agile teams loathe heavy process, code review practices can easily fail. However, lightweight peer code review aligns well with the central tenets of agile—keeping feedback close to the point of creation, increasing team velocity by finding defects faster, and improving collective code ownership through frequent collaboration. Gregg Sporar shares recent research on code review practices and describes an agile code review approach—how much time to spend, which code to review, how much code to review at a time, how to set goals, the value of annotation, and more. After comparing four styles of code review—pair programming, over-the-shoulder, email, and tool-assisted—Gregg gives specific advice for creating review checklists and dealing with the social effects of code review in an agile environment.
Code Review
Presentation from Agile Base Camp 2 conference (Kiev, May 2010) and AgileDays'11 (Moscow, March 2011) about one of the most useful engineering practices from XP world.
Voxxed days 2015-hakansaglam-codereview
At Peak Games, one of the most important development practices is Code Review. We believe that, with Code Review we have
* increased the code quality
* decreased the bugs
* encouraged collaboration
* kept the code maintainable
* created common language in the team
In this presentation I try to give some samples and practices about
* How we are doing Code Review.
* What are the findings to be able to make it more effective.
* What are we doing to make “Code Review” as a part of our development culture.
Viewers also liked (19)
EclipseCon: Test Confessions - What Eclipsers think and do about testing
EclipseCon: Test Confessions - What Eclipsers think and do about testing
Code Review for Teams Too Busy to Review Code - Atlassian Summit 2010
Code Review for Teams Too Busy to Review Code - Atlassian Summit 2010
The Impact of Code Review Coverage and Participation on Software Quality
The Impact of Code Review Coverage and Participation on Software Quality
Improving Code Quality Through Effective Review Process
Improving Code Quality Through Effective Review Process
Similar to How to Code Review
LogStash - Yes, logging can be awesome
Logging. Everyone does it. Many don't know why they do it. It is often considered a boring chore. A chore that is done by habit rather than for a purpose. But it doesn't have to be! Learn how to build a powerful, scalable open source logging environment with LogStash.
Network Security Testing Tools
The document discusses various security testing tools categorized by their functions - networking, operating systems, packet crafting, scanning, fuzzing, debugging, benchmarking and web. It provides descriptions and usage examples of tools like nmap, ngrep, hping, nikto, ethtool, ping, netstat, ab, netcat, metasploit, tcpdump and iperf. The document also covers related topics like SNMP, NTP, DoS attacks and references for further reading.
netwatch 2.0
This document discusses various tools and techniques for aggregating content from blogs and social networks including RSS, twitter, mixi, and others. It provides tips for using RSS readers like Bloglines, automation tools like AutoPagerize and LDRize, and APIs for interacting with services like twitter and mixi. Specific scripts and applications are also mentioned for following users, posting updates, and filtering content.
The Zeitgeist Movement
Plagger is a pluggable RSS/Atom aggregation platform that allows users to create custom applications by combining different plugin modules. It supports aggregating feeds from various sources and formats, processing and filtering entries, and publishing or notifying updates in different ways. While powerful, Plagger currently lacks documentation and has some room for improvement. The developer is looking for contributions to help spread awareness and enhance Plagger.
India Pr Wire May 11, 2009 Sensex Down 193 Points On Profit Booking
“Markets are certainly looking at election results with some apprehension, but what is also true is that they are in for a correction. Elections might act as the trigger for such a correction,” said Jagannadham Thunuguntla, equity head at SMC Capitals.
Linux 系統管理與安全：進階系統管理系統防駭與資訊安全
- The document discusses various Linux system log files such as /var/log/messages, /var/log/secure, and /var/log/cron and provides examples of log entries.
- It also covers log rotation tools like logrotate and logwatch that are used to manage log files.
- Networking topics like IP addressing, subnet masking, routing, ARP, and tcpdump for packet sniffing are explained along with examples.
Ruby and Rails Packaging to Production
This document discusses packaging Ruby and Rails applications for production. It covers using system packages versus gems, configuration management tools like Chef and Puppet, creating Debian packages, packaging gems, build servers, pain points like outdated Rubygems packages, and ideas for deeper Bundler integration and packaging gems by default. Overall it presents strategies for deploying Ruby applications as system packages for production servers.
Raspberry Pi 3 + UART/Bluetooth issues
A talk I gave at Hackware v1.6 about issues relating to the UART and Bluetooth issues associated with the new Raspberry Pi 3.
The recorded video of this talk can be found here. https://engineers.sg/video/raspberry-pi-3-uart-bluetooth-issues--609
You can also consult my Github Gist on configuring UART and Bluetooth on Arch Linux. https://gist.github.com/yeokm1/d6c3ca927919c61257cd
Building an Automated Behavioral Malware Analysis Environment using Free and ...
The document describes building an automated malware behavioral analysis environment using free and open-source tools. It details setting up analysis machines running Debian, installing analysis tools including Volatility, RegRipper, and AIDE. Samples are submitted to the machines via SSH and analyzed for network traffic using tools like tcpdump, DNS queries with fauxDNS, and open ports with connections. The results including OS identification, registry changes, and network indicators are summarized for analysts.
Log files: The Overlooked Source of SEO Opportunities
The document discusses log files and how they can provide insights for search engine optimization. It provides examples of log file entries and explains what each part of the entry means. It also discusses how log files can be used to analyze search engine crawler behavior, popular pages, error codes, and desktop vs mobile traffic. Tips are provided like segmenting log file data and using it to debug analytics.
Debugging Ruby Systems
Aman Gupta's presentation about debugging ruby systems. To view the full recording of his talk, visit: http://www.engineyard.com/video/16710570
Plagger the duct tape of internet
Plagger is a pluggable RSS/Atom aggregator that allows users to combine ("pipe") various plugins to customize how feeds are aggregated, filtered, and published/notified. It aims to be the "UNIX pipe of the internet" by providing a simple yet powerful framework to connect different data sources and processing modules in a customizable workflow. The document provides many examples of how Plagger can be used to aggregate feeds from sources like Bloglines or OPML files and publish them to email via Gmail by chaining together relevant subscription, filter, and publish plugins.
IAA Life in Lockdown series: Securing Internet Routing
APNIC Training Delivery Manager Tashi Phuntsho, presents on practical ways to implement RPKI at the IAA Life in Lockdown online event, 'how to stop heists, hijacks and hostages', held on 21 July 2020.
Creating "Secure" PHP applications, Part 2, Server Hardening
The document provides guidance on server hardening techniques. It discusses using netstat to view listening services on a server and using update-rc.d or chkconfig to disable unnecessary services from starting at boot. It also recommends enabling access control lists (ACLs) in file system mounts, using SELinux or AppArmor to enforce mandatory access controls, and setting reasonable PHP memory limits to prevent potential denial of service attacks. The document stresses the importance of only allowing approved applications to execute and knowing the resource limits of the server to avoid potential outages.
Miyagawa
Plagger is a pluggable RSS/Atom aggregation platform that allows users to create custom applications by combining different plugin modules. It provides plugins for subscription, aggregation, filtering, publishing, notification, and search functions. The document gives examples of how Plagger can be used to build applications like a Bloglines to Gmail importer, an RSS bot for IRC, and a planet generator. However, the author notes that Plagger currently lacks documentation and has many dependencies, technical issues, and feature requests logged on its website.
Miyagawa
Plagger is a pluggable RSS/Atom aggregation platform that allows users to create custom applications by combining different plugin modules. It supports aggregating, normalizing, filtering, and publishing feeds. The speaker provides examples of applications that have been built with Plagger, including aggregating blog feeds to Gmail, an RSS bot for IRC notifications, and generating a planet page. While Plagger has potential, it currently lacks documentation and has a large number of dependencies, but contributions are welcome to help improve and spread awareness of the project.
Miyagawa
Plagger is a pluggable RSS/Atom aggregation platform that allows users to create custom applications by combining different plugin modules. It supports aggregating, normalizing, filtering, and publishing feeds. The speaker provides examples of applications that have been built with Plagger, including aggregating blog feeds to Gmail, an RSS bot for IRC notifications, and generating a planet page. While Plagger has potential, it currently lacks documentation and has a large number of dependencies, but contributions are welcome to help improve and spread awareness of the project.
Miyagawa
Plagger is a pluggable RSS/Atom aggregation platform that allows users to create custom applications by combining different plugin modules. It supports aggregating, normalizing, filtering, and publishing feeds. The speaker provides examples of applications that have been built with Plagger, including aggregating blog feeds to Gmail, an IRC bot that notifies about new RSS items, and generating a planet page. While Plagger has potential, it currently lacks documentation and has a large number of dependencies, but contributions are welcome to help improve and spread awareness of the project.
Linux 系統管理與安全：基本 Linux 系統知識
The document provides information on systemd service management commands. It shows examples of using systemctl to start, stop, restart, and check the status of the httpd service. It also displays the output of systemctl status httpd which shows details about the loaded unit, active state, process IDs, and log entries for the Apache HTTP Server service.
Similar to How to Code Review (19)
India Pr Wire May 11, 2009 Sensex Down 193 Points On Profit Booking
India Pr Wire May 11, 2009 Sensex Down 193 Points On Profit Booking
Building an Automated Behavioral Malware Analysis Environment using Free and ...
Building an Automated Behavioral Malware Analysis Environment using Free and ...
Log files: The Overlooked Source of SEO Opportunities
Log files: The Overlooked Source of SEO Opportunities
IAA Life in Lockdown series: Securing Internet Routing
IAA Life in Lockdown series: Securing Internet Routing
Creating "Secure" PHP applications, Part 2, Server Hardening
Creating "Secure" PHP applications, Part 2, Server Hardening
More from Gong Haibing
Ansible Introduction
This document provides an introduction to Ansible, an open source automation tool. It discusses what Ansible is, highlighting that it is a simple yet powerful IT automation system. It then covers Ansible fundamentals like architecture, modules, inventory, playbooks and variables. The document also discusses advanced Ansible topics such as YAML, debugging, SSH and plugins. It concludes with best practices for Ansible such as using roles and the automation server Tower.
Nginx Essential
This document outlines an agenda for an Nginx essentials presentation. The presentation introduces concepts like HTTP protocols and web servers. It covers installing and configuring Nginx, including its HTTP module and features like load balancing and SSL. It also discusses debugging, customizing Nginx using modules like Tengine and OpenResty, and provides example use cases and references for further reading.
A Byte of Software Deployment
- What's Software Deployment
- A Minimal Python Web Application
- Trouble Shoot
- Interface between Web Server and Application
- Standardization/Automation/Monitoring/Availability
Sponia with QingCloud
This document discusses setting up a cloud computing site like OpenPlay. It outlines the traditional stages of initial setup on physical hardware in a data center, running and maintaining the site, scaling it up, and eventually recycling the hardware. It also provides technical details on OpenPlay's development including issues addressed between versions 1.0 and 2.0, software used like Ubuntu, MongoDB, and Redis, and VPN configurations. The document ends with reference materials on related topics like data centers, cloud computing, networking protocols, and virtualization.
Search Engine
This document discusses search technologies including ElasticSearch, Lucene, SQL, NoSQL, and inverted indexes. It provides information on ElasticSearch features such as its RESTful API, indexing, mapping, aggregations, highlighting, autocomplete, and evaluation metrics like precision and recall. Examples are given of using ElasticSearch with MongoDB through Mongo-Connector and Chinese text segmentation with Jieba.
Jenkins-CI
This document discusses Jenkins-CI, an open source tool for continuous integration and continuous delivery. It provides an overview of Jenkins-CI capabilities including building and testing software projects continuously, integrating changes, and continuously delivering software. The document also demonstrates Jenkins-CI in action with a live demo and discusses configuring Jenkins jobs, managing Jenkins, and requirements for deployment beyond Jenkins-CI like standardization, workflow, monitoring, and high availability.
Linux Fundamental
This document provides an overview of Linux fundamentals including concepts related to Ubuntu desktop and server, Linux distributions and architecture, the philosophy of Linux including the idea that everything is a file, and profiles of key figures like Linus Torvalds. It also summarizes common Linux skills and tools such as the bash shell, VIM text editor, SSH, directory structure, permissions, links, redirection, piping, cron jobs, iptables firewall, and containers versus virtual machines. References are provided for further reading.
Database Fundamental
- Database Concept
- Database History
- Theory and SQL of RDBMS
- Advanced Tops
- Distributed Database and CAP
Git Real
This document provides an overview of Git, including what it is, its internals, and workflows. Git is a distributed version control system that was designed as a content tracker and file system rather than a traditional SCM. It uses a non-linear development model and stores content in compressed objects including blobs for files, trees for directories, commits for snapshots, and tags for labels. Git allows for distributed and non-linear workflows through features like branching, merging, and rebasing. Common Git workflows include Gitflow and GitHub Flow.
More from Gong Haibing (9)
Recently uploaded
Gamify it until you make it Improving Agile Development and Operations with ...
So many challenges, so little time. While we’re busy developing software and keeping it operational, we also need to sharpen the saw, but how? Gamification can be a way to look at how you’re doing and find out where to improve. It’s a great way to have everyone involved and get the best out of people.
In this presentation, Ben Linders will show how playing games with the DevOps coaching cards can help to explore your current development and deployment (DevOps) practices and decide as a team what to improve or experiment with.
The games that we play are based on an engagement model. Instead of imposing change, the games enable people to pull in ideas for change and apply those in a way that best suits their collective needs.
By playing games, you can learn from each other. Teams can use games, exercises, and coaching cards to discuss values, principles, and practices, and share their experiences and learnings.
Different game formats can be used to share experiences on DevOps principles and practices and explore how they can be applied effectively. This presentation provides an overview of playing formats and will inspire you to come up with your own formats.
原版制作贝德福特大学毕业证（bedfordhire毕业证）硕士文凭原版一模一样
原版一模一样【微信：741003700 】【贝德福特大学毕业证（bedfordhire毕业证）硕士文凭】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Pro-competitive Industrial Policy – OECD – June 2024 OECD discussion
Pro-competitive Industrial Policy – OECD – June 2024 OECD discussionOECD Directorate for Financial and Enterprise Affairs
This presentation by OECD, OECD Secretariat, was made during the discussion “Pro-competitive Industrial Policy” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/pcip.
This presentation was uploaded with the author’s consent.
Artificial Intelligence, Data and Competition – SCHREPEL – June 2024 OECD dis...
Artificial Intelligence, Data and Competition – SCHREPEL – June 2024 OECD dis...OECD Directorate for Financial and Enterprise Affairs
This presentation by Thibault Schrepel, Associate Professor of Law at Vrije Universiteit Amsterdam University, was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
Using-Presentation-Software-to-the-Fullf.pptx
Slides on 7 Commonly Used Presentation Softwares; thier usage and features.
The Intersection between Competition and Data Privacy – CAPEL – June 2024 OEC...
The Intersection between Competition and Data Privacy – CAPEL – June 2024 OEC...OECD Directorate for Financial and Enterprise Affairs
This presentation by Tim Capel, Director of the UK Information Commissioner’s Office Legal Service, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
ServiceNow CIS-ITSM Exam Dumps & Questions [2024]
• For a full set of 530+ questions. Go to
https://skillcertpro.com/product/servicenow-cis-itsm-exam-questions/
• SkillCertPro offers detailed explanations to each question which helps to understand the concepts better.
• It is recommended to score above 85% in SkillCertPro exams before attempting a real exam.
• SkillCertPro updates exam questions every 2 weeks.
• You will get life time access and life time free updates
• SkillCertPro assures 100% pass guarantee in first attempt.
Disaster Management project for holidays homework and other uses
It talks about disaster management in a helful way.
Artificial Intelligence, Data and Competition – OECD – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – OECD – June 2024 OECD discussionOECD Directorate for Financial and Enterprise Affairs
This presentation by OECD, OECD Secretariat, was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
ACTIVE IMPLANTABLE MEDICAL DEVICE IN EUROPE
This presentation will help you to know about the classification ,approval process and article related to active implantable medical device
Artificial Intelligence, Data and Competition – ČORBA – June 2024 OECD discus...
Artificial Intelligence, Data and Competition – ČORBA – June 2024 OECD discus...OECD Directorate for Financial and Enterprise Affairs
This presentation by Juraj Čorba, Chair of OECD Working Party on Artificial Intelligence Governance (AIGO), was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
2 December UAE National Day - United Arab Emirates
UAE National Day, celebrated on December 2nd, commemorates the unification of the seven emirates and reflects national pride and unity.
The Intersection between Competition and Data Privacy – OECD – June 2024 OECD...
The Intersection between Competition and Data Privacy – OECD – June 2024 OECD...OECD Directorate for Financial and Enterprise Affairs
This presentation by OECD, OECD Secretariat, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
Pro-competitive Industrial Policy – LANE – June 2024 OECD discussion
Pro-competitive Industrial Policy – LANE – June 2024 OECD discussionOECD Directorate for Financial and Enterprise Affairs
This presentation by Nathaniel Lane, Associate Professor in Economics at Oxford University, was made during the discussion “Pro-competitive Industrial Policy” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/pcip.
This presentation was uploaded with the author’s consent.
The Intersection between Competition and Data Privacy – KEMP – June 2024 OECD...
The Intersection between Competition and Data Privacy – KEMP – June 2024 OECD...OECD Directorate for Financial and Enterprise Affairs
This presentation by Katharine Kemp, Associate Professor at the Faculty of Law & Justice at UNSW Sydney, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
怎么办理(lincoln学位证书)英国林肯大学毕业证文凭学位证书原版一模一样
原版定制【微信:bwp0011】《(lincoln学位证书)英国林肯大学毕业证文凭学位证书》【微信:bwp0011】成绩单 、雅思、外壳、留信学历认证永久存档查询，采用学校原版纸张、特殊工艺完全按照原版一比一制作（包括：隐形水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠，文字图案浮雕，激光镭射，紫外荧光，温感，复印防伪）行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备，十五年致力于帮助留学生解决难题，业务范围有加拿大、英国、澳洲、韩国、美国、新加坡，新西兰等学历材料，包您满意。
【业务选择办理准则】
一、工作未确定，回国需先给父母、亲戚朋友看下文凭的情况，办理一份就读学校的毕业证【微信bwp0011】文凭即可
二、回国进私企、外企、自己做生意的情况，这些单位是不查询毕业证真伪的，而且国内没有渠道去查询国外文凭的真假，也不需要提供真实教育部认证。鉴于此，办理一份毕业证【微信bwp0011】即可
三、进国企，银行，事业单位，考公务员等等，这些单位是必需要提供真实教育部认证的，办理教育部认证所需资料众多且烦琐，所有材料您都必须提供原件，我们凭借丰富的经验，快捷的绿色通道帮您快速整合材料，让您少走弯路。
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
【关于价格问题（保证一手价格）】
我们所定的价格是非常合理的，而且我们现在做得单子大多数都是代理和回头客户介绍的所以一般现在有新的单子 我给客户的都是第一手的代理价格，因为我想坦诚对待大家 不想跟大家在价格方面浪费时间
对于老客户或者被老客户介绍过来的朋友，我们都会适当给一些优惠。
Why Psychological Safety Matters for Software Teams - ACE 2024 - Ben Linders.pdf
Psychological safety in teams is important; team members must feel safe and able to communicate and collaborate effectively to deliver value. It’s also necessary to build long-lasting teams since things will happen and relationships will be strained.
But, how safe is a team? How can we determine if there are any factors that make the team unsafe or have an impact on the team’s culture?
In this mini-workshop, we’ll play games for psychological safety and team culture utilizing a deck of coaching cards, The Psychological Safety Cards. We will learn how to use gamification to gain a better understanding of what’s going on in teams. Individuals share what they have learned from working in teams, what has impacted the team’s safety and culture, and what has led to positive change.
Different game formats will be played in groups in parallel. Examples are an ice-breaker to get people talking about psychological safety, a constellation where people take positions about aspects of psychological safety in their team or organization, and collaborative card games where people work together to create an environment that fosters psychological safety.
Artificial Intelligence, Data and Competition – LIM – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – LIM – June 2024 OECD discussionOECD Directorate for Financial and Enterprise Affairs
This presentation by Yong Lim, Professor of Economic Law at Seoul National University School of Law, was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
Recently uploaded (20)
Gamify it until you make it Improving Agile Development and Operations with ...
Gamify it until you make it Improving Agile Development and Operations with ...
Pro-competitive Industrial Policy – OECD – June 2024 OECD discussion
Pro-competitive Industrial Policy – OECD – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – SCHREPEL – June 2024 OECD dis...
Artificial Intelligence, Data and Competition – SCHREPEL – June 2024 OECD dis...
The Intersection between Competition and Data Privacy – CAPEL – June 2024 OEC...
The Intersection between Competition and Data Privacy – CAPEL – June 2024 OEC...
Prsentation for VIVA Welike project 1semester.pptx
Prsentation for VIVA Welike project 1semester.pptx
Disaster Management project for holidays homework and other uses
Disaster Management project for holidays homework and other uses
Artificial Intelligence, Data and Competition – OECD – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – OECD – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – ČORBA – June 2024 OECD discus...
Artificial Intelligence, Data and Competition – ČORBA – June 2024 OECD discus...
2 December UAE National Day - United Arab Emirates
2 December UAE National Day - United Arab Emirates
The Intersection between Competition and Data Privacy – OECD – June 2024 OECD...
The Intersection between Competition and Data Privacy – OECD – June 2024 OECD...
Pro-competitive Industrial Policy – LANE – June 2024 OECD discussion
Pro-competitive Industrial Policy – LANE – June 2024 OECD discussion
The Intersection between Competition and Data Privacy – KEMP – June 2024 OECD...
The Intersection between Competition and Data Privacy – KEMP – June 2024 OECD...
Why Psychological Safety Matters for Software Teams - ACE 2024 - Ben Linders.pdf
Why Psychological Safety Matters for Software Teams - ACE 2024 - Ben Linders.pdf
Artificial Intelligence, Data and Competition – LIM – June 2024 OECD discussion
Artificial Intelligence, Data and Competition – LIM – June 2024 OECD discussion
How to Code Review
- 1. @dylanninin
- 6. OpenPlay 1.0 / - - - … : - http://bit.ly/1TfZFpV
- 7. OpenPlay 1.0 - - - … : - http://bit.ly/1Tk7zOX
- 9. - if else - - http://bit.ly/1VUBI8f
- 10. Rating - rating/motm - rating/motm - … - http://bit.ly/1UE2CCj - http://bit.ly/1PGTPaa
- 12. Cub ElasticSearch - - - - … - http://bit.ly/1M25XI1 - http://bit.ly/1M25wxz
- 14. Redis pubsub - / - pubsub, list - - http://bit.ly/1M26wSg
- 16. Admin Stats - 1.x (MongoDB) —> 2.x (ElasticSearch) - DownloadMixin - crontab -> queue -> queue/msg - http://bit.ly/1VUBrSM - http://bit.ly/1PGTPaa
- 23. • • • • • •
- 24. Python
- 25. >>> import this The Zen of Python, by Tim Peters Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!
- 28. Hello World
- 35. • • • GitHub + Pull Request + Issue • • •
- 38. - • • • •
- 40. - • • • • “ “ • API
- 41. • • • -
- 42. Just Do It
- 43. Q & A
- 44. Reference • https://en.wikipedia.org/wiki/Code_review • Code Review • What to look for in a Code Review • Stop More Bugs with our Code Review Checklist • code-review-best-practices