Slicing Pie: Funding Your Company Without Funds31We80f2z1L._SX310_BO1,204,203,200_

You and a partner go into business together and split the equity 50/50. You do all the work and your partner slacks off. He owns half your business- now what?

Slicing Pie outlines a process for calculating exactly the right number of shares each founder or employee in an early stage company deserves.

You will learn:

  • How to value the time and resources an individual brings to the company relative to the contributions of others
  • The right way to value intangible things like ideas and relationships
  • What to do when a founder leaves your company
  • How to handle equity when you have to fire someone
  • Important issues to discuss with your lawyer
  • Much more

Research shows that dynamic equity split models, like the one outlined in Slicing Pie, is the best way to avoid conflicts as the company grows.

The new and improved Version 2.3 contains updated information about legal issues, idea valuation, retrofitting and much more!

The Founder’s Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup (The Kauffman Foundation Series on Innovation and  41qyfyCw3hL._SX329_BO1,204,203,200_Entrepreneurship)

Often downplayed in the excitement of starting up a new business venture is one of the most important decisions entrepreneurs will face: should they go it alone, or bring in cofounders, hires, and investors to help build the business? More than just financial rewards are at stake. Friendships and relationships can suffer. Bad decisions at the inception of a promising venture lay the foundations for its eventual ruin. The Founder’s Dilemmas is the first book to examine the early decisions by entrepreneurs that can make or break a startup and its team. Drawing on a decade of research, Noam Wasserman reveals the common pitfalls founders face and how to avoid them. He looks at whether it is a good idea to cofound with friends or relatives, how and when to split the equity within the founding team, and how to recognize when a successful founder-CEO should exit or be fired. Wasserman explains how to anticipate, avoid, or recover from disastrous mistakes that can splinter a founding team, strip founders of control, and leave founders without a financial payoff for their hard work and innovative ideas. He highlights the need at each step to strike a careful balance between controlling the startup and attracting the best resources to grow it, and demonstrates why the easy short-term choice is often the most perilous in the long term. The Founder’s Dilemmas draws on the inside stories of founders like Evan Williams of Twitter and Tim Westergren of Pandora, while mining quantitative data on almost ten thousand founders. People problems are the leading cause of failure in startups. This book offers solutions.

Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist51p0oeLn-PL._SX337_BO1,204,203,200_

As each new generation of entrepreneurs emerges, there is a renewed interest in how venture capital deals come together. Yet there is little reliable information focused on venture capital deals. Nobody understands this better than authors Brad Feld and Jason Mendelson. For more than twenty years, they’ve been involved in hundreds of venture capital financings, and now, with the Second Edition of Venture Deals, they continue to share their experiences in this field with you.

Engaging and informative, this reliable resource skillfully outlines the essential elements of the venture capital term sheet–from terms related to economics to terms related to control. It strives to give a balanced view of the particular terms along with the strategies to getting to a fair deal. In addition to examining the nuts and bolts of the term sheet, Venture Deals, Second Edition also introduces you to the various participants in the process and discusses how fundraising works.

  • Fully updated to reflect the intricacies of startups and entrepreneurship in today’s dynamic economic environment
  • Offers valuable insights into venture capital deal structure and strategies
  • Brings a level of transparency to a process that is rarely well understood

Whether you’re an experienced or aspiring entrepreneur, venture capitalist, or lawyer who partakes in these particular types of deals, you will benefit from the insights found throughout this new book.


2016-05-13 丑灿 大数据技术









Data Science for Business



——来自Amazon用户m I的读后感


The Art of Data Science







Big Data:Principles and Best Practices of Scalable Realtime Data Systems


——来自Amazon用户Kirk D. Borne的读后感



 Big Data Now: 2015 Edition



03.Apache HadoopDISCOVERY



Hadoop: The Definitive Guide


——来自Amazon用户AI Gordon的读后感


Hadoop Explained



04.Apache SparkDISCOVERY



 Learning Spark




《掌握Apache Spark》

Mastering Apache Spark

这本书是我们收集关于使用Apache Spark的各种具体细节的最后一块终极瑰宝。





Pattern Recognition and MachineLearning (Information Science and Statistics)





Elements of Statistical Learning


——来自Amazon用户Enceladus Transit的读后感




Python MachineLearning


——来自Amazon用户Brian M. Thomas的读后感



An Introduction to StatisticalLearning with Applications in R







Neural Networks and Deep Learning


  • 一个绚烂的受生物学启发得到的程序设计范例,可以让计算机从所观察到的数据进行相应内容的学习
  • 深度学习,神经网络中强大的学习技术




Deep Learning

