They mention things like bridges that need to work, and we wouldn't let anyone build a bridge without certification. But would you blame the engineers if someone learned the layout of the bridge, and the precise spot to put tnt to blow it up as an act of terror? Because that's what we're talking about with software. Bad actors CONSTANTLY trying to break your stuff. Are there people actively, constantly and in an automated fashion trying to destroy that bridge? Potentially hundreds of times every second? If, in that scenario, the bad actors succeeded, would the bridge engineers be at fault?

Sweet, terminal access. Ifbattery bat0 recharge Ifbattery bat0 up Vroom vroom. (So lame... I apologize)

Come on this is great! A Linux club, with a waiting list? Any way you look at it if you are a Linux enthusiast you had to have smiled a bit, even if it was on the inside, when you read that.

I worked at a startup. it was my first job out of college. I remember being so excited because "we were going to make a difference," but really I was just fooling myself. I had no experience and this place was the only job I found that would take me before I ran out of rent money. 12-15 hour shifts, no health insurance, I had to bring my own computer (I only had a tower, no laptop so that was interesting), and we worked out of a basement. Eventually it became a little more professional with health insurance, and a proper work building, they bought me a computer. I pushed my boss hard for this stuff. Then I had a child and couldn't work the hours, so I went to greener pastures with a more sane work environment. Fast forward a year after I left and I get a call from one of the previous employees who I refer to as my "war buddy" because of all the strange and difficult happenings at this previous place of employment for both of us. He tells me the boss just killed his wife at the work place by cutting off her head. That was my first boss, my first work experience. Every job since then has been a cake-walk.