Totally agree, super annoying. I will highlight and re-highlight a paragraph over and over as I read through it. I'm not sure why I do it, maybe it's my impulse to go faster that I can satisfy by moving my cursor rather than reading more rapidly.
164 karma · joined September 15, 2011
Thanks for calling it out early.
Thanks for finding that, fix being deployed right now!
Thanks for the heads up!
Sorry about that! We've removed the misleading parts to avoid any further confusion. Thanks!
I think she thinks it's hers... =)
Well finding technically skilled people who are available and willing to work on your project isn't exactly easy. He may have embraced that a little sooner than other entrepreneurs and decided to go for something juicy enough that he could make headway.
What's the main difference between you and dribbble? They let you people message designers about projects too, no?
Good luck!
I'd say the two biggest challenges for hackers who want to take projects is lead-generation and sales. They sound simple, but they aren't and you'll waste a lot of time talking to a lot of tire-kickers.
For lead-gen, that just means finding work. Where do you start? There's a few ways to go, you can network with friends, college alumni, startup circles. You could contact incubator companies and ask if they need any extra help, etc. I have to mention GroupTalent too because this is one of the biggest problems we solve.
When it comes to sales, you don't land projects just because you've got "software developer" in your job title. It still comes down to convincing them that you're not going to botch the project, and that's based on what you've done before. They want to see examples of your work, including anything at hackathons (those are good examples of how quickly you can crank out prototypes). The closer it is to what they've done the better because buyers don't buy you, they buy the thing you'd be building them. It's easier to visualize success with you if they see something close.
On the question of whether to work by yourself or as a team, I'd say go as a team. I've seen first hand that not only will you be happier working with a friend, but the idea of getting a package is a big perk for clients. Speed is often a big deal for them, and 2 is faster than one.
Also, clients gravitate towards hackers who can build web apps, not as much static sites. Anybody can code up css/html, but can you build functioning prototypes? Push that as your core skill-set and you'll have a better chance at finding gigs.
Most developers and designers hate spending half their time shmoozing, networking, meeting and dealing with people who just want to meet for the free advice. It just sort of comes with the territory. In the end, success will come from getting access to the right clients, and traditionally that has meant knowing the right people. This is one of the reasons we're building what we are.
Lastly, don't take projects you aren't interested in. When you're building your own product, and working on the side, it needs to be interesting enough that you can power through the finish and earn the paycheck regardless of what's happening with your company.
Oh – and one more thing, payment can be a huge hassle. Make sure to establish payment terms before starting or you might get burned. I know folks who just don't get paid. We make project owners pay up front for teams, we hold it in escrow, and pay out on a per sprint basis. If you want to do something similar on your own without an escrow-like service, you might do half up front before a sprint starts, and then half after each sprint. But seriously, break it down into sprints that deliver functionality costing no more than $5k. More sprints at lower cost is better, it's easier to get them to pay for $3k + $4k +$5k know what I mean? It's progressive cost increase for progressive emotional commitment. Otherwise things have a tendency to go unchecked, and then people change their minds, and it's wasted work, and oh should we pay for that or not, etc etc.
If you have any questions, tweet me @superkinz
It's about forcing people to get off their lazy butts and make a phone call. And as much as we complain, I bet 99% of people here haven't made that call yet.
It can kill morale depending on how it's treated, and how the company culture rewards. Just because you choose to meet a goal as a team that requires more than average number of hours put in for 4 weeks does not mean everybody is being dragged along. What does upset the folks doing the heavy lifting is when requirements get added at the last minute with "oh, can we please please just have this one more thing? It would be so awesome" from upper management. That's pure bullshit, and tends to rip apart morale above anything else.
I'm not saying it can't work, but it does get hairy with "social debt" and how different people interpret that. "My time as a developer is worth $150 an hour, and yours is worth $75 an hour, so the time I put in is worth twice yours." I heard one dev tell a designer that once.
I graduated 6 years ago back when they hardly taught any web/UI work. I started out in print and at first loved it, but quickly grew to hate it. I learned enough about myself that it was clear that it was time to move on. Then I finally accidentally landed a job at a startup and found what I really loved - UX/UI. Then did that really well, and now I'm on to product design and business.
Long story short, you're pretty likely to have an evolving set of interests and that will allow you to get really good at a number of facets. You should still be doing 60 hours a week or more if you want to be making big leaps forward. Once you get burnt out on working your ass off doing that one thing, you'll find something else really interesting and inspiring. Then go chase that.
There are always new things to learn, so make sure you've got supporting network to chat about your challenges with so that you know you're not alone. A lot of times, there are little things you can do to keep your zeal for life even though what you're hammering on may not be as interesting as it used to be. But when it becomes downright depressing to go to work every day for 1-2 weeks, you better quit.
So you know what we did? We all spent 3-4 days a week on contracting gigs, and the other 3-4 days a week working on our product together. Aside from the fact that we really didn't see eachother for half the week (which sucked because communication broke down), the contracting worked great. I set up expectations with my client and did some amazing work for them, and in the same week we made great progress on product.
Is it ideal? No. But does it keep the lights on and the health insurance paid and food on the counter? Yes. Assuming that everybody who decides to start a company has $50k saved up in their account is ludicrous.
And you know what? If we could have worked on the same project when we were bootstrapping rather than different ones, our communication and camaraderie would have been a lot better.
I completely agree that if you have a good deal of runway through savings or venture capital, staying heads down and avoiding distractions is the right move. But Christeso, that's not what this product is for. It's for all the other guys who need to hustle and scrape together enough money to keep going.