这本由Ian Goodfellow,、Yoshua Bengio和Aaron Courville合著的书籍正在筹备阶段,有可能是未来最佳的关于深度学习的书籍。这本书的开发版每月都在更新,在最终出版的时候读者可以免费获取。




Data Mining:Concepts and Techniques, Third Edition





Mining of Massive Datasets





《SQL 第二版》

Learning SQL,Second Edition


——来自Amazon用户Jack D. Herrington的读后感



Learn SQL The Hard Way






Statistics inPlain English, Third Edition


——来自Amazon用户Shyam Goli的读后感


《Think Stats:程序员需要的概率论统计学,第二版》

Think Stats:Probability and Statistics for Programmers, Second Edition

Think Stats强调了让你使用简单的技术进行数据和有趣问题答案的开发。这本书介绍了美国国家卫生研究院使用数据进行的案例的研究。


Recommended Reading for Developers

Jeff Atwood

This list was last updated in March 2015.

Why are updates to my reading list so rare? Because computers change a lot in 10 years, but people don’t.

To make better software, you need to understand how people work, and that is what the books I recommend tend to focus on.

Code Complete 2


Steve McConnell’s Code Complete 2 is the Joy of Cooking for software developers. Reading it means that you enjoy your work, you’re serious about what you do, and you want to keep improving. In Code Complete, Steve notes that the average programmer reads less than one technical book per year. The very act of reading this book already sets you apart from probably ninety percent of your fellow developers. In a good way.

I like this book so much that the title of this very website is derived from it – the examples of what not to do are tagged with the “Coding Horror” icon. There’s nothing funnier than a Coding Horror – until you have to deal with one yourself. Then it’s suddenly not so funny any more. Do yourself a favor. Make this the first book you read, and the first book you recommend to your fellow developers.

The Mythical Man-Month


Arguably the only classic book in our field. If you haven’t read it, shame on you.

I challenge any developer to pick up a copy of The Mythical Man Month and not find this tale of a long-defunct OS, and the long-defunct team that developed it, startlingly relevant. This twenty-five year old book boldly illustrates one point: computers may change, but people don’t.

Reading this classic work will certainly be a better use of your time than poring over the latest thousand page technical tome du jour.

Don’t Make Me Think


The single best book on usability I’ve ever read. The title says “web usability” but don’t be fooled by its faux specificity. Steve Krug covers every important usability concept in this book, and covers it well. It’s almost fun. If you choose to read only one book on usability, choose this one. It’s chock full of great information, and it’s presented in a concise, approachable format. It’s suitable for any audience: technical, non-technical, user, developer, manager, you name it.

sample graphic from Don't Make Me Think

Er… yeah. Never been in a meeting like that. The solution to this problem, by the way, is quick and dirty usability testing. Imagine that: making decisions based on actual data instead of never ending, last man standing filibuster style religious debates. Revolutionary!

Rapid Development


The full title of this book is Rapid Development: Taming Wild Software Development Schedules, which isn’t just long-winded and vaguely ridiculous, it’s also an unfortunate misnomer.

Rapid Development isn’t about rapid development. It’s about* the reality of failure* . The vast majority of software development projects will fail: they will overrun their schedules, produce substandard results, or sometimes not even finish at all. This isn’t an argument; it’s a statistical fact. The unpleasant truth is that your team has to be very good to simply avoid failing, much less to succeed. While that may sound depressing – okay, it is depressing– you’ll still want to read this book.

Why? Because half* of success is not repeating the same mistakes you, or other people, have made. The epiphany offered in this book is that making mistakes is good– so long as they are all new, all singing, all dancing mistakes. If you’re making the same old classic mistakes, you’ve failed before you’ve even begun. And you probably have no idea how likely it is that you’re making one of these mistakes right now.

Our field is one of the few where change is the only constant, so it’s only natural to embrace that change and try different “Rapid” development techniques. But the converse isn’t true. We can’t assume that so much has changed since 1970 that all the old software development lessons are obsolete and irrelevant when compared to our hot new technology. It’s the same old story: computers have changed; people haven’t. At least have some idea of what works and what doesn’t before you start– in McConnell’s words, “read the instructions on the paint can before painting.” Sure, it sounds obvious enough until you read this book and realize how rarely that actually happens in our field.

* According to the book, technically, one-quarter. But I think it’s more than that.



If you’ve ever seen the performance of an all-star sports team suffer due to poor coaching, you’ll appreciate this book. It doesn’t matter how many “coding superstars” you’ve got when none of them can talk to each other, or agree on anything. And it no developer, however talented, can work effectively when constantly being barraged with minor interruptions. Developers aren’t known for their people skills, per se, but here’s the ironic part: the success of your project may hinge on just that. If you have any legitimate aspirations to be a “Team Leader” in practice instead of in name only, you need to pick up a copy of this book.

