Aportaciones a los sistemas full-dúplex con vídeo digital Limitaciones

Hannah remained predominately a programmer as the project moved forward, and as the project passed its mid-point, she finally had a breakthrough with the code, solving the issue she’d been previously having with calling the data (18.04.26 lns 3-17):

Hh: Uhhh so our biggest problem that we wanted to deal with was be able to know how to grab the data we want to be able to do something with it and the thing we wanted to do was combos um so they helped us through the email that one of their other um colleagues

sent us through the iteration the loop to go through all of the data take out which ones are reviews and put them in an object

R: Okay

Hh: And in that object it had a list of all of the different sorts of* ASIN ids and next to that there’d be an array that would contain all of the reviews that had reviewed on that product uh so we got that sorted which is organised and everything separated them based on the product that they’ve commented on so from that we could literally just reference the array put it in and create the combo um which the guy helped us with so um

[Cambridge Intelligence employee] the woman in the pink jumper helped us with the iteration process of it and then the other guy who I’m not sure what his name was umm helped us with the combos and so that’s all basically sorted now and then on the Trello as you can probably see in the to-do list there’s so much to do now that we are able to get at that data and do something with it so we’ve got quite a lot of stuff to do next week

By this point, Hannah had a much more complete view of the issue her team had been facing, due in part to her own research and in part from the guidance received from emails to the Cambridge Intelligence team. In the end, the solution was a relatively simple one, as Hannah was quite willing to admit (18.04.26 lns 18-23…38-46):

R: Okay um it looked like it was something relatively small that they were able to fix Hh: Yeah

R: Like some you had something on one line that you needed to separate something out Hh: Yeah so we had uhhh for the iteration process an ‘if’ statement and it had two arguments within that ‘if’ statement and all she did was split it into two separate statements and that was it…

R: Is there a reason that this particular type uh these two types of statement would have had an issue, was one dependent on the other or?

Hh: I wasn’t well I wasn’t really sure at first cause basically we had ‘if the node we are looking at is a review and the object doesn’t have it already, put it into the array’ and then

all she did was go ‘if the object is a review’ and then another one saying ‘if it’s not in the array put it in’ so then if it is a review uh but it is in the array it just skips past that but what it was doing I think was if it’s part of the review it was making a new array anyway so it was making a separate array for all of them instead of checking the statement twice it just did it in one I think that is what she was trying to get at with it

Hannah did not merely allow the experts to make the changes, she followed closely what they were doing so as to better understand what to do if she again faced a similar issue. She had again, however, oversimplified the solution; while splitting of the statement did in fact solve the issue her team had been facing, Hannah has overlooked the importance of the actions

surrounding the splitting of the nested if statement. Among other things, the expert “changed the ASIN number from a number to a string” (18.04.26 ln 25), and may likely have cleaned up the syntax at the same time. These changes, largely disregarded by Hannah here, may have

ultimately been as much a part of the solution as the splitting itself, as splitting such a statement is largely a cosmetic solution (Else, M., personal communication, February 15, 2019).

As Hannah had stated early on, issues can arise from something as simple as a missed semi-colon, so the possibility that she overlooked such a change here is possible as well. Regardless, the changes made here represented another shift in the project, as well as the dynamics of the group. With the most pressing issue sorted, Hannah’s thoughts once more turned to planning, and she actually relinquished her Head Programmer position for the

following week, in favour of working with the report and allowing Jane some programming time (18.05.01 lns 37-46):

Hh: I think so yeah because obviously if I don’t know what’s in the report and someone asks me a question on it I’m a bit like uh no idea I think report writing is important for everybody everyone’s gonna have to do it at some point um so if we all partake in that it will obviously help us develop our skills with that as well and with the presentation part we all have to present so we all have to know what we’re doing what how with the report and everything so yeah it’s really important that we all have an input into that

R: Okay umm and then you will still be doing a little bit of coding tomorrow is that the plan?

Hh: Yeah yeah it is everyone’s gonna cause Jane hasn’t done any coding yet Matthew kind of has he’s been looking at the code but not actually coding anything umm so everybody’s going to have the chance to do everything tomorrow which will be good. Hannah and her team were purposefully putting themselves in situations in which building multiple competences is necessary. While Hannah had already shown evidence of this (see above), it is clear she felt she can still make improvements to this area by editing the report and building another transferrable skill. She also believed that having the programmers doing some of the reporting will add value to the report itself, most likely in the form of refined detail.

As the team went to put final touches on the project, Hannah had returned to her role as Head Programmer. Jane’s attempt at coding had not produced a successful change in the code, and so Chris had taken charge while Jane returned to the report and worked with Hannah on that. Following this, Hannah seemed to focus more on using collaboration more to meet targets than she had previously (18.05.11 lns 9-17):

Hh:…now all our reviews are colour coded based like on the rating that they gave umm and then I’ve also the other day made brand combos umm within those brand combos are umm the products umm but it’s not the actual product combos that are inside I’ve got to combine them now umm so we’ve got loads of brand combos over here and then loads of product combos over here and they’ve just kind of got to be morphed together umm we did try and attempt to do that link thing I was talking about linking the reviews if they’re by the same person uhhh but I started doing that and it was quite complicated so I think Chris might have to help me with that cause we usually can work quite well together when we find a problem…

As the project reached its conclusion, Hannah had accepted that teamwork and collaboration were her best options for hitting her remaining programming targets, such as creating links between her now completed combos. While certainly one might assume she had planned all along to engage in some form of collaboration based on her preliminary interviews, Hannah had by this point abandoned much of her expressed beliefs regarding her elevated status within the group, and completed the project as an equal partner with the rest of the coding team.