101 karma · joined March 12, 2008
Regardless of how you feel about PHP, I've spent enough time with it that I can make it work and write good code, quickly.
I do want to switch to another language at some point (I'll leave the reasoning for that out of this discussion).
Why switch to Python 2.7 if it's going to be old in a year or two? Even if there isn't a huge difference between 2.7 and 3.x it sounds like it would be a nightmare trying to upgrade any of the old work that I would have done in 2.7. So either I've got some projects that will be on 2.7 forever, or I go through the hassle of trying to upgrade. I'd rather just wait and avoid the whole debacle.
.btn {color: red;}
This way your toolbox is much lighter and easier to carry around (easier to keep up to date with improvements to the code and easier to maintain). I think it's about breaking things into smaller pieces.
Here's our pitch for foodwithafriend.com:
It can be hard to keep up with friends from all of your different social circles.
Wouldn't it be great to be able to catch up with a different friend each week over some delicious food? Food with a Friend will automatically match you up with one of your friends each week for a tasty meal at a local establishment.
You tell us what days you're generally free and we'll match you up. Then all you have to do is pick a restaurant!
If we can get 100 people to sign up, we'll build it. Otherwise we might choose a different idea.
What do you think?
That being said, there are a number of great start-ups coming out of University of Wisconsin, supported by a really exciting entrepreneurship community here. There was a TechCrunch article a while back about Wisconsin start-ups and Capital Entrepreneurs, a group that really supports the start-up community here in Madison (http://techcrunch.com/2010/07/24/wisconsin-land-of-beer-chee...).
Start ups from public institutions are out there! 94 labs, a Wisconsin incubator program that I went through just graduated 14 companies, many of which had founders from UW schools.
We wanted to share our work with HN. The algorithm is pretty simple now. It looks at the list of tags for the products that you like, and searches for products with similar tags. It's not perfect but works pretty well givent its simplicity.
We would love to get HN's feedback on the design, possible improvements for the algorithm (or any good reading I could do on the subject), and thoughts for monitization. We never really intended for the project to make any money, so we're pretty happy just making something that's useful. Corey is trying to get a job at etsy, so he figured this would be a good project to help out with that. But if you have any good ideas for how to monitize that would be an added bonus!
So to answer your question, user experience is more about the process of how to build good features.
One suggestion: After submitting a url for one recipe I get a list of ingredients, great! It would be cool if the text box at the top of that page would allow me to add another url to append the ingredients from another recipe to the list.
As far as the TOS go, I'm a little too poor right now to hire a lawyer but the university near me has a great program where law students (supervised by a lawyer) offer free services to entrepreneurs. I'm signed up for that program but it doesn't start until June.
Any suggestions for how to fill that privacy policy and tos in the mean time?
I posted an idea on there a while back and got several responses from interested developers and designers.
In the end I decided that I wanted to work with someone who I could meet face to face and who I had a previous relationship with. I think it's hard to set this type of thing up through a website.
Our HTML markup is so ugly :(