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.
When I was first starting with WPF, I heard about Expression Blend. I downloaded and installed it. The app was completely unusable. Monochrome icons and gray text on a darker gray background. I couldn't see anything in the app. Switching themes did no good, as they all had the same low contrast "oh, don't have anything distract from the work" design. I complained on Microsoft Connect about the app's usability. They closed and deleted my issue immediately with no response.
They closed and deleted my issue immediately with no response.
That's interesting because that's the 7th level of pain/annoyance that these kinds of frustrating issues create: you can't even report the issue because they just close them since it cannot be true that their design is terrible.
I don't bother reporting issues to Microsoft any longer. Every time I have they've either responded with a form response ("did you try rebooting?" ), or closed the issue with no comment. My experience has been that they treat most developers with nothing but contempt.
I agree with you. Not sure why they have that attitude about it but that's the same experience I've had in reporting issues to them.
I've reported a couple of real bugs with Visual Studio a couple of times and provided details and screen shots so they can reproduce and they just post back, "not a bug" and close or even delete the issue. The one I had reported was reported by a large number of users and they closed it anyways.
The fun thing about problems like this is to figure out what makes it easy for you. We are really good at categorizing / grouping recursively without thinking, and computers have to be programmed to do this stuff.
So, why is this easy for the brain to figure out? How do you capture that ease in an algorithm?
I've given up on LALR parsing for now because my tables are off - for some grammars - and i can't figure out why.
So instead what I'm doing is improving my LL(1) parser with automatic grammar refactoring so you can use grammars that are not intrinsically LL(1) - LL(1) being very limiting in terms of expressive power.
And this is part of the process. The full process is explained here at the link below, fortunately I got accustomed to understanding heavy Indian accents and Indian-English vernacular while at Microsoft. =)
... who posts those dumb questions. I was watching the film "Jason Bourne" last night (yes, I know). At the beginning was the usual scene, a darkened room with a few people controlling the world from their laptops. As their fingers were playing over the keys I heard someone say "Use SQL to corrupt their database(s)".
Having performed my time writing SQL, yes I can see that. The best way to do this is to have inexperienced people try to "improve" the SQL code for you... that will irreparably booger up a database faster then you can say STOP! NO DON'T!
It was broke, so I fixed it.
Last Visit: 15-Jun-19 10:37 Last Update: 15-Jun-19 10:37