This is a horrible way to go about things, IMHO. The code should be written to match the planned design, but you should *not* need a comment to describe every bit of code. When the code changes, the comments are often left unchanged, and you're left with comments that are worse than useless, they are downright misleading.
do believe Kerry did the horrible thing in conceding
Horrible? Or honorable? I'll refrain from pointing out the rest of what's wrong with your comment, but I must say you're not helping the majority (51%) of Americans look any better this morning...
Your attitude is awful. I will never work for someone who thinks the way you do. Even if someone is posting from work right now, it doesn't neccessarily make them less productive. Breaks are neccessary here and there to clear your head and allow you to be productive. You cannot require someone to have internet access (or in particular, fast internet access) in order to be able to work additional hours. How does it show distain for the company if they don't have internet access or a cell phone? Having a life outside your job is not distain for the company, it's healthy.
Broadband is one thing, but cell phones (for work use), pages, and blackberries are another. I work from home, so have a strong argument to be able to expense my broadband connection, however I don't expect to be able to because I would have it anyways. However, my cell phone is provided and I would fight tooth and nail if it were not. Do they expect that you'd pay for work related text messages from servers/services that need attention? That seems outlandish. In the case of broadband, you'd probably already have it, and it's not metered, so it is irrelevant how much traffic is work / personal related. However it is not reasonable to expect you to provide things like a pager for work emergencies yourself.
Waaah, no one helped me. If that's your attitude, you should be using windows.
Re:Caps lock is where control ought to be
on
Is Caps Lock Dead?
·
· Score: 1
Indeed! I do this too, as I am used to sun keyboards and having control where caps lock is. I take it a step further and remap capslock to control on sun keyboards as well, so I always have 2 control keys in the same places.
Definetly - I noticed that as well. I've never had cable, and I don't plan to, so maybe if/when I have kids they'll be lucky enough not to think that way...
As I mentioned in another comment, the company I work for practices pair programming successfully. I'm not sure why everyone is convinced it doesn't work, as I watch it work every day. If you have any questions, just shoot (jeff at zeroclue dot com).
Regaring Peer Programming - we do it 99% of the time at the company I work for, management is fine with it, and for the most part the developers are too. Sometime small changes are made and then peer reviewed, or one coder will continue on where he/she left off with a pair and catch their pair up later. It can be a bit boring to watch someone else code, but the fact of the matter is that it works. You end up with code that makes more sense (as it has to make sense to 2 people in the first place), you are never stuck having the "Search Engine Guy" since you're guarunteed that at least 2 people worked on it, the code is significantly more bug-free because other people catch things you don't, etc, etc. I believe management at my company is OK with it because the code that's been developed under the XP model is so much better than what came before it.
1) This is evidence that the developers you work with are "small" people. People with over-developed egos shouldn't be hired into an XP environment
2) If brittle features are being produced, then the coding is poor. It's my belief that short cycles are more likely to produce better code, given a decent coder.
3) I think this needs to be taken with a grain of salt. It's not the absolute simplest thing that can work that should be done, but the simplest thing that makes sense that should be done. A co-worker of mine has a sticky note that says "don't copy broken code". That might be ammended to read "don't write crap code". also see me response to #4
3b) If the developer is tweaking a test just to co home, they need a swift kick in the ass. see the recommendation not to write crap code above
4) This is what re-factoring is for. As soon as you have repeated code in a few places, it's time to site down, actually think, and refactor the code to remove the duplications.
It very much sounds to me like the problems you've had with XP are not problems with XP itself per se, but problems writing decent code in general. XP is not a magical want that will make everyone's code beautiful, efficient, and flawless, but it does provide a framework in which high quality software can be produced and maintained relatively efficiently and painlessly. My experience with it has been extremely positive - maybe I'm biased;)
Note that it looks to me like the "Copyright holder" has to notify the Justice Department 7 days before they "take action", though I expect that this wouldn't be to rigourously enforced, of course... (in response to point 2) [http://www.politechbot.com/docs/berman.coble.p2p. final.072502.pdf page 4 line 4]
You can do quite a lot with a default install of OpenBSD. A default install does not have all services turned off - for example, SSH runs by default. The idea is, however, that you should have a pretty good idea what services you're adding, and be careful to ensure you do so securely - generally this is a much better idea than starting with a system whose services were enabled by default and then attempting to secure neccessary ones and disable unneccessary ones...
Don't pull an iso for debian - just do a netinstall using floppies (it only takes a few, depending upon whether or not you need to load any modules). At the most, pull the debain netinstall iso, as it's not very big.
I have used Bugzilla in a small (6 people) development team, and it worked very well. Additionally, other employees of the company who were not developers had no trouble learning how to file bug reports, etc. Getting them to write good, detailed bug reports was a different story, but that's not Bugzilla's fault. All in all I'd say it's a really decent piece of software, though if you want to alter its functionality you will find the source an ugly mess...
I don't know that a building with 3 sides would make much sense, as winds often come from one direction predominately (sp?). I think the ideal would be to have a building that could rotate, even if only a little bit, to keep its turbines directly in line with the current wind. though it might be a bit of a challenge to get into and out of such a building;)
Not exactly. I think the concern is that if the building is designed to chanel the wind, air will be passing over the sides of the building near the turbine faster, which would result in more cooling.
Slashdot Mirror
write the code to match the comments
This is a horrible way to go about things, IMHO. The code should be written to match the planned design, but you should *not* need a comment to describe every bit of code. When the code changes, the comments are often left unchanged, and you're left with comments that are worse than useless, they are downright misleading.
do believe Kerry did the horrible thing in conceding
Horrible? Or honorable? I'll refrain from pointing out the rest of what's wrong with your comment, but I must say you're not helping the majority (51%) of Americans look any better this morning...
Is this really the first anyone on /. has heard of dodgeball.com??
Your attitude is awful. I will never work for someone who thinks the way you do. Even if someone is posting from work right now, it doesn't neccessarily make them less productive. Breaks are neccessary here and there to clear your head and allow you to be productive. You cannot require someone to have internet access (or in particular, fast internet access) in order to be able to work additional hours. How does it show distain for the company if they don't have internet access or a cell phone? Having a life outside your job is not distain for the company, it's healthy.
Broadband is one thing, but cell phones (for work use), pages, and blackberries are another. I work from home, so have a strong argument to be able to expense my broadband connection, however I don't expect to be able to because I would have it anyways. However, my cell phone is provided and I would fight tooth and nail if it were not. Do they expect that you'd pay for work related text messages from servers/services that need attention? That seems outlandish. In the case of broadband, you'd probably already have it, and it's not metered, so it is irrelevant how much traffic is work / personal related. However it is not reasonable to expect you to provide things like a pager for work emergencies yourself.
Waaah, no one helped me. If that's your attitude, you should be using windows.
Indeed! I do this too, as I am used to sun keyboards and having control where caps lock is. I take it a step further and remap capslock to control on sun keyboards as well, so I always have 2 control keys in the same places.
Definetly - I noticed that as well. I've never had cable, and I don't plan to, so maybe if/when I have kids they'll be lucky enough not to think that way...
1) moderators, get a clue, this is vaguely amusing
2) it wouldn't matter, the coffee wouldn't spill unless the train was accelerating or decelerating
The power, man, the power is getting better. Ever try to plug a sparc in inside a cave? Pain in the arse, I tell ya
As I mentioned in another comment, the company I work for practices pair programming successfully. I'm not sure why everyone is convinced it doesn't work, as I watch it work every day. If you have any questions, just shoot (jeff at zeroclue dot com).
Regaring Peer Programming - we do it 99% of the time at the company I work for, management is fine with it, and for the most part the developers are too. Sometime small changes are made and then peer reviewed, or one coder will continue on where he/she left off with a pair and catch their pair up later. It can be a bit boring to watch someone else code, but the fact of the matter is that it works. You end up with code that makes more sense (as it has to make sense to 2 people in the first place), you are never stuck having the "Search Engine Guy" since you're guarunteed that at least 2 people worked on it, the code is significantly more bug-free because other people catch things you don't, etc, etc. I believe management at my company is OK with it because the code that's been developed under the XP model is so much better than what came before it.
1) This is evidence that the developers you work with are "small" people. People with over-developed egos shouldn't be hired into an XP environment
;)
2) If brittle features are being produced, then the coding is poor. It's my belief that short cycles are more likely to produce better code, given a decent coder.
3) I think this needs to be taken with a grain of salt. It's not the absolute simplest thing that can work that should be done, but the simplest thing that makes sense that should be done. A co-worker of mine has a sticky note that says "don't copy broken code". That might be ammended to read "don't write crap code". also see me response to #4
3b) If the developer is tweaking a test just to co home, they need a swift kick in the ass. see the recommendation not to write crap code above
4) This is what re-factoring is for. As soon as you have repeated code in a few places, it's time to site down, actually think, and refactor the code to remove the duplications.
It very much sounds to me like the problems you've had with XP are not problems with XP itself per se, but problems writing decent code in general. XP is not a magical want that will make everyone's code beautiful, efficient, and flawless, but it does provide a framework in which high quality software can be produced and maintained relatively efficiently and painlessly. My experience with it has been extremely positive - maybe I'm biased
Tsunami = tital wave.
Manhattan is "the Island"
Note that it looks to me like the "Copyright holder" has to notify the Justice Department 7 days before they "take action", though I expect that this wouldn't be to rigourously enforced, of course... (in response to point 2) [http://www.politechbot.com/docs/berman.coble.p2p. final.072502.pdf page 4 line 4]
damn. here's a working link...
Looks like Unisys could spend a little more improving their service and a little less hyping it...
You can do quite a lot with a default install of OpenBSD. A default install does not have all services turned off - for example, SSH runs by default. The idea is, however, that you should have a pretty good idea what services you're adding, and be careful to ensure you do so securely - generally this is a much better idea than starting with a system whose services were enabled by default and then attempting to secure neccessary ones and disable unneccessary ones...
Don't pull an iso for debian - just do a netinstall using floppies (it only takes a few, depending upon whether or not you need to load any modules). At the most, pull the debain netinstall iso, as it's not very big.
I have used Bugzilla in a small (6 people) development team, and it worked very well. Additionally, other employees of the company who were not developers had no trouble learning how to file bug reports, etc. Getting them to write good, detailed bug reports was a different story, but that's not Bugzilla's fault. All in all I'd say it's a really decent piece of software, though if you want to alter its functionality you will find the source an ugly mess...
I would think that it should be possible to somehow setup 2 turbines 180 degrees out of phase that cancel each other's noise...
True that. Wind turbines are more or less silent. Compared to the noise of your average city, I don't think it's much of a concern.
I don't know that a building with 3 sides would make much sense, as winds often come from one direction predominately (sp?). I think the ideal would be to have a building that could rotate, even if only a little bit, to keep its turbines directly in line with the current wind. though it might be a bit of a challenge to get into and out of such a building ;)
Not exactly. I think the concern is that if the building is designed to chanel the wind, air will be passing over the sides of the building near the turbine faster, which would result in more cooling.