I would believe it. I just heard one of our kind-of boss simply told someone after he said is code was not working correctly to put ON ERROR DO NOTHING in the code as the technology we use apparently support this. And of course that mean ignore why the error is, etc. and implicetely accept all the error that may cause in the end-result.
So go ahead and tell me your story.;-)
There was no Article;-)
Also... I believe there would be different manager. But in IT, in a big project, someone who can at less get an overview of the project and can broke down the project in small piece has a greater chance to achieve his goal. Estimating correctly is yet another goal. Most developper can't even do #1 (broke down correctly or even logically think sometime... no matter how many time they are allowed). As for #2, it depends of a lot of factor. If the broke down is small enough, if you are sure that your whole overview is not fuzzy, etc. Else a lot of time it is a big bet.
There is a problem and it is not just about being a manager. Even being a techy, I realize that there is a lot of people who have serious logic problem when it comes to develop. I have noticed this at school (not 10% of bad, but rather 90%, maybe I exagerate, but maybe not), I notice it at work, etc. Some people thought have some capacity, but are not as fast as the other would want. That lead them to do bad move and fuck up.
It is maybe very hard, but a good leader/manager in a team with a great technical vision might be the best. The problem is when it comes bureaucratic and the reunion, etc. grab your time, so you have none to think correctly. Sometime just go slowly to think and then go fast once you have the solution is the best way to go. Unfortunately some system make it harder for us to apply. Indeed human communication is something that make it even more complicated.
There is project that are also deemed to failure since beginning. Some good project leader are able to say yes or not from seeing this, in other case, it is just a matter of time. I guess that is part of life. Your story, my rambling, etc.;-)
I completely agree with you there. The best documentation should at first be the code. So always try to make the most readable code (when you can) and that code being the comment itself.
You should also know from now, that a comment is not good if you don't update it. Some people tend to update the code and not update the comment (if there is too much comment, you can be they will get desynch too. I don't want to comment all line of code, but block of code that is ok.)
However, there is moment (time pressure, bad code hack, etc.) -- where comments are really helpful, at less as personal notes.
What about GoofIE;-)
Now beside say:
"You wasted all your time on the internet today"
They will say:
"You were GoofIEng all your time on slashdot today"
(or beside explore the internet, you will just goof it)
Slashdot Mirror
But if those teacher are the ones who are not good enough for the company, that might be overally wrong for the industry.
If antioxydant is a topic that interest you -- you would want to read this too: http://www.mercola.com/blog/2005/aug/29/coffee_ame ricas_leading_source_of_antioxidants
I would believe it. I just heard one of our kind-of boss simply told someone after he said is code was not working correctly to put ON ERROR DO NOTHING in the code as the technology we use apparently support this. And of course that mean ignore why the error is, etc. and implicetely accept all the error that may cause in the end-result. So go ahead and tell me your story. ;-)
There was no Article ;-)
Also... I believe there would be different manager. But in IT, in a big project, someone who can at less get an overview of the project and can broke down the project in small piece has a greater chance to achieve his goal. Estimating correctly is yet another goal. Most developper can't even do #1 (broke down correctly or even logically think sometime... no matter how many time they are allowed). As for #2, it depends of a lot of factor. If the broke down is small enough, if you are sure that your whole overview is not fuzzy, etc. Else a lot of time it is a big bet.
There is a problem and it is not just about being a manager. Even being a techy, I realize that there is a lot of people who have serious logic problem when it comes to develop. I have noticed this at school (not 10% of bad, but rather 90%, maybe I exagerate, but maybe not), I notice it at work, etc. Some people thought have some capacity, but are not as fast as the other would want. That lead them to do bad move and fuck up. It is maybe very hard, but a good leader/manager in a team with a great technical vision might be the best. The problem is when it comes bureaucratic and the reunion, etc. grab your time, so you have none to think correctly. Sometime just go slowly to think and then go fast once you have the solution is the best way to go. Unfortunately some system make it harder for us to apply. Indeed human communication is something that make it even more complicated. There is project that are also deemed to failure since beginning. Some good project leader are able to say yes or not from seeing this, in other case, it is just a matter of time. I guess that is part of life. Your story, my rambling, etc. ;-)
I completely agree with you there. The best documentation should at first be the code. So always try to make the most readable code (when you can) and that code being the comment itself.
You should also know from now, that a comment is not good if you don't update it. Some people tend to update the code and not update the comment (if there is too much comment, you can be they will get desynch too. I don't want to comment all line of code, but block of code that is ok.)
However, there is moment (time pressure, bad code hack, etc.) -- where comments are really helpful, at less as personal notes.
Now if only I could read the slashdotted article!
Heading to http://finance.yahoo.com/ ...
What about GoofIE ;-)
Now beside say:
"You wasted all your time on the internet today"
They will say:
"You were GoofIEng all your time on slashdot today"
(or beside explore the internet, you will just goof it)