This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer DevelopmentEngineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you?
Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.
Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior SoftwareEngineer at There.com, leading efforts in agile softwaredevelopment and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.
The technical interview is at the heart of these challenges when building a productdevelopment team, and so I thought it deserved an entire post on its own. For softwareengineers, I think this absolutely has to be a programming problem solved on a whiteboard. Thats OK, were not trying to hire a therapist.
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, softwareengineering, and computer programming. The economics of these process trade-offs are discussed in the Principles of ProductDevelopment Flow.)
Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in SoftwareEngineering's Process model. March 26, 2010 8:42 AM ankur aggarwal said. the link given in this blog "CI" is very impressive.
Nand changed the culture of the JAIC, bringing in Silicon Valley tools for productdevelopment, product management and for the first time a culture that focused on UI/UX, MVPs and continuous integration and deployment. JAIC Is Applied AI – Focused on Impact. AI is not a single technology. I want you to come into that.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content