Version One Ventures
APRIL 11, 2019
Instead of asking three questions as we did with Bala, we’re going to take a very deep dive into a critical topic: code quality. What follows below are Sin-Mei’s words on how she (and Shippo) define code quality. How do you define code quality? or “What does code quality mean to you?” Functional quality.
Andrew Payne
FEBRUARY 17, 2020
I developed them in 3 days, by writing a C program to automatically generate the range of tests. I don’t tell that story to brag, but to talk about the “10x developer” If you write code at all, you’ve surely heard of the idea there are programmers ten times as productive as others.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. The current code is spaghetti, but the new code will be elegant.
Startup Lessons Learned
SEPTEMBER 30, 2008
It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software?
YoungUpstarts
DECEMBER 11, 2014
Funding – Knowing the right people (and how to pitch them) so your business gains additional capital for the things that matter like product development, hiring, service, and expansion. Here are but a few you and the business could stumble upon: 1.
Startup Lessons Learned
JULY 29, 2009
But there is more to technical debt than just the interest payments that come due. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In particular, try these three things: Invest in technical debts that may never come due.
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Expert insights. Personalized for you.
99 
Let's personalize your content