You can have all the cameras and motion sensors in the world, thats still not going to physically stop an intruder.
Home Defense comes down to the basics:
1. Your home is your "castle", defend it at all costs. Most states have a "castle doctrine", meaning that while you can't blast somebody away on the streets, you can in your home (legally) in a last ditch effort to prevent an intrusion. Of course this varies by state.
2. With the Assault Weapons Ban expiring on Monday, I suggest going out and buying up a few M-16s and other large capacity handguns. Don't forget a few thousand rounds of ammo. Place these weapons strategically throughout your house (you may be cooking in the kitchen when somebody breaks in).
3. Take training courses on how to use those weapons.
4. For goodness' sakes don't keep those weapons UNLOADED or with LOCKS. Theres nothing worse than having a non-functional gun.
5. Apply for a concealed-carry license (depending on your state of course).
6. Carry atleast one full size weapon along with 2 extra magazines.
7. Live a life of avoidance, deterrance, and de-escalation.
Disclaimer: IANAL, YMMV, caveat emptor, boni anima teuri amen, and all that.
I never learned this until I had my Software Engineering course in college; but there is a huge difference between a programmer and a software engineer, and also that script kiddie who you buy simple PHP scripts from.
The "programmer" role I'm talking about is usually in a small team setting to do simple tasks. From what I've seen (and I used to be one) is that these coders take what they do seriously and actually produce elegant code because they have coding "style". Not just simple formatting and tabs, but artistic style in what they do. To me a programmer is sort of an artist. Anybody can splash paint on a canvas, but few people in this world can really make art.
Script Kiddies usually have one single purpose: produce something that works. Regardless if it isn't portable or scalable, as long as it works during the demonstration to the buyer/manager/professor then thats all that matters. This was my first stage in computer science. My projects in school were simply to get them done to get an A on them. Thankfully I eventually developed some form of artistic style.
A software engineer to me is someone who works with a group of other software engineers who use methodical/repeatable methods to produce software. Because this is usually a big team effort, communication, documentation is very important here. From what I've noticed in school and industry is that most software engineers aren't some hot-shot coder who writes compilers on the weekend for thrills, but rather classically educated SCIENTISTS who work together with others well to produce great software and meet the goals of that project. The goal here isn't to make "elegant" code or have fancy formatting. The goal here is to be so close with your team that they should automagically know what your code does. That doesn't say your style can be crappy and hard to read.
Slashdot Mirror
You can have all the cameras and motion sensors in the world, thats still not going to physically stop an intruder.
Home Defense comes down to the basics:
1. Your home is your "castle", defend it at all costs. Most states have a "castle doctrine", meaning that while you can't blast somebody away on the streets, you can in your home (legally) in a last ditch effort to prevent an intrusion. Of course this varies by state.
2. With the Assault Weapons Ban expiring on Monday, I suggest going out and buying up a few M-16s and other large capacity handguns. Don't forget a few thousand rounds of ammo. Place these weapons strategically throughout your house (you may be cooking in the kitchen when somebody breaks in).
3. Take training courses on how to use those weapons.
4. For goodness' sakes don't keep those weapons UNLOADED or with LOCKS. Theres nothing worse than having a non-functional gun.
5. Apply for a concealed-carry license (depending on your state of course).
6. Carry atleast one full size weapon along with 2 extra magazines.
7. Live a life of avoidance, deterrance, and de-escalation.
Disclaimer: IANAL, YMMV, caveat emptor, boni anima teuri amen, and all that.
I never learned this until I had my Software Engineering course in college; but there is a huge difference between a programmer and a software engineer, and also that script kiddie who you buy simple PHP scripts from.
The "programmer" role I'm talking about is usually in a small team setting to do simple tasks. From what I've seen (and I used to be one) is that these coders take what they do seriously and actually produce elegant code because they have coding "style". Not just simple formatting and tabs, but artistic style in what they do. To me a programmer is sort of an artist. Anybody can splash paint on a canvas, but few people in this world can really make art.
Script Kiddies usually have one single purpose: produce something that works. Regardless if it isn't portable or scalable, as long as it works during the demonstration to the buyer/manager/professor then thats all that matters. This was my first stage in computer science. My projects in school were simply to get them done to get an A on them. Thankfully I eventually developed some form of artistic style.
A software engineer to me is someone who works with a group of other software engineers who use methodical/repeatable methods to produce software. Because this is usually a big team effort, communication, documentation is very important here. From what I've noticed in school and industry is that most software engineers aren't some hot-shot coder who writes compilers on the weekend for thrills, but rather classically educated SCIENTISTS who work together with others well to produce great software and meet the goals of that project. The goal here isn't to make "elegant" code or have fancy formatting. The goal here is to be so close with your team that they should automagically know what your code does. That doesn't say your style can be crappy and hard to read.
Okay, just use C#/Mono and be done with it.