The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Its a bit amazing and scary at the same time, how much traction a murderous idea is getting by people of profession which are generally known as introverts and socially awkward. Then again that might be the reason why.
I may just be scared because I'm the know-it-all in my team
Pitchforks at the ready everyone, we got another one over here
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
You should be free to state that "persistence of an opinion is not the same as knowledge or professionalism". However, the problem with these folks is that summary execution does not help, and they will keep talking even when the head is chronically severed from the body.
We call them "zweefteef" but I can't seem to find a suitable translation.
At the least, only verbally tell your friend. You don't want to be implicated with a paper trail. Also before telling them, check them for any recording devices. Maybe also do the meeting in the server room so the deafening noise masks anything you say.
Just playing devil's advocate here: is it possible he's right (just overly enthusiastic)?
In my example, I got to my current place where these HPCs are, "MVC is too hard", "Linq makes weird queries and is too hard", "ADO.NET is better than EF", etc, etc.
Then running around babbling about adding memory to SQL Server because their crappy sprocs return every record that qualifies for a search, rather than one page's worth of things.
Rewrote our main search into EF/linq, a little skip/take action later, our SQL memory problem disappeared.
I don't know if React is a good or bad thing. We need to keep moving forward, but in a sensible manner.
Maybe it should be added, but as a project unto itself? As opposed to, "I'm making this other change which doesn't require react, but while I'm up, I'll throw that in."
I had a similar issue way back in the 1970s when I was working with IBM's excellent System 3/Model 12 systems.
I was learning development at that time but the manager hired a "super star" just like the guy you describe.
This new fellow was a complete idiot because he thought he could do no wrong. Well, he did plenty wrong. One day he came in and simply removed a disk while it was being backed up, scrambling the entire system to pieces. The operator, who I had trained to an expert capability was not in the computer room when this jerk simply did his thing so he could get on with his work.
Other times he would take perfectly well written applications that did exactly what they were supposed to do and turn them into gargantuan nightmares filled with bugs and defects.
By the time I left this position I had developed the entire ticket tracking and inventory systems, which were quite extensive at the time. Each system had a single operator intervention with the computer and then they could be left run overnight. These systems ran like clock work for months on a regular basis without a single issue.
Before I left, I prepared exact instructions on how to update the source code and run the two systems. Well the jerk here thought he knew better. He took both systems and turned them into unworkable messes.
When I cam back for a visit with some friends they told me that the inventories had not been completed in 6 weeks and the still couldn;t get them to run properly.
So when a know-it-all shows up on the premises bury him at least 20 feet down, deep in a forest, and then pour lime on the body. Make sure the ditch is covered with used soil and ensure there is no trace of a burial...
Sr. Software Engineer
Black Falcon Software, Inc.
Sounds familiar. (true story) A previous company I worked for hired a fresh out of university engineer. He insisted that the engineers, with years of experience, who designed the whole system, did it all wrong, because that was not what he was taught in school.
Funny, it had been working for a decade with almost no failures. Of course the fact that between FCC fines and customer contract failure costs (Thousands of dollars per minute of down time), there is a certain amount of intensive for doing it right.
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
Last Visit: 3-Apr-20 17:39 Last Update: 3-Apr-20 17:39