25 karma · joined February 3, 2014
When I first had a look I got quite pessimistic about my chances of finding work and money through it but decided nonetheless to give it a fair go.
I passed a few tests that gave me an initial edge as a newcomer, and decided to follow most freelancing advice I found on the internet: don't down-value yourself with a bad hourly rate, and apply to jobs professionally. It took me a few weeks to get a first contract, and after a month or so I was working 60h per week. I also read "The Freelance Pricing Guidebook" by Glenn Stovall which is a simple pdf of a dozen of pages which really gave me a good think of how to approach being independent and potential pricing strategies.
I also try to get out of the platform once I built the relationship with the client but it is not without risk if they run out of money, you don't have that nice guarantee that the platform offers. It happened to me that a client owed me 5 digits amounts and I regretted for a while having gone directly to him (he ended up paying, he had just ran out of cash).
If you find an USA client and you are not in the USA, with the strong USD it can be really advantageous for both parties. If you are in the USA I'd still say you can do well (I think Australia is more expensive than USA).
Maybe I really got lucky, or necessity forced me to succeed since my girlfriend got sent to a rural area with no work for me. Now days my work is so much more interesting, better paid and I met some amazing people thanks to that platform.
Also I'd like to add that some of the companies that I work for have found some great talent through the platform.
Also I find that some of these 3d party apps use a notation like >= Django 1.X but that's not really true because of backwards incompatibility. A clearer way to know what exact version Django apps are compatible with would already be really helpful.
Good luck!
What I like the most personally is how easy it is to install and experiment with 3d party tools. You want an elastic search stack? In one command you have a webserver hosting Kibana with Elastic Search and Logstash properly configured on your local. Jenkins, Elastic Search, Redis, Postgres, etc: they all have their dockerfiles and can be installed as one liners. Removing them is equally as easy.
Oh and I don't know why it is written that running a Docker registry is "extremely complex". Just like any Dockerized app it is a one-liner.
This new ease-of-install just by itself is worth of my gratitude to the guys that build it.
I don't understand why clicking on a selected criteria on the 'Create Your Perfect Programming Test' doesn't deselect it. It made my first interaction weird since Javascript is always selected.
The close button made me close the tab a few times. I was expecting a back behaviour. Not that it matters since I see your site opens its own links in a new tab which is also something I do not like.
One thing I would emphasise in the first paragraph is that you need at least other provisioning/configuration tools to set up the servers where the docker containers will be deployed to. I know it would obvious to most, but you would still need to start/stop these machines with correct docker install, firewalls rules, and probably more. The VM layer has been flushed out, but still exists and needs attention.
After spending more than a week looking into Docker, my one frustration with Docker is that I have not found a way to correctly develop with it. Most of the docs I see are about deploying established apps, but I would love to see tutorials about how to develop, and start from scratch with it. Does Docker stand in your way when developing or does it make it easier? Maybe a solution is to create docker wrappers for our favourite framework that would abstract Docker. Anyways, I'd love to see more on this.
The equivalent in the cycling example would be that trains have to give way to cyclists which was not my point.
I do agree with a lot of this article about the uselessness of enforcing outdated road rules to cyclists. I personally will rarely completely stop at stop sign. I find the danger much higher to try to immobilize the bike, un-clip the shoe and start again with a very slow speed (potentially exposing myself for a much longer period of time in that dangerous crossing zone).
To solve accidents between all of these actors, I think there should be a simple rule of giving the slowest vehicle always the right of way, which is what courteous people do. A pedestrians should always have priority over a cyclist and or a motorist. If accident happen, the cyclist/motorist should take the full responsibility for it. Likewise a cyclist should have priority over a motorist. The person at fault should be proven guilty unless proven innocent of some unpredictable situation.
It is a bit the same on the water, where motor boats have to give way to wind powered boat for the same logical reasons.