While Peopleware is full of great, totally valid points, it also implies a level of employee control over the workplace that is pure fantasy at most companies. But at least you’ll know when your work environment, or your team, are the real problem – and more importantly, what to do about it.

The Design of Everyday Things


It can be incredibly frustrating to develop software, because so much can go wrong. A lot of what we do is defensive: trying to anticipate what will go wrong before it does. It’s mentally fatiguing, and can eventually manifest itself in some negative ways. I sometimes describe this to non-technical people as building a watch with a thousand moving parts, all of which can fail randomly at the slightest provocation. Good times!

Designing software is difficult, to be sure, but designing a door is difficult too. The nuances of design extend into every object you touch, whether it’s some hot new SQL engine, or a humble shoe. This book will give you a new appreciation of the “devil in the details.” If designing a door isn’t the no-brainer we thought it was, maybe it’s time to give ourselves a break for not being able to design software perfectly, either.

About Face: The Essentials of Interaction Design


Alan Cooper, father of Visual Basic, godfather of usability. I’ve owned a few versions of this book now (this is version four), and it is the rare book which is getting better and better as it is revised, and more authors are added for different perspectives.

About Face is full of generally applicable guidelines for mobile and web. Of the GUI problems used for illustration – with examples from the hoary old Windows 95 UI – it’s interesting to compare which have been mostly resolved (using visual examples to show the effects of dialog selections before you make them), and which have not (stopping the proceedings with modal idiocy).

It’s a fantastically useful book; I’ve used whole chapters as guides for projects I worked on.

The Inmates Are Running the Asylum


This is the book that introduced the world to the concept of personas: rather than thinking of users as an abstract, difficult-to-describe, amorphous group of people, personas instruct us to talk about specific users who have names, personalities, needs, and goals. Would our users want a print preview feature? Who knows? But if Gerry Manheim, Account Executive, has to print out his weekly expense report as a part of his job, you better believe print preview needs to be in there. There’s nothing magical here; as always, it boils down to knowing who your users are and what they really do – and the personas technique is a great way to get there.

There’s also an interesting analysis here of how developers tend to think themselves qualified to make usability decisions on behalf of “regular” users, when in reality they’re anything but. Developers are freakish, extreme users at best– “Homo Logicus” versus “Homo Sapiens.” Unless you happen to be writing a compiler where developers are the end users.

One hidden lesson in this book is that sometimes it doesn’t matter how good your design is: the scanner software and the web development software which Alan consulted on, and uses as examples in this book, both failed in the marketplace for reasons that had nothing to do with their usability– which was verifiably excellent.* Sometimes great products fail for reasons beyond your control, no matter how hard you try. Feel free to use this fact to counterbalance the sometimes bombastic tone of the book.

* I owned the exact model of “behind the keyboard” USB scanner pictured in the book, and I was quite impressed with the bundled scanning software. I eventually gave this scanner to my Dad. One time I was chatting on the phone with him and without any prompting at all, he mentioned to me how much he liked the scanning software. This was before the book had been published!

Programming Pearls


I hesitated to include Programming Pearls because it covers some fairly low-level coding techniques, but there are enough “pearls” of software craftsmanship embedded in this book to make it well worth any developer’s time. Any book containing this graph..

.. is worth its weight in gold. TRS-80 versus DEC Alpha to illustrate 48n versus n3 algorithms? Come on folks, it just doesn’t get any better than that. Programming Pearls is the next best thing to working side by side with a master programmer for a year or so. It is the collective wisdom of many journeyman coders distilled into succinct, digestible columns.

I won’t lie to you: there are entire chapters that can probably be ignored. For example, I can’t imagine implementing sorting, heap, or hash algorithms as documented in columns 11, 13, and 14 respectively, given today’s mature libraries of such basic primitives. But for every textbook-tedious exercise, there is real, practical advice alongside. Just scan through the book, ignoring the code sections, and I doubt you’ll be disappointed. Column 8, “Back of the Envelope” is essential, probably the best treatment of estimation I’ve seen anywhere. It also goes a long way towards explaining those crazy interview questions that companies love to annoy us with.
You can read sample sections of the book online if you’re still on the fence. I recently used the chapter on strings to illustrate the use of Markov chains in generating synthetic data to fill an empty database with – a performance estimation technique covered in “Back of the Envelope”.

The Pragmatic Programmer: From Journeyman to Master


