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.
That looks like it'd be the final item one's next of kin could cross off their bucket list for them. However, when I was younger.. that would have been a ton of fun.. slower and without the jumps though. But then again, what do I know, I drove into work today (8" of snow in Portland, OR).
We can program with only 1's, but if all you've got are zeros, you've got nothing.
Expert Beginner's are developers who do not understand enough of the big picture to understand that they aren't actually experts. What I mean by this is that they have a narrow enough perspective to think that whatever they have been exposed to is the best and only way to do things. Examples include a C# developer who pooh-poohs Java without ever having tried it or a MySQL DBA who dismisses the NoSQL movement as a passing fad.
I've never seen this explained so well before.
I finally know the term (Expert Beginner) to use for the contractor I worked with at a large mortgage bank who knew that he knew everything.
This guy had convinced a publisher to publish his book so he basically threw it on my manager's desk and my manager hired him. It was proof enough that he was a genius.
At one point I asked the contractor a question about his XML parsing code that he had written as part of a larger project.
Me: I see you seem to have written some functionality that manipulates the XML. Why didn't you just use the XML classes built into .NET? ExpertDev:I tried those classes but they weren't any good so I wrote my own. Me <slowly>: Umm... First of all, you've now created proprietary code that everyone throughout the company has to examine and understand just to interact with your section of code now. That's one problem. ExpertDev: Well, I'm telling you the Microsoft libraries are 5 times slower than my code. Me: So you're telling me that you wrote better code than the .NET team at Microsoft? ExpertDev: All I can tell you is that mine parses the XML 5 times faster. I have performance data. Me: Yes, you're right. It is 5 times faster than the .NET XML DOM parser. That's because the .NET one parses it into a structured object that is easy to manipulate. The problem is that in your code your "XML" is actually just a string that you reference via indexes. You see the difference there right? ExpertDev:I'm telling you, mine's faster.
At this point the discussion was a little heated and a bit loud for the bloodless cubicle environment and my manager came out of his office. Manager: What're you two yakking about out here? Get back to work!
A long time ago I worked for a guy that had written a book. He knew absolutely nothing. To make matters worse, his hair was thinning and someone had convinced him to, well, paint his scalp black under the hairline to make it look like he had more hair. You can guess how much respect he got.
Hair plugs are worse. Trust me.
I had to train a technical bod from our New York distributer - good bloke, spoken to him on the phone loads of times. So he flew over and we meet for the product training ... And he had hair transplants.
All the hair on his head was in little identical clumps, in absolutely straight rows and columns, and while you're talking to him your eyes are continually rising up, and up in fascinated horror to the regular field of - presumably - butt hair all over his head ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
I worked with a person once who was having to parse XML. Person would scream every time the schema (we used DTDs) changed. Now, I would think screaming is normal because the schema should not change after development started (at least not much). So I kept my head down and ignored it.
Well, this person screamed much worse and never stopped. The person would scream from one day to the next - even until the next schema change happened, at which time the person claimed the code had just started working again due to the previous change. One day this person left the company. A second person who was working with this person was now responsible for the code...
The second person came to me and asked if it was right... I looked at the code and the first person was parsing the entire LARGE XML structure manually as a string. Nothing worked and it was bug ridden. I looked at the 2nd person funny, who never raised the alarm while working with the 1st person. Both had degrees from prestigious universities - but could not ask anyone else in the company how to parse XML. We were using MS products of course, which have built in libraries for doing such things.
That is my XML story...
Lesson 1... be humble and ask for help. Ten minutes of help could have saved weeks of screaming
Lesson 2... if your employees scream too much... you should code review their work before it is too late
Last Visit: 31-Dec-99 18:00 Last Update: 29-May-17 7:12