A return to coding gripes today.
I've mentioned plenty on the issues of wrangling this code and getting it to work. We have basically something that does what it needs to at this point, with a couple cosmetic changes and one new function to add and it should hopefully be done and off the table.
I just get irritated when the other coder asks me why something isn't working and won't take "I don't know" as an answer. He changes something in my code to fit something he wants to add and then I have to retrace the steps to find out what's wrong. It's not my code, so I'm not that familiar with it - and I get frustrated enough when it's not doing what I want as opposed to also trying to figure out what HIS code did to it.
It's also doesn't help that he seems to ignore or not understand my suggestions when it comes to what to do (warning, minor technical stuff to follow!). He added a list to a user creation page that I had finagled together and I told him that he should use a separate stored procedure for it and then do a loop function to check and then add each highlighted item in the list with said SP to the cross-reference table.
Oh no no no, he'll just add it to my save SP that just stores text field data. And his list-grab code just repeatedly overwrites the the previously stored list item information with the new one. And thus only saves the last item on the list to the xref table when the SP is called. Shocking. Fortunately, I managed to somehow explain to him what was happening and he wrote a proper code and corresponding SP to add the information (along with how to handle updates to the list since he didn't apparently think of that).
I just got reminded of this because of one of the changes he made that I noted. There's a field on a page that's supposed to supersede a drop-down list if you write in it (basically, the ability to provide your own information if what's in the drop-down doesn't match). And I almost got into an argument with the guy explaining that it's just there for report purposes and it shouldn't add to the drop-down list because that was explicitly stated to be the job of the administrator. It ultimately ended with him saying we should talk to the PM about it... who I'm HOPING will agree with me and not suggest some overly convoluted alternate method to the basically cut-and-dry approach I'm trying to provide.
At least I've made all the fixes and updates to my sections that were requested. All that's left is the new functionality and the changes to HIS stuff. Which will be... fun, as you can very well guess.
I've mentioned plenty on the issues of wrangling this code and getting it to work. We have basically something that does what it needs to at this point, with a couple cosmetic changes and one new function to add and it should hopefully be done and off the table.
I just get irritated when the other coder asks me why something isn't working and won't take "I don't know" as an answer. He changes something in my code to fit something he wants to add and then I have to retrace the steps to find out what's wrong. It's not my code, so I'm not that familiar with it - and I get frustrated enough when it's not doing what I want as opposed to also trying to figure out what HIS code did to it.
It's also doesn't help that he seems to ignore or not understand my suggestions when it comes to what to do (warning, minor technical stuff to follow!). He added a list to a user creation page that I had finagled together and I told him that he should use a separate stored procedure for it and then do a loop function to check and then add each highlighted item in the list with said SP to the cross-reference table.
Oh no no no, he'll just add it to my save SP that just stores text field data. And his list-grab code just repeatedly overwrites the the previously stored list item information with the new one. And thus only saves the last item on the list to the xref table when the SP is called. Shocking. Fortunately, I managed to somehow explain to him what was happening and he wrote a proper code and corresponding SP to add the information (along with how to handle updates to the list since he didn't apparently think of that).
I just got reminded of this because of one of the changes he made that I noted. There's a field on a page that's supposed to supersede a drop-down list if you write in it (basically, the ability to provide your own information if what's in the drop-down doesn't match). And I almost got into an argument with the guy explaining that it's just there for report purposes and it shouldn't add to the drop-down list because that was explicitly stated to be the job of the administrator. It ultimately ended with him saying we should talk to the PM about it... who I'm HOPING will agree with me and not suggest some overly convoluted alternate method to the basically cut-and-dry approach I'm trying to provide.
At least I've made all the fixes and updates to my sections that were requested. All that's left is the new functionality and the changes to HIS stuff. Which will be... fun, as you can very well guess.
~