数据结构

若能回到五年前,我会告诉自己这些创业道理

编者按:Ben Dixon,一名Ruby/Android开发者,开发运营极客。他是Reliably Deploying Rails Applications的创始人,并创建了makeitwithcode.com,一个教导非开发者通过代码创建有用事物的网站。日前,他做了一件有趣 的事儿:
如果可以回到五年前,我会告诉刚开始创业的自己什么道理?
Ben Dixon总结了这些,我们进行了节选,排名不分先后:
  1. 关于创业的想法总有人与你相同,这不是坏事
  2. 如果别人要求你必须在签保密协议后才能听取他们的想法,请拒绝
  3. 线性增长有时比没增长更糟糕
  4. 谈论失败的人大多并未亲身经历过
  5. 每个人都有隐藏的实力
  6. “这是行不通的,因为什么什么”这类思想,很容易让人作出过度评判和应对,应该避免这种情况
  7. 对于上一条情况的新人,要避免与其交谈,应请专职人员来引导
  8. 听别人讲述一个你已经失败了无数次的想法,很痛苦,你更应该做的是找出其中轻微的不同或你令你感兴趣的地方
  9. 成为技术主干并不意味着他知道如何去掌控事情
  10. 编程语言/框架的争斗是非常有趣的,但是在现实生活中的价值是有限的
  11. 优秀开发者可以在几周内学会任何一个语言或平台
  12. 我仍然不懂真正的投资者是什么
  13. 夸大你将要做的东西会很累
  14. “溺爱”一件产品(相比问题而言)是很危险的
  15. 如果不知道一个哈希表是如何工作的,请点击右上角的X(关闭按钮),当你最终学会时,你会发现它是令人满意的
  16. 对Big O符号也是一样
  17. 一夜成名不是事,社交网络依旧演绎着这样的故事
  18. 我依旧不明白PR
  19. 大多数技术解决方法相比如何让产品进入人们手中来说是微不足道的
  20. 相比创造你想要的东西,创造一些人们想要的东西可能更有意思
  21. 你想要的并不意味着人们想要,因为你的产品是一个业务
  22. 如果没有先亲身体验一个行业,你可能会错误理解工作方式、遇到的问题、解决之道等,请多与人交流
  23. “Ads”是商业模式的坟墓
  24. “我们将数据货币化”是新的“Ads”
  25. 你最终想要一起工作(和帮助)的人应该是那些总是试图帮助你的人,请珍惜他们。
  26. 要擅长问事情,大多人会无缘由地将你的问题打折扣,有选择性地回答你。
  27. 学会说不
  28. 在好的商业理念及好产品中找到一个平衡点,不要是太偏执于一方
  29. 写作(博客、书、日志)是一个好习惯
  30. 不要太在意你所写文章下面的评论,总有人不喜欢
  31. 大多数创业公司的建议是可怕的。每个人都会有不同的建议,所以相信自己的直觉
  32. 由于现实原因,没人使用比特币ATM
  33. 创业者会面临先开发或融资,如果不能兼得,选择前者
  34. 很多问题的解决之道并不全是技术做得到的
  35. 将你的想法告诉尽可能多的人
  36. 与别人能成为朋友并不表示就能与其融洽工作
  37. 小的团队可以快速的转移到VERY,所以慎重加入额外的人,敏捷性很重要
  38. 多任务不是单一的事情,转换成本是巨大的,所以一次只做好一件事情
  39. 推荐读Paul Graham所写的文章
  40. 在科技新闻(综述类的)上的时间投资,回报率是很低的,请选择书籍和交谈
  41. 推荐阅读Founders Stories、Fooled By Randomness和The Four Steps to the Ephiphany
  42. logo在开始时并不是那么重要,找一个简单的、可重复用于不同项目的logo即可
  43. 如果有机会,多参与到开源中并随便写一些项目,你会遇到同样兴趣的人
  44. 常常每天工作十二个小时并不是一个好事
  45. 与所有人交谈
  46. ……
来自HN的评论:映入眼帘的评论是关于第11点“一个好的开发者可以在几周内学会任何一个语言或平台”,这句话说的对也不对,原文使用了“picking up”一词,与实际上的擅长还是有区别的,Norvig有篇著名的文章“用十年时间自学编程”,其中说过这么一段话:
在24小时内你可以了解一些C++的语法(前提是你已经了解另一种语言),但是你无法在这么短的时间里学会很多关于语言使用的知识。简而言之, 如果你是一个Basic程序员,你可以使用C++语法编以Basic风格编写程序,但是你不知道C++实际上是好是坏,这有什么意义呢?Alan Perlis曾说过:“一个不能影响你思考编程方式的语言是不值得去知道的”。
英文原文点此查看。 对于创业过程中的点点滴滴,有相同有不同,你会有怎样的体会呢?欢迎留下评论。

What I'd tell myself about startups if I could go back 5 years.

