-
Googling Aggressively. This is something that I learned at a young age(I suppose it was yahooing or lycosing aggressively when I started. You don't need to reinvent the wheel. Given the population of the earth and the amount of intelligent people on it, chances are people have tried to do the same thing you are attempting. Learning how to quickly identify the problem, articulate it in a colloquial way has saved me many times.
-
From the coding I have done so far, my issues almost entirely come down to micro-decisions. The little things I overlooked when I was moving too quickly. I need to acknowledge that naming conventions matter and that I need to be consistent with the format and convention I choose to use.
-
Saying I don't know has been one of the best learning experiences in my life. We all have egos, but when we come up against something we don't know, it is important to acknowledge the fact as quickly as possible so that you can quickly move to finding a solution or answer.
We don't know what we don't know. The very practice of thinking through a process in order to create a checklist gives us the opportunity to avoid mistake we might make if we just "jump in". Using a checklist during my time at Turing will be essential. We will be juggling so many different projects, ideas, timelines, names, dates, I'm not sure will be able to survive without the use of lists.
What is your impression of strengths-based development? What questions do you have about this kind of development?
I have been a part of three separate companies that have used strengths-based development in their core structure. Each company used separate programs. Lominger, BriggsMeyer and DISK. In each case, I learned something new about myself that aligned with the other programs. I believe that although strength-based development programs shouldn't be looked at as gospel in all cases, they are incredibly valuable for understanding your strengths and how to use your strengths to make up for your weaknesses.
My top strengths have proven to be my ability to work with others in an empathetic and understanding manner to overcome challenges. I am typically good at leading a team by helping to naturally divide work in an equitable and efficient manner.
I have the ability to zoom out and see a project from a higher point of view and break things down into their individual tasks.
I don't give up. I like to see a problem through to the end. I know this through my various assessments as well as the work I've done in the past.
How do you hope to develop your strengths for your new career in software development?
I hope to develop my hard skills in a way that complements the soft skills I already have. I want to be able to analytically think through a problem in a technical way. I hope to development a comprehensive understanding of how software is created and deployed.