Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:The six is on the right side. (Score 1) 240

I took typing classes, and they taught that the 6/Y/H/N are typed by the right hand (and 5/T/G/B by the left) as you say, but I have been programming for 16+ years and have gotten into the habit of typing 7/Y/H/B with my right and 6/T/G/V with my left. It just feels more natural. I don't know why they teach it the way that I learned it. Just doesn't make sense to me.

And just for reference, I primarily use Mac computers, and all of their (modern) keyboards have the 6 key significantly closer to the left hand (about 3/4 of an inch "as the crow flies" from the F to the 6 vs the J to the 6).

Comment Re: Perfect? Really? (Score 1) 340

Most importantly, no one is even close to solving no limit -- where you are allowed to vary your bet size. That changes everything.

If we are under the same assumption of unlimited games allowed and unlimited resources, then yes, they have: http://en.wikipedia.org/wiki/M...

Comment Re:Doesn't matter in the end (Score 1) 472

I thought the same thing, but git shows that they were written by the same developer in a single commit. This same developer has caused the developers at my company SO much trouble. He documents the stupid things, and performs useless 'no-op' conversions (another example from Python, str is already a string: str = "%s" % str... not only did is the code confusing [str() anyone?], it's a no-op). On top of that, our code is filled with comments such as "This is a hack" followed by 400 lines of illegible, undocumented code (unless you count "This is a hack" as documentation).

Comment Re:You get what you pay/wait for (Score 1) 491

Oh, and also, I was basing my comments on previous experience. I have worked using a waterfall model in the past, and in my experience it wasn't usually executed well, or didn't work as well as the team I am a part of now. So no, I don't know the best way to do things, but I do know what has and has not worked for me.

Comment Re:You get what you pay/wait for (Score 1) 491

I didn't mean to come across as knocking other approaches. The core of my point was that in my situation, with my team, agile works well. And to address the questions you posed:

Fast - By change of direction, I meant for the REST of the project, not work that was already completed. You can change directions on a weekly basis with agile (if your situation supports it, as someone else suggested, this won't work for the design of an airplane for example).

Cheap - My team tends to use the words priority and value interchangably. The highest priority task is the one that brings the most value to the business as a whole (which can, admittedly, be difficult to judge the "highest" sometimes, but we do our best and people seem happy).

Good - Short development time means we don't have to go back to the research and designing we did 3 months ago to remind ourselves what we're doing. The research and design is done in very small chunks and is usually from the past week. Yeah, some things take more than our one week time to complete, but we have SOMETHING done each week that is measurable, predictable, and best of all, sustainable.

Of course you can't flap your arms and fly to the moon. After a while you'd run out of air to push against.

Working...