Remove Continuous Deployment Remove Global Remove Japan Remove Operations
article thumbnail

Lessons Learned: Please teach kids programming, Mr. President

Startup Lessons Learned

these devices all need human instruction to enable correct and desired operation. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuous deployment makes releases n.

Insiders

Sign Up for our Newsletter

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

article thumbnail

What would you want to tell Washington DC about startups?

Startup Lessons Learned

So heres my simple question: What do folks in Washington need to know about the global community of entrepreneurs? Id like to see if we can come up with policy suggestions, concerns, or questions that might promote entrepreneurship generally - and globally. Ease the process for startups to get access to global talent.

DC 90
article thumbnail

Embrace technical debt

Startup Lessons Learned

Lean vs. debt In the world of physical goods, the leaner a supply chain is, the less debt is required to operate it. Once we can see opportunities for truly global efficiency gains, all that remains is to ensure our team actually makes room for those investments. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Because there are no tests for new features (or operational alerts for the production code), the code that supports those new features could go bad at any moment. I'm sure we all agree the technology landscape has changed in the last 30 years, but are you blaming agile development for the global financial crisis?