InfoQ Homepage Communication Content on InfoQ
-
Remain in Tech by Becoming a Staff Plus Engineer
Engineers who want to remain focused on tech can follow the path toward a staff plus engineer. Staff plus engineers enable others to have impact. Bringing the people along can be hard; you need to work on your communication and influential skills. Nicky Wrightson presented The Secret Strategy for Landing That Staff Engineer Role at QCon London 2022 and will present at QCon Plus May 10-20, 2022.
-
How Open Source Can Pave the Path Towards a Staff+ Role
Open source contributions and long-term community engagement can help you on your path to a staff+ engineer role. Written communication skills are key for the async and remote work which is common in open source. Your contributions should be aligned with business needs, which can give you visibility that opens up career possibilities. Alex Porcelli presented at QCon London 2022.
-
Becoming a Staff Plus Engineer: Leadership and Communication Training Matters
The poor industry support for engineers who want to pursue a technical career affects them; many outstanding technical individuals find themselves forced to seek a management position. The path to a staff plus engineer role is not straightforward. Training on leadership and communication for staff plus engineers can help them to become a better tech leader.
-
Creating Tight Cohesive Tech Teams for Women to Thrive
Women in tech need a dynamic, valuing team, stimulating work, push and support, local role models, nonjudgmental flexibility, and personal power. Tight cohesive teams can provide high-quality interactions, making people feel valued.
-
Increasing Collaboration at Ericsson: Hardware and Software Developers Learn Each Other's Language
You can integrate hardware and software development with a cross-border team setup, where it’s important that hardware and software developers speak each other’s languages. The suggestion is to focus on “us” instead of “we” and “them”, and on the technical competence that connects developers over agile or lean terminology.
-
Shifting to Asynchronous Communication in Software Teams
As some companies begin to go back to the office and embrace hybrid working, they are at risk of alienating those who wish to remain remote, which is looking to be a considerable number of workers in our industry. James Stanier suggests using more asynchronous means of communication and spending more time writing to each other rather than speaking in meetings.
-
How to Work Asynchronously as a Remote-First SRE
The core practices for remote work at Netlify are prioritising asynchronous communication, being intentional about our remote community building, and encouraging colleagues to protect their work-life balance. Sustainable remote work starts with sustainable working hours, which includes making yourself “almost” unreachable with clear boundaries and protocols for out of hours contact.
-
Adapting a Zero Bug Policy to Solve Bugs
Applying a zero bug policy made it easier to prioritize bugs and increased team visibility and responsiveness towards bugs. As it’s a radical change, you will need to adapt it to your context regarding decision-making and time to fix a bug.
-
Dealing with Cognitive Biases in Software Development
Cognitive biases help us to think faster, but they also make us less rational than we think we are. Being able to recognize and overcome biases can prevent problems and increase the performance of software teams.
-
Assessing Remote Employee Experiences for Hybrid-Remote Work-Settings
Employers and employees have begun to prepare for their return to the office. One of the options is a hybrid-remote work setting which aims to support individual preferences when it comes to where, when, and how to work. According to Kaleem Clarkson, assessing your remote employee experience can help to make decisions on workplace flexibility policies.
-
Distributed DevOps Teams: Supporting Digitally Connected Teams
To establish a digital connection within a globally distributed team, an organization provided the team members with both collaboration tools and supplied an extra monitor with a visualization board. Collaboration using the online chat and white board initially posed challenges, as the board was tweaked towards the teams’ needs.
-
How to Improve Your Team's Communication and Psychological Safety
Mapping your team’s typical communication style can help improve communication and psychological safety, reduce friction within a team, and make conflict more productive. When we understand how we communicate and how we like to be communicated with, we not only have a better understanding of ourselves, but also of others, and this can play to our and their strengths accordingly.
-
The Impact of Radical Uncertainty on People
Humans look for certainty as that makes them feel safe. Suddenly becoming an entirely distributed team due to the pandemic disrupted people. According to Kara Langford, radical uncertainty can cause people to believe they are in danger and lead to health issues. People will respond differently; uncertainty has also shown to lead to fresh ideas, innovations, and social good.
-
Developing Testing Skills outside of Working Hours
Gamifying your way of testing, joining online testing communities of practice, and virtual traveling; these are examples of activities you can do outside of working hours that can make you a better tester. You can practice continuous learning with other testers in the world, and then implement things you learned at your workplace and share them with your team to improve ways of testing.
-
Becoming Personally Agile for Mental Health
Feeling the need to be constantly producing high-quality deliverables with a high sense of perfection can lead to stress and can cause burnout. You have to first accept that you have a problem to find your way out of burnout. Applying agile on a personal level can help you to achieve high goals while reducing stress and lowering the chance of getting burnout.