This book reminds me a lot of Programming Pearls, but it’s actually better, because it’s less focused on code. Instead of worrying about code, the authors boiled down all the practical approaches that they’ve found to work in the real world into this one book. Not all of these things are technically programming. For example, asking yourself “why am I doing this? Is this even worth doing at all?” isn’t thinking outside the box; it’s something you should incorporate into your daily routine to keep yourself – and your co-workers – sane. And that’s what makes Pragmatic Programmer such a great book.

If you’d like to know a little more about the book, I created a HTML version of the pullout reference card included inside, which provides a nice overview of the contents.

Designing Web Usability


Jakob Neilsen is well known for his usability site, and his career as a usability expert extends back to 1989 when his first book was published. Designing Web Usability is of course a full-on web usability primer, so it’s a bit different than the GUI-oriented Cooper books.

The Visual Display of Quantitative Information


Visual Explanations: Images and Quantities, Evidence and Narrative


Envisioning Information


Beautiful Evidence



Information is beautiful. And so is a well-designed GUI.

You don’t need to own all four books in the series unless you’re a completist (or a masochist, I suppose), but the first two are essential.

Chris Sells has some interesting insight on the Tufte books based on a Tufte seminar he attended in June 2004.

Regular Expressions Cookbook


UNIX has a well-deserved reputation for being complex and impenetrable. So do Regular Expressions.

I may be a card carrying member of the “Keep It Simple Stupid” club, but I’m making a meteor sized exception for regular expressions. Written properly, they will save you a tremendous amount of time in string manipulation, and I’ve never run across a project where they didn’t come in handy somewhere.

Once you delve into the world of regular expressions, you may become drunk with the amazing power and potential they have, which results in things like Perl. Remember, absolute power corrupts absolutely. But it also rocks absolutely.

5 insanely great books about mathematics you should read

Kelly J. Rose

Source: https://wp.kjro.se/2013/12/27/5-insanely-great-books-about-mathematics-you-should-read/

I’ve been asked over and over for good books about mathematics for a layperson, someone who hasn’t taken advanced courses in university and is more simply interested in learning about what math is, and some of the more interesting historical figures and results from mathematics. Ironically, when you are a mathematics major at Waterloo, you get the opportunity in 4th year to take a course on the history of mathematics and you get introduced to a few really good books that start to explain the mindset and philosophy behind mathematics and not simply just the theorems and proofs.

Here are the 5 books about I most recommend to those who want to understand the mathematical mind and philosophy.

Boyer’s a History of Mathematics

A History of Mathematics,
Carl B. Boyer

This is the textbook from the History of Mathematics course I took almost a decade ago now, and it is still one of the best and most thorough discussions of how mathematics developed over the past millenia. It starts in with Egyptian and pre-classical mathematics, explaining how simple tasks were complicated by a lack of mathematical tools and then how over time different tools were developed that led to quantum leaps in our understanding of the field. It’s quite a tome, with over 700 pages of details, but it is fully accessible to the non-technical reader.

This is well worth having in any library and it can be read in chunks as each chapter covers a different aspect of mathematical history.

Journeys Through Genius

Journeys Through Genius

Journey through Genius
William Dunham

I picked up this book at a secondhand store many years back simply because it caught my attention and was a good price. I thought it would be an enjoyable read, but I never expected to be as amazed and excited by the contents as I started to dig through it. This book takes some of the most important and paradigm-shifting theorems of mathematics and explains them in a clear and accessible fashion. Historical artifacts around the development of the theorems are displayed in a fun and pleasing fashion, keeping the importance of the discovery in context with the time. As well, most importantly, beyond explaining the theorems, the characters behind the work as shown and their lives are taken into context with the immensity of their work. This is a beautiful read and worth picking up if you want to learn more about the biggest theorems in mathematics.

The Mathematical ExperienceThe Mathematical Experience,
Philip J. David, Reuben Hersh

My professor for the history of mathematics course lent me his copy of this book and it was probably one of the most eye-opening reads I’ve ever had. I spent an entire weekend reading it cover-to-cover and then re-reading it again, devouring and absorbing all of the ideas and concepts within it.

Without a doubt, this is the best book I’ve got on my library from the perspective of discussion what it means to be a mathematician and the experience shared by mathematicians worldwide. This book covers the entire gamut, from the philosophical to the social-emotional experience of a mathematician. It is well-written, concise and strikes a real chord with me. In this book I really felt that I was reading someone who got what it meant to love mathematics and get excited by it without delving really deep into difficult to process material. If there is one book on this entire list that I recommend going and purchasing right now, it is this one.

Go, buy it now!

Proofs from the Book

Proofs from the Book

Proofs from the Book,
Martin Aigner, Günter M. Ziegler

