Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:That's great news! (Score 1) 517

That's a terrible analogy. An accurate one is two runners - one with a red shirt, the other with a green one. Since red is an energizing, aggressive color, the green shirt must obviously be better because they wore a shirt that relaxed them. Right?

The red shirt must be a better runner because they were looking at the relaxing green shirt. Who pays attention to their own shirt color during a race?

Comment: Re:Learning programming through motivation. (Score 4, Funny) 315

by Krishnoid (#49442389) Attached to: Ask Slashdot: How To Introduce a 7-Year-Old To Programming?

That's a bit draconian. Try this instead:

  • Write a program to unlock this box.
  • If you can unlock it, you can get your smartphone out of it.
  • You can't use your smartphone until you get it out of there.
  • A person typically goes insane without smartphone use in 7 hours, and comatose in 14 hours. Shorter for teenagers.
  • Good luck.

Comment: Re:I'm all for abolishing the IRS (Score 1) 349

by Krishnoid (#49374881) Attached to: Sign Up At Before Crooks Do It For You

Let's assume I am a billionaire who commutes mainly via private helicopter. It doesn't bother me at all to throw a few thousand dollars toward a local road-improvement project. For a struggling single parent to do the same would be a significant hardship, even though they would be far more likely to actually use and benefit from the improved road.


Billionaire: Why are you late getting here to fly me to work?

Pilot: Hit a pothole and got a flat.


Billionaire: Why can't we take off?

Pilot: Fuel truck hit a pothole and got a flat.


Comment: Plan B (Score 1) 298

by Krishnoid (#49357143) Attached to: Ask Slashdot: What Makes Some Code Particularly Good?

... functional, readable, testable ...

From the maintenance perspective, when you can't make the code meet some standard, comments describing what you missed and why (time, spec conflicts, didn't care enough) are helpful. This hints to the next maintainer that modifying a piece of code that missed some good-practices target has additional considerations or hidden pitfalls, or that it can be fixed/extended/replaced with impunity.

The absent ones are always at fault.