article thumbnail

Codacy nabs $15M to improve code reviews with automation

TechCrunch

Code review is a key step during the software development process — it’s when people check a program by viewing and reading parts of the source code. But despite its importance, not all developers are pleased with the way traditional code reviews work. Image Credits: Codacy.

article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

5 ways to do Continuously Improved Testing

Xebia

Definition of Done – a team needs to agree that executing these tests is part of delivering changes and when changing code, new tests should be added. principles of testing (popularized by the book Clean Code by Robert C Martin ). From a process perspective, you should aim to ensure they are executed before the code is merged.

Testing 130
article thumbnail

Getting Stuff Done Days in Apiumhub: R&D in software development

Apiumhub

Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the software development and boost a proactive, continuous improvement-based engineering culture in their organizations. Take time to review the existing work and refactor properly if needed. Excellence. Productivity.

article thumbnail

Learn how to build a resilient software team

CircleCI

The rollercoaster of 2020 highlighted the competitive advantage that well-oiled software delivery teams provide. The minute COVID-19 hit and everyone had to become not just remote-first, but remote-only, many engineering teams were forced to reckon with the number of manual processes they had in place. Think of Amazon’s Two Pizza Rule.

article thumbnail

A guide to personal retrospectives in engineering

CircleCI

This post was written by Stig Brautaset, CircleCI Senior Software Engineer, in collaboration with Cian Synnott, CircleCI Senior Staff Software Engineer. Retrospectives are a well-established resource in the software and systems engineering toolbox. What is a personal retrospective? What went badly?

article thumbnail

Forbes names CircleCI to America's Best Startup Employers list

CircleCI

From rolling out major product additions like CircleCI Insights and private orbs , along with educational resources like our developer hub and State of Software Delivery Report that includes the first CI/CD benchmarks for high-performing engineering teams, it seems like every day there is something new to look forward to.