
One dataset visualized 25 ways …

Personal collective of ideas, thoughts and notes




















































If you want to go fast, go alone. If you want to go far, bring others along”
African Proverb

Source: http://www.usabilitycounts.com/author/admin-2/
Even for a MVP, it takes a village to build a product.
The village has several roles, and selecting the right team early can make or break your idea. Your village will never be of an ideal size, but understanding what you need from your townsfolk can help you make some hard decisions on how to staff the team. Early on, flexibility is the key. You may also have to split up the work if it’s a side project and everyone has a day job.
The composition of the ideal team has been a question that’s been on Quora, and great advice can be traced to a simple model that Dave McClure of 500 Startups advocates — Hustler, Hacker, and Designer — but it has to be viewed within the context of what you’re building. This article covers all the roles that go into building a product, and places where you can “cheat”, i.e. fill in with people that are in other roles. Minimum viable product projects are about building something to a level that gets you started, within extreme constraints.
In my early twenties I was adamant I was going to develop an Open Source ERP Platform, now working for SAP, I get to contribute to that dream, but probably will not get a chance to fulfill the base ambition 🙂 This flow chart always helped me understand the many aspects of ERP design, its processes and high tightly coupled each element and step was.

Understanding the ontology architecture of knowledge is a crucial step in moving toward general artificial general intelligence. Over the past few years, the diagrams and slides have helped add some context to the underlying nuances of mapping, processing and predicting natural language and the foundational elements of text.




You must be logged in to post a comment.