Expert Beginner Dev's Know They Know Everything
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
"If all you have is a hammer, everything looks like a nail."
I wanna be a eunuchs developer! Pass me a bread knife!
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
:thumbsup: 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. :)
-
:thumbsup: 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. :)
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
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 X| Lesson 2... if your employees scream too much... you should code review their work before it is too late :doh:
-
"Convinced him"? As in, he actually did it? If there ever was a time to roll out the "pics or it didn't happen" meme, this is it...
This was a long time ago, before the internet and smartphones. But probably something like this: 1990's INFOMERCIAL HELL #19: Spray paint the bald away with GLH, by Ronco, of course! [^]
-
:thumbsup: 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. :)
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
Much the same way that Jeremy Clarkson's "Sports Train" is faster than a regular train. :sigh:
-
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 X| Lesson 2... if your employees scream too much... you should code review their work before it is too late :doh:
-
Much the same way that Jeremy Clarkson's "Sports Train" is faster than a regular train. :sigh:
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
raddevus wrote:
The problem is that in your code your "XML" is actually just a string that you reference via indexes.
I'm sure, that one who sees XML as a string will fall over escaped chars in an entity... Take some time to create the proper data and you will see miracles... :cool:
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
So you have an issue with programming methodolgies that can affect the product, timelines, people's sanity and probably profitability and instead of sitting down to dig into the issue he tells you to get back to work? The problem isn't ExpertDev. The problem is the manager.
cheers Chris Maunder
-
R. Giskard Reventlov wrote:
paint his scalp black under the hairline to make it look like he had more hair
That's an _interesting_ solution. :~
He was an object of mirth for the few months that he blessed us with his presence.
-
:thumbsup: 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 ... :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
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 ... :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
:laugh: :laugh: :laugh:
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
raddevus wrote:
a C# developer who pooh-poohs Java without ever having tried it
When the C# developer has tried Java he will still pooh-pooh it though :D Erik's blog on the expert beginner was in The Insider a while back. The problem is that the more you know the better you know what you don't know. That's why the good people are modest, while the people who know just a little bit shout the hardest.
Best, Sander arrgh.js - Bringing LINQ to JavaScript SQL Server for C# Developers Succinctly Object-Oriented Programming in C# Succinctly
-
So you have an issue with programming methodolgies that can affect the product, timelines, people's sanity and probably profitability and instead of sitting down to dig into the issue he tells you to get back to work? The problem isn't ExpertDev. The problem is the manager.
cheers Chris Maunder
Chris Maunder wrote:
The problem is the manager.
Nailed it!! Very astute of you. You noticed the subtext of the story. I actually told the manager that it was crazy because of all the reasons you mentioned and he said,
Quote:
"[Contractor] is smart enough that I'm sure he is doing the right thing."
X|
-
He was an object of mirth for the few months that he blessed us with his presence.
-
raddevus wrote:
a C# developer who pooh-poohs Java without ever having tried it
When the C# developer has tried Java he will still pooh-pooh it though :D Erik's blog on the expert beginner was in The Insider a while back. The problem is that the more you know the better you know what you don't know. That's why the good people are modest, while the people who know just a little bit shout the hardest.
Best, Sander arrgh.js - Bringing LINQ to JavaScript SQL Server for C# Developers Succinctly Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
The problem is that the more you know the better you know what you don't know.That's why the good people are modest, while the people who know just a little bit shout the hardest.
Two great truths. Too bad the whole world doesn't know them better.
-
While reading this book, Amazon.com: The Expert Beginner eBook: Erik Dietrich: Kindle Store[^] I stumbled upon this...
Quote:
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
I replaced such an 'expert' who had written a book. He spent 3 months delivering sod all, so they got me in, and I delivered it in 2 weeks. Experts, fuck em. Oh, and then there was the USB expert. What a twat. Thought a transaction error was to do with the transaction translator needed to run full speed device on high speed hubs! He delivered shit for months till I lost patience and put my own code in the driver.
