Release: Granular analysis on diffs
On changeset analysis, we now raise issues only on the changed lines, not files.
Release: Actions on issues, ignore rules
New actions on your repository dashboard that help you tweak how issues are reported.
Change severity of issues, create ignore rules for specific issues, and more.
Release: Test coverage, meta config for analyzers
Quick update that highlights recent product releases and improvements we’ve made.
8 new anti-patterns for Python
Freshly added in DeepSource's Python analyzer.
Detecting files opened improperly, returning multiple variable types in a function, accidentally enabling debugger in production code, and more.
Python and Kubernetes Events: March 2019
Meeting developers at local meet-ups in Bangalore.
The team was present at local meetups in Bangalore to talk about Continuous Quality and Kubernetes. Here's the gist of the talks.
Effective code reviews: a primer
Simple steps which make peer code reviews work better for teams.
Peer code reviews as a process have increasingly been adopted by engineering teams around the world. It is worth the time and effort to put together a code review strategy and consistently follow it in the team. Here's a primer on how to do that.
5 best practices for using Git
Simple conventions which make Git work best for a team.
Git has become ubiquitous as the preferred version control system (VCS) used by developers. Here's a list of best practices you should follow to ensure sanity when using Git in your team.
Exponential cost of fixing bugs
How the cost of finding and fixing defects increases with time.
After software has been released and is in production, the cost of finding and fixing defects in incredibly higher as compared to early stages of development -- often by an order of magnitude or two.
6 benefits of Continuous Quality
Reasons why adding CQ to your development pipeline is worth it.
Implementing Continuous Quality (CQ) alongside CI and CD can help improve the impact of engineering teams. Here are 6 ways how.
Importance of software documentation
Comments age like fish, unlike code.
Software evolves, and changes to software is inevitable. In general, any work done to change the software after it is in operation is considered to be maintenance work. Maintenance consumes over 70% of total life-cycle cost of a software project. If you think about it for a while, you would realize how critical maintenance work is to keep the software alive. Interestingly, the act of reading code is most time-consuming component of all maintenance activities performed by software developers.
Join like-minded developers and engineering leaders
Stay updated with DeepSource's product updates and insights by subscribing to our newsletter.