“8条保证软件创业成功的提示”的文章在Digg引起了很多的批评，看来群众的眼睛是雪亮的。这篇文章应该将标题改为“8种让软件创业失败的提示”，呵呵。摘录几条如下，权作娱乐。
- Hmm… So that’s why all 200 of my start-up companies failed…. you’re actually supposed to WRITE the code first…. drag…
- great, great post. Although I think code for code’s sake does not a business make!
- I’ve also heard the argument “outsource all the boring parts” instead of growing, because you make the same as a larger company, only you just do the cool stuff.
At least that’s what I heard from a local company which is apparently well off, and small. - i enjoyed the list starting out at 0… made me giggle a little bit, silly computers
- it’s a balance for a start up to work. There are too many start up cases with A+ engineers, but failed because their biz team were just clueless
- My Tip: If you need to read a digg article on startup tips, you’re not ready for a startup.
- I wish all of what he said was true, but I have a problem with the whole intro to the article. The fact is, lots of successful startups have started with what I would consider “bad code”. In order to get the thing out the door, they don’t think about the future. Instead, management will believe that they have time to fix the code after they are successful. That never happens.
- Reply 7：I agree. The manager can take a lot of load off the team and have short meetings every couple of days with individuals on the team, catching up with the status, monitoring the bug reports and liaising with QA and Management so the coders on the team can just code and never have to sit in a meeting unless they absolutely have to be there. Think of it as the manager being there for the team, instead of the team being there for the manager.
- WHy start with good code, just start with functional code and charge more money for each version upgrade thats what major companies have been doing.
- Completely disagree with point 4. Don’t ask questions about code, look at their code yourself. Take for example myself–I have been programming for ten years, four years professionally, with no formal education in the area and although I do not know what some algorithms are called I can still write more efficient code faster than the software engineering graduates I have worked with over the years.
- It’s a laundry list of how to make a startup fail.
Lousy article.
“0 – Must have code.” Um, what? Isn’t that what the business is for? Isn’t this a bit of a chicken-and-egg problem? Or is he saying, “you must have code in order to get funding,” which quite a different situation.
“5 – Avoid hiring managers.” I’ve been at a startup. The only thing that kept us working together (since we were all ‘passionately’ working in our own area) was our excellent, excellent manager. How about just, “don’t hire douchebags who waste time”? Also, “the best startup engineers are people who are young and hungry to write code.” WTF? Without wisdom, you will be implementing awful, hamstringing practices and probably writing shite code.
The best engineers are a little lazy and highly experienced. Why? Because we see the value of coding for the future as well as the present.