Tell HN: I made a freelance translation site in only 5 months
caterpi.com
caterpi.com
* I understand why you want to list A->B and B->A separately, but I'd say it should be the default that someone is able to translate both ways, so favour the common case and let users correct it later.
* Also, If I am fluent in N languages, I must list all the individual pairs, but it seems unlikely someone able to translate english to swedish and english to norwegian wont be able to do swedish to norwegian too. I'd say "list languages you can work with, then review pairs" is a better option.
What is there to guarantee the quality of the translation? I0've seen the stars, but they only make sense after a translator has worked for a long time. * Couldn't translators at least link/list previous works in the language pair? * Could we have some kind of meta-moderation? Say, each translator from lang x/y is randomly given a snippet of someone else's translation and can rate it. * Couldn't we have preventive moderation? Request translation of a tiny text for some non-profit org, say, two sentences of wikipedia, and submit it to other translators for validation (or just check it's not google translate's output)
I've seen abhorrent translations between niche languages (e.g. hungarian & italian) because the customer has no way to tell if the translation is good, and usually does not even have structure in place to _collect feedback about it_.
This means there is not even the chance of going back post facto to take back your money/improve your translation/give bad rating. In practice this translates into a perfect market for lemons
Finally: technical writing is not marketing writing, nor literature, nor drama and especially not legal speak, I believe listing categories in which you are confident is much needed.
But all in all, I wish you the best luck and these are mostly minor nitpicks :)
Your other points I totally agree with. At this point, I'm in the midst of bootstrapping, so it'll be awhile before I can do some form of community moderation. This will of course present some new problems to solve, so much time will have to be spent thinking about the pros and cons :)
Thanks, I appreciate the feedback.
This way you can keep your preferred default of only one direction but allow adding the other more easily.
http://deanza.campuseagle.com/books/
Then again, Django is an awesome web framework, I copied someone else's recaptcha integration, I worked my ass off, and the code is generally full of hacks, such as discarding all but the longest keyword when a user searches.
But I'm not the fastest:
http://r09.railsrumble.com/entries
I could use a forum dedicated to programmer professional development. I'm not interested in TopCoder because I'd rather work on my own projects, but I am interested in discussions of how long other people take to finish things, what the right place to be on the coding speed/code elegance continuum is for various project sizes, how to make fewer stupid mistakes that cost you 5 minutes, etc. It seems possible that some of the supposed 10x productivity differences in developers are due to trainable aptitudes, doesn't it?
There's a few reasons why I think I took so long. Listed, in order of time taken:
1. Going off on many, many tangents before buckling down and focusing on the core product.
2. Design. I'm a poor designer, and it took me about 7 iterations to get to the version you see now.
3. Fixing bugs. There's just so many of them.
4. Learning about, and implementing custom localization on appengine (needed because there are no filesystem writes for .mo/.po files)
5. Working on it part time
Thanks. Actually I did everything but the design :-P
"1. Going off on many, many tangents before buckling down and focusing on the core product."
Yeah, if I had counted those tangents it would have taken me longer too :-) It took me a little over a month starting from scratch, but there were a few weeks of learning before that.
"4. Learning about, and implementing custom localization on appengine (needed because there are no filesystem writes for .mo/.po files)"
Nice. I actually initially built my site for App Engine, but I decided I needed to have control over my IP address (Amazon's Product API, which I will probably integrate with if I continue working on the site, throttles requests by IP address.) So I went with Linode, which gives you your own IP and the option of renting more for $1/month/IP.
I'll bet people would appreciate it if you open-sourced your app engine localization solution, especially if no solutions are currently available.
I'm not sure if the language dropdown is supposed to work. It doesn't work for me on the iPhone. You shouldn't care about this at all, just a note.
The design polish is a huge plus. It looks nice all around, something I don't often see with projects like this. I think it could use a touch of UI polish, but it honestly doesn't matter at this phase.
Product: Seems OK. Your core issue is solving the chicken/egg problem. You need to convince freelancers to join without jobs and you need to convince people with jobs to join without translators. In that light, features like forums seem like massive scope creep. Forums don't get you any closer to getting traction. That should be your sole goal at this point.
Marketing: The value prop isn't super clear to me. You're not effectively answering the question "Why do I need this?" and "Why do I need you, over the other guy?"
Overall decent job. Keep up the hard work.
Thanks for the feedback
a. “Orders” and “Jobs” both lead to only a sign-in form. I would expect some short information and more explicit motivation for signing up there. Does it make sense for the “Orders” item to even show up in the menu for unregistered users?
b. I would expect the Gravatar hash images to be rather confusing for people who do not know what Gravatar is.
About the Orders and Jobs links.. I've been annoyed in the past with the UI completely changing for some sites after logging in (especially the main navigation buttons).
I'll have to think of something to put there :)
As of now, it looks clean, usable and has potential. Grats.
It's a small thing, but on the language selection menu it'd be nice if I could skip to a language by typing.
From the FAQ A: Your text is sent to a pool of translators, one of which [/whom] may choose to accept the job.
As a programmer, I never realized how much work is involved in marketing!
Check out this German start-up: http://www.tolingo.com They have a bit of a head start but never mind. Crucial about their service is that 2 people work independently on each piece of customer copy.
How customers end up with one correct copy in the end, I have no idea, but this is part of their pitch and this is what customers are concerned about.
Also, your About page is an FAQ, but you need an 'About Us' page.
Great start -- not sure what about this took you 5 months -- now it's about execution and continuous improvements ;)
A wants Engish (E1) to French B translates Engish (E1) to French (F1) website facilitates C translating French (F1) to English (E2) without seeing the original English copy (E1).
It would essentially double the cost though .. hrm. Or maybe part of (F1) would be translated back into English (E2) for validation. Hopefully is a couple sentences are accurate the whole thing is?
I agree with other posters that the Buyer is at the mercy of the Translator. Its like those people with Chinese tattoos that they thing mean "Love & Peace" but they really mean "Supermarket"
You might look at these similar sites for ideas:
https://www.onehourtranslation.com/ (they also offer an interesting free tweet translation service)
http://trans-aid.jp/ (seems to be all volunteer, Japanese-oriented)
Customers also have the option to request changes / corrections, and even to reject if they are not fully satisfied.
Anyways, just an alternative solution. The online-translation market gets interesting by the day :)
I would suggest that freelance translators are asked to enter their profile information in all languages they translate to and from. Depending on initial language a site user has chosen, profile information can be updated to that language. That way a customer who speaks only one of the languages can understand too.
For example, technical and scientific translations usually fetch much higher prices. Thus, translators with technical expertise are unlikely to use your site and compete with the lower priced general purpose translators, unless their special skills can be easily differentiated.
then, a good things: 1. Website is pretty clean, I like that.
If I need any translation services, your site is bookmarked.
i would love to see a feature (eventually) that allows you to easily hire a "team" of translators to either collaborate on a translation or translate them individually in parallel (you would have to work out the granularity here) and rate each other's work. I'd love to have more than one opinion for critical / tricky pieces.
Good spam filters killed it (gmail and co).
URL is solid.
I know it's early on, but I'd like to see some examples or sample translations somewhere. And when you can get some press and testimonials it will make the site feel more trusted.
I'd also consider adding some type of image(s) on the homepage. It's missing a human element and at the end of the day it will be someone translating this stuff so I'd recommend adding translator user photos on the frontpage.