Really push the boundary of the design to stand out from the rest.
Also don't take this as all web 2.0 sites are similar, or you can't pull inspiration from them. Just something refreshing to break the mold of mundane would be nice.
13 karma · joined February 28, 2012
Really push the boundary of the design to stand out from the rest.
Also don't take this as all web 2.0 sites are similar, or you can't pull inspiration from them. Just something refreshing to break the mold of mundane would be nice.
Make sure to read my post thoroughly, even I know what the OP is asking is impossible without a basic understanding of what to measure by. I'm just giving them ideas of what to research themselves to help apply some ideas for their "quality" measure.
Also if you can't code a problem without requiring redundancies in your logic, then you might be looking at the problem wrong. This is not absolute, but there are better ways at problem solving in most cases.
edit: grammar
1) Are they commenting their code?
2) Formatting structure of code
3) Are there redundancies in logic, that over complicate a simple idea.
4) Are they using "common" best practices while developing the code?
5) How long is it taking them to create/implement base elements like functions, classes, variables, etc.
These are just some ideas to look at. A lot of programmers are really great at what they do, but lack organization of what they build. Some programmers are great at organization, but over complicate simple ideas. It's variable based on what your "expecting" with the end product.
Do you want, just get it done, and it works code?
Do you want clean, efficient, and best practices code?
Also the design seems flexible enough to support percentages, so "a" won't be much of an issue.
1. Did you have positive sales/user traction? 2. Is your product B2B? 3. Do you feel there are a number of products like yours already in the market that isn't big? 4. Was there a true need to involve investors that you couldn't make up in sales?
In my honest opinion, I think you gave away too much equity. 45% is a lot for only 100K, and with ideals for growth in mind as well. That means you increase your revenue exponentially to offset the need for additional funding in the future, or hope for the next round of investing that investors only want a small chunk. Slightly doubtful once they look at how much you initially gave up.
The issue isn't really "too much" text, but the way your conveying that text is boring and mundane.
If your going to give "bulletin point synopsis" of information. Make it enticing to read, or simplify your approach all together.
Great design is always impacting, and straight to the point. Your a website you have a limited window of capturing one's attention.
The part with the pause mechanic is interesting. I'm interested to know what tool that is as well.
The main issue is licensing, and showing the "old guard" the new ways to capitalize on the market instead of relying on the current traditions.
Also wanted to add the "current traditions" are similar to the music and movie industry. More so in the vein of music, with the evolution of how fans can acquire anime. So they see no real need to pay for something that comes out months to a year later.
Then your course of action would be to find statistical data on auto parts that have a high volume of demand, and begin there.
edit: grammar
So pick one you feel slightly stronger about than the others, and then mention the others in the application.
The idea pg is implementing is for people with "zero" idea of what they want to do.
What are exactly the merits to determine "good" untested founders?
My other question is, which has been eating at me slightly is the trend of the startups I have seen come from Y Combinator being "extremely" similar to each other. Of course there is going to be overlap, but even the backgrounds of founders are largely similar creating this trend of "hive" mind ideologies for startups. Is this intentional?
Overall, I'm curious to see how it will turn out either way.
With that said, IMO would start her off with logic and OOP. That's if she really wants to code.
If it's just a simple understanding of how the web works, the posters comments about HTML would suffice as a starting point.