Remove Agile Remove Architecture Remove Metrics Remove Software Engineering
article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software?

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. At the time, I was a die-heard Java zealot.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. The same might be said of good software. We owe a lot to this seminal document. But what about Commodity?

article thumbnail

CEO Friday: Why we don’t hire.NET programmers

blog.expensify.com

The vast majority of patterns and architecture patterns that we see in PHP, Ruby and other scripting languages are incomplete implementations of stuff the Java and C# guys created. It is clear that good software engineers avoid you. Really skillful software engineers do not use.NET. Joel Martinez. Elaine Kenny.

Java 107