You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
focusing
Maria Ronauli
mronauli
focusing
Excited for an opportunity to forge my path as a software engineer and help individuals form stronger connections with each other through technology
What is your greatest strength and how do you know?
My greatest strength is civic: I communicate effectively, work well in teams, and am aware of societal concerns. I know this because according to my Pairin results, my qualities are caregiver, people developer and lover of humanity. This is true in my professional life because although I can work independently, I prefer to work on a team. I like to analyze each individuals' strengths as well as my own and play to each accordingly.
How do you work best?
I work best in an environment that provides some order and definition, but without heavy structure. In addition, I work best on a team environment that is supportive and encourages risk and growth. Such environment fosters collaboration which is important to me. I enjoy listening to others' opinions and ideas and believe it is important to have a well-rounded opinion by assessing all sides of an argument. For instance, I tend to have my own ideas and op
What role does empathy play in your life and how has it helped you?
Empathy has helped me grow personally and professionally. In both instances, empathy allows me to be an active listener and participant of a conversation. Such use of empathy allows for efficient communication which is vital in getting projects done. In addition, listening has allowed others to contribute more in my personal relationships and work environments when certain individuals are at first timid to give his or her opinion. In addition, empathy has helped me work on self-awareness by allowing me to indentify and manage my own emotions.
How does empathy help you build better software?
Empathic design helps us build better software by "turning preconceived notions on their heads," "revealing opportunities for new product applications," and "revealing future mistakes". Instead of coming up with a solution we think is best, empathic design allows us to hear what solution the people want. Next, when we list
What are each of our learning goals for this project? What drives us in this project?
Maria: I would like to gain a better understanding of methods and when to call methods on certain classes. In addition, I would like to get more comfortable with writing code using little reference. Alex: I would like to improve the syntax of my methods, get a better understanding of the workflow for a paired project and develop the soft skills to work efficiently with a partner. Common Goals: Push our understanding of the concepts (structures, git workflow, etc.) further.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
We’d like to try a ping-pong type of collaboration (for example, one of us will write out a test while the other one codes the method) and work more independently once we both feel comfortable with it.
How do you communicate best? How do you appreciate receiving communication from other
I have learned that implementing an agile workflow is more efficient than a waterfall workflow in terms of saving time. By this, I mean we broke out the requirements, design, implementation, and quality assurance steps each team we would complete an iteration instead of going through the requirements, design, implementation, and Q&A process once at the start of our project. By doing this, we were able to debrief with each other, refactor our code and receive feedback from our instructors along the way. The worse case scenario had we approached our project using waterfall workflow is that our project could have been implemented using logic that does not make the most sense.
Our group used Trello as a project manager. We held each other accountable by talking through the code that we wrote individually the next day. While working on iteration 3 and 4, we stayed at Turing to work on the methods assigned to each individual and rubber ducked each other if we were in an unproductive struggle.
What is one thing that went unusually well during this project? I think our group gelled pretty well together in terms
of personality which translated well into our workflow. In addition, we had concrete steps and plans of action in terms of what we wanted to accomplish each day.
In hindsight, is there anything you would have done differently? In general our workflow was smooth, however we spent a good chunk of Saturday waiting for one piece of functionality from another. We had anticipated that working on pieces seperately would not disrupt the flow, however this wasn't exactly the case. This resulted in a bit of time wasted.