Sounds like a case of package profiling to me!
I'm sure running a school in the US is a tough job, but perhaps the individuals involved in the situation could have taken in a little more context with their analysis .
"Lets see, where would a timer device be appropriately used in a bomb? Perhaps an unattended package?"
But it sounds like it was in his possession the whole time. If someone is willing to blow themselves up they don't need a timer.
I bike a 2 hour round trip every day. And in the last 3 months:
- Was knocked off my bike while doing 25k, while in a bike lane (truck turned right in front of me while I was beside him). I ended up in emerg.
- Driving my car to work (a rare occurrence), I missed getting t-boned by a pickup, by 6 inches. He hit 2 other cars beside me when I hit the brakes.
- Other day I got in my car after I biked home, and then swore at a slow biker who took up the whole lane: he was ignoring the 1-meter wide bike lane beside him.
- saw a biker nearly get hit when he ran a stop sign at a 4-way, where a car had been waiting then started to go, then slammed on the brakes. Biker waved cheerily.
- Nearly got hit by a car turning left onto highway, as I crossed the highway on my green light: he was tailgating a van, didn't see me, he skidded sideways to a stop.
- And virtually every day a car mirror whizzes past at less then 1 foot, doing 60-70k .
Well indisputably, bikers do stupid things. However I note there seem to be a lot more drivers (most who never bike), than there are bikers. Without question, driving is more frustration inducing than biking. Usually due to traffic. Which leads to a lot of unhappy, near road-rage individuals out there behind the wheel. And that's not likely going to change any-time soon.
In fact, I think all the bikers could disappear tomorrow, and the drivers would still be just as neurotic and unhappy.
What these car drivers should learn is that many of us ride because we used to drive everywhere, but ended up hating what it made us become.
Master C++? What an oxymoron. It is quite difficult to master C, even though it is 1/10 (1/100th) the complexity of C++.
People that are smart enough to master C++ are probably too smart to get sucked into doing lowly programming for a living.
And yes, I have 30+ years of C coding experience, so I guess that makes me a moron.
I second that. Geany is everything other IDE's are not. The closest experience to it's speed? Turbo Pascal on CPM in 27 Kb. I kid you not.
My favourite: an uncaught exception (like from map.at()) causes the program to exit with no trace of where the problem originated.
It's a matter of scale. C provides 10 feet of rope. C++ provides 10 miles of rope.
Worse, to understand any of a C++ program, you need to understand all of it, due to the tentacles of inheritance
C casts are a necessary evil! While "C++ cast operators are nothing but a major annoyance":
When you know a language well, there's no problem writing good code in it. But truly few can claim to know C++ well enough to make that assertion. The language is far too big and complicated and provides too many ways to do the same thing.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (6) Them bats is smart; they use radar.