This post explores the ins and outs of building AWS Lambda serverless functions with .NET Core. The focus is on the programming model, the particularities of the .NET runtime, and tooling.
Developers and testers will often be on the same team, but accomplish drastically different tasks. A developer will typically write code, test the code, and document the feature. A tester will verify that the feature conforms to its requirements and find any bugs. Some of these tasks can happen at the same time whilst others can’t.
They create anxiety and confusion. Discover how to implement them successfully in your project.
SmartBear recently released their annual State of Code Review, in which they look at trends in the code quality space. Some interesting insights and areas of improvement can be found by interpreting the survey results.
One of your colleagues is asking you to review the code she wrote. Instead of haphazardly looking at the code to find issues with it, use these three simple steps to provide a meaningful, thorough review that will help both yourself and your colleague improve the quality of the code being checked in.
There are a number of excellent products out there to help make code reviews more effective. Today we’re going to look at ReviewBoard to see how it differentiates itself from its main competitors. ReviewBoard has been quietly improving its product since its initial release in 2009 to provide a great code review experience for teams of any size.
Long used by pilots to prepare an airplane for the every phase of a flight, it serves us in much the same way for code review.
The average suggested time to spend on a code review is between 30 to 60 minutes. So how do you find time to do anything else?