Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Re:Evil? (Score 1) 572

If employees do X, the company may be liable. There's no justification in that reasoning for not telling the employees you're doing the scanning. A company policy that says, "Hey, we have hired experts to watch all your traffic to protect the company" is pretty different from one that reads, "Hey, don't use the company resources for private things."

Comment Re:Write clear code, remove comments (Score 1) 472

I'm glad you mentioned this book - it's what I follow now too. The post says there's no penalty for a full explanation of the code, but there are lots of penalties: 1: The explanation is a translation from one language to another, and there will be inconsistencies 2: When the code changes, the comment might not change, which can be misleading, and 3: When the code changes, that's a ton of work to update every comment! If I use a refactoring tool to change the names of a function, that might be dozens of places automatically changed... I'm going to read each one to see if a comment needs changing?

Comment There are things you don't understand (Score 2) 515

It could be that your coworkers don't want to spend time learning new things. It could also be that they understand the magnitude of effort required to change systems more than you do. It sounds like, in the case of the new computers, you solved a problem they didn't solve - good job! In general, there may be circumstances in which it does not make business sense to invest in new systems.

When you write things like "after almost 30 seconds I fixed the problem" you sound cocky. When you say things like "I'm young and learn stuff and old people don't learn stuff, what's up with that?" you sound cocky and naive. You could be RIGHT... but I recommend you work on your communication skills.

Slashdot Top Deals

"In the fight between you and the world, back the world." --Frank Zappa

Working...