Unwashed Village

General Discussion => Unwashed Village => Topic started by: BlueCross on January 19, 2011, 07:56:53 PM

Title: Searching for code...
Post by: BlueCross on January 19, 2011, 07:56:53 PM
The amount of chaff among the wheat in Google searches has reached monumental proportions.  In fact, if you try to do the math now, I think you get a divide overflow.  The amount of crap that people post in response to technical issues is... well... to borrow from a movie review I just saw, it's "so amazingly stupid that it's profound!".

Some guidelines, please:
1.  If you don't know crap, then stfu!
2.  Don't post any code you didn't test!
3.  Read the fucking original question so at least you can stay in the ballpark when you answer.
4.  Don't post solutions that include "just Google xxxxxx"; how fucking dumb is that.
5.  Avoid posting links as solutions; if you do, the link better be damn good.
6.  Don't ask "why would you want to do this anyway?" which is at the top of my "most stupid fucking questions of all time".

Here are some responses I got recently while trying to find a solution to using a Datagridviewcomboboxcolumn that had 'issues':

"I'm sorry that I cannot help you technically coz i just lost touch with C# but I could give some ideas logically."

"As per my knowledge nothing has to be done for this."

"Off the top of my head... " followed in a few sentences by "I will try an update the article later"

"Unfortunately there is no answer yet for this question..."




And some comments by other posters facing same problem that I had:

"What ever happened to the days when I knew what I wanted to do with my data, be it from a database or other source, and I told the application how to work"

"this terrible DataGridViewComboBoxColumn binding is really silly... "
Title: Re: Searching for code...
Post by: Chucara on January 27, 2011, 12:07:03 AM
Working with WPF? Lovely piece of technology, that is...
Title: Re: Searching for code...
Post by: BlueCross on January 27, 2011, 01:51:10 AM
Working with WPF? Lovely piece of technology, that is...

Actually, it's Windows Forms (slightly different).

What I have learned since going back to work:
1. Visual Studio 2008 sucks, sucks, sucks...
2. Visual Studio 2010 is really pretty nice.

Windows Forms is a good for quick dialogue and simple database interfaces.  The DataGridView (and assorted methods, events, etc) is quite powerful but sometimes lining up all the MicroSoft ducks in a row to get something to work properly can be incredibly difficult.  More than once I've spent a couple hours just working on one line of code, and when it finally worked, I almost had an orgasm.  Almost...

3.  MicroSoft Office 2007 should be avoided at ALL COSTS!  Don't even go near that abortion.  After I suffered with it for a few days, I googled and found this review:

"Pros: there are NO pros to this product. It is counterintuitive, and designed by squirrels, clearly.
Cons: its existence - useless and unnecessary
Summary: This is the worst and stupidest excuse for 'word processing' I've ever seen or attempted to use. I almost threw my new laptop out the window because of it - I have used the thing exactly twice during the trial period, and didn't take MS up on their 'free' 'offer' - what happened to the days when the software was bundled in the cost of a PC? WordPerfect is SO much more superior, and always has been. I predict this will cause Microsoft to TANK. Offices will NEVER use this. Office workers will NEVER change over to this - they will resign and stay home. Back to typewriters, or back to WordPerfect.

---A now confirmed Luddite. Screw Gates & Co. - complete and utter waste of time.
"

That pretty well sums up my opinion as well.

Title: Re: Searching for code...
Post by: Solwyn on January 27, 2011, 07:55:15 PM
Actually, it's Windows Forms (slightly different).

If you have a problem, and you go to anything with "Windows" in the name, now you have two problems.
Title: Re: Searching for code...
Post by: BlueCross on January 27, 2011, 11:40:38 PM
Actually, it's Windows Forms (slightly different).

If you have a problem, and you go to anything with "Windows" in the name, now you have two problems.

Some are born with Windows, some achieve Windows, and some have Windows thrust upon them.

(I fall in Category 3)

Title: Re: Searching for code...
Post by: Hoopy Frood on January 28, 2011, 01:59:44 AM
My workplace uses Office 2007.
Title: Re: Searching for code...
Post by: BlueCross on January 29, 2011, 01:19:20 AM
My workplace uses Office 2007.

*runs from Hoopy's workplace, screaming...*
Title: Re: Searching for code...
Post by: Hoopy Frood on January 29, 2011, 10:43:59 PM
My workplace uses Office 2007.

*runs from Hoopy's workplace, screaming...*

To be honest, I'm probably not that far behind you, not because of Office 2007, but because it's time for me to move on from there.
Title: Re: Searching for code...
Post by: AcdQueen89 on February 02, 2011, 03:44:31 AM
3.  MicroSoft Office 2007 should be avoided at ALL COSTS!  Don't even go near that abortion. 

it's working fairly well for me. but then again i only use word. *shrug*