624 karma · joined February 17, 2008
http://startup-marketing.com/steve-blanks-sll-keynote-its-a-...
General tips:
------------
- Make sure there's enough food & drink. It's very hard to think and keep working when you're thirsty or hungry.
- Second monitors for everybody involved are a must.
- Definitely still use version control. I've seen some people avoid this for the sake of speed but the ability to try things out and quickly recover is vital in a chaotic coding environment of a hackathon. Take the time to set it up.
- Don't keep things in your head for too long. It's faster to express yourself and communicate on paper. Bring LOTS of scratch paper and pencils.
- Take breaks unless you're in the zone. Get up, stretch out, walk around, get food, talk with others. It'll help re-energize your thinking.
- Don't sleep. All my hackathons were less than 24 hours and I didn't sleep. I got a good night's rest the night before I started and I stayed away from naps because it's very hard to wake up once you fall asleep.
- TDD is optional. If it's part of how you already code all your projects, keep at it. If you're not in the church of testing, don't bother. It will only slow you down. A hackathon is not about coverage or whether your code is well-tested, it's about whether you have code that works at all.
Splitting time:
--------------
- Never hesitate to stop and brainstorm, just don't let a session go on for more than 30 minutes.
- Leave visual design for last. My goal has always been to build something functional, not necessarily pretty or usable. I can also crank out CSS pretty quickly so I'm comfortable leaving most or all of the visual design for the very end.
- It's worth sketch out the flows early on. It will help guide and structure your code and other ideas. Just don't obsess over a great user experience in the beginning.
- Spend the vast majority of your time coding. Iterate like you've never iterated before. Hack, hack, hack, and only refactor if the latency is really bothering you. Get to something that works first and foremost, then worry about code quality, performance, readability, and all the things you're supposed to when you have more time.
Learning about your customers should be top priority. I would definitely follow up with those 25% via a very friendly email, as mentioned in previous comments. Don't be surprised or upset if very few of those 25% reply to your email (would you - for a service you abandoned?). Good luck learning!
Don't you feel like you miss out interesting and relevant tweets with that kind of random access? Imagine if the proposed filters were in place. They would give you the best and most relevant of everything. Isn't that better than random access?
Would love your thoughts here or over email: arthur@slipstre.am
My approach changes dramatically when I'm working for somebody else because it's hard to find something to care about on the same level as your passion projects.
So the key seems to be passion. Have a lot of it? "Work" more because it's not really work. Have a little? Mind your hours and your rate.
So is this just a pickier StackExchange?
How do they plan to offer objective answers (or is this just restating what StackOverflow does today)?
I wonder what Caterina Fake would say about Joel's list (http://www.caterina.net/archive/001234.html), assuming the hackers he's speaking to are also entrepreneurs?
"Every time I drive by Sand Hill Road, I see clumps of “fresh fish”, shuffling from pitch to pitch, who equate raising VC with having a successful company. Look, this is hard; if you’re really building something of value, it’s going to be hard, and you have to be prepared to endure a lot. The finish line is liquidity for your shareholders, investors, and employees, not a VC raise."
{ "error": { "type": "Exception", "message": "You can only access the \"outbox\" connection for the current user: " } }
Does that mean I have to be logged in to get at that data?