|
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
|
|
|
|
|
Where? Where?
(I just thought I'd get that in before Nagy did!)
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
You are quick this morning or Nagy's already working on the G&T?
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
|
|
|
|
|
I'd blame the Guinness!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Ewe are so bad!
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
|
|
|
|
|
Do you mean a team of one?!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
We have a single one. 
|
|
|
|
|
By working with a team it is easier to discuss about architecture or ways to solve things.
Besides this I don't like it that only one single person knows about the code of a product. I prefer that all the members of my team can work on any product.
Dreeke
|
|
|
|
|
... for one person to finish solo in a reasonable time frame; some are too small to work sensibly with two or more people.
It's a balancing act: if there is more than one man-year of work, it is definitely team material. If it's less than a man-month then it's probably solo.
Having said that, I haven't worked in a team for twenty years...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
The way I see it:
Some projects are just too big for a team of people to finish in a reasonable time frame; some are too small to finish solo - it will get done way too quickly.
|
|
|
|
|
OriginalGriff wrote:
Having said that, I haven't worked in a team for twenty years...
LoL
|
|
|
|
|
If I can do it myself and am familiar with the code, then I work on my own.
If I am not familiar with the code, then I prefer a team. Always nice to see some expertise when coding around me.
|
|
|
|
|
seem to be reasonably sensible, no one has voted for number 3. Some pillock will naturally vote for solo - large, team - small before the week is out.
While I prefer solo work it just does not make sense on large projects, not with a reasonably delivery time at least.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