This is, in no particular order, what I'd tell myself about startups if I could go back in time to when I first got involved. Which is probably the same as what I've learned. This is most definitely not advice, the "you" here is directed at me. So is "I". Grammar is hard.

  1. You're definitely going to end up building too much and shipping too late. Be obsessive about avoiding this

  2. Someone's always already working on the same idea and that's not a bad thing

  3. Always refuse if someone asks you to sign an NDA before hearing their idea

  4. Like it or not, most networking in London is focused around drinking. Find a way to deal with that without having a constant hangover

  5. The people who are really getting somewhere aren't the people who are always out for drinks

  6. Linear growth can be worse than no growth

  7. Most people who talk about failing fast, aren't actually practicing this

  8. It's really easy to kid yourself that you're "doing customer development" when actually you're finding ways to make what your customers are saying fit with what you want to build

  9. Everyone has a hidden stash of domains they've never used

  10. It's really easy to become hyper-critical and respond to every idea with "yeah but that won't work because of x". This is lazy, don't do it.

  11. Be especially careful to avoid the above when talking to people who are new to the scene. Call out other people who do it

  12. It's really hard to listen to someone pitching an idea you've seen fail several times already and focus on working out if there's something slightly different and interesting there

  13. Someone being a technically competent developer does not mean they know how to ship things. I'd always rather work with someone who ships over someone who's technically brilliant

  14. The programming language/ framework wars are great fun in the pub, but of limited value in real life

  15. A good developer can pick up any language or platform in a few weeks

  16. I still don't know any real investors

  17. Constantly exaggerating how well you're doing can be very tiring. It makes it harder to publicly celebrate the real victories

  18. It's really hard to build a product if you don't have a big personal investment in the problem it solves

  19. Falling in love with a product (rather than the problem) is really dangerous

  20. You can get away without knowing how a hash table works, but it's really satisfying when you eventually learn it

  21. Same goes for Big O notation

  22. Overnight success isn't a thing. The Social Network is still a great movie

  23. I still don't understand PR

  24. Most technical solutions are trivial compared to how you get the product into peoples hands

  25. Make something people want is probably a less useful heuristic than make something you want

  26. But you wanting it doesn't mean enough people want it for it to be a business

  27. If you don't have first hand experience of an industry, you're probably wrong about how it works, what problems they have and so how they should be solved. Talk to people

  28. "Ads" are where business models go to die

  29. "We'll monetize the data" is the new "Ads"

  30. The people you end up wanting to work with (and help) are the ones who always try and work out how they can help you. Be more like them

  31. But get really good at asking for things. Most people will give you a discount for no reason other than you asked. If you see someone important and influential, introduce yourself

  32. Get good at saying no to things, from people asking you for discounts to interesting projects you really don't have enough time for

  33. Think hard about a pivot which makes good business sense but leads to a product you no longer care about

  34. Writing (blogging, books, journaling) is a really positive experience

  35. Don't pay too much attention to internet comments about something you've written, there's always someone who didn't like one particular sentence (see point about trolls below)

  36. One troll can wipe out a hundred positive interactions, be ruthless in keeping them out of your communities

  37. If you end up pitching to someone over coffee, ask to hear their pitch afterwards

  38. Only say you're going to introduce someone or send them something if you're actually going to do it. People quickly get a reputation for never following through

  39. Show don't tell. "I'm going to build this amazing thing" is a LOT less interesting than "I've built this slightly crappy thing that actually does something". EVERYONE is GOING to build something, most people never do

  40. Building things is awesome, don't get too caught up with the whole "Lean Startup Landing Page" mindset

  41. Lean Startup is awesome, but it's a pamphlet not a book, read the first few chapters and you'll get the idea. Four steps to the epiphany is more technical and probably a better book

  42. Most startup advice is terrible and the good advice is usually obvious. Everyone will give different advice, trust your gut

  43. Except when it comes to what your customers want, then ignore your gut and trust them

  44. No-one has ever used a Bitcoin ATM for practical reasons

  45. Do back of napkin financial forecasts for every potential business model you come up with, just to see if it's in the right ballpark to a couple of orders of magnitude

  46. It's really easy to automatically dismiss everyone who starts a conversation with "I'm looking for a technical co-founder". Doing this means you miss talking to some interesting people. But be upfront that you're not that co-founder so no-one feels like their time is wasted

  47. Trying to raise money and apply to accelerators is a full time job. You're probably either building or fund raising. Not both. If in doubt, choose building

  48. The solution to many, many problems, is not technical. That won't stop people trying solve them with apps

  49. Facebook is the Facebook for X

  50. The idea you laughed at when you saw them pitch at a hackathon may well be the one that's still alive and kicking long after whatever you pitched fails

  51. If there are people who genuinely like failing, I've never met them

  52. That was not "your idea" unless you shipped something, otherwise I invented Facebook, Nest and Oculus Rift

  53. People don't steal ideas. Tell as many people as possible. Never ask someone to sign an NDA before hearing your idea, you'll instantly lose all credibility

  54. Being friends with somebody is not the same as being able to work well with them

  55. Small teams can move VERY fast, be really careful getting extra people involved in any project where agility is important

  56. Multi-tasking isn't a thing, switching costs are huge, do one thing at a time and do it really well. Find a way to block out interruptions

  57. Read every essay Paul Graham has written

  58. Tech news (and news in general) has a very low return on time invested. Prefer books and conversations

  59. Read Founders Stories, Fooled By Randomness and The Four Steps to the Ephiphany

  60. The logo doesn't matter at the start, find a simple text based logo you can re-use for different projects

  61. If you possibly can, open source and write up any side project. Every now and then you'll meet somebody really interesting as a result

  62. Regularly working 12 hour days is probably never a good idea. If this is happening a lot, find a way to optimise

  63. Talk to everybody

Ben Dixon. Without
      Aviators.

Ben Dixon

I'm a CTO, developer (Elixir, Ruby, Typescript), lover of good coffee and above all, making things. Huge devops & LLM geek, especially Kubernetes and anything to do with realtime use of massive datasets. Railsconf speaker and travel addict. Co-founder of Sona and author of Reliably Deploying Rails Applications. Chat to me on twitter @talkingquickly