Pdf/cond-mat/0303516v1.pdf. Want to Know Difference Between a CTO and a VP of Engineering? I recently did a post for startups on understanding sales people. A few people asked me to try and define the perfect startup organization chart. I don’t believe that one exists. Every team configuration is different. But I do have more insight into understanding your startup team.
This time I thought I’d try and address engineering talent. Often I’m asked by startup CEO’s about how to best build an engineering team. I have much experience in this domain. Because more technology people probably read startup blogs I’m guessing this post will come under more scrutiny. This post is designed mostly for non-technical founders. Let’s start with the basics. 1. So I believe that every great technology startup has the technology visionary inside the company. Trying to work without this person is like wanting to build a world class sky scraper but not having a great lead architect and civil engineer. In fact, it my experience the best technologists are akin to artists. 2. 3. In summary. OK.
SQL vs. NoSQL. So, what is the big deal about NoSQL databases? For one, they've introduced new ways (or perhaps re-introduced old ways) of thinking about what databases are and what they can do. For another, they're shiny and new, and all the cool kids seem to be using them. You could argue that Google's BigTable is the database that inspired the NoSQL movement. Or, maybe it was Amazon's S3. Both of them are closed source, but they were (or are) impressive enough to inspire open-source interpretations. The current NoSQL field includes HBase, Cassandra, Redis, MongoDB, Voldemort, CouchDB, Dynomite, Hypertable and several others.
Instead of having tables with columns and rows like you would find in a traditional RDBMS, most NoSQL databases are simple “key-value stores”. A step beyond simply having keys and values are the so-called document databases. Why do traditional database users dislike these newcomers? Most classic RDBMSes initially were designed to run on a single large server.
This Is Generation Flux: Meet The Pioneers Of The New (And Chaotic) Frontier Of Business. The 18 Mistakes That Kill Startups. October 2006 In the Q & A period after a recent talk, someone asked what made startups fail. After standing there gaping for a few seconds I realized this was kind of a trick question. It's equivalent to asking how to make a startup succeed—if you avoid every cause of failure, you succeed—and that's too big a question to answer on the fly. Afterwards I realized it could be helpful to look at the problem from this direction. If you have a list of all the things you shouldn't do, you can turn that into a recipe for succeeding just by negating. And this form of list may be more useful in practice. In a sense there's just one mistake that kills startups: not making something users want. 1. Have you ever noticed how few successful startups were founded by just one person?
What's wrong with having one founder? But even if the founder's friends were all wrong and the company is a good bet, he's still at a disadvantage. The last one might be the most important. 2. Why is the falloff so sharp? FeaturePlan - Product Management Software. FeaturePlan FeaturePlan is a central knowledge base and decision making tool that stores all your product information, from new customer ideas and customer enhancement requests, to market and technical requirements.
It allows you to identify market problems and define the features and roadmaps to best respond to your customers needs through the products you develop. An agile, enterprise-class solution, FeaturePlan enables collaboration across all of your company's product groups, including marketing and sales, engineering, professional services, support, and product management. In addition to supporting day-to-day product management activities, FeaturePlan product management software also provides robust analytics and reporting capabilities that dig deeper into your processes to help you leverage best practices in product management within your company.
IBM aims to formalize the social enterprise movement. Amid more chatter about the social enterprise than the tech industry can stand, IBM is aiming to formalize training and services to help companies adopt new tools and processes. The so-called social enterprise---a term that has been pitched repeatedly by Salesforce.com CEO Marc Benioff---is in the early innings, but there's a lot of interest. The general aim is to connect companies, customers and networks. Benioff in his recent keynotes indicated that Salesforce.com holds sessions with companies to map out what their social enterprise would look like. IBM appears to be picking up that baton with more formal software and services. Related: Social enterprise, meet master data management | Salesforce.com CEO Benioff calls for 'corporate Spring' IBM is planning to offer services to help customers develop skills and technical support for social networking. Among the key social enterprise items from IBM:
Www.windley.com/docs/Product Management.pdf.