Access Manager is an extremely capable enterprise class single-sign-on product (It's the current incarnation of Novell's iChain SSO product). I'm using it here to protect about 30+ backed web-applications. I can do access restrictions based on LDAP group memberships, inject identity information in http headers, do behind the scenes form-fill login for applications that wouldn't know what SSO was if it fell on them and so much more. Currently just finished a Radius server integration for 2 factor auth. It's one of the two best pieces of enterprise software I've ever used. (Riverbed's Stingray appliance being the other).
Yes, in the effort to make trucks more economical, they've really engineered out a of ruggedness. I can flex a body panel on any new truck by leaning on it. I can lean hundreds of pounds against my '81 Ford with no visible deflection in the panel. Its possible this is a way to actually address these concerns of people who use trucks have. Can we make things stronger and lighter at the same time? I'm cautiously optimistic that this won't suck and will actually make the trucks better.
Of course there is always the view that the language you "learn" with in school is largely irrelevant, learning how to develop software and solve problems is the skill. The underlying concepts are what's important, not that you understand the specific syntax of the language -- My undergrad program was taught *entirely* in Java -- I haven’t written a single line of Java code since graduation.
Second is that it is MUCH easier to control emission at the generating station than it is to try to do it on every tailpipe out there. Would you rather have one big filter or millions of small ones?
Of course it's much easier to control one point than many, but until the EPA gets serious about a carbon cap or other controls on the dirtiest power plants -- I'll stand by my argument.
Instead of coal you can power it with natural gas or even oil.
You *can*, but many folks don't have the option of choosing where their power comes from.
'based on a Lotus Elise' would be the Tesla *Roadster* - which they haven't produced for a couple of years now. the car everyone is talking about in this story is the Model S, which is built from the ground up by Tesla as a pure electric vehicle, and is therefore a much more optimal solution.
Oh, I don't doubt that it's a fine electric automobile, based on a Lotus Elise, it would be hard to make it bad, however; the very concept of a battery car is what I take issue with, as a gear-head I have just a have a personal prejudice against.
Personal prejudices and preferences aside, my biggest issue with electric cars is that you're really just shuffling the emissions around. Instead of the source of pollution being from a very tightly regulated source (tail-pipe emissions), they are now likely to come from a largely unregulated and dirty power plant -- 42% us power came from coal in 2011. Until we get a point of 100% clean renewable energy, I'm not sure the trade-off is worth it.
I'm sorry, I just don't care for battery cars, just like I don't care for iDevices -- perhaps the (dumb) analogy is more accurate than the author intended.
Verizon has all but abandoned the copper infrastructure around here. It's FIOS or nothing. No new TP copper installs. No TP copper repairs! The "repair" for being on a bad pair was the FIOS installation guy showing up my door. No thanks.
Among the employees of a University, Faculty are the 1st class citizens. Us staff folks are not. We are subject to all the normal stuff that you would expect of any employer. Faculty just have a different relationship with their employer. Not making a judgment call on this, I'm just stating the reality of the situation.
As faculty, I would expect that my email would not be ready without my knowledge and that there would be some sort of committee to determine if HR had the right or reasonable cause to search my email before it happened.
As staff, every bit I generate is subject to search and inspection...including these made on "company time".
Around here I pay $0.18 per kWH. My Server draws about 90W -- That's about $11-12/month. My hardware was free, though I put a couple $$ worth of upgrades into it -- though, I havn't spent any money on hardware for it in the last 3 years. Also, the key to running your own stuff, is that you own it, which is something that's tough to put a price on, but I'd say has quite a high value.
Hmm, yes, My 3000 is sitting on cardboard to keep the goo contained. It's a 700, with the EV45+ 225 Mhz chip. I don't run it all the time as the sucker pulls 250 watts just sitting there idle. Though running the VAMP stack on it is entertaining...and a good conversation starter.
Yeah, the job I just recently left, definitely still had some a few of these running in production. They were legacy systems, scheduled to be decommissioned within the next year or two...but still, not quite vintage.
My own "vintage" collection, is a mid 90's DEC 3000 running VMS 8.4, An HP ML370 G2, which runs my home network, network storage, email, and a some websites, Then there are the IBM XTs and 8-bit ataris, though they don't get much play these days.
Use a Web CMS (Wordpress or Drupal) and pickup a book on building your own theme. Using an IDE would probably be the most sane approach. A lot of the starter themes supplied are already setup pretty good for SEO and some are even on their way to Section 508 compliance. This lets you concentrate on design and functionality (through add-on modules) without reinventing multiple wheels.
Save the handcoding for a hobby -- just like I save screwing with old hardware as a hobby (as much fun as my IBM AT is to play with) -- use modern tools and a modern approach to do real work.
But the first step, should be what are the customer's requirements and figure what tools best fit that job.
Actually, many trucking firms put 1,000,000 + on their vehicles before retiring them. UPS, in particular are fanatical about maintenance, and the brown trucks are good for 20-25 years of delivery service...
There is so much going on in this thread....where to start.
I live 50 miles from work. It takes me between 1 and 1.5 hours each way. It's horrendous, but it's what I have to do. I got a great job that pays well, lots of opportunities for my future, etc etc. This, after I bought a house and the housing market crashed. So, I do the commute. If I sell the house now, I'll take too big of a loss, I wont be able to afford anything comparable close to my job. So, I commute in a paid off 20 yr old car that gets 20 mpg. Ideal? Not at all, but it would take me years of commuting a lesser distance to make up for the loss on the house. I could get a better job, but not one that would be as good as this one for my career right now. Maybe in another year or two.
As for my location, I live in a Northern NJ suburb. I commute south to Mercer County. All Mass transit New Jersey runs to NYC. It would take me 3 hours each way and 2x the cost of gas to take NJTransit to work -- not worth it.
As far as mass transit in general goes: I've traveled in the UK and Europe. Some of by Train, some of it by car where the trains don't go -- that's right there are rural parts of Europe too, it's not just one big city. When you get out of the populated areas, you still need a car. There is no mass transit in the Scottish Highlands, just a lot of sheep farmers.
When it comes to the US, our cities could absolutely do with better mass transit. Some places have decent options from suburbs into City Centers, though it's still a major PITA. In general though, it's an issue of scale here, especially when talking about travel between city centers, unless you're talking about Amtrak's NorthEast Corridor Line (Between Boston and DC) Intercity mass transit virtually non-existent. I highly recommend to all of you to take a Coast to Coast trip across the US someday. I did it with my wife (then gf) about 5 years ago -- it was a real eye opening experience -- this place is f-ing huge! It's an easy 5 day drive -- you can do it in 4 if you really push. The only real option for speedy travel between city centers is by air -- though the TSA has pretty much ruined that a pleasant alternative. Also, while the flight is only two hours to Boston, add the trip to the airport, plus 2 hours for security, 45 minutes for delay at Newark, plus collecting bags, rent a car, etc in Boston -- Guess what, I can drive it in 5 for less $.
Smoothness:
One of the neat things about a rotary is that the faster it spins the more stable the combustion becomes. Where as many piston engines will be about ready to shake themselves to pieces at 7K, a rotary couldn't be happier there.
Power Delivery:
The torque curve on a rotary is very flat. This is due to lack of valve timing issues. This means you get a really smooth pull all the way to redline without being peaky.
Uniqueness:
Something a bit different is nice now and again.
I'm currently the admin for our SharePoint 2007 system. I agree, the product is a cesspool of poor code and limited functionality. I've administered several WebCMSs over the years and SharePoint is by far the worst. It's a blackbox where the buttons are either not labeled, poorly labeled, or mis-labeled all together.
What Bigbutt says about an his companies upgrade to 2010 sounds about right. We're currently testing SharePoint 2010. While the backend architecture is actually much better than in 2007, there is still a lot of Beta quality code in the software. We've actually stopped testing on 2010 until SP1 comes out, hoping it's better.
I hate the Windows centric half I my job. I love the Linux half. The sooner I can dump this SharePoint Turd on someone else (as it was dumped on me) the better.
Slashdot Mirror
30 Million! My AM environment is serving barely 5K. I'd love to get some details on your infrastructure. How many IDPs and AGs are you running?
Access Manager is an extremely capable enterprise class single-sign-on product (It's the current incarnation of Novell's iChain SSO product). I'm using it here to protect about 30+ backed web-applications. I can do access restrictions based on LDAP group memberships, inject identity information in http headers, do behind the scenes form-fill login for applications that wouldn't know what SSO was if it fell on them and so much more. Currently just finished a Radius server integration for 2 factor auth. It's one of the two best pieces of enterprise software I've ever used. (Riverbed's Stingray appliance being the other).
Yes, in the effort to make trucks more economical, they've really engineered out a of ruggedness. I can flex a body panel on any new truck by leaning on it. I can lean hundreds of pounds against my '81 Ford with no visible deflection in the panel. Its possible this is a way to actually address these concerns of people who use trucks have. Can we make things stronger and lighter at the same time? I'm cautiously optimistic that this won't suck and will actually make the trucks better.
Of course there is always the view that the language you "learn" with in school is largely irrelevant, learning how to develop software and solve problems is the skill. The underlying concepts are what's important, not that you understand the specific syntax of the language -- My undergrad program was taught *entirely* in Java -- I haven’t written a single line of Java code since graduation.
Second is that it is MUCH easier to control emission at the generating station than it is to try to do it on every tailpipe out there. Would you rather have one big filter or millions of small ones?
Of course it's much easier to control one point than many, but until the EPA gets serious about a carbon cap or other controls on the dirtiest power plants -- I'll stand by my argument.
Instead of coal you can power it with natural gas or even oil.
You *can*, but many folks don't have the option of choosing where their power comes from.
'based on a Lotus Elise' would be the Tesla *Roadster* - which they haven't produced for a couple of years now. the car everyone is talking about in this story is the Model S, which is built from the ground up by Tesla as a pure electric vehicle, and is therefore a much more optimal solution.
you're right, mea culpa.
Oh, I don't doubt that it's a fine electric automobile, based on a Lotus Elise, it would be hard to make it bad, however; the very concept of a battery car is what I take issue with, as a gear-head I have just a have a personal prejudice against.
Personal prejudices and preferences aside, my biggest issue with electric cars is that you're really just shuffling the emissions around. Instead of the source of pollution being from a very tightly regulated source (tail-pipe emissions), they are now likely to come from a largely unregulated and dirty power plant -- 42% us power came from coal in 2011. Until we get a point of 100% clean renewable energy, I'm not sure the trade-off is worth it.
I'm sorry, I just don't care for battery cars, just like I don't care for iDevices -- perhaps the (dumb) analogy is more accurate than the author intended.
Really?
Verizon has all but abandoned the copper infrastructure around here. It's FIOS or nothing. No new TP copper installs. No TP copper repairs! The "repair" for being on a bad pair was the FIOS installation guy showing up my door. No thanks.
Oh for a Mod point. This is exactly it.
Among the employees of a University, Faculty are the 1st class citizens. Us staff folks are not. We are subject to all the normal stuff that you would expect of any employer. Faculty just have a different relationship with their employer. Not making a judgment call on this, I'm just stating the reality of the situation.
As faculty, I would expect that my email would not be ready without my knowledge and that there would be some sort of committee to determine if HR had the right or reasonable cause to search my email before it happened.
As staff, every bit I generate is subject to search and inspection...including these made on "company time".
Around here I pay $0.18 per kWH. My Server draws about 90W -- That's about $11-12 /month. My hardware was free, though I put a couple $$ worth of upgrades into it -- though, I havn't spent any money on hardware for it in the last 3 years. Also, the key to running your own stuff, is that you own it, which is something that's tough to put a price on, but I'd say has quite a high value.
Hmm, yes, My 3000 is sitting on cardboard to keep the goo contained. It's a 700, with the EV45+ 225 Mhz chip. I don't run it all the time as the sucker pulls 250 watts just sitting there idle. Though running the VAMP stack on it is entertaining...and a good conversation starter.
Yeah, the job I just recently left, definitely still had some a few of these running in production. They were legacy systems, scheduled to be decommissioned within the next year or two...but still, not quite vintage.
My own "vintage" collection, is a mid 90's DEC 3000 running VMS 8.4, An HP ML370 G2, which runs my home network, network storage, email, and a some websites, Then there are the IBM XTs and 8-bit ataris, though they don't get much play these days.
...Like we used to say in the shop -- Cross threads are better than no threads!
Seriously, back it out and try again, does wonders sometimes.
Use a Web CMS (Wordpress or Drupal) and pickup a book on building your own theme. Using an IDE would probably be the most sane approach. A lot of the starter themes supplied are already setup pretty good for SEO and some are even on their way to Section 508 compliance. This lets you concentrate on design and functionality (through add-on modules) without reinventing multiple wheels.
Save the handcoding for a hobby -- just like I save screwing with old hardware as a hobby (as much fun as my IBM AT is to play with) -- use modern tools and a modern approach to do real work.
But the first step, should be what are the customer's requirements and figure what tools best fit that job.
Why would you use an Atari 2600 for playing games? All the games are on the PDP11.
Yes, it is a clbuttic mistake:
http://thedailywtf.com/Articles/The-Clbuttic-Mistake-.aspx
(the comments are genius)
Actually, many trucking firms put 1,000,000 + on their vehicles before retiring them. UPS, in particular are fanatical about maintenance, and the brown trucks are good for 20-25 years of delivery service...
But your point is otherwise valid.
There is so much going on in this thread....where to start.
I live 50 miles from work. It takes me between 1 and 1.5 hours each way. It's horrendous, but it's what I have to do. I got a great job that pays well, lots of opportunities for my future, etc etc. This, after I bought a house and the housing market crashed. So, I do the commute. If I sell the house now, I'll take too big of a loss, I wont be able to afford anything comparable close to my job. So, I commute in a paid off 20 yr old car that gets 20 mpg. Ideal? Not at all, but it would take me years of commuting a lesser distance to make up for the loss on the house. I could get a better job, but not one that would be as good as this one for my career right now. Maybe in another year or two.
As for my location, I live in a Northern NJ suburb. I commute south to Mercer County. All Mass transit New Jersey runs to NYC. It would take me 3 hours each way and 2x the cost of gas to take NJTransit to work -- not worth it.
As far as mass transit in general goes: I've traveled in the UK and Europe. Some of by Train, some of it by car where the trains don't go -- that's right there are rural parts of Europe too, it's not just one big city. When you get out of the populated areas, you still need a car. There is no mass transit in the Scottish Highlands, just a lot of sheep farmers.
When it comes to the US, our cities could absolutely do with better mass transit. Some places have decent options from suburbs into City Centers, though it's still a major PITA. In general though, it's an issue of scale here, especially when talking about travel between city centers, unless you're talking about Amtrak's NorthEast Corridor Line (Between Boston and DC) Intercity mass transit virtually non-existent. I highly recommend to all of you to take a Coast to Coast trip across the US someday. I did it with my wife (then gf) about 5 years ago -- it was a real eye opening experience -- this place is f-ing huge! It's an easy 5 day drive -- you can do it in 4 if you really push. The only real option for speedy travel between city centers is by air -- though the TSA has pretty much ruined that a pleasant alternative. Also, while the flight is only two hours to Boston, add the trip to the airport, plus 2 hours for security, 45 minutes for delay at Newark, plus collecting bags, rent a car, etc in Boston -- Guess what, I can drive it in 5 for less $.
I've worked with windows -- first in 1996 and most recently December 2011. It is as user unfriendly now as it was in 1996.
Smoothness: One of the neat things about a rotary is that the faster it spins the more stable the combustion becomes. Where as many piston engines will be about ready to shake themselves to pieces at 7K, a rotary couldn't be happier there. Power Delivery: The torque curve on a rotary is very flat. This is due to lack of valve timing issues. This means you get a really smooth pull all the way to redline without being peaky. Uniqueness: Something a bit different is nice now and again.
Give jolkona.org a look. As I understand it, it's pretty much exactly like kickstarter for charities.
I wonder why Eric Idle decided not to join in?
+1 I'd love to see how you set this up.
What Bigbutt says about an his companies upgrade to 2010 sounds about right. We're currently testing SharePoint 2010. While the backend architecture is actually much better than in 2007, there is still a lot of Beta quality code in the software. We've actually stopped testing on 2010 until SP1 comes out, hoping it's better.
I hate the Windows centric half I my job. I love the Linux half. The sooner I can dump this SharePoint Turd on someone else (as it was dumped on me) the better.