in reply to Avoiding "brain drain" in the corporate realm

Coding is only about 50% of the problem. The rest is getting people to understand and solve the problem as a group. I recall when I was in college I used to detest group projects, because the quality of the group you got to work in varried greatly. At work, likewise, espeically as the project gets larger and more complex, the more time you will have to spend communicating your ideas, and learn how to effectively navigate human interaction problems. If you can't explain to other people the scope of the project you're working on and why it's important, don't expect project managers to gleefully say 'go forth and conquer', until you have the paper trail to back your idea up...


----
Zak - the office
  • Comment on Re: Avoiding "brain drain" in the corporate realm

Replies are listed 'Best First'.
Re: Re: Avoiding "brain drain" in the corporate realm
by flyingmoose (Priest) on Feb 24, 2004 at 21:04 UTC
    Ah, I was just the opposite. I ended up leading our Software Engineering team of 12 people quite by accident. I'm drawn to this. Yes, we had some bad apples, but we dealt with it. Senior Design was more collaborative, as was another Design Project...pretty much leaderless infrastructure, but it still worked. In industry, I've found working as a group is actually harder than in college. People have more to gain/lose, and it gets personal -- it shouldn't.