article thumbnail

TechCrunch+ roundup: Technical due diligence, web3’s promise, how to hire well

TechCrunch

So far, web3 has not paid off on the Promise of the Premise : open source software that runs live on the blockchain. Use discount code TCPLUSROUNDUP to save 20% off a one- or two-year subscription. 8 questions to answer before your startup faces technical due diligence. “It’s still much easier to develop a Web 2.0

article thumbnail

Doing Diligence Well In Venture Investing: Going Back To The Future

Crunchbase News

By Nicolas Sauvage Due diligence has made a comeback. According to a study of 700 venture capital firms , a typical deal once took 83 days to complete. On an average deal, VCs would spend 118 hours on due diligence and call 10 references. The assumption was often that someone else had already done the diligence.

Insiders

Sign Up for our Newsletter

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

Trending Sources

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. To date, Codacy has raised $28 million.

article thumbnail

Daily Crunch: After glitch causes a two-hour global outage, WhatsApp restores service

TechCrunch

8 questions to answer before your startup faces technical due diligence. Outsiders study multiple facets of a startup to determine its value and quality, and codebase health is one of them. After technical due diligence (TDD) begins, no amount of storytelling can cover the secrets buried in GitHub and Jira.

article thumbnail

Checklist for an Efficient Code Review

Dzone - DevOps

Why Is Code Review Important? Peer code review is a widely used technique by software engineering teams. The intuition is that if more software engineers review the code, there will be fewer bugs, and, in general, the maintainability of the code will be improved.

article thumbnail

Simple sabotage for software

Erik Bernhardsson

When possible, refer all matters to committees for “further study and consideration” Attempt to make committees as large as possible — never less than five. Leverage any production issue as a reason to “pull the brakes” Introduce very complex processes for code change and common workflows.

article thumbnail

Article: From Async Code Reviews to Co-Creation Patterns

InfoQ Culture Methods

This article dives into the throughput and quality of the async code review process, which are very important dimensions to optimize for in product development teams.