|
You write as if "contract work" means you never talk to anyone at all, and it's just not the case. As a freelance developer, I have to communicate with clients and end users all the time. I subcontract out some work, so I have to work with them, oversee some work, manage timelines, etc. > Plus contract jobs are effecting the basic needs of human beings - "food, clothing & shelter", due to the very nature of uncertainly... Until your job (or department) is eliminated, or targeted for reductions. You'll have a similar level of uncertainty, but will have less control over doing anything about it. > I was learning something new everyday, when I was working in a team. Great for you, but at some point, you won't be learning much. Or you'll start to learn that "we're doing it joe's way because he's been here the longest". Or "we're going to use nodejs because XYZ... " but what it really means is dave wanted to learn node so his resume looked better when he left for the next job last month. > and having to deal with crappy co-workers. But that is how you grow. You can "grow" in a number of ways. Figuring out how to get clients, get work done and deliver projects to get paid is at least as much 'growth' as learning how to deal with office politics and crappy co-workers, many of whom may not share your work ethics, drive or priorities (yet their ethics, drive and priorities will still impact your ability to get things done). > I personally feel that for that one rock star to actually perform, there needs to be a team behind to support. And I've seen the opposite - where 1 or 2 people did 90% of the work - they were the true experts (domain, tech, etc) yet the entire team was praised, even when they either didn't contribute or in some cases were actual drains on the project. To publicly call out the bad team members, by, say, moving them to a different project, would look bad and make the manager(s) look bad, so things were kept as they were. There is no one right setup for all projects or personalities. |