Continuous Deployment Cost Open Source Operations 
Startup Lessons Learned
SEPTEMBER 15, 2008
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. One that is powered by three drivers, each of which is a part of a major trend: The use of platforms enabled by open source and free software.
Startup Lessons Learned
NOVEMBER 13, 2008
Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. Five whys helps us keep our cool.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 4, 2008
It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Case Study: Continuous deployment makes releases n. Agile software development.
Startup Lessons Learned
JULY 29, 2009
We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. Although it costs to pay down the principal, we gain by reduced interest payments in the future. Leverage product development with open source and third parties.
Startup Lessons Learned
SEPTEMBER 8, 2009
That is just currently a full personal money sucking process, as you're taxed on income and have no business breaks yet, besides supplies, the majority of costs to start up a business have no tax advantages to creating a start up. Case Study: Continuous deployment makes releases n. September 8, 2009 6:25 PM dbsaid.
Startup Lessons Learned
JANUARY 12, 2009
When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. At the cost of a little extra indirection, you can organize your code around a series of long-lived objects, each of whom communicates with the other objects in simple, easy-to-understand ways.
Startup Lessons Learned
JANUARY 4, 2009
This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. Im talking about the actual data-fetching operation. This information is normally maintained by your operations team.
Expert insights. Personalized for you.
168 
Let's personalize your content