There are lots of stories of SELinux saves out there now. This is one I saw just recently:

https://www.reddit.com/r/linux/comments/1xdokz/selinux_saved...

I myself have had several SELinux saves. It's definitely proven itself valuable as an additional security control.

ASCII via frequency analysis! Dude, you are awesome!

Stephen was wrong, Kip was right! :)

#kernel-panic on freenode for good Linux and tons of other good discussion. Been there for years. Active right now with 34 people. But pretty much every major FOSS project has an IRC channel, usually on freenode. Every programming language, framework, etc. is represented there. I get tons of good help there and help others as well. IRC is definitely very much alive. I rue the advent of modern one-on-one IM as it really ruins teamwork. A few months ago we threw up our own openfire jabber server and required everyone in the company to be present and it has really boosted awareness of what is going on and replaced the "hallway conversations" we were missing from our distributed development environment.

Because often you can ram a bunch of gunk down the hole and have it stay there. This is how they have been controlling wells and stopping gushers since the beginning.

The problem with asking non petroleum engineers this sort of question is that you get incorrect and useless answers based on very limited "intuition and common sense" and not based on actual knowlege of the discipline.

Python. For a lot of reasons. It's easy. It has a lot of libraries. The Python based CMSs are better. And most importantly it's easier to find decent python programmers. The vast majority of PHP guys I have interviewed ONLY know one language: PHP. The python guys tend to be much more well rounded. Of course the PHP guys are usually cheaper. You get what you pay for in this case. I would also have to recommend against perl. I did perl for 10 years before I switched to python 4 years ago. I think their philosophies say it all: Perl: There's more than one way to do it. Python: There's one obviously right way to do it. Sure, that's a huge generalization but I find it true in a lot of cases. Perl really is line noise compared to Python. And reading someone else's Perl is a real challenge.

I can tell ya that reading and understanding some of my own Perl from even 3 or 4 years ago is a real challenge. ;)

All I can say is that I hope I'm getting better.

I read about this a month or two ago. Watched the video, read the whole paper, it's awesome. A great way to demonstrate that computers are really just machines and not magical at all.