A) had it been commented, it would have been easier B) A comment should take a few second. If you are taking an hour for every 8 hours of code for commenting, then you are doing it wrong.
At least the next poor sap will ALSO have to take longer to change something because you didn't comment it either.
You people are just making excuse for being sloppy.
" Most code should be readable on its own. " that was wrong 25 years ago, and it's wrong today.
It is not possible. You need to tell why the function was made. You can't dictate that accurate through just code.
How do I know something is wrong if I assume everything you wrote is doing what it is suppose to because it's 'self documenting'?
and yes, use clear names.
"Documenting code itself is pretty far down that list of things I would prioritize." then you are just wasting more of the company time. and code documenting should never take more then 30 seconds for a new procedure, so not a lot of time at all. And 30 seconds is gererous.//Calculate arrival time for ship
Now I know what the programmer is trying to do. SO when I see they are calling a function that assumes no movement on a holiday, I can immediately see what the problem is, even if I am just reviewing the code.
Yeah, I hear the 'there isn't any time' argument. Usually by people who came to my cube to take 5 minutes to bitch about who shot whom first in some Sci-Fi show.
". Documenting each variance " You comment the why you are doing something. refactoring does not change that.
And it should take you 30 second to write the why. If it takes you longer then that, then either you don't know what you are suppose to be doing, or your object/function/procedure is doing too much, break it up.
// Calculate travel time for ship to get from point A to point B.
That's a why. When I read that, I can know what it is actually supposed to do.
I use that example, because I was working on that code, and saw that they where taking holidays into account. Hint, ships don't strop in the middle of the ocean because it's Christmas.
Without the why, I can't know what the goal of the code is, and I can't tell if it works properly.
Commenting make it easier for different developers to knwo whats suppose to happen,. and in 6 months YOU will be a different programmer.
No. It's an excuse people use to not do it. Code documentation is essential, and if you aren't taking the time to do it into account with your estimates then you need to gain some more professionalism. It's not hard, and it doesn't take that long to do.
the GUI in windows is just an application on top of a shell. If you don't know that, then shut up.
I don't know what I expected, you either didn't understand the rest of the article, or you just skimmed it for the first thing you thought you could whine about. I'm not sure what is worse.
Someone is reading too much into that statement. Command line is the recommend method now, and will be. They won't get rid of the GUI. Of course if you are really an expert, you can do almost everything quicker in the GUI. Hot Keys are your friend.
How do you handle the issue where almost no company really knows how to rate performance of software or office work.
Why you think that can't be abused by slightly and constant increasing performance demand until some has to work 12 hours a day, every day is beyond me.
because most companies aren't sane, and many companies 'offer competitive vacations' but in reality you are expected to work.
If you are a company that already treat the employees properly when on vacation a law wouldn't impact you, it would only impact people who abuse there employees on vacation.
The government is spending beyond it's means because of the Bush tax cuts. remember the end of last millennium? yeah, we were doing good. The the pub cronies butchered the revenue without cutting anything.
Intentional to create FUD so the can kill SS and medicare.
And I wasn't a complete meltdown. Is was almost as bad as the 80; which is bad, but lets leave the drama on Fox.
"C are at the mercy of the boss or you will be the one at Walmart next unless you are very highly skilled far beyond the general public." bullshit. It's nice to see you have the indentured servant mentality.
No, it's not scary because that wont' happen; but you would need to actually understand the economics instead of letting other people tell you how to think.
And yes, that WAS a real possibility, but TARP saved us.
Remember kids: When TARP is remembered to be a Bush white house decision it was good, when people think it was started by Obama, it's bad. THAT'S how fucked up Fox and the pub are right now.
If you let the environment dictate when and how you look for a job, you aren't doing it right.
Job fairs? only good if you can meed some actually in the dept. If it's just HR collecting resume, don't bother. The side door is the best way to get tech jobs.
The current bank will be fine. Sheesh, find a source that isn't so alarming.
I worked at a place where In would give notice 90s ina dvance, and then would say another word.
Becasue if you gave 30 days notice, suddennly they where angling to cancel it.
I ddn't work there long, cause it was a pit. There comay sirvied on thiere data. the product was there data. no services, no manufacturing, just information.
When I looked into the backup process, there machines hadn't been backup in 5 years. When I mentioned this, the brought out some POS home tap backup system that could hold about 1% of our data. When I told them what the really needed to spend, they refused to do it. Multi-million dollar company could literally be gone with one disk failure. Oh, and the person in charge of it's maintenance left 3 months prior.
I swear the other people that worked there where experiencing Stockholm syndrome. And yes, I heard the a couple of months later, the system crashed. Still no backup, still didn't hire anyone to maintain it. On the plus side,. the manager would have 3 hour meeting where he told navy stories. . . not any good one tho'
Slashdot Mirror
Because you are wrong. many people follow through.
I comment, and I demand other programmers do so.
A) had it been commented, it would have been easier
B) A comment should take a few second. If you are taking an hour for every 8 hours of code for commenting, then you are doing it wrong.
At least the next poor sap will ALSO have to take longer to change something because you didn't comment it either.
You people are just making excuse for being sloppy.
" Most code should be readable on its own. "
that was wrong 25 years ago, and it's wrong today.
It is not possible. You need to tell why the function was made. You can't dictate that accurate through just code.
How do I know something is wrong if I assume everything you wrote is doing what it is suppose to because it's 'self documenting'?
and yes, use clear names.
"Documenting code itself is pretty far down that list of things I would prioritize." //Calculate arrival time for ship
then you are just wasting more of the company time. and code documenting should never take more then 30 seconds for a new procedure, so not a lot of time at all. And 30 seconds is gererous.
Now I know what the programmer is trying to do. SO when I see they are calling a function that assumes no movement on a holiday, I can immediately see what the problem is, even if I am just reviewing the code.
Yeah, I hear the 'there isn't any time' argument. Usually by people who came to my cube to take 5 minutes to bitch about who shot whom first in some Sci-Fi show.
Wrong.
1) "check that your code behaves as expected." How does that next programmer know what is expected?
2) "show how to call your code," That's the API documentation, not the code documentation.
3) Again, how does the next programmer know what the behavior is supposed to be?
4) "improve the stability of your program, and reduce the QA time." That has nothing to do with documentation.
yes, write tests. But you need to ALSO let the next program know why you did something and what it's goal is.
Yes, I have done Agile development, yes I like it, but there is STILL going to be maintenance later on by someone.
". Documenting each variance "
You comment the why you are doing something. refactoring does not change that.
And it should take you 30 second to write the why. If it takes you longer then that, then either you don't know what you are suppose to be doing, or your object/function/procedure is doing too much, break it up.
Sigh. Yes and No.
developer commenting is about the why of specific items.
You examples are stupid. Sorry, but that are.
""This class maintains a multi map of triangle pointers,"
Why is it doing that?
Get a good editor that collapses comments.
" I can scream at him or her. "
If you ever scream at me, I will trash your car.
// Calculate travel time for ship to get from point A to point B.
That's a why. When I read that, I can know what it is actually supposed to do.
I use that example, because I was working on that code, and saw that they where taking holidays into account. Hint, ships don't strop in the middle of the ocean because it's Christmas.
Without the why, I can't know what the goal of the code is, and I can't tell if it works properly.
Commenting make it easier for different developers to knwo whats suppose to happen,. and in 6 months YOU will be a different programmer.
No. It's an excuse people use to not do it. Code documentation is essential, and if you aren't taking the time to do it into account with your estimates then you need to gain some more professionalism.
It's not hard, and it doesn't take that long to do.
It's called being lazy and short sighted.
If you aren't documenting your code, you are bad at your job.
the GUI in windows is just an application on top of a shell. If you don't know that, then shut up.
I don't know what I expected, you either didn't understand the rest of the article, or you just skimmed it for the first thing you thought you could whine about. I'm not sure what is worse.
Learn? if you don't use powershell now, you are a failure of a windows admin.
Someone is reading too much into that statement.
Command line is the recommend method now, and will be. They won't get rid of the GUI. Of course if you are really an expert, you can do almost everything quicker in the GUI. Hot Keys are your friend.
How do you handle the issue where almost no company really knows how to rate performance of software or office work.
Why you think that can't be abused by slightly and constant increasing performance demand until some has to work 12 hours a day, every day is beyond me.
doing what? Not that I would work for a place with that attitude..again.
Maybe that, right there, is why you can't find anyone to hire.
See what union make you do? they'll make you commit mass suicide!
That's from the "Prediction of Fox news headline" book~
Of course their was. Don't blame your laziness on 'nothing I can do about it.'
Whats that? the company that did wrong doing said you couldn't do anything about it? well no shit.
I have never worked for a private company that didn't expect you to do some work on vacation.
I have been working sine the late 70s.
I now work for a city government. I work 40 hours and get vacation. And for the record, yes, I do work hard.
Time. Everything as about time.
because most companies aren't sane, and many companies 'offer competitive vacations' but in reality you are expected to work.
If you are a company that already treat the employees properly when on vacation a law wouldn't impact you, it would only impact people who abuse there employees on vacation.
8 hour day, on average, gets 6 hours of work done.
The government is spending beyond it's means because of the Bush tax cuts. remember the end of last millennium? yeah, we were doing good. The the pub cronies butchered the revenue without cutting anything.
Intentional to create FUD so the can kill SS and medicare.
And I wasn't a complete meltdown. Is was almost as bad as the 80; which is bad, but lets leave the drama on Fox.
"C are at the mercy of the boss or you will be the one at Walmart next unless you are very highly skilled far beyond the general public."
bullshit. It's nice to see you have the indentured servant mentality.
No, it's not scary because that wont' happen; but you would need to actually understand the economics instead of letting other people tell you how to think.
And yes, that WAS a real possibility, but TARP saved us.
Remember kids: When TARP is remembered to be a Bush white house decision it was good, when people think it was started by Obama, it's bad. THAT'S how fucked up Fox and the pub are right now.
If you let the environment dictate when and how you look for a job, you aren't doing it right.
Job fairs? only good if you can meed some actually in the dept. If it's just HR collecting resume, don't bother. The side door is the best way to get tech jobs.
The current bank will be fine. Sheesh, find a source that isn't so alarming.
sounds like that company was either not an american country, or was sued in the past. Or had Union in its roots.
I worked at a place where In would give notice 90s ina dvance, and then would say another word.
Becasue if you gave 30 days notice, suddennly they where angling to cancel it.
I ddn't work there long, cause it was a pit. There comay sirvied on thiere data. the product was there data. no services, no manufacturing, just information.
When I looked into the backup process, there machines hadn't been backup in 5 years. When I mentioned this, the brought out some POS home tap backup system that could hold about 1% of our data. When I told them what the really needed to spend, they refused to do it.
Multi-million dollar company could literally be gone with one disk failure. Oh, and the person in charge of it's maintenance left 3 months prior.
I swear the other people that worked there where experiencing Stockholm syndrome.
And yes, I heard the a couple of months later, the system crashed. Still no backup, still didn't hire anyone to maintain it.
On the plus side,. the manager would have 3 hour meeting where he told navy stories. . . not any good one tho'
Start talking to a lawyer. There is no reason you, or anyone should be treated that way.