Thanks much for the kinds words! You can get the link to our Coding Standards and Naming Convention web page at: extragood.info/coding That will also give you the PDF that this video was based on. Happy coding!
Thank you, I had a huge benefit, that's a great vidoe. I have only one question, why would you black list that developer maybe he would understand his mistakes and improve and become a much better programmer.
Thanks for the question. I did explain to him the reason he was being fired and I hope he used that information to improve his coding standards for future clients. I was working for a payroll processing company at the time. I felt I just couldn't trust his code after I discovered that. I felt I would have to review every single line of code he wrote which would take almost as much time as writing it myself. I worried that if other developers currently working for the company now or in the future copied/pasted some of his code it would not work as expected because the variable's value meant different things depending on where you copied it from. It was just too big a mistake and too big a risk. He was supposedly a senior-level programmer but someone that did not understand that basic logic requirement made me question his judgement and design skills overall.
Thank you for the detailed reply, I appreciate it. I wonder how developers like that could be mistaken to be seniors in the first place. I have been thinking for a while now what’s real and what’s not about the hiring process being broken.
@@mohammadalaaelghamry8010 There are frauds in every industry. Sometimes you can't tell if a person's programming ability is good or not until you really look at the code. When hiring contractors we only looked at his finished products which were Windows executables. Those looked fine. Whenever hiring someone for a long-term position I always recommend looking at their source code. You can tell much more from that. Do they indent properly, do they have good naming conventions, do they comment when the code is unintuitive, etc. We interviewed a guy for a mid-level programming position for that company and he passed the HR interview, passed the spoken interview by one of the other senior techs, but failed horribly on the simple coding test I gave him. Turns out he was more of a computer user than a computer programmer and he couldn't even write a simple function.
"Sit down Steve, I saw your code and I know its working, but you were not consistent in your True/False statements, thats why you pack your staff and fack off" lul
If we was a junior programmer then definitely I would have used it as a training opportunity. If he was a mid-level programmer and made that mistake I would have explained/trained him on his error then given him another chance and assigned him several tedious code-cleanup tasks as punishment. This true/false problem was made by a senior-level subcontractor. For a senior-level developer to make that... unforgivable. Fired!
![โฮ่ง! (SUGOI) - LYKN [ OFFICIAL MV ]](http://i.ytimg.com/vi/nFp4zjAARFs/mqdefault.jpg)
As an Informatics Engineering major, I'm taking notes of this for my future assignments. You explained things better than my professor!
Thanks much for the kinds words! You can get the link to our Coding Standards and Naming Convention web page at: extragood.info/coding
That will also give you the PDF that this video was based on. Happy coding!
Wonderful video, audio quality top notch!
Thank you, I had a huge benefit, that's a great vidoe. I have only one question, why would you black list that developer maybe he would understand his mistakes and improve and become a much better programmer.
Thanks for the question.
I did explain to him the reason he was being fired and I hope he used that information to improve his coding standards for future clients.
I was working for a payroll processing company at the time. I felt I just couldn't trust his code after I discovered that. I felt I would have to review every single line of code he wrote which would take almost as much time as writing it myself. I worried that if other developers currently working for the company now or in the future copied/pasted some of his code it would not work as expected because the variable's value meant different things depending on where you copied it from.
It was just too big a mistake and too big a risk. He was supposedly a senior-level programmer but someone that did not understand that basic logic requirement made me question his judgement and design skills overall.
Thank you for the detailed reply, I appreciate it. I wonder how developers like that could be mistaken to be seniors in the first place. I have been thinking for a while now what’s real and what’s not about the hiring process being broken.
@@mohammadalaaelghamry8010 There are frauds in every industry. Sometimes you can't tell if a person's programming ability is good or not until you really look at the code. When hiring contractors we only looked at his finished products which were Windows executables. Those looked fine.
Whenever hiring someone for a long-term position I always recommend looking at their source code. You can tell much more from that. Do they indent properly, do they have good naming conventions, do they comment when the code is unintuitive, etc.
We interviewed a guy for a mid-level programming position for that company and he passed the HR interview, passed the spoken interview by one of the other senior techs, but failed horribly on the simple coding test I gave him. Turns out he was more of a computer user than a computer programmer and he couldn't even write a simple function.
"Sit down Steve,
I saw your code and I know its working, but you were not consistent in your True/False statements, thats why you pack your staff and fack off"
lul
Seems overly harsh to fire someone for something like that, as it's something that can easily be trained out of someone.
If we was a junior programmer then definitely I would have used it as a training opportunity. If he was a mid-level programmer and made that mistake I would have explained/trained him on his error then given him another chance and assigned him several tedious code-cleanup tasks as punishment.
This true/false problem was made by a senior-level subcontractor. For a senior-level developer to make that... unforgivable. Fired!
18:15 hahahaha