3 ms·
"As a freelance AI engineer, you are expected to, for example, start with a client, familiarize yourself with the product and the codebase, submit the first PR
by FpUser 7y ago
"As a freelance AI engineer, you are expected to, for example, start with a client, familiarize yourself with the product and the codebase, submit the first PR within a couple of days"
Although I have my doubts maybe this is true specifically for AI area. In general contracting, getting familiar with the large project and "submitting the first PR within a couple of days" is a wet dream. I will exclude cases when one is hired to find and fix bug in some simple, short piece of code.
- sbacic 7y agoAre you trying to say it's unreasonable to expect a freelancer to start contributing within a couple of days? Or the opposite? Because I can't remember a single project where I wasn't expected to contribute something immediately, especially with new clients (that need to be convinced of the value).
- FpUser 7y agoI guess we are talking about different kind of projects. I had few very short limited scope projects (shortest one 3 days I think) but generally I design and develop products from ground zero (some I own, some made for corporate clients). It could take me a month sometime to write first line of code. And no one in their right mind would expect me to start coding big product with no design in place on a first day. As for trust - I have big portfolio and stellar references from satisfied clients and some of my products can be seen on the web. In my case this is normally what counts, not me banging on keyboard from the first hour. You do not start coding major project without without first having a clear and documented picture of what exactly is being built. Doing it other way is a recipe for major disappointment.