Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Stephen Whitfield
16,771 PointsBuilding products out of your comfort zone?
I just recently landed a contract deal with a great company based out of Los Angeles and what they're asking of me is a little daunting. I wouldn't say that I can't do it, but I'm not as talented in the language they're wanting me to code it in (Swift) as I am the language I want to code it in myself (Objective-C). Also the time frame they're wanting me to do it in sounds impossible on top of the project being overwhelming itself. I have confidence that I can get this out, but I am admittedly scared to death that I won't get it out in time. Have any of you professionals had to do something you were unfamiliar with in a short time span? If so, how did you deal with it?
Sam Soffes Amit Bijlani Andrew Chalkley Ryan Carson , what about you guys?
3 Answers
Ryan Carson
23,287 PointsHey Stephen
Great question - thanks for asking.
I would recommend a couple things:
- Ask them to pay you hourly - this will protect you against scope creep
- Ask to be paid in installments. 50% up front, 75% after beta 100% after launch
- Remember that all projects are scary
- Try to explain why their timeline isn't possible. It's much better that they have realistic expectations instead of getting super frustrated that you haven't delivered it by their unrealistic deadline
Amit Bijlani
Treehouse Guest TeacherFirstly, congratulations on landing your contract!
As Ryan mentioned that most projects are scary and you have to start somewhere. I remind myself of this quote whenever I face something challenging: "Smooth seas do not make skillful sailors." My recommendation is to make sure you scope out the project before you get started. Scope can ensure that both parties are on the same page when it comes to expectations. As for Swift, remember that nobody out there has 5 years of experience with Swift, so don't sweat it.
Time frame is tricky because most clients want you to deliver a fully featured app yesterday. The trick is set realistic expectations and phase out a project. Weed out the nice-to-have features and put them on the back-burner for another phase.
Finally, make sure you manage your time well so you don't get overwhelmed or burned out.
Stephen Whitfield
16,771 PointsThanks guys. Both great replies that have eased my nerves a bit. Ryan, We have both agreed that I am to be paid hourly. I'm having a meeting with the end-user and my team to discuss everything in detail that they want in the app. After that, I'll work on building a 'roadmap' on how I want to build this thing. From what I know of the project, though, this will be a ridiculously huge learning experience more-so than a project for a client.
Amit, thanks! One of the biggest complaints I've read about developers is that they get burned out too easily. I feel the burnout will come quicker having to do this in Swift than in Objective-C, but like you said, it is new and no one is a 'ninja' at it just yet. I just hope my team understands that too!