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
This post expands on a recent podcast I did with Living Corporate outlining the story behind my career switch to softwareengineering. My undergrad was in Nutritional Science at UT Austin, and I have a graduate business degree from Arizona State University. This has all been a plot twist I didn’t think was possible.
At its heart, DDD outlines an approach to softwaredevelopment with a set of principals and tools. We are focusing on four primary principals from DDD: an emphasis on business value, cross-functional collaboration and a focus on the big picture, all while employing software best practices.
I wasn’t a very good softwaredeveloper, and I was only modestly capable as a UX designer, but I learned enough to recognize clean code and effective, inspiring design when I saw it. I learned that softwareengineers?—?or or developers?—?are are just as much artists as they are scientists. family of brands.
The good news is that with a little more thinking before things become a problem and proper education for the development team, most of these problems can be avoided.
The good news is that with a little more thinking before things become a problem and proper education for the development team, most of these problems can be avoided.
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.
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. Ive attempted to embed the relevant slides below. Take a look and let me know what you think.
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