Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:Step 1: Don't own any BitCoin (Score 1) 61

"Your teeth will get through anything," Mr. Kayll advised. "But it will bloody well hurt."

Speak for yourself, my teeth will barely get through a cheese sandwich at my age.

There's nothing like a good smack to the beitzim to stop a would-be rapist. And there's nothing like biting someone if it's all the leverage you have.

Remember, this is not a video game or a sanctioned fight in a boxing ring. This is your life versus the life of a terrorist or other attacker. Kill or be killed. Learn to fight.

Comment Re: It a guidebook... (Score 1) 235

my son's teacher told us that it helped with developing fine motor control, particularly in children that had below average motor control.

For one, is this based on research or speculation? Second there are different kinds of motor control. Following an existing pattern or shape is one type, while cursive is another because one tends to develop patterns based on personal preferences.

Comment Re:More than meets the eye (Score 1) 235

In 5th grade my teacher wanted to wring my neck because I was growing quite skillful in drawing and art, yet my cursive writing was worse than a drunk doctor's. I didn't see them as connected, but it was in the teacher's mind. I had a semi-impressionistic art style such that stroke precision mattered less.

Comment Re:Async bloat (Score 1) 90

I guess I'm not working on "typical CRUD apps" then?

Based on your description, no, you are not, other than maybe "data stores". Sounds like systems programming. And it's rare to need such for app-level database access (unless you did something wrong or bad).

other than async and await keywords here and there.

It tends to force the need to parts that have nothing to do with asynchronous programming other than being referenced by parts that do. It pollutes and spreads like prions in a brain.

Comment Do your research (Score 2) 10

This sort of attack is inevitable when you have open-access software repositories. If anybody can upload a package, that implies any bad guy can upload a package. So:

  • Ask yourself if you really need a package for this, or is it simple or straightforward enough you can code it yourself and avoid the dependency and the associated supply-chain risks.
  • Do your research. Don't just grab the first package that looks like it fits your needs. Review all of the results, then look at who published them and look them up on the web. Look at their web site. Look at what other packages they've published. Look at how active they are aside from the package you're looking at. Toss any that have red flags like no history aside from this package.
  • Validate your packages. Authors often sign packages. If they do, get their keys and enable validation so you only accept packages signed by the author you know. That way if a package gets hijacked it'll fail the signature check.

Slashdot Top Deals

"It is hard to overstate the debt that we owe to men and women of genius." -- Robert G. Ingersoll

Working...