The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Yeah, there is a bit of truth to "confirming what you think" as being valuable.
Yes, we recently turned it on in a web project, to track some how many times users were told "more information is available", and who clicked on Reload, vs. Ignore...
Management was OVERLY concerned with the impact on users, and reloads, etc. It was useful, in this case, we found only 5% of the people got the message. 85% of those IGNORED the extra information (meaning they did not care).
As always in this field, the correct answer is: "It Depends" )))
It really depends on who needs the information, and what it could possibly change. In our case, it prevented wasting ANY MORE development time on this one issue. In general, it was easy enough to collect and turn this type of stuff on.
My understanding is that Microsoft works very closely with a few companies and gets most of their product input and bug fix requirements from those companies. Otherwise, Microsoft appears stone deaf to bug reports/fix requests, suggestions, comments, etc. Several years ago I attended a local SQL user group meeting where the manager of the MS BI stack was speaking. He said that they only received a very low number of comments and suggestions for their next release and commented that the #1 suggestion for SQL Server Management Studio was...Sound a "bell" alert option when the query finished processing. The audience did not take this at face value, however, and quite a few attendees pointed out that they had submitted detailed and sometimes lengthy suggestions and bug reports and got no response. And the requested features never showed up either. Since the Microsoft manager was clueless about all these suggestions, most of which the audience indicated were good ones, it left us with the impression that Microsoft truly does not care about developer or DBA or user input.
Now, several years later, and based upon personal experience, I conclude that they still don't. Hopefully, this will change.
One of the BEST things in the past with Microsoft Analysis Services was Mosha. He was on the development team and wrote lengthy blogs about the product and its use which was (is) very complex. He was admired by all SSAS developers and his insight, coming from the inside, was PRICELESS. He finally went to Bing and that was the last of that unfortunately.
Can we see something like this in the near future from Microsoft for all their various product areas to have a DEVELOPER EVANGELIST/BLOGGER/HELPER person? It would be invaluable!
Thanks for sharing that. I think you are indeed right that MS only gets their feedback from a group of companies. Reading other people's comments about this seems that they indeed turn a blind eye to user feedback. It seems like then what's the point for even asking then? Strange, but who knows why they go through the charade.
I will concede maybe they do user for specific things here or there such as UI related things, but for other things such as bug fixes or new features it seems like they do with what you have experienced.
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
So here I am tooling down the road on my way to work when some guy grabs a ladder that was propped up against a broken street light (this was one of those big 12 foot ladders) and starts staggering across the road with it. He loses his balance and the thing starts swinging right at my windshield! I had to swerve out of the way which meant I almost ran him over. I called the police to report this lunatic. Sure glad I didn't hit him, that would have ruined my day!
I was working on a streetlight in the early morning. Some drunk guy stumbled across the road and nearly got hit by a car (whose driver may also have been drunk, or maybe just half asleep). The drunk guy then stole my ladder out from under me, forcing me to grab on to the light I was fixing. As the drunk was making off with my ladder, some other bloke walking his dog saw the spectacle, but instead of helping me, he just phoned the police to report a burglar. He must've seen me, because he looked directly at the busted streetlight from which I was hanging. Why on earth did he not help me? I had to hang there for over an hour, clinging on for dear life, before some good Samaritan helped me down.
What is this talk of release? I do not release software. My software escapes leaving a bloody trail of designers and quality assurance people in its wake.
Looked out of my window this morning cause the streetlight had gone out and I wondered why. There was this bloke with a dog following a man with a ladder, obviously up to no good as he was keeping out of sight of the ladder carrier. Luckily a passing car lit them both up so I could pass the description on to the police.
Awful! They sound like bloody hairdryers. I went to the Hungarian GP many times and it was brilliant, the sheer brut power could be heard roaring around the track. That? Barely hear it across the road.
I was walking the dog this morning I saw a suspicious looking man dressed in dark clothing, crossing the street with a ladder. He had even gone to the trouble of disabling the street light so as not to be seen. I got a good look at him though as he was lit up by an oncoming car. I have passed his description on to the Police.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Yes. Most of my professional life was in tech support so I was trying to debug other people's code. I did enjoy the occasional break to write some code for myself, but soon got fed up and went back to debugging.
I have to agree. I learn a lot from chasing down the answers to the bugs to get the program to act how I want it to. Especially since a lot of times I'm parsing text files. I think I've learned a 100 different ways to manage strings.
Given that right now I'm trying to figure out why the application reports one record when the database query says I should have some 70 or so records, well, this isn't fun. It's not code that I've written, if I had I would have done it a lot differently (yes, I know, the mantra of all programmers working on someone else's stuff), but I definitely prefer writing code than debugging.
That said, I like to write code as if I'm debugging -- what I mean by that is that I imagine the whole stack, the possible exceptions, the possible paths the code can take, and I try coding for all of that. I imagine everyone does that. And when working with F#, I write everything first in the interactive console, test it, then put it into the application. I would love for something like FSI for C# development.
But personally, my first and true love is architecture. But I would have to say that many of my beautiful architecture ideas turn into puddles of mud when I actually try coding them against real world requirements. A good way to learn the difference between theory and application!
That said, I like to write code as if I'm debugging -- what I mean by that is that I imagine the whole stack, the possible exceptions, the possible paths the code can take, and I try coding for all of that.
I try to do that to. But sometimes it comes down to not getting the output I need from a certain block of code.
I would love for something like FSI for C# development.
After working in C++ for a very long time, with edit-compile-debug cycle lengths measured in minutes or even hours, I find the 15-45 second turnaround time from my C# development refreshingly quick. On top of that, I have my entire C# application in a single solution. My C++ stuff had to be broken up into several solutions to bring the individual compile times down to something reasonable.
well actually both are like two side of a coin we can't say exactly that i like this one more than that. good code helps in reducing the chance of generating bug and good debugging skill helps to write better code. as a Programmer i like both coding and debugging.
I'm definitely a coder. Debugging means either (i) you didn't write your code well enough in the first place, so you have to debug it later, which is a failure and I don't like failing; or (ii) you are working in someone else's code which is always painful, and if you're debugging it it means it doesn't work and isn't well enough documented or tested to isolate the problem without debugging. Neither of those things is fun to me.
Last Visit: 31-Dec-99 19:00 Last Update: 10-Dec-16 19:28