I don't think this will ever fly, either. There is a lot of time/money invested in cataloging library materials... they can't afford books walking out the door with no accountability. Which I can GUARANTEE would happen in spades.
A deposit to cover the cost of the book isn't enough. Even a hefty processing fee wouldn't cover it. It's not just money, either... the library has chosen the item for a reason, and wishes it to be available to the public. When an item is lost&paid, it isn't available until it can be re-ordered/re-added, which takes time... enough of this takes place already (via both legitimate claims AND white lies) without helping it along with a "hey, it's like a bookstore!" option.
See, I work for a library (sysadmin) and I can tell you straight up that librarians don't actually give a crap about fines, fees, and replacement charges.
They just want their stuff back, so other people can use it. It's what we're here for, right? Fines are nothing more than a necessary incentive to bring stuff back when you are supposed to. So other people can use it. Without them, people wouldn't. Sometimes they don't anyway. Many libraries hold "amnesty weeks" on a regular basis to encourage people just to give us back the stuff, and we'll forget about the whole thing. Replacement charges are there to accomodate legitimate cases of patrons losing material, allowing them to make it right.
Amazingly enough, There are those that just take stuff and pay the charges anyway.
It's tough enough already to keep stuff from being stolen. Add an anonymous aspect to the "I can just pay for this item instead of return it" attitude... my goodness! How on earth would we keep half of the stuff from walking out the door for good?
Besides, this is a solution to a non-problem. Librarians are ingrained with the traditions of "freedom to read", and protecting patrons right to privacy in that regard. You think you hate the Patriot Act? Most librarians spit venom at any mention of it. (Not out on the floor with the public of course.)
I've sat in seminars with over a thousand of my peers (at vendor sponsored conferences, no less) where honoring those traditions and preserving patron privacy in the face of Patriot Act was the topic of the day. Presentations were given by libraries and organizations that fought it from the get-go. Not sure why I tell you this, other than perhaps hoping it inspires some kind of confidence.
If you are truly concerned about privacy, and how your library handles it, ask the librarians. They'll probably be happy to help you. They may even refer you to the director, invite you to a library board meeting, or put you in contact with a sysadmin that might be happy to chat. (Yeah, we're busy. But some stuff is important, and public perception of privacy is a biggie on that list.)
Have you discovered your library has no privacy policy, or a lousy policy? Ask about getting it changed. Talk to the Director. No luck? Go straight to the library board and hit them up with it. Still no luck? Ask the ALA what you can do about it. Put a bug in the local media's ear. If there is a "Library Friends" group of some kind, join it. Heck, get yourself on the library board. Don't just sit & bitch. Kick some ass!
Now, check this bit from the article:
Unfortunately, if an over-zealous special agent on a fishing expedition wants to know who checked out Anti-Flag's album The Terror State yesterday, the librarian will probably have little choice. Under the USA PATRIOT Act, he or she would have to surrender the personal identity information that was originally collected to protect the library's materials.
Yeah, well... there's a reason must of us purge logs that would disclose personal circulation history (and similar info) on a daily basis. Doesn't neccessarily have anything to do with the Patriot Act o
Now, a tidbit that should further clarify what was going on in that story...
In many ancient cultures (in particular Mesopotamian/Middle Eastern) to "name something" was to establish control/power/dominance over it. Basically names were very important and conferring a name on something meant you were the master of it.
Interestingly enough, the Genesis 2 creation account (there are two separate and different creation myths in Genesis) is by far the older of the two, predating the Priestly account (of Genesys 1, written during Babylonian captivity) by hundreds of years at the least.
I can assure you there are plenty of well educated people with decent language skills in the military. Not every single person of course... but no less a percentage than you'd find in any other slice of the common populace.
He vouched for the Army... I'm piping up for the USMC.
The terms you list are really no big deal anyway.
Common civilian opinion aside, it's certainly not some "dumb guys with guns" club. Your disclaimer of "no disrespect" is noted, but... you are in error with your underestimation.
Sand dunes are not snow, and they behave differently.
You're right about the friction bit, and that going easy is a good idea. But sand does not melt and polish into ice, which gives you another option (and set of rules) to fall back on. In particular if we are talking about deep, loose sand on a slope... it may be your only option. Not all vehicles are equipped or capable, which is why you don't see them putting around on sand dunes.
With properly designed tread (paddles and similar designs) and sufficient wheelspeed, you CAN spin right out of sand. A change in weight distribution is also helpful, if possible. Of course, it is a risky proposition... lack of sufficient wheelspeed (or too slow of a transition from rest to full speed) will do exactly what you describe... dig you in deeper.
Basically you have to grip sand and throw it backward fast enough to push yourself forward. Sort of like a propeller, but not quite. You have to do it hard and fast enough so that you don't run out of propellent (sand) before you've gained enough momentum to keep from sinking into the sand. (If you've dug down to the floor of the vehicle, your wheels are left spinning in empty space, intead of throwing sand.)
Of course this is totally irrelevant in the case of the rover. Even with the right tread and motor capability they could not afford the power drain it'd take to do it.
And the other poster talking about air pressure is absolutely correct. You let just enough air out to increase the surface area, decreasing the pressure on the sand, enabling you to "float" on it a little better. It doesn't matter if you go slightly convex, either. (In fact it helps... the sand in the concave compresses and holds you up just a tad better.) There is no danger of this compression turning the sand into a slick solid with a wet surface, like there is with snow.
It sounds like you deal with snow a lot. I don't. But I grew up next to one of the best patches of dunes in the US, and used to play out there (in many different types of vehicles as well as on foot) on a regular basis. Not just weekends or special occasions, either. (Heading out for an hour or two after school was common.)
Wow, that is a coincidence. I just heard of them for the first time today... but for rather sad reasons.
They just recently had their trailer stolen after a show in Portland OR. Nearly all of their equipment and instruments were stolen. They weren't insured against the loss. The trailer has been recovered, but was emptied out.
Word has been spread throughout the Portland musician community to be on the lookout for the gear, which is how I heard about it. (They published a list of everything, including serial numbers.)
Some of their fans set up a donation fund to help replace the gear... their tour dates are being postponed in the meantime, because they have no way to perform them.
All this can be found at http://www.decemberists.com/news
Most of the beaches around here aren't very wide... maybe 50-100 yards on average. (Bigger here, smaller there.) They also aren't very crowded at all... don't really need to fear crowds getting bottlenecked at escape points.
Speaking of which, no bridges or anything like that. Beaches aren't really developed at all. You might have to run up a sand berm (full of dune grass), dirt trail, or clamber over some rocks to save time (instead of heading for a regular path)... but most places it's easy to get on/off of the beach itself.
At any of the beaches I frequent, You also gain elevation pretty quickly. Once you hit the edge of the beach, you are going up... could gain 30-50 feet in less than a minute. In some places 100 or more, if you can hack it.
In other words... you'd have to run for it, but you MIGHT just stand a chance, depending on where you are and how big it is. A 30-50 footer might get you wet, but given a minute or two you have a chance at getting to someplace where it might not kill you. Anyone know how long you get once that water starts heading out?;)
Everywhere else I go you don't need to run... you're already looking down at the ocean from a few hundred feet above it.:)
Here are some pics of my favorite beaches... Sunset & Simpson Coves. (Collectively referred to as Shore Acres.) Most of the shots don't show the beaches themselves... you mostly see just the cliffs around them. (You've gotta hike some unmarked trails to get to where some of these shots were taken). But one is looking back at Sunset Cove from a tidepool area off to one side. (Note, I took none of these. Just found 'em at google. Apparently a few photographers know my spots!)
Also grew up on the Oregon Coast. (North Bend/Coos Bay area) How the hell can you not know this? For the original poster's information, it is taught in schools. Some of them, at least.
There are also tsunami warning signs at nearly every single beach, that even tell you about that particular warning sign if you bother to read them. I'm talking all over the Oregon coast, not just where I'm originally from.
There are even signs pointing out tsunami escape routes in some places.
Jeez... I thought everyone around here knew that stuff. Just like everyone knows about our rip-tides. Right??
It should be obvious at an elemental level... watch the waves at the beach any time. The water goes out, then comes back in with each wave. Well, if the water REALLY goes out... it's REALLY gonna come in! RUN!
Here is a not quite scientifically accurate (but not too far off) example that illustrates the effect pretty well for those that have trouble getting the concept:
Take a rectangular pan of water and give it a single good rock from one side to the other, then back. Note that the water on the first side gets really shallow while the water has gone to the other side. But then it comes crashing back along with the water from the other side, probably splashing out of the pan and getting all over the floor.
Not quite what happens with a tsunami, but the effect is similar. The big wave of energy rolls along till it hits shallow water, then starts to rise up. That rising water comes from somewhere... much of it from the beach ahead. Don't stick around to see where all that water went off to. It didn't go far, and it's gonna come right back atcha with a vengeance very quickly. Just like the pan of water in your kitchen, but amplified just a bit... let's say, a few million times or more.;)
Um... I've been using Netscape, Mozilla, other Gecko-based browsers, and Firefox on the Wells Fargo online banking site for years. (We're talking over 6 years, at least.) Usually from linux, sometimes from Winders.
Not a single problem, ever. Never had to touch browser reporting, either.
WTF are you talking about?
In addition, the sites that do have issues are becoming more and more rare. I maintain a bank of busy library public access machines running Firefox, so I hear about it whenever it happens. In other words, nearly (but not quite) never.
Now, you are dead on in the case of internal corporate sites and web applications. If there is a problem with Firefox support, that is where it lives.
But also capable of dropping horizontal to the surface. (Just like a real soldier)
Like an ant. Give it 6 limbs. Bottom two work as legs when upright, top two as arms. (Perhaps middle pair fold to sides.) Make the back most heavily armoured. Drop to ground to scurry around quickly like an ant, with a low profile. Stand up for longer range vision, more humanoid mobility, etc.
Go install DeMudi. It's Debian, but tweaked for audio & music production.
It "just works". Didn't have to do or set up squat... it was all there ready to rock as soon as the install finished. Hardware, software, ALSA, JACK, Ardour... the whole ball of wax.
Didn't even have to touch anything to get our Delta 1010 working.
I've shown the setup to peeps used to doing audio on windows, and left them in awe... asking me to burn a copy off for them. They've all come back to thank me a few days later.
For some reason when reading it I could picture it in my head, but...
It was accompanied by an overwhelming sense that my mind's picture was superimposed with the old farmer Neham's well. From Lovecraft's "The Colour Out of Space".
OK, the reactor light was blue while the color in the story was unidentifiable... but other than that they appeared so alike in my head as to really creep me out.:)
Even the results of exposure were horribly similar.
Re:Mixed enterprise environments
on
IT Myths
·
· Score: 1
Maybe not, but he could always be the "Company Computer Guy".
Because this a recommended solution for those same IT people to implement. A way for them to keep those programmers happy and productive, without turning the rest of the users into proverbial bulls in china shops.
If they aren't interested in that... then they probably stopped reading already.
I don't buy your consequences for messing something up... not in most environments. Unless there was an additional rule. Let's say when a programmer messes up something that effects another network user's productivity (which might have been prevented if the admins had at least been consulted) that they get to face the chopping block too!;)
(I've seen it happen. Just as there are lousy admins, there are lousy programmers.)
Good policy for locking things down is to identify those types of things... wallpaper, colors, etc. Things that users like control over, but have nothing to do with functionality (and won't hurt anything.) Leave that stuff wide open.
With one exception... in some organizations there are machines that will be seen by customers, in a service desk type of setting. It isn't a bad idea to require a standard backdrop/appearance for those stations.
And hopefully put more thought into it beyond just choosing that ugly blue everyone hates.:)
Truth is, you're both right about your respective situations, and wrong about each others.
Those in programming jobs always seem to have a hard time understanding that they aren't the only people around using computers in their workplace. And not everyone works for a company that produces software. (For any company that doesn't, any programmers on board are support staff too.) The vast majority of people using computers at work have nowhere near the expertise programmers do. They just try to use the machine as a tool to do their work.
On the flip side, admins (at least the sort you are ranting about) are overexposed to those users with minimal experience and knowledge w/computing in comparison. (Anyone who admins those kinds of users can tell you they NEED to be restricted, or they WILL break everything in sight on a regular basis and support costs will go through the roof.) Trouble is they get stuck in that mindset... and put all users in that same boat. Which is a problem... particularly when managing machines for programmers. For all the reasons you give.
Solution? Easy...
Admins should treat programmers as a separate class from other users and give them permissions (within reason) to manage their own machines accordingly.
And programmers should understand that when admins are talking about needing to restrict users, they are talking about Joe MBA and Jane Marketing types, not you.
We started in Salem w/a caravan of vehicles. (Dad purchased some property along the Susitna & we were going to build a big cabin. Bringing all the materials & tools with us!) A big flatbed truck, an old motorhome pulling a flatbed trailer, and a camper van pulling a jet boat. (A workhorse, not some ski boat or anything.)
Took 7 days to get to Wasilla. Then we chartered a barge to meet us at Deshka Landing & everything but the vehicles went on it. Following w/the boat it took a few hours to get down the Susitna river to a smaller river, and we went up that one all the way to the lake property. That leg woulda taken about an hour, but the BARGE BROKE DOWN. We towed that damn barge up this winding river (only barely wide/deep enough for the barge) with a jet boat, and a few guys with long poles trying to keep us from running aground on one side, then the next.
I'll just say that jet boats were never meant to tow anything big and heavy.:)
After 6 weeks camped out, the three of us finished building, & headed back in just the motorhome. Took 5 days, and a nasty blizzard followed us all the way from AK to the Washington border. Jeez.
The trip up was one of the prettiest drives I've ever been on. The trip back was pretty too, but I spent about half the time scared outta my mind. (Going down a steep, narrow, hairpin twisting grade on 2 inches of solid ice with crazy wind gusts and snow blowing everywhere... all while glancing nervously over the edge of an immediate 1000+ ft sheer drop into a rocky/snowy canyon on our right. That's what I remember most. Oh yeah, forgot to mention the big trucks coming the other way that own the road, period, and take however much room they need... lanes be damned. Whatcha gonna do, complain to the cops? They don't exist out here!)
Ah, it was great fun. Sometimes freaky, but I'd do it again in a minute.:)
Thats a great observation, and appears to be correct. It think there's another bit to add, though.
I think the "I-" designation sticks not only because they were the only interstates in town, but because they actually ARE interstates. In the true sense of the name. They aren't just interstates in the sense that they are large freeways that cut through town in various directions. They really are "true" interstates. They don't just stop or join something else at the edge of town... they actually go someplace else.
Such as, for example... Washington. Idaho. California. Other states... hence the name interstate.;)
OK, I'll grant that 205 crosses the river. But it still won't take you beyond the general Portland/Vancouver area.
I-5 and I-84 are the only interstates in town that can take you someplace far away. So they've earned the right to be called "I-". Or something like that.:)
Same here in the middle. Us Oregon folks call it I-5, too.
Let's see... up north it's I-5. Here it is I-5. I'm hearing a few different names down south, but I-5 is one of 'em. That's what my friends down there call it, too.
So I think it's safe to call it I-5. Although "the fucking five!" kinda has a nice ring to it, too.:)
I'll second that. I did Oregon to Minnesota & back a few years ago, and took that route. The gorge in Oregon, The mountains in Idaho/Monanta etc were great. Too bad going through Dakota sucked all the fun out of it.:)
Yeah. I've done that trip (Salem to LA & back) and it'd dead boring.
However, I've taken 101 all the way from LA to Lincoln City, then over to Salem. Much more interesting. The stretch of Oregon coast between Florence and Newport is particularly gorgeous.
I'd have to say I'd take I-5 over driving through S Dakota any day. Gawd. Nothing. Some Wall Drug signs for mild amusement, but that's it.
Now if I were to do something like this and had to pick a highway... without a doubt, the AlCan. The Alaska-Canada highway was one of the longest and most beatiful drives I've ever been on. Beat the hell out of Oregon to Georgia & back.
Since they are your students, you have the opportunity to inform them of that. Maybe give a class on all of the wizardry that makes what they hear... so different from the reality.
I've got recordings of Metallica raw material... their own demos and scratch tracks. They aren't hard to find. (Stuff like that for other artists may be.) The difference between those and the final mastered studio recording is a fascinating contrast for those that have never done any recording.:)
There's a million bands and musicians around the country trying to do just that. The number I know personally is staggering by itself.
Trouble is, "the system" (industry) rarely takes chances on them in return. They can't guarantee they can sell it as a product, so the musician is left to struggle and try to get their music out on their own. With whatever meager resources they may have.
If they're extremely lucky, they might get on an indy. They're usually full of good stuff, but they miss a lot too.
But if you really want to find passionate people making music for music's sake, go out and see some shows. Local venues, that will book local (and regional) artists. Go see those people. You might have to sit through a few turds, but there will be good stuff. Visit their websites of the ones you like and follow their links around to other locals. There may still be a lot you won't care for, but some real gems can be found that way.
Slashdot Mirror
I don't think this will ever fly, either. There is a lot of time/money invested in cataloging library materials... they can't afford books walking out the door with no accountability. Which I can GUARANTEE would happen in spades.
A deposit to cover the cost of the book isn't enough. Even a hefty processing fee wouldn't cover it. It's not just money, either... the library has chosen the item for a reason, and wishes it to be available to the public. When an item is lost&paid, it isn't available until it can be re-ordered/re-added, which takes time... enough of this takes place already (via both legitimate claims AND white lies) without helping it along with a "hey, it's like a bookstore!" option.
See, I work for a library (sysadmin) and I can tell you straight up that librarians don't actually give a crap about fines, fees, and replacement charges.
They just want their stuff back, so other people can use it. It's what we're here for, right? Fines are nothing more than a necessary incentive to bring stuff back when you are supposed to. So other people can use it. Without them, people wouldn't. Sometimes they don't anyway. Many libraries hold "amnesty weeks" on a regular basis to encourage people just to give us back the stuff, and we'll forget about the whole thing. Replacement charges are there to accomodate legitimate cases of patrons losing material, allowing them to make it right.
Amazingly enough, There are those that just take stuff and pay the charges anyway.
It's tough enough already to keep stuff from being stolen. Add an anonymous aspect to the "I can just pay for this item instead of return it" attitude... my goodness! How on earth would we keep half of the stuff from walking out the door for good?
Besides, this is a solution to a non-problem. Librarians are ingrained with the traditions of "freedom to read", and protecting patrons right to privacy in that regard. You think you hate the Patriot Act? Most librarians spit venom at any mention of it. (Not out on the floor with the public of course.)
I've sat in seminars with over a thousand of my peers (at vendor sponsored conferences, no less) where honoring those traditions and preserving patron privacy in the face of Patriot Act was the topic of the day. Presentations were given by libraries and organizations that fought it from the get-go. Not sure why I tell you this, other than perhaps hoping it inspires some kind of confidence.
If you are truly concerned about privacy, and how your library handles it, ask the librarians. They'll probably be happy to help you. They may even refer you to the director, invite you to a library board meeting, or put you in contact with a sysadmin that might be happy to chat. (Yeah, we're busy. But some stuff is important, and public perception of privacy is a biggie on that list.)
Have you discovered your library has no privacy policy, or a lousy policy? Ask about getting it changed. Talk to the Director. No luck? Go straight to the library board and hit them up with it. Still no luck? Ask the ALA what you can do about it. Put a bug in the local media's ear. If there is a "Library Friends" group of some kind, join it. Heck, get yourself on the library board. Don't just sit & bitch. Kick some ass!
Now, check this bit from the article:
Unfortunately, if an over-zealous special agent on a fishing expedition wants to know who checked out Anti-Flag's album The Terror State yesterday, the librarian will probably have little choice. Under the USA PATRIOT Act, he or she would have to surrender the personal identity information that was originally collected to protect the library's materials.
Yeah, well... there's a reason must of us purge logs that would disclose personal circulation history (and similar info) on a daily basis. Doesn't neccessarily have anything to do with the Patriot Act o
Excellent observation.
Now, a tidbit that should further clarify what was going on in that story...
In many ancient cultures (in particular Mesopotamian/Middle Eastern) to "name something" was to establish control/power/dominance over it. Basically names were very important and conferring a name on something meant you were the master of it.
Interestingly enough, the Genesis 2 creation account (there are two separate and different creation myths in Genesis) is by far the older of the two, predating the Priestly account (of Genesys 1, written during Babylonian captivity) by hundreds of years at the least.
Along w/the other poster...
I can assure you there are plenty of well educated people with decent language skills in the military. Not every single person of course... but no less a percentage than you'd find in any other slice of the common populace.
He vouched for the Army... I'm piping up for the USMC.
The terms you list are really no big deal anyway.
Common civilian opinion aside, it's certainly not some "dumb guys with guns" club. Your disclaimer of "no disrespect" is noted, but... you are in error with your underestimation.
Sand dunes are not snow, and they behave differently.
s .htm
You're right about the friction bit, and that going easy is a good idea. But sand does not melt and polish into ice, which gives you another option (and set of rules) to fall back on. In particular if we are talking about deep, loose sand on a slope... it may be your only option. Not all vehicles are equipped or capable, which is why you don't see them putting around on sand dunes.
With properly designed tread (paddles and similar designs) and sufficient wheelspeed, you CAN spin right out of sand. A change in weight distribution is also helpful, if possible. Of course, it is a risky proposition... lack of sufficient wheelspeed (or too slow of a transition from rest to full speed) will do exactly what you describe... dig you in deeper.
Basically you have to grip sand and throw it backward fast enough to push yourself forward. Sort of like a propeller, but not quite. You have to do it hard and fast enough so that you don't run out of propellent (sand) before you've gained enough momentum to keep from sinking into the sand. (If you've dug down to the floor of the vehicle, your wheels are left spinning in empty space, intead of throwing sand.)
Of course this is totally irrelevant in the case of the rover. Even with the right tread and motor capability they could not afford the power drain it'd take to do it.
And the other poster talking about air pressure is absolutely correct. You let just enough air out to increase the surface area, decreasing the pressure on the sand, enabling you to "float" on it a little better. It doesn't matter if you go slightly convex, either. (In fact it helps... the sand in the concave compresses and holds you up just a tad better.) There is no danger of this compression turning the sand into a slick solid with a wet surface, like there is with snow.
It sounds like you deal with snow a lot. I don't. But I grew up next to one of the best patches of dunes in the US, and used to play out there (in many different types of vehicles as well as on foot) on a regular basis. Not just weekends or special occasions, either. (Heading out for an hour or two after school was common.)
http://gorp.away.com/gorp/resource/us_nra/or_dune
Yeah, I know.
;)
Heck, our old practice studio was broken into and a bunch of stuff taken in a hurry. My bass, two guitars, etc.
That's rough, but doesn't stop you in your tracks. You can usually borrow or get what you need.
But everything at once, in mid-tour... ouch!
Now, I have to return to a local conversation about the issue, and on gear/trailer security in general.
Wow, that is a coincidence. I just heard of them for the first time today... but for rather sad reasons.
They just recently had their trailer stolen after a show in Portland OR. Nearly all of their equipment and instruments were stolen. They weren't insured against the loss. The trailer has been recovered, but was emptied out.
Word has been spread throughout the Portland musician community to be on the lookout for the gear, which is how I heard about it. (They published a list of everything, including serial numbers.)
Some of their fans set up a donation fund to help replace the gear... their tour dates are being postponed in the meantime, because they have no way to perform them.
All this can be found at http://www.decemberists.com/news
Most of the beaches around here aren't very wide... maybe 50-100 yards on average. (Bigger here, smaller there.) They also aren't very crowded at all... don't really need to fear crowds getting bottlenecked at escape points.
;)
:)
_ coast_87n_WP.jpg t %20029.jpg o rthwest/nw-oregon%20coast.jpg t /beach1.jpg
s 2/12.jpg s 2/29.jpg o re_acres_high.jpg s .jpg
Speaking of which, no bridges or anything like that. Beaches aren't really developed at all. You might have to run up a sand berm (full of dune grass), dirt trail, or clamber over some rocks to save time (instead of heading for a regular path)... but most places it's easy to get on/off of the beach itself.
At any of the beaches I frequent, You also gain elevation pretty quickly. Once you hit the edge of the beach, you are going up... could gain 30-50 feet in less than a minute. In some places 100 or more, if you can hack it.
In other words... you'd have to run for it, but you MIGHT just stand a chance, depending on where you are and how big it is. A 30-50 footer might get you wet, but given a minute or two you have a chance at getting to someplace where it might not kill you. Anyone know how long you get once that water starts heading out?
Everywhere else I go you don't need to run... you're already looking down at the ocean from a few hundred feet above it.
Here are some examples of our beaches:
http://www.picturesof.net/_wallpaper/brookings_gb
http://www.geomembrane.com/040227%20Oregon%20Coas
http://www.rawdonsbar.com/charliegallery/images/n
http://www.htmlhelp.com/~liam/Oregon/Coast/Newpor
Here are some pics of my favorite beaches... Sunset & Simpson Coves. (Collectively referred to as Shore Acres.) Most of the shots don't show the beaches themselves... you mostly see just the cliffs around them. (You've gotta hike some unmarked trails to get to where some of these shots were taken). But one is looking back at Sunset Cove from a tidepool area off to one side. (Note, I took none of these. Just found 'em at google. Apparently a few photographers know my spots!)
http://www.naosmm.org/confer/port-or/gifs/jackpic
http://www.naosmm.org/confer/port-or/gifs/jackpic
http://www.jobo-usa.com/gallery/images/surf_at_sh
http://www.hackstadt.com/adv/1998/195b-shore-acre
Some more good ones here:
http://www.coos-bay.net/coastalphotographs.html
Also grew up on the Oregon Coast. (North Bend/Coos Bay area) How the hell can you not know this? For the original poster's information, it is taught in schools. Some of them, at least.
;)
There are also tsunami warning signs at nearly every single beach, that even tell you about that particular warning sign if you bother to read them. I'm talking all over the Oregon coast, not just where I'm originally from.
There are even signs pointing out tsunami escape routes in some places.
Jeez... I thought everyone around here knew that stuff. Just like everyone knows about our rip-tides. Right??
It should be obvious at an elemental level... watch the waves at the beach any time. The water goes out, then comes back in with each wave. Well, if the water REALLY goes out... it's REALLY gonna come in! RUN!
Here is a not quite scientifically accurate (but not too far off) example that illustrates the effect pretty well for those that have trouble getting the concept:
Take a rectangular pan of water and give it a single good rock from one side to the other, then back. Note that the water on the first side gets really shallow while the water has gone to the other side. But then it comes crashing back along with the water from the other side, probably splashing out of the pan and getting all over the floor.
Not quite what happens with a tsunami, but the effect is similar. The big wave of energy rolls along till it hits shallow water, then starts to rise up. That rising water comes from somewhere... much of it from the beach ahead. Don't stick around to see where all that water went off to. It didn't go far, and it's gonna come right back atcha with a vengeance very quickly. Just like the pan of water in your kitchen, but amplified just a bit... let's say, a few million times or more.
Um... I've been using Netscape, Mozilla, other Gecko-based browsers, and Firefox on the Wells Fargo online banking site for years. (We're talking over 6 years, at least.) Usually from linux, sometimes from Winders.
Not a single problem, ever. Never had to touch browser reporting, either.
WTF are you talking about?
In addition, the sites that do have issues are becoming more and more rare. I maintain a bank of busy library public access machines running Firefox, so I hear about it whenever it happens. In other words, nearly (but not quite) never.
Now, you are dead on in the case of internal corporate sites and web applications. If there is a problem with Firefox support, that is where it lives.
Go in between.
Something capable of 2 legged upright motion.
But also capable of dropping horizontal to the surface. (Just like a real soldier)
Like an ant. Give it 6 limbs. Bottom two work as legs when upright, top two as arms. (Perhaps middle pair fold to sides.) Make the back most heavily armoured. Drop to ground to scurry around quickly like an ant, with a low profile. Stand up for longer range vision, more humanoid mobility, etc.
Go install DeMudi. It's Debian, but tweaked for audio & music production.
It "just works". Didn't have to do or set up squat... it was all there ready to rock as soon as the install finished. Hardware, software, ALSA, JACK, Ardour... the whole ball of wax.
Didn't even have to touch anything to get our Delta 1010 working.
I've shown the setup to peeps used to doing audio on windows, and left them in awe... asking me to burn a copy off for them. They've all come back to thank me a few days later.
Trust me... it's sweet as can be.
For some reason when reading it I could picture it in my head, but...
:)
It was accompanied by an overwhelming sense that my mind's picture was superimposed with the old farmer Neham's well. From Lovecraft's "The Colour Out of Space".
OK, the reactor light was blue while the color in the story was unidentifiable... but other than that they appeared so alike in my head as to really creep me out.
Even the results of exposure were horribly similar.
Maybe not, but he could always be the "Company Computer Guy".
Did I just say that?
Why yes, it does.
;)
Because this a recommended solution for those same IT people to implement. A way for them to keep those programmers happy and productive, without turning the rest of the users into proverbial bulls in china shops.
If they aren't interested in that... then they probably stopped reading already.
I don't buy your consequences for messing something up... not in most environments. Unless there was an additional rule. Let's say when a programmer messes up something that effects another network user's productivity (which might have been prevented if the admins had at least been consulted) that they get to face the chopping block too!
(I've seen it happen. Just as there are lousy admins, there are lousy programmers.)
I agree that's a dumb thing to lock down.
:)
Good policy for locking things down is to identify those types of things... wallpaper, colors, etc. Things that users like control over, but have nothing to do with functionality (and won't hurt anything.) Leave that stuff wide open.
With one exception... in some organizations there are machines that will be seen by customers, in a service desk type of setting. It isn't a bad idea to require a standard backdrop/appearance for those stations.
And hopefully put more thought into it beyond just choosing that ugly blue everyone hates.
Whoah. You sound pretty pissed. Chill.
Truth is, you're both right about your respective situations, and wrong about each others.
Those in programming jobs always seem to have a hard time understanding that they aren't the only people around using computers in their workplace. And not everyone works for a company that produces software. (For any company that doesn't, any programmers on board are support staff too.) The vast majority of people using computers at work have nowhere near the expertise programmers do. They just try to use the machine as a tool to do their work.
On the flip side, admins (at least the sort you are ranting about) are overexposed to those users with minimal experience and knowledge w/computing in comparison. (Anyone who admins those kinds of users can tell you they NEED to be restricted, or they WILL break everything in sight on a regular basis and support costs will go through the roof.) Trouble is they get stuck in that mindset... and put all users in that same boat. Which is a problem... particularly when managing machines for programmers. For all the reasons you give.
Solution? Easy...
Admins should treat programmers as a separate class from other users and give them permissions (within reason) to manage their own machines accordingly.
And programmers should understand that when admins are talking about needing to restrict users, they are talking about Joe MBA and Jane Marketing types, not you.
Sounds great.
:)
:)
We started in Salem w/a caravan of vehicles. (Dad purchased some property along the Susitna & we were going to build a big cabin. Bringing all the materials & tools with us!) A big flatbed truck, an old motorhome pulling a flatbed trailer, and a camper van pulling a jet boat. (A workhorse, not some ski boat or anything.)
Took 7 days to get to Wasilla. Then we chartered a barge to meet us at Deshka Landing & everything but the vehicles went on it. Following w/the boat it took a few hours to get down the Susitna river to a smaller river, and we went up that one all the way to the lake property. That leg woulda taken about an hour, but the BARGE BROKE DOWN. We towed that damn barge up this winding river (only barely wide/deep enough for the barge) with a jet boat, and a few guys with long poles trying to keep us from running aground on one side, then the next.
I'll just say that jet boats were never meant to tow anything big and heavy.
After 6 weeks camped out, the three of us finished building, & headed back in just the motorhome. Took 5 days, and a nasty blizzard followed us all the way from AK to the Washington border. Jeez.
The trip up was one of the prettiest drives I've ever been on. The trip back was pretty too, but I spent about half the time scared outta my mind. (Going down a steep, narrow, hairpin twisting grade on 2 inches of solid ice with crazy wind gusts and snow blowing everywhere... all while glancing nervously over the edge of an immediate 1000+ ft sheer drop into a rocky/snowy canyon on our right. That's what I remember most. Oh yeah, forgot to mention the big trucks coming the other way that own the road, period, and take however much room they need... lanes be damned. Whatcha gonna do, complain to the cops? They don't exist out here!)
Ah, it was great fun. Sometimes freaky, but I'd do it again in a minute.
Thats a great observation, and appears to be correct. It think there's another bit to add, though.
;)
:)
I think the "I-" designation sticks not only because they were the only interstates in town, but because they actually ARE interstates. In the true sense of the name. They aren't just interstates in the sense that they are large freeways that cut through town in various directions. They really are "true" interstates. They don't just stop or join something else at the edge of town... they actually go someplace else.
Such as, for example... Washington. Idaho. California. Other states... hence the name interstate.
OK, I'll grant that 205 crosses the river. But it still won't take you beyond the general Portland/Vancouver area.
I-5 and I-84 are the only interstates in town that can take you someplace far away. So they've earned the right to be called "I-". Or something like that.
Same here in the middle. Us Oregon folks call it I-5, too.
:)
Let's see... up north it's I-5. Here it is I-5. I'm hearing a few different names down south, but I-5 is one of 'em. That's what my friends down there call it, too.
So I think it's safe to call it I-5. Although "the fucking five!" kinda has a nice ring to it, too.
I'll second that. I did Oregon to Minnesota & back a few years ago, and took that route. The gorge in Oregon, The mountains in Idaho/Monanta etc were great. Too bad going through Dakota sucked all the fun out of it. :)
Yeah. I've done that trip (Salem to LA & back) and it'd dead boring.
However, I've taken 101 all the way from LA to Lincoln City, then over to Salem. Much more interesting. The stretch of Oregon coast between Florence and Newport is particularly gorgeous.
I'd have to say I'd take I-5 over driving through S Dakota any day. Gawd. Nothing. Some Wall Drug signs for mild amusement, but that's it.
Now if I were to do something like this and had to pick a highway... without a doubt, the AlCan. The Alaska-Canada highway was one of the longest and most beatiful drives I've ever been on. Beat the hell out of Oregon to Georgia & back.
Excellent point.
:)
Since they are your students, you have the opportunity to inform them of that. Maybe give a class on all of the wizardry that makes what they hear... so different from the reality.
I've got recordings of Metallica raw material... their own demos and scratch tracks. They aren't hard to find. (Stuff like that for other artists may be.) The difference between those and the final mastered studio recording is a fascinating contrast for those that have never done any recording.
There's a million bands and musicians around the country trying to do just that. The number I know personally is staggering by itself.
Trouble is, "the system" (industry) rarely takes chances on them in return. They can't guarantee they can sell it as a product, so the musician is left to struggle and try to get their music out on their own. With whatever meager resources they may have.
If they're extremely lucky, they might get on an indy. They're usually full of good stuff, but they miss a lot too.
But if you really want to find passionate people making music for music's sake, go out and see some shows. Local venues, that will book local (and regional) artists. Go see those people. You might have to sit through a few turds, but there will be good stuff. Visit their websites of the ones you like and follow their links around to other locals. There may still be a lot you won't care for, but some real gems can be found that way.
Er... better than the "Brown Note of Death" I suppose. ;)
No kidding. I'm not sure if I clicked anything wrong but...
:)
I happen to be a white dude with a shaved head and long red goatee.
That site tried to tell me I look like Barry White.
Um... OK.