Software Development

Creating a Culture of Trust and Psychological Safety in Engineering Organizations

Creating a culture of trust and psychological safety is crucial for engineering organizations. This article explores the five pillars of building trust and credibility within a team: building relationships, transparency, vulnerability, consistency, and communication. Building relationships involves getting to know team members on a personal and professional level. Transparency is about being open and sharing both good and bad news. Vulnerability means sharing failures and not having all the answers. Consistency involves being reliable and meeting commitments. Communication is key, and it is important to be explicit, ask questions, and actively listen. By focusing on these pillars, teams can foster strong relationships and create an environment where team members feel safe to take risks and share ideas.

Top 7 software bloggers to follow

This blog highlights the top 7 bloggers in the field of software engineering and product development. These bloggers provide valuable insights and ideas on software design, processes, and methodologies. The list includes Martin Fowler, known for his expertise in software patterns; Kent Beck, the creator of Extreme Programming and Test Driven Development; Paul Graham, co-founder of Y Combinator and an expert on startups and entrepreneurship; Jeff Atwood, co-founder of Stack Overflow; Andy Hunt, founder of the Pragmatic Programmer series; Joel Spolsky, a blogger who offers both sensible and surprising perspectives; and Steve Yegge, known for his entertaining content. Following these bloggers can help software engineers improve their skills and gain knowledge from the best in the field.

Maximizing Your Growth: A Guide to Getting the Best from Platohq Mentorship

Plato platform's mentorship program is designed to empower individuals on their journey towards success. By setting clear objectives, establishing a strong relationship with your mentor, actively engaging and participating, seeking feedback and implementing suggestions, continuously learning and growing, and reflecting on the experience, you can maximize the benefits of the mentorship program. Mentorship is a continuous journey of learning and growth, and by embracing the opportunity, you can unlock your full potential in pursuit of your professional aspirations.

10 Engineering Leadership lessons I learned with Customer Success Managers

Customer Success Managers can teach Engineering Leaders valuable lessons on prioritizing user needs and experience over technical complexities. By emphasizing customer-centric approaches, Engineering Leaders can ensure that products align with user expectations, enhancing satisfaction and retention. Effective communication and collaboration between technical and non-technical teams are highlighted as important for a holistic understanding of user requirements and driving product innovation. The text provides 10 lessons learned from Customer Success Managers that can optimize software development processes and deliver solutions that resonate with end-users and drive long-term success. These lessons include the importance of empathy for customers, putting into action what is advocated, enhancing the leadership voice of the customer within engineering, the significance of persuasion, the balance between support and confrontation, managing expectations, asking great questions, being invested in customers, seeking obstacles and issues beyond the product's scope, and the benefits of proactivity. By integrating these insights and strategies, Engineering Leaders can drive product development and enhance customer satisfaction, leading to increased loyalty and long-term success.

Learnings of a Solo Game Developer — Wacky Drivers video game

The author shares their journey of creating a video game called "Wacky Drivers" for Android and iOS. They had the idea for the game since they were a teenager and decided to use Unity as their development tool. They emphasize the importance of having a Game Design Document (GDD) to stay on track and discuss the development process, including creating reusable components and optimizing performance. They also highlight the importance of refining aspects such as controllers, game balancing, settings, and particles. The author advises releasing a minimum viable product (MVP) and gathering feedback early on. They also discuss their marketing efforts and future plans for expanding the game. The author encourages readers to try the game and provide feedback, and concludes by emphasizing the importance of consistency and sharing their enthusiasm for video game development.