Great, so now the network being down means I can get absolutely no work done.
This is already the case for many companies. If certain servers in our environment go down (requiring a hardware replacement and/or restore from tape, usually), they actually will send people home if management thinks people won't get much accomplished in the business day remaining after it's online, if it even comes back up before 5 PM.
If the email servers go down, everything comes to a screeching halt. Too much institutional knowledge is in our "groupware" and people can't seem to grasp the concept of communicating by phone or personal visit to someone's office.
IIRC, the Coral Cache folks themselves wrote one that adds 2 items to the link context menu, "Coralize Link" which opens the link via Coral, and "Coralize Link in New Tab" which should be relatively obvious from the previous description.
I think I'll stick with recording my exception logs in my own database where I have some measure of security around it, and can look at all of them, not the last 100.
Or one that GM has a minority stake in, like Subaru (GM has 20% of Subaru IIRC). I just bought an '03 Subaru and OnStar was an option then. When I was looking at the new ones on the lot, I didn't see OnStar on any of them, at least not "standard."
The wattage doesn't matter. It's the decibels and proximity to the ear. Those iPod earbuds aren't anywhere near 6 watts, let alone 60 watts, yet they'll do plenty of damage.
In the realm of online trading and other time-sensitive transactions, obviously it matters.
Outside that, as long as the reponse "feels" fast enough, and you're getting zero complaints, either it's good enough or no one's using it. Imposing artifical hard & fast numbers (like "no more than 5 second response time") leads to budget overruns and disappointment all around. The overall experience for the user is what's important. Your server logs will tell you if no one's using the app/site/system.
For example, this morning I went on my insurance company's site to get a quote on making a change to my policy. Moving from step to step of the "wizard" was pretty snappy. At the end, when they told me "ok, now we'll submit the quote", it took a little longer, but I also knew that at this point, it was more than data collection - it was actually crunching numbers. At this point, I think most users are accustomed to this.
I have worked on a few systems that had severe performance problems, and you will know when people aren't happy with performance - they speak up loudly and frequently. One of them, we were never able to really fix it, both because of architecture and beauracracy. The other, we found a huge speed boost on the front page, and even though I wasn't happy with response on a couple pages deeper in, users/management found it acceptable.
The die-hard fans who are complaining have already seen the movie and given their 10 bucks. I'm not dissing the casual market, but I'm guessing all of the Daredevil fans out there that considered the movie "sacrelige" did so after boosting the opening weekend gross quite nicely.
I'm barely a "casual" comic fan, but I was pissed that I dropped $17.50 (2 tickets at $8.75 each) on Daredevil. Not because it was a crappy film adaptation of a comic book (I know nothing of the DD backstory), not because it was "sacrilege", but because it just a bad movie, period - comic adaptation or not.
I've checked Salary.com for my job title and region, and found that it was about 20% higher than what I make. So either I'm being underpaid, people are lying about their jobs/salaries, or only the ones making the big bucks are there bragging about it. I don't think it's that I'm underpaid, because most companies are interested in offering me 20%-30% less than my current salary.
The job market is whacked right now. There is almost certainly someone else who'll do your job for a significantly lower amount just so that they have any job, and that makes it harder to get what you really want. Because to that person, taking a job for 50% what the salary should be still beats living off savings and low-interest credit cards.
It wouldn't hurt our allies and those we've helped in the past to say "hey, guys, you need a hand?"
Right now it looks like the primary need isn't money, it's manpower/equipment, medical attention, sustenance, and shelter. All things that can be flown in from anywhere.
The Coast Guard (and National Guard, and others) is flying round the clock to lift people off rooftops, but the crews are going to be fatigued fast and there aren't enough choppers to get to everyone in time.
Potable water is needed everywhere, and people need to eat.
Medical - obvious. Diabetics need their insulin refrigerated and their properly-sized meals.
Shelter - again, should be obvious. People need safe, dry places to sleep.
Whether it actually did anything to patch a vulnerability would be a secondary issue, and not nearly as important.
Surely that is what *is* important.
You'd think so, but actually no. What we're being checked for is "is the OS/software up to date with all security patches that have been released?" If the answer is yes, then we're clean. Now, if there's an exploit that a patch is issued for, but the patch doesn't entirely cover it, what are we to do? We're in compliance with patching rules (we've got all the patches that we could possibly install), but we've still got a compromisable system. At which point, the issue is with the vendor, not our procedures (just like with SOX - it doesn't matter how screwball your rules and procedures are, as long as you follow them you're in the clear).
We got slammed by a regulatory agency a few years ago because we were woefully behind on keeping systems patched. We're now current with our patches, and that's what they were concerned about.
When you have a couple hundred servers and various regulatory agencies breathing down your neck about not having your OS patches up to date, you can't take a lot of time manually looking at a patch and saying "well, on box A we don't use what patch 1 fixes, so we won't install it there. But we will do it on box B, and we don't need patch 2 on box B but we do need it on A"
As I understand the process, we scan our environment using tools like Shavlik to find out what servers are missing what patches, based on the patches released by MS, file versions on the servers, etc. If a patch only applies to one DLL, and a particular server doesn't even have a copy of that DLL on it, then the patch doesn't get installed (or if it's attempted, it'll exit without installing anything. The tool then distributes and installed the required patches to each server. We install to our dev and integration testing environments on consecutive evenings, and spend the following day checking that nothing broke. If all's well, we go forward with the production servers.
We don't validate that it "installs without errors" as that would be short-sighted - we validate that it installs cleanly and, more importantly, doesn't break our applications. In some cases, we've had to force-feed a patch onto a particular box. In other cases, the patch has reset a config setting to its factory default and we've had to go in and clean up after it. If a patch really, really hoses something, we'll back out, retest (to make sure the backout was clean), then re-evaluate.
But generally, we don't have significant trouble with MS's patches. They've gotten much better over the last couple years.
The people who usually bitch about certifications are the ones who have met a person who is an MSCE and is an idiot
Several years ago, nearly all our Windows admins were MS-certified, and our servers were a disaster. They honestly believed that the best way to distribute anything to the servers was via a floppy, carried from box to box. One of them was well-known to have the domain admin ID and password under his keyboard. And I don't mean "everyone in the datacenter" - I mean a third of the entire IT department knew it.
All the certified ones left (via a variety of methods, most of them not entirely voluntary), and the non-MS-certified replacements/guys remaining whipped our datacenter into shape astonishingly quickly. We now have MS's monthly patches evaluated, tested and rolled out in under a week, and management of them is entirely centralized. The systems are more stable and more secure.
With all the religions and traditions in our society you'd think people would be more understanding and accepting of differences
Many religions have a long, long history of being neither accepting nor understanding of "differences." How many wars have been started because one guy prayed to a different invisble man in the sky than another guy (paraphrasing Carlin)?
How many are physical defects vs. user incompetence vs. software issues (both bad/deteriorating software and viruses/malware (which could also be user incompetence))?
If you don't want to keep it you can always sell them after use, and probably recover more than a third of the original price.
I went to sell my old textbooks on Amazon.com a few months ago and found that I could actually make a profit on them! For example, my Operating Systems book ("the Dragon Book") had a $60 sticker on it from when I bought it in '98 or '99. Amazon was selling it new for over $100, my copy wasn't horribly abused, so I listed it for $80.
Lesson: Do not sell your textbooks back to the college bookstore. You'll get shafted. Do it online.
He probably has a standing offer from the landlord to buy the house he's renting. The landlord's already paid off the mortgage on the house (and then some) with the rent money, so he can say "well, you've already paid $20K into what the house is worth to me, so I'll knock that off the appraised value when you want to buy it off me."
No, he wants a small switch (actually, he asked that I purchase a "router" complete with a WAP built in, even though the company doesn't support wireless networks and it'd be a big security problem if left open) just in my cube to serve only me. I'm one of a very few people who have a second computer, so the idle LAN drops in the other 90% of cubes (yes, they wired 2 for each cube, but don't use them) are going to remain idle for a very, very long time.
Wait till bosses realise that a $500 piece of kit and a couple of days setting up could be replaced by 5 mins configuration by a dolt.
You sure about that? My boss told me to buy a switch so that I could have additional ports in my cube (I have 2 and need 2, but one is used by the workgroup printer), as opposed to having someone move the printer 6 feet to hook up to an unused second port in another cube - or just get a longer LAN cable.
IE/Win 5.x gets the box model wrong. IE6, if you don't specify a DOCTYPE, will behave the same. However, if you do specify a DOCTYPE, it will follow the box model correctly.
They could (should?) extend this in IE7. Specify a DOCTYPE, it behaves properly. Pop into quirks mode, and it acts like IE of old.
Re:Another web developer here...
on
IE7 Bugs and Reviews
·
· Score: 2, Informative
CSS, HTML and JavaScript affect me more than PNG, but that's just me.
Re:Does it support W3C standards?
on
IE7 Bugs and Reviews
·
· Score: 5, Informative
From what I've read so far (direct from MSDN), there's nothing that significantly improves the lives of web developers. Only 2 of the many CSS bugs have been resolved, no improvement in CSS implementation/support, no good debug tools.
Slashdot Mirror
If the email servers go down, everything comes to a screeching halt. Too much institutional knowledge is in our "groupware" and people can't seem to grasp the concept of communicating by phone or personal visit to someone's office.
IIRC, the Coral Cache folks themselves wrote one that adds 2 items to the link context menu, "Coralize Link" which opens the link via Coral, and "Coralize Link in New Tab" which should be relatively obvious from the previous description.
I think I'll stick with recording my exception logs in my own database where I have some measure of security around it, and can look at all of them, not the last 100.
Or one that GM has a minority stake in, like Subaru (GM has 20% of Subaru IIRC). I just bought an '03 Subaru and OnStar was an option then. When I was looking at the new ones on the lot, I didn't see OnStar on any of them, at least not "standard."
The wattage doesn't matter. It's the decibels and proximity to the ear. Those iPod earbuds aren't anywhere near 6 watts, let alone 60 watts, yet they'll do plenty of damage.
In the realm of online trading and other time-sensitive transactions, obviously it matters.
Outside that, as long as the reponse "feels" fast enough, and you're getting zero complaints, either it's good enough or no one's using it. Imposing artifical hard & fast numbers (like "no more than 5 second response time") leads to budget overruns and disappointment all around. The overall experience for the user is what's important. Your server logs will tell you if no one's using the app/site/system.
For example, this morning I went on my insurance company's site to get a quote on making a change to my policy. Moving from step to step of the "wizard" was pretty snappy. At the end, when they told me "ok, now we'll submit the quote", it took a little longer, but I also knew that at this point, it was more than data collection - it was actually crunching numbers. At this point, I think most users are accustomed to this.
I have worked on a few systems that had severe performance problems, and you will know when people aren't happy with performance - they speak up loudly and frequently. One of them, we were never able to really fix it, both because of architecture and beauracracy. The other, we found a huge speed boost on the front page, and even though I wasn't happy with response on a couple pages deeper in, users/management found it acceptable.
I've checked Salary.com for my job title and region, and found that it was about 20% higher than what I make. So either I'm being underpaid, people are lying about their jobs/salaries, or only the ones making the big bucks are there bragging about it. I don't think it's that I'm underpaid, because most companies are interested in offering me 20%-30% less than my current salary.
The job market is whacked right now. There is almost certainly someone else who'll do your job for a significantly lower amount just so that they have any job, and that makes it harder to get what you really want. Because to that person, taking a job for 50% what the salary should be still beats living off savings and low-interest credit cards.
What!? My mother was a saint!
It wouldn't hurt our allies and those we've helped in the past to say "hey, guys, you need a hand?"
Right now it looks like the primary need isn't money, it's manpower/equipment, medical attention, sustenance, and shelter. All things that can be flown in from anywhere.
The Coast Guard (and National Guard, and others) is flying round the clock to lift people off rooftops, but the crews are going to be fatigued fast and there aren't enough choppers to get to everyone in time.
Potable water is needed everywhere, and people need to eat.
Medical - obvious. Diabetics need their insulin refrigerated and their properly-sized meals.
Shelter - again, should be obvious. People need safe, dry places to sleep.
We got slammed by a regulatory agency a few years ago because we were woefully behind on keeping systems patched. We're now current with our patches, and that's what they were concerned about.
When you have a couple hundred servers and various regulatory agencies breathing down your neck about not having your OS patches up to date, you can't take a lot of time manually looking at a patch and saying "well, on box A we don't use what patch 1 fixes, so we won't install it there. But we will do it on box B, and we don't need patch 2 on box B but we do need it on A"
As I understand the process, we scan our environment using tools like Shavlik to find out what servers are missing what patches, based on the patches released by MS, file versions on the servers, etc. If a patch only applies to one DLL, and a particular server doesn't even have a copy of that DLL on it, then the patch doesn't get installed (or if it's attempted, it'll exit without installing anything. The tool then distributes and installed the required patches to each server. We install to our dev and integration testing environments on consecutive evenings, and spend the following day checking that nothing broke. If all's well, we go forward with the production servers.
We don't validate that it "installs without errors" as that would be short-sighted - we validate that it installs cleanly and, more importantly, doesn't break our applications. In some cases, we've had to force-feed a patch onto a particular box. In other cases, the patch has reset a config setting to its factory default and we've had to go in and clean up after it. If a patch really, really hoses something, we'll back out, retest (to make sure the backout was clean), then re-evaluate.
But generally, we don't have significant trouble with MS's patches. They've gotten much better over the last couple years.
All the certified ones left (via a variety of methods, most of them not entirely voluntary), and the non-MS-certified replacements/guys remaining whipped our datacenter into shape astonishingly quickly. We now have MS's monthly patches evaluated, tested and rolled out in under a week, and management of them is entirely centralized. The systems are more stable and more secure.
Not only do the "designers" think it looks good, the (l)users demand it, saying that default-coloured scrollbars ruin the look of the site.
It will never come to fruition. They have purposely left off any indication of a timeframe because they don't really intend to do it.
How many are physical defects vs. user incompetence vs. software issues (both bad/deteriorating software and viruses/malware (which could also be user incompetence))?
Lesson: Do not sell your textbooks back to the college bookstore. You'll get shafted. Do it online.
He probably has a standing offer from the landlord to buy the house he's renting. The landlord's already paid off the mortgage on the house (and then some) with the rent money, so he can say "well, you've already paid $20K into what the house is worth to me, so I'll knock that off the appraised value when you want to buy it off me."
more fine works like Deep Impact and Chain Reaction.
Oh yeah, the parts of Contact that I saw sucked too. Keep trying, Hollywood!
No, he wants a small switch (actually, he asked that I purchase a "router" complete with a WAP built in, even though the company doesn't support wireless networks and it'd be a big security problem if left open) just in my cube to serve only me. I'm one of a very few people who have a second computer, so the idle LAN drops in the other 90% of cubes (yes, they wired 2 for each cube, but don't use them) are going to remain idle for a very, very long time.
Not necessarily.
IE/Win 5.x gets the box model wrong. IE6, if you don't specify a DOCTYPE, will behave the same. However, if you do specify a DOCTYPE, it will follow the box model correctly.
They could (should?) extend this in IE7. Specify a DOCTYPE, it behaves properly. Pop into quirks mode, and it acts like IE of old.
The documentation is publicly available. No need to join MSDN (I haven't even installed the beta anywhere for lack of an available box) http://msdn.microsoft.com/library/default.asp?url= /workshop/essentials/whatsnew/whatsnew_70_sdk.asp
Says only Alpha Channels have been added.
CSS, HTML and JavaScript affect me more than PNG, but that's just me.
From what I've read so far (direct from MSDN), there's nothing that significantly improves the lives of web developers. Only 2 of the many CSS bugs have been resolved, no improvement in CSS implementation/support, no good debug tools.
So IE7 will continue holding us back.