3 ms·
I'm taking a break from writing an iPhone app right now. I was on track to bang out this app in 2-3 days. It's a client for the API stack from one of my favorit
by aaronbrethorst 16y ago
I'm taking a break from writing an iPhone app right now. I was on track to bang out this app in 2-3 days. It's a client for the API stack from one of my favorite web services. Things were going great until I hit a serious snag with some poorly documented API calls. Oops.
I guess the answer is 'it depends.' It depends on whether you're doing anything 'new' or if everything that is comprised by the code you're writing is well-known to you.
If I had an occasion to build a client for this web service before, I probably wouldn't be having this problem (not least because I'd have working code sitting somewhere on my hard drive).
I build iPhone and Rails apps for a living. If someone asked me to whip up a simple blog platform in Rails for them (along the lines of the 15 minute blog screencast), it would probably take me 15 or 20 minutes to write it.
In contrast, if someone asked me to whip up a Django app that does the same thing, it would probably take me a day to install Django, figure out how everything works, write a really terrible version, throw it away and then write a more-tolerable version.
- Periodic 16y agoIt all depends on your familiarity. I recently started a job working with a Java + JBoss + Struts application, having written about 1000 lines of Java total in my life. I can easily waste an hours figuring out how to get a local application server running properly or rewriting the build file to suit my needs, and yes I've done both. Think of every time you have to "figure something out" and then think about how much faster your code would be if you already knew the answer. That is what experience gives you.