|
Artoo?
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
|
|
|
|
|
Teams are fine; when appropriate. The current and popular team attitude is not.
Having been a coder in the profession for almost two decades; as an independent consultant the latter half, the most troubling aspect I have seen is to be found in the current manifestation (more like infestation) of coding as a team-only activity dedicated to the assembly line.
Most coders were; and probably are one of the following: nerd, goth, outcast, loner, artsy, dork, gamer etc. Of them in the past, our industry exists because of these outcasts and loners.
Now younger coders form teams in which each member must think the same, act the same, sit side-by-side, never stand out and never, ever be a "lone wolf". What happened! Now to be a successful coder, you cannot be a loner or outcast?
The coding profession was created and populated by non-conformists; give me a talented weirdo over one of the "dudes" any day. A coder who can talk for hours about futurist concepts, I trust. One obsessed with sports and "the team", not so much.
That is the problem with many teams: they have become social fraternities.
|
|
|
|
|
That is a wall everyone (Browsing CodeProject to learn more) keeps on hitting. But I don't think that any of them can do something about it (or at least climb it).
|
|
|
|
|
Sure you can do something. When they came to assimilate me into their team, I told them that I already had forgotten more about programming than they and their team ever had known. After that, working on this particular project became bearable. At least most of the time. The price for that was to look for another place to work, of course. If I wanted to join a religious sect, I would have done that without their help.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
Coding is akin to an artist working on a painting. A single artist can produce a cohesive and beautiful work of art. Multiple artists will have different techniques and while the final product may or may not be interesting, it's rarely a masterpiece. However, if the project is a giant mural or covers a city block, it's not practical for a single artist to complete. Likewise, there are projects where sheer size dictates the need for multiple coders. So I'm voting preferably solo, but a team for large projects.
|
|
|
|
|
I was a fine artist before becoming a coder (many many years ago). The transition was easy since the approach, process and creative practice were the same. This is a truth the industry refuses to recognize.
|
|
|
|
|
Strongly agree with "Coding is like art..."
When working in a team... too many ideas for solving a single problem...
Too many cooks spoil the soup
http://www.zapiro.com/Cartoons/m_101125mg.jpg[^]
But the problem of solo is.... it will take plenty of times to complete a large project alone.
So... em... I'm in the process of learning to work in a team...
|
|
|
|
|
Because I get to play god and make all the decisions and direction. Beside I don't have to please anyone other than myself. Team works when the team members have like mind set, especially ego.
|
|
|
|
|
If you are a part of a team do not seek the guy how learns tow steps ahead of the team. LEARN IT YOURSELF.
|
|
|
|
|
I have been an independent contractor/consultant for many years so I obviously support the solo coder; still, I have learned to find the most talented member of the team and forget my self-image. Just watch and learn. If I discover that I am the most talented on the team, I take the opportunity to mentor others into becoming confident, talented SOLO coders who eventually start their own businesses.
Not like Managers who like to keep the herd in place with policies, procedures, group-think and control; if you are in this situation, get out. Never worth it.
The worst type of team is "The Brotherhood"; the coding fraternity, who demand your complete allegiance. Should just kick them out into sales where they belong.
|
|
|
|
|
If it support I can provide. However, When I'm on the run for the last day before a deadline, I can't help but wish I was a less of a nice-guy and kick them out.
|
|
|
|
|
While code teams are often necessary; I have worked well in quite a few, the process of coding is similar to fine art in which the artist faces a blank canvas on which an idea must be designed and created. As in art, code is the realm of the individual mind.
Minds of mediocrity demand an assembly line process in which coders are interchangeable. They establish cliques of hive minds in which everything is collective. They make religions out of processes and procedures and demand the same zealotry of others.
In my decades in the profession I have found these team-only disciples to be people of little talent with no innovation or creativity. They conceal these inadequacies by hiding within groups: teams, pair-programming, hive-mind reviews.
Individuals create; groups consume. Every major innovation in history has been that of the individual. Of course, teams developed the atomic bomb and we know that result...
|
|
|
|
|
And you will never get to really experience the sorrow unless you are forced to make a mediocre mind into a creative one (WITHOUT USING MAGIC).
But...
Imagine tow or three Creative minds working together. What they can do, What they can Make!!!
|
|
|
|
|
Mediocrity hiding within the collective "we" of a team should be exposed and driven out of the industry; unfortunately, this "team sports" approach to coding creates a sanctuary for them and drives talent away.
When I lead a team, I follow neither code dogma nor implement stringent procedures. I allow each coder to develop as he or she feels most comfortable. If the coder is a complete introvert who prefers to develop at 3am while wearing two hats; so be it. I had and have only three rules: keep your promises, be ethical and make sure I am impressed by your work.
|
|
|
|
|
What if you can spot mediocre minds and stay away from those circles.
Working with people of the same height and coding sight, Making sure to finish all the important projects leaving the rest to... do whatever they do.
|
|
|
|
|
I like going solo if it's a small project (Yes, I fix all the bugs myself). But I also like having a team for bigger projects. When I'm stuck, there are others to bounce off ideas. Also, it's fun in the break room and going to lunch together.
|
|
|
|
|
...as long as they do everything my way!
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
|
|
|
|
|
When you find a cure for that tell me.
|
|
|
|
|
My philosophy on coding is this. Software engineering and development is a team sport akin to wrestling, swimming, and track & field. The team relies on every member to do their individual best. Each member needs to do their own best work, and the team will succeed as the sum of the individual parts. This also means that team members share their expertise and knowledge, mentor each other, and of course encourage and a slap one another when they do stupid stuff. :cool
David
|
|
|
|
|
Or everybody is kept on a short leash, constantly supervised and kept in line by endless rules and conventions. Round that off with some code style tools and a sufficiently efficient culture of blaming all 'heretics' and there you have it: A cargo cultish sweat shop where everybody is held equally dumb.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
Always seem to get this question when being asked to describe myself and how I like to work.
What I have learned over the years is that I prefer working in organizations where they have a team of software engineers. I don't mind so much working solo on a but project but I can't work in organizations where I am the only software developer. I like having that comradery of having individuals who think as software developers around me.
|
|
|
|
|
Work is independent, but the coordination of data (storage, formatting, conventions, &etc.) is what really makes things click.
Give it a thought: how you work with others, and they with you, will vary for each pair interaction. If no one feels crowded or abandoned (that Team Spirit thing), then things just move along.
Rant: too many of the various coding styles are, when it comes down it, trying to create a one-size-fits-all work environment.
For coding - particularly if you've got creative people - that is a bogus premise. Just outsource the stuff to some overseas code-mill if you want the mundane.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I have multiple personalities!
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|
|
So... what do you do with the VB guy?
Software Zen: delete this;
|
|
|
|
|
He's the black sheep!
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|