During a school coding project, I noticed one of my teammates was heading in the wrong direction. He was trying to solve a problem by using abstract classes that, albeit they would have worked, took a lot more effort to implement than regular classes. The regular classes would have done the job, and although it would have been nice to customize our classes, we had a deadline and at our current rate, we were not going to make it. This problem was hard for me to address because he had already spent a lot of effort and time in this implementation. I did not want to belittle his efforts. To make matters worse, this would get rid of the majority of our code. For a moment I was victim of the straw man fallacy: I felt I had to choose between keeping my teammate happy or make our implementation more efficient and in time with our schedule. I realized the choice was an illusion, and I had to find the way to accomplish both. I prepared my arguments and called for a meeting. First and foremost, I praised his code for what it really was: an eloquent …show more content…
While the easier way to do this was definitely to just ask for help, I wanted to see how far I could take it myself. After trying to lift it, push it, and pull it, I realized it was too heavy to move in its current state. The friction between the rug and the desk was high. Also, when I tried to pull one of the sides, the legs in the other side of the desk gave a squealing noise, which made me afraid I would break it. I realized I had to solve these two problems in order to move the desk: move both legs at the same time and reduce the friction. My solution: find a cardboard long enough to place underneath the desk. This reduced the friction and allowed me to move the desk without pulling its parts. I’d like to say I thought outside the box, but I really just used a box to solve my