Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Easy life (Score 1) 190

by greg1104 (#49163105) Attached to: Research Suggests That Saunas Help You Live Longer

You know what else minimizes the risk of musculoskeletal problems caused by weight-training? Not doing it, and instead training with something that's considered a less hardcore workout.

Workout intensity has a large range of activity in it, each with a corresponding risk. I don't think it's appropriate to talk about the benefits of serious strength training without also noting the associated dangerous parts. If you're young enough that you only have been lifting for 12 years (hint: half as long as me), you're unlikely to know about how tricky this gets when you get older yet.

Comment: Re:Easy life (Score 1) 190

by greg1104 (#49159831) Attached to: Research Suggests That Saunas Help You Live Longer

You'd have to browse Pubmed with blinders on to miss all the studies of how weight training leads to injuries. Just picking one author who writes about them, here's 1 2 3 4 studies on it. I only do body weight exercises now, and I count myself lucky that I only have one mild uncorrectable shoulder injury from my lifting days.

Comment: Re:80% Slower? (Score 1) 158

by greg1104 (#49104775) Attached to: Nvidia Faces Suit Over GTX970 Performance Claims

There are plenty of examples of both usages of slower, showing that it is ambiguous across popular usage. For example, there's a whole 800% slower "genre" on Youtube where songs are played at 1/8 of their original speed. When popular usage is so sloppy, it's better to avoid the phrasing altogether in favor of something precise instead.

Comment: Re:Don't be so hard on him... (Score 1) 323

In your interview process, ask obscure low-level architecture questions, like "What is a trap?" or "What does the BEQ/JEQ/JE opcode do?" These questions will rule out anybody who hasn't ever worked with any form of assembly language.

No, it will just make you a trivia-based interviewer. You need to be a serious authority on every aspect of a thing before you can create a comprehensive question like that. These two both have problems. I can tell how old you are from how you asked them.

The i386 processors that are all many people use now call those interrupts, not traps. And there are over 30 branch instructions in that set. JE is one of them, but I wouldn't expect people with only a small amount of assembly language background to remember that particular combination. You can easily write non-trivial 386 programs and never use JE.

This is not that hard: ask "have you ever written anything in assembly language?", and if they say yes, ask how it worked. No opcode trivia is necessary.

Comment: Re:Web Developer/Public-Private Key? (Score 1) 809

by greg1104 (#49056143) Attached to: Ask Slashdot: What Portion of Developers Are Bad At What They Do?

Web development now is all about plugging components together as quickly as possible to ship code. Anyone who pauses to try and actually learn how things work is at a disadvantage. While you're doing that, your competitors have already shipped something that worked well enough for people to use it.

Also, there's little sense really digging into things like libraries when they change so quickly. I'm doing this project right now that's all Go based. People who did a deep dive into learning how their previous tools are again regretting that.

If it's not in the computer, it doesn't exist.