3 ms·
Here are my personal anecdotes: >1. It is very hard to pin down who is responsible for anything. Fair for some situations but my team and I use git and share
by crystalPalace 10y ago
Here are my personal anecdotes:
>1. It is very hard to pin down who is responsible for anything.
Fair for some situations but my team and I use git and share the repo with our clients so they can see who is committing code.
>2. You end up explaining everything twice - once to your front wo/man contact and then again to the clueless intern who is tasked with implementing what you want.
My team and I always make sure we are in the same email thread with the client.
>3. It is near impossible to determine the competency of the person who will be doing the work in advance. The front person is usually quite good, but the person who actually does the work is often not. You can’t work that out until you are well into the project.
I've had situations were my entire team has interviewed separately but I can see how this is unfeasible for some teams especially past a certain size.
- danieltillett 10y agoI am sure there are good teams (and you sound like you are part of one), it is just really hard to work out who is a good team and who is not until you are well into the project. I think if you had a really large project then a team would be a good idea especially if you require skills in a lot of different areas, but in my case all my projects have been smallish and focused. I have worked with some amazing freelancers over the years who can do things in days that would have taken me months.