I hereby claim:
- I am jf-lalonde on github.
- I am jf_lalonde (https://keybase.io/jf_lalonde) on keybase.
- I have a public key ASAtPnxNcy-6o8aRW3z0MsYgBlHukq7P-540N2fY3u69nAo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Setting Group Expectations
Group Member Names:
When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
Build on your professional story by thinking about how you're progressing at Turing. Answer the questions below in your own gist to use your StrengthsFinder themes to add to your story:
Use only the "string concatenation" technique to complete the following:
What role does empathy play in your life and how has it helped you?
Empathy is something that I hadn't given too much thought too until I became a manager. I found that the most effective way to communicate with others was by first attempting to see their side of the situation, so that we could move forward based on the same presuppositions. I wouldn't say I have come anywhere near to perfecting my ability to think empathetically, but I try to place myself in that mindset when working with others. I look forward to challenging my opinions and attitudes when faced with someone who thinks differently than I do.
How does empathy help you build better software?
I hadn't thought about this until reading some of the articles, but putting yourself in your target demographic's shoes is a brilliant way to think outside of the constraints your group might be in when developing software. If you develop in a vacuum, you could have the exact product you