- Say "I don't know".
- Absorb massive criticism with ease.
- Be capable of writing bad code.
As someone who is starting this journey as a coder later in life, I realize I am behind in terms of general knowledge as someone else the same age as me. However, what gives me great hope for this field is that the technology and software is ever changing and therefore once the groundwork for understanding how one software works is understood, it will be translatable to any new software that comes out. But first I need to get to understanding the foundation, and to do that I need to set ego and pride aside and learn as much as I possibly can in a short amount of time as possible to achieve that. To do this I need to be a student long after I have left Turing, learning from as many people as I can willing to teach me.
Checklists provide an easy way to make sure the basics aren't overlooked, it can be very easy to overlook things when you become overconfident in what you are doing to miss something very simple. It also provides a way for less experienced people in the room to be more confident about speaking up, whereas they may have been more intimidated before because someone else was more senior or experienced. As a student a checklist would be useful as we will be learning a lot of new information daily and then moving on, having a checklist of basics to check would help us make sure nothing was overlooked while we are concentrating on the new task at hand. Introducing ourselves to each other as we work in groups will hopefully allow everyone in the group to be vocal if they think something is being done wrong or could be done better.
I can see strength-based development being useful in a large company that's constantly looking for innovation such as Facebook, but I wonder about how this would be brought about in a smaller company. My questions would be about how this would be used in a smaller company that is asking their group of software developers to build something specific rather than trying to innovate. In a large company like Facebook, they have the resources to shift around their talented pool of employees so that they can try out different fields they might not have considered before, whereas a smaller team may not have that luxury and must work on the task at hand. I think it's hard to tell this early what my strengths will be, but I really enjoy the logic aspect of coding. I feel my time at Turing will help hone in on my strengths, much like employees being put into different projects at Facebook, so that I can go towards something that will align with the strengths I discover.