Paul Erdös, one of the most prolific mathematicians of the 20th century would commonly refer to a proof that was singularly beautiful as being “from the book.” As in, “from the book of God himself.” This book is a collection of some of the proofs that many mathematicians think to be essential and important, while still be uniquely beautiful in their elegance. If you want a book which is still accessible, but allows for exploration of the theorems themselves in am ore rigourous fashion, this is the book for you. It’s clean and covers some of the best proofs in a very wide variety of fields.

Proofs and Refutations

Proofs and Refutations

Proofs and Refutations,
Imre Lakatos

This books is probably the most advanced of the books on this list. It is however brilliantly written in the form of a discussion between a professor and their students. Lakatos weaves in and out over the process of mathematics, covering how mathematics is really done and evolves as theorems adapt based on a variety of very easy to understand techniques.

If you, or anyone you know, is actually considering to go into mathematics as a profession, I would recommend reading this book. This especially includes teachers as it explains how working through the technique and philosophy can help with overall understanding and creative use of the new tools learned as you move forward. This is a truly wonderful book and can be a very quick read.



2016-02-10 方军 做書







 01 《网络经济的十种策略》

凯文·凯利(Kevin Kelly, KK),广州出版社,2000年





 02 《创业维艰:如何完成比难更难的事》






 03 《麦哲伦传》






 04 《一代新机器的灵魂》





我们创造的多数是网站、APP、商业系统,但是,所经历的过程是一样的。其实这本书和迈克尔·刘易斯记录早期互联网创业的《将世界甩在背后》(The New New Thing)争夺一个清单推荐位,而最终选择了《机器》,因为读它的过程很多感慨,而《世界》并没有。

 05 《黑客与画家:硅谷创业之父Paul Graham文集》

Paul Graham/著,人民邮电出版社,2011年


YC创业营的创办人Paul Graham已经变成一种象征,推荐这本书实际上并非仅仅推荐这本书,因为这本书是完结不变的,而他还在不断地写作长文(essay),讲述他的思考,值得持续关注。

比如他最近有一篇新文章讨论的是“Life is short”,他讨论的这个问题,他的答案隐藏在题目中:“从问题的终极反过来看,去培养一种对你想做的事迫不及待的急躁习惯。”


 06 《精益创业:新创企业的成长思维》




 07 《创业必经的那些事》







 08 《启示录:打造用户喜欢的产品》

Marty Cagan/著,华中科技大学出版社,2011年



 09 《四步创业法》

Steven Blank/著,华中科技大学出版社,2012年


仔细读过《精益创业》的都了解这本名为《The Four Steps to the Epiphany》的书,它是《精益创业》的灵感之源,埃里克·莱斯说他送了很多箱出去。


 10 《大决策:九个不朽的领导力传奇故事》





 11 《丰田汽车案例:精益制造的14项管理原则》


“丰田模式可以扼要地总结为两大支柱:一为“持续改进”(continuous Improvement),二为“尊重员工”(respect for people)。






 12 《跨越鸿沟:颠覆性产品营销圣经》



这就是提出技术产品接纳周期曲线、指出这条曲线里的 “鸿沟”(Chasm )的那个杰弗里·摩尔最早的作品之一。


 13 《创新者的窘境》



这就是时下热门的“颠覆式创新” (disruptive creation,破坏式创新)的原典,最早读夹杂在汉译大众精品文库中这本时,做了非常多笔记,尤其对克里斯坦森对理论和现实的看法感兴趣,在当面向他请教时提了很多问题,但现在已经完全不记得那一个多小时问了什么,只依稀记得讨论linux、google docs等等。


 14 《企业参谋》




 15 《创业之初你不可不知的融资知识》





 16 《错不在我?》
卡罗尔·塔夫里斯、艾略特·阿伦森/著, 中信出版社,2013年

“在有意识撒谎欺骗他人与下意识地自我辩护欺骗自己之间,有一块被不可靠、自利的记忆掌握的灰色地带。记忆通常都会受自我提升偏误(self-enhancing bias)修正和改变,让过去发生的事情变得模糊,减轻责难,扭曲事实的真相。”



 17 《创业无畏:指数级成长路线图》








 18 《九败一胜:美团创始人王兴创业十年》



原来的美团,已经合并大众点评变成新美大(据说英文名为China Internet Plus),但它还在奋战。


 19 《深度生存:生还是死难?》




 20 《卓有成效的管理者》




与之相似的,英特尔的格鲁夫也有一本平淡无奇的书《格鲁夫给经理人的第一课》(high output management),他相对更关注系统的高效率一些,也值得推荐。