In software engineering, we are often encouraged to think about our contribution...

๐Ÿ‘‰ What did " I " do yesterday...?
๐Ÿ‘‰ What am " I " doing today...?

The language we use, both inwardly and outwardly, sets the tone for how we work and interact with othersโ€ฆ

Software engineering is a team game; our language should reflect thatโ€ฆ

The obvious:
๐Ÿ‘‰ What did "the team" do yesterday?
#developers #coding #softwaredevelopment #softwareengineering #wellbeing #mindset #mentalhealth

๐Ÿ‘‰ What are "the team" doing today?

These are useful questions to ask, but itโ€™s unclear how we contribute to the teamโ€ฆ

๐Ÿ‘‰ What did "I" do to "help my team" yesterday?
๐Ÿ‘‰ What am "I" doing to "help my team" today?

Now we are getting somewhereโ€ฆ

These are not just questions to be answered in a stand-up type meeting; you can reflect on them regularly to ensure you're adding value and making an impact.

The difference is subtle, but the scope for action is increased and feels more meaningful.

The value you add could be:
๐Ÿ‘‰ Providing clarity to a BA
๐Ÿ‘‰ Checking in on a colleague
๐Ÿ‘‰ Providing constructive feedback
๐Ÿ‘‰ From a conversation with a product owner
๐Ÿ‘‰ Helping QA understand the changes you've implemented

** The value you add to your team as a software engineer is not limited to the lines of code that you write. **

What questions can you ask to help focus more on your team? ๐Ÿ‘€