Wrong. It will be in the next version of VS. Right now, it is a pretty awful implementation for TDDers (very slow, but some cool integration features), but they are working on making that better.
Not that I agree with what is going on with Jamie. All he ever asked for was the clause he was violating and he would happily remove it. They haven't provided that yet.
I worked for Hillsborough County and got the pleasure of having her as a commissioner. It really does amaze me sometimes how little the media around here pays attention to things.
At least I know why I couldn't find a good used CD shop in Tampa anymore.
I did. This certainly wasn't my first job, so I knew what to do. But they refused to give me any more information then that, basically just letting it go.
No matter, I took a job with a competitor. They may not have all of the fancy benefits, but they have great insurance, interesting people, and it's fun to tout Linux on the internal mailing lists.;)
I interviewed with them about a year and a half ago. The first interview was awesome - lasted about 3 hours on the phone, and we talked about a multi-threading race condition. The second interview was really short, and it seemed to go well. I got a call from the hiring manager that they weren't continuing on because they didn't like the way I "thought".
Oh well, we really weren't sure about moving to Mountain View anyway. But I sure wish I knew what the heck that meant.
Actually, it depends on how large of an installation you have. As usual, money talks.
But that's not entirely true. I worked for a small company and we were writing our own wrapper around Reporting Services, and found a bug, and they got a hotfix to us that day. We had no fancy contract - we were using one of our free support incidents.
I've seen my share of bugs that won't be fixed too - but I've seen those in the open source projects I've been a part of as well.
Even if you build it, they may not come. Someone could release an outlook/exchange replacement tomorrow and it may very well have zero-effect.
There's something else in that. Sure, people are buying Exchange and Outlook because of their feature set. But they also buy them for the support.
Let's say that the Thunderbird/Google/OpenOffice trifecta becomes your corporate IT standard. Now let's say you have a problem. With Google, you have a company to call, but I don't know how good their support it. Thunderbird and OpenOffice have the support of the community, which may lead to faster fixes, but may also depend on who is available when.
Don't get me wrong. I'm not an MS fanboy. But I'm seeing more and more that companies I go into choose MS solutions because it has the features they need and a face to yell at if something goes wrong. When OSS can provide the feature set *and* the unified support, it will be hard to beat.
The funny thing is that the cross-platform solution Microsoft recommends for developers needing to work with VS Team System and Team Foundation Server is Java-based from Teamprise.
I never did understand why they would push that over a Mono-based solution for Linux.
Re:Author's credentials? And too specialized?
on
Pro Java ME MMAPI
·
· Score: 1
Actually, there isn't a lot of filler (Disclosure: I'm the reviewed;)). The book is pretty short, and a very fast read. I read it in about 2 hours on a trans-atlantic flight.
The book is pretty specialized, and it probably would fit well into an ME book, but I think it fills a good niche if you are having to do these kinds of things.
And, since the story is about to drop off the main screen, looks like this review will set a record for the lowest number of comments on a front-page story.;)
I would be willing to bet big money that if MS did anything it lobbied against this change. It is a Really Big Deal, and not something that is easy to just modify.
Also, by the US doing this it created more time zones. How? Mexico is choosing not to go along with the DST updates, therefore anywhere in Mexico using PST effectively isn't anymore.
Huh? How does that happen, assuming you're a good boy and using timestamps in UTC in the first place? You know, the ones that look like "Sat, 3 Mar 2007 08:06:08 -0800 (PST)", the ones you find in e-mail headers for example?
The problem is when that gets interpreted to the local machine.
Let's say you schedule the above meeting during the DST change. If I don't have the update, when I get the alert, it will be an hour off because the calculation to local time will take into account the DST rules for you, but not for me.
As an engineer who is right in the middle of helping our customers make the changes necessary for the DST fix, it is much more complicated than that.
First, you have all of the servers and clients which rely on one another. The biggest effect is on mail - Exchange/Outlook/OWA.
Second, you have to do it in the right order, at about the same time. If you update the server, then clients who schedule appointments will be off until they update.
Third, you've got software which calculates various things based on that date. Think financial transactions, etc.
I wish it was as easy as just updating a script, but when you have to coordinate that change across 10s or 100s of thousands of servers, clients, etc, it's not an easy task.
And let's not forget Microsoft isn't the only one having to make changes. Lotus Notes, Groupwise, Blackberries - they all have changes that have to be made. I'll personally be glad when this is all done. Ugh.
In the past 6 years I've had 6 different jobs. They looked like:
3 years with a government org 6 months with a startup as an independent contractor 3 months as a contractor with a financial 1.25 years with a startup 9 months with a private org 4 months on my current job
However, what you don't see is that between the first and second, we moved. The two contract jobs were easy to explain (contract expired), then between job 4 and 5 we moved, and 5 and 6 we moved.
So, if you are just hopping to hop - you might want to just find contract positions instead of full-time positions. A lot easier to explain. But, if there are reasons behind it (more targetted to your field, previous employer wasn't a good fit, moved closer to family), then most companies won't question it.
True, but I wonder how long it will be before Google provides an appliance like their search one to provide this, while keeping everything inside the company firewall...
Any major company whose business relies on having software that nobody else can reproduce exactly has a stake in this. It is to the benefit of -none- of them to lose patents. AT&T, Adobe, Apple, IBM, SCO, just to name a few.
Well, I don't know either, but I do know that we lost our email in the box. They restored it from the previous nights backup, so we only really lost that morning's email, but it happened.
I don't think it had to do with running out of disk space, but some setting that had on the accounts to limit how much mail could be in them. Sorry, not a GW expert, so I don't know the specifics (I wish I did though!)
You reminded me of the time our network admin wanted to setup a failover for our main (high-traffic) website. He figured that he could just add the IP address of our off-site emergency server as a third entry in DNS, since (at least to him) DNS worked by always hitting the first IP, and only moving down the list if it couldn't hit the previous one.
Only it doesn't. It round-robined the requests, so 1/3rd of our traffic was immediately and swiftly rerouted to our emergency site, which some enterprising webmaster had setup to email the webmaster box if anyone hit it (to make sure, I guess, that no one was going to it).
We noticed it because 5 emails came in at once, and then 10 more, and then it didn't stop until Groupwise crashed. We lost all the email in the box, and emails were coming in at some insane rate. We figured it out maybe 3 minutes in, but by the time we logged in and made the change, it was way too late.
If you want to switch just for the sake of switching, then really, you should be fired.
I disagree somewhat with this. For some people, it goes beyond technology to beliefs of free and open systems. It was me deciding to switch "just to switch" that led me to the great programs I use today (Firefox, Thunderbird, Eclipse, etc), and a desktop I enjoy (Gnome on Gentoo).
As long as he takes into account all of the things (like are they going to pay for support if one of the systems does down - or do they even/need/ support if it goes down) I think it is a good thing to at least investigate what is involved in switching. If we don't investigate alternatives, we won't know the ways our current stuff could be better.
Flaky? I haven't seen that, and I'd be happy to bring up whatever it is you are seeing with flakiness. The only thing I was aware of was I think around some of the debugging features.
As far as TFS merge - I'll look into that and put up some info on my site if I find out any more info.
I don't speak for MS, just get a paycheck for them. But my guess is that most consumers get their OS's through whatever is installed on the computer when they buy it. And Vista is a small part of everything that just got released - new Office, new Team Systems, Source control, process management, communications - there is a crapload of stuff coming out, most of it targetted at, um, errr, [I don't want to say it...], enabling businesses.;)
Sorry to be such a downer, but I read some serious delusion in your post.
First, you aren't bursting my bubble. I came to MS as someone who never, ever, though they would go work for them. I run Linux on several home computers, write and speak about Ruby, have run JUGs and LUGs, etc.
I didn't mean to come across that everyone is all giddy and that the only reason they aren't upgrading is because of corporate policies. But I'm sure you all would like to use a lot of the new features - if it fit in your environment.
So I guess there is two things here - some people avoid upgrading just because they don't like change. Some avoid because it affects their bottom line, or doesn't provide the value. But, to extend further, I'm sure that you all take the same approach with any of your upgrades, not just Microsoft ones. I highly doubt (and please correct me if I'm wrong) that when Linus publishes 2.8, you all are going to just grab the bits and shove them on your machines. You'll test, you'll see what the community says, and you'll use all the proper precautions.
Which is ultimately my real point. Being cautious about upgrades is fun to bash on MS about, but any reasonable shop is going to do that for all of their tools and systems.
And, again, please don't get me wrong that I'm all lovey about MS. I might have a blue badge, but that doesn't cover my eyes to everything else going on out there.
your an employee at Microsoft and you haven't had a chance to use it yourself?
I am an employee at Microsoft, and you better darn believe that they push us hard to make sure we are running Vista. A lot of people have been running it since early alphas, providing a lot of feedback.
I'm a field engineer, so I spend most of my time on site at large customers. A lot of them are excited by the features in it - just like they are excited about the features in.NET 2.0 (and 3.0), VS 2005, etc. I've also worked for shops where we were excited about the latest version of Eclipse, Java 5, Ruby on Rails, etc.
People aren't switching because they don't want to. They aren't switching right now because large companies have lengthy install processes that force things to take a long time. It doesn't matter if it's Windows, Linux, Eclipse, Visual Studio, or a host of other things. I'm sure we can find people running solidly on 2.2 kernels, with not a lot of inkling of jumping to 2.6.
It's just the way big businesses operate, and is generally independent of the actual software being discussed. It's a shame that it always seems to get spun that way.
Thanks for posting that. There was no way I was going to go to the site, but I did wonder what their spin was. You'd definitely get modded up if I had points right now - so kudos will have to do.
Slashdot Mirror
No kidding. It must be awful to have two people, both developers, producing similar products, with the same name, both getting nastygrams from MS.
Wrong. It will be in the next version of VS. Right now, it is a pretty awful implementation for TDDers (very slow, but some cool integration features), but they are working on making that better.
Not that I agree with what is going on with Jamie. All he ever asked for was the clause he was violating and he would happily remove it. They haven't provided that yet.
It doesn't. It /does/ require debugging privileges, which can be granted without having to grant Admin access.
+1
I worked for Hillsborough County and got the pleasure of having her as a commissioner. It really does amaze me sometimes how little the media around here pays attention to things.
At least I know why I couldn't find a good used CD shop in Tampa anymore.
I did. This certainly wasn't my first job, so I knew what to do. But they refused to give me any more information then that, basically just letting it go.
;)
No matter, I took a job with a competitor. They may not have all of the fancy benefits, but they have great insurance, interesting people, and it's fun to tout Linux on the internal mailing lists.
I interviewed with them about a year and a half ago. The first interview was awesome - lasted about 3 hours on the phone, and we talked about a multi-threading race condition. The second interview was really short, and it seemed to go well. I got a call from the hiring manager that they weren't continuing on because they didn't like the way I "thought".
Oh well, we really weren't sure about moving to Mountain View anyway. But I sure wish I knew what the heck that meant.
Actually, it depends on how large of an installation you have. As usual, money talks.
But that's not entirely true. I worked for a small company and we were writing our own wrapper around Reporting Services, and found a bug, and they got a hotfix to us that day. We had no fancy contract - we were using one of our free support incidents.
I've seen my share of bugs that won't be fixed too - but I've seen those in the open source projects I've been a part of as well.
There's something else in that. Sure, people are buying Exchange and Outlook because of their feature set. But they also buy them for the support.
Let's say that the Thunderbird/Google/OpenOffice trifecta becomes your corporate IT standard. Now let's say you have a problem. With Google, you have a company to call, but I don't know how good their support it. Thunderbird and OpenOffice have the support of the community, which may lead to faster fixes, but may also depend on who is available when.
Don't get me wrong. I'm not an MS fanboy. But I'm seeing more and more that companies I go into choose MS solutions because it has the features they need and a face to yell at if something goes wrong. When OSS can provide the feature set *and* the unified support, it will be hard to beat.
The funny thing is that the cross-platform solution Microsoft recommends for developers needing to work with VS Team System and Team Foundation Server is Java-based from Teamprise.
I never did understand why they would push that over a Mono-based solution for Linux.
Actually, there isn't a lot of filler (Disclosure: I'm the reviewed ;)). The book is pretty short, and a very fast read. I read it in about 2 hours on a trans-atlantic flight.
;)
The book is pretty specialized, and it probably would fit well into an ME book, but I think it fills a good niche if you are having to do these kinds of things.
And, since the story is about to drop off the main screen, looks like this review will set a record for the lowest number of comments on a front-page story.
I would be willing to bet big money that if MS did anything it lobbied against this change. It is a Really Big Deal, and not something that is easy to just modify.
Also, by the US doing this it created more time zones. How? Mexico is choosing not to go along with the DST updates, therefore anywhere in Mexico using PST effectively isn't anymore.
Huh? How does that happen, assuming you're a good boy and using timestamps in UTC in the first place? You know, the ones that look like "Sat, 3 Mar 2007 08:06:08 -0800 (PST)", the ones you find in e-mail headers for example?
The problem is when that gets interpreted to the local machine.
Let's say you schedule the above meeting during the DST change. If I don't have the update, when I get the alert, it will be an hour off because the calculation to local time will take into account the DST rules for you, but not for me.
Here's a little more info on the DST thing and MS.
Hahaha.
As an engineer who is right in the middle of helping our customers make the changes necessary for the DST fix, it is much more complicated than that.
First, you have all of the servers and clients which rely on one another. The biggest effect is on mail - Exchange/Outlook/OWA.
Second, you have to do it in the right order, at about the same time. If you update the server, then clients who schedule appointments will be off until they update.
Third, you've got software which calculates various things based on that date. Think financial transactions, etc.
I've blogged about the tool we have to help customers figure out what has to be done.
I wish it was as easy as just updating a script, but when you have to coordinate that change across 10s or 100s of thousands of servers, clients, etc, it's not an easy task.
And let's not forget Microsoft isn't the only one having to make changes. Lotus Notes, Groupwise, Blackberries - they all have changes that have to be made. I'll personally be glad when this is all done. Ugh.
I say - it depends.
In the past 6 years I've had 6 different jobs. They looked like:
3 years with a government org
6 months with a startup as an independent contractor
3 months as a contractor with a financial
1.25 years with a startup
9 months with a private org
4 months on my current job
However, what you don't see is that between the first and second, we moved. The two contract jobs were easy to explain (contract expired), then between job 4 and 5 we moved, and 5 and 6 we moved.
So, if you are just hopping to hop - you might want to just find contract positions instead of full-time positions. A lot easier to explain. But, if there are reasons behind it (more targetted to your field, previous employer wasn't a good fit, moved closer to family), then most companies won't question it.
True, but I wonder how long it will be before Google provides an appliance like their search one to provide this, while keeping everything inside the company firewall...
Isn't that what copyrights are for?
Well, I don't know either, but I do know that we lost our email in the box. They restored it from the previous nights backup, so we only really lost that morning's email, but it happened.
I don't think it had to do with running out of disk space, but some setting that had on the accounts to limit how much mail could be in them. Sorry, not a GW expert, so I don't know the specifics (I wish I did though!)
You reminded me of the time our network admin wanted to setup a failover for our main (high-traffic) website. He figured that he could just add the IP address of our off-site emergency server as a third entry in DNS, since (at least to him) DNS worked by always hitting the first IP, and only moving down the list if it couldn't hit the previous one.
Only it doesn't. It round-robined the requests, so 1/3rd of our traffic was immediately and swiftly rerouted to our emergency site, which some enterprising webmaster had setup to email the webmaster box if anyone hit it (to make sure, I guess, that no one was going to it).
We noticed it because 5 emails came in at once, and then 10 more, and then it didn't stop until Groupwise crashed. We lost all the email in the box, and emails were coming in at some insane rate. We figured it out maybe 3 minutes in, but by the time we logged in and made the change, it was way too late.
I disagree somewhat with this. For some people, it goes beyond technology to beliefs of free and open systems. It was me deciding to switch "just to switch" that led me to the great programs I use today (Firefox, Thunderbird, Eclipse, etc), and a desktop I enjoy (Gnome on Gentoo).
As long as he takes into account all of the things (like are they going to pay for support if one of the systems does down - or do they even
Flaky? I haven't seen that, and I'd be happy to bring up whatever it is you are seeing with flakiness. The only thing I was aware of was I think around some of the debugging features.
As far as TFS merge - I'll look into that and put up some info on my site if I find out any more info.
I don't speak for MS, just get a paycheck for them. But my guess is that most consumers get their OS's through whatever is installed on the computer when they buy it. And Vista is a small part of everything that just got released - new Office, new Team Systems, Source control, process management, communications - there is a crapload of stuff coming out, most of it targetted at, um, errr, [I don't want to say it...], enabling businesses. ;)
First, you aren't bursting my bubble. I came to MS as someone who never, ever, though they would go work for them. I run Linux on several home computers, write and speak about Ruby, have run JUGs and LUGs, etc.
I didn't mean to come across that everyone is all giddy and that the only reason they aren't upgrading is because of corporate policies. But I'm sure you all would like to use a lot of the new features - if it fit in your environment.
So I guess there is two things here - some people avoid upgrading just because they don't like change. Some avoid because it affects their bottom line, or doesn't provide the value. But, to extend further, I'm sure that you all take the same approach with any of your upgrades, not just Microsoft ones. I highly doubt (and please correct me if I'm wrong) that when Linus publishes 2.8, you all are going to just grab the bits and shove them on your machines. You'll test, you'll see what the community says, and you'll use all the proper precautions.
Which is ultimately my real point. Being cautious about upgrades is fun to bash on MS about, but any reasonable shop is going to do that for all of their tools and systems.
And, again, please don't get me wrong that I'm all lovey about MS. I might have a blue badge, but that doesn't cover my eyes to everything else going on out there.
I am an employee at Microsoft, and you better darn believe that they push us hard to make sure we are running Vista. A lot of people have been running it since early alphas, providing a lot of feedback.
I'm a field engineer, so I spend most of my time on site at large customers. A lot of them are excited by the features in it - just like they are excited about the features in
People aren't switching because they don't want to. They aren't switching right now because large companies have lengthy install processes that force things to take a long time. It doesn't matter if it's Windows, Linux, Eclipse, Visual Studio, or a host of other things. I'm sure we can find people running solidly on 2.2 kernels, with not a lot of inkling of jumping to 2.6.
It's just the way big businesses operate, and is generally independent of the actual software being discussed. It's a shame that it always seems to get spun that way.
(Disclaimer: I'm the reviewer)
Someone else already pointed it out, but those are the sections. Trust me, I wouldn't have written it that way if it wasn't.
Thanks for posting that. There was no way I was going to go to the site, but I did wonder what their spin was. You'd definitely get modded up if I had points right now - so kudos will have to do.