-
For me, the 3 most important behaviors are saying "I don't know", being able to absorb massive criticism with ease, and move fast and break things. I've been in software development for a long time, and I think these specifically show vulnerability (and allow for the greatest personal and professional growth) and teach you to focus on what matters. By moving fast and breaking things, you are learning to deal with risks and unknowns, and recover when you fall, which is going to happen often in software development.
-
The benefits of a checklist are numerous, and I think it evolves as you move from a student into a professional career as a software developer. Keeping track of priorities, which will constantly change, is a big thing for me and a checklist. It also helps to know that you are making progress on something. Once you get a job writing software, it's easy to let things fall through the cracks and forget to track work, which is why checklists remain important as you graduate into a career of software development.
-
StrengthsFinder
What is your impression of strengths-based development? What questions do you have about this kind of development? I've used StrengthsFinder in my professional life on numerous occasions and I am a big fan of a strengths based approach to things. I don't have any questions about it at this time, since I'm fairly familiar with the psychology behind it.
What do you feel are your top strengths? How do you know? When I last took the SF assessment, my top 5 strengths were Achiever, Arranger, Ideation, Individualization, and Maximizer. I'll be very interested to see if those have changed, since it's been about 10 years since I took the assessment.
How do you hope to develop your strengths for your new career in software development? I think I'm so used to applying this thinking to a management/leadership role that just getting back into focusing on strengths as they apply to a more hands-on endeavor will be very challenging, and fullfilling at the same time.