Hi garrettdimon, sine there are so many bug & issue tracking websites, why do you choose it to startup your business? Thanks!
9 karma · joined September 27, 2010
http://imwilsonxu.com
btw, you don't wanna miss repeat.vim if you stick with surround.
Since I've been working in an angel investment company in China, after dealing with a lot of startupers, I found most of them haven't realized how big huge potential promption value video.
I see the idea: 1) Write htmls (with some rules, e.g. add '.actionable' class) 2) Library turn them to js codes.
Benefits: 1) Write zero js codes. 2) Make basic and repetitive functionalities eaiser.
But, just wondering, why don't you wrap codes which deal with basic and repetitive functionalities into js functions then reuse them, but write a library to turn htmls codes to js codes?
My question is, html has its job and js has its, too. Is it a good idea to mix them?
meta-feature is like a magic, which is behind the scene and plays a big role.
On the other hand, reading facebook status or tweets is like listening or chatting with friends. Contents are impromptu and often out of context. However, it's much easier to interact.
- Logo. A logo should be simple and friendly to print. Your logo (cat in box) looks more like an picture than a logo.
- Text. - Tell people more on "easy and simple to send files". - Cut half of texts (from book "Don't make me think")
- Input box and button. - They look too identified by appearance (texts in a gray border). Don't "Violating Design Conventions" (http://www.useit.com/alertbox/9605.html #8). Make a input box looks like an input box and a button like a button.
- Expression. - I clicked "Get in touch, we'd love to talk" because I want to know what exactly "easy and simple to send files" is. However, it turned out to an email link. So why not just write "Email us"?
Hope it helps.
I have to zoom in to 144% (in Chrome) to make it readable.
yahoo google facebook ...
Pattern? "dboule o"! :)
- For ownership, fairness, and the perception of fairness, is the most important because arguments are very likely to kill the company. 50-50 is simple and acceptable.
- For stakes, divide people into layers by risks they take. Taking the biggest risks, founders the first layer should end up with 50% of the company, total. Each of the next layers take 10% respectively, split equally among everyone in the layer.
- Do use vesting to prevent some jerk that quit after two weeks and still think he owns 25% of the company for his two weeks’ work.
My thoughts.
- For founders, ownership can never be calculated accurately. We’re human beings, we can come up with excuses as many as possible to claim our benefits. That’s why 50-50 works in most cases.
- 50-50 is a perception of fairness, is a symbol of “Hey guys, we are equal to each other, we are working for our company, not any of us!”, no matter who brings up the idea, who has more experiences, etc.
- Ownership is a process, not a decision. What determine your cake is risks you took, value you created, how long and hard you got involved, etc. Instead of a meeting, a discussion, or even an email.
A step-by-step example helps alot.
two things after playing around: 1. it's a little inconvenient to hover on the pics to checkout the price every time. 2. where's the navigation, sth like 'next page'?
However, if you are looking for something more pragmatic, Steve's Don't Make me Think and JJG's The Elements of User Experience should be the top of your reading list, especially on web design.
Diff from big-fat-cat company, startup has a big advantage that it's going to grow and employees can really feel it.
This is a good chance to cultivate ownership, loyalty, sense of belonging, etc.
Good luck :)
However, I think there are too much text on almost every page, dizzy...
I remember Steve mentioned something like "cut off half text and do it again" in his book "Don't Make Me Think". Maybe you wanna try it out.
Cool stuff!