Friday, January 2, 2026 — Meeting Recap

LinkedIn and Python Group Updates

The small group meeting began with Shawn noting his absence due to flu, while Neil shared details about his Orca 4th Anniversary Limited Edition Sweater. The group discussed LinkedIn networking, with Dee expressing concerns about managing social media engagement while D shared advice about maintaining authenticity and relevance in connections. The Python group update from D mentioned their work on CloudTrail and JSON, with plans to cover Bodo and AWS SDK in the coming weeks, and they are recording sessions for sharing with the group.

LinkedIn Strategy and Engagement

The group discussed LinkedIn usage and social media engagement, with Don expressing feelings of obligation and platform fatigue. Tyler advised against using LinkedIn if it causes anxiety, suggesting focus on real-world networking instead. The group agreed that LinkedIn should be used strategically, with Michael sharing how he uses it for career opportunities while maintaining a minimal presence. Stryker shared that despite their negative views, LinkedIn is sometimes necessary for professional requirements, and the group discussed ways to make the platform more manageable by controlling notifications and focusing on meaningful connections rather than constant posting.

Cultural Differences in West Coast Workplaces

Stryker discussed his nervousness about joining a West Coast company, but the group reassured him that cultural differences between East and West Coast are often overstated. Neil advised focusing on establishing credibility through listening and understanding rather than being overly aggressive, sharing his experience working in Israel where direct communication is common and the work schedule differs from standard US hours. The group also shared anecdotes about cultural differences in various regions, with Shawn highlighting the more inclusive nature of West Coast workplaces compared to East Coast's more formal approach.

Developer-Customer Communication: Balancing Roles

The team discussed the challenges and risks of developers directly communicating with customers, with Neil advocating for maintaining a barrier between technical staff and customers to prevent over-promising or miscommunication. Jay and others agreed that while technical staff should not promise features or argue with customers, they can play a valuable role in customer discussions when properly trained and when a product manager is present to interpret customer needs. The discussion highlighted that while some companies successfully train developers for customer interactions, others struggle with this transition, leading to both under- and over-reliance on technical staff in customer conversations.

Enhancing Cross-Functional Communication

The team discussed the importance of effective communication between sales engineers, product managers, and developers. Juninho emphasized the need for clear communication of customer needs and the importance of PMs and engineering managers in customer conversations. Neil and Shawn highlighted the role of technical staff in influencing product development and translating customer requirements into actionable improvements. Michael raised concerns about the lack of training in communication and negotiation skills in organizations, while Jay discussed the challenges of bridging the gap between technical and business perspectives in cybersecurity. The team agreed on the value of training and the need for better alignment between technical and business goals.

Challenges in Cybersecurity Roles

The group discussed challenges in cybersecurity roles and organizational dynamics, with Stryker highlighting how cybersecurity professionals often face expectations to perform diverse tasks beyond their core responsibilities. Jay noted that cybersecurity teams are viewed as cost centers, explaining why business leaders may not prioritize understanding cybersecurity. The discussion concluded with Neil suggesting that building champions within different organizational domains, particularly in DevOps, could help bridge communication gaps between security teams and other departments.

Security Program Scaling Strategies

The group discussed strategies for scaling security programs across large organizations, with Jay describing SAP's approach of creating security experts through a 14-16 month Secuulum program and working with 40,000 developers across 20 product lines. Justin shared his experience with an internal Slack channel for security questions and a security champions program that has been successful without major issues. The discussion highlighted the importance of finding and empowering "diplomats" or "ambassadors" within teams to promote security awareness and knowledge sharing, with Stryker and others emphasizing the need to translate technical security concerns into business-relevant terms to gain organizational buy-in.

Security Risk Analysis and Communication

The meeting focused on security risk management and how to effectively communicate risk to business leaders. Jay explained their organization uses quantitative risk analysis, including Monte Carlo simulations, to model potential security incidents and create loss exceedance curves. This analysis helps demonstrate the cost-effectiveness of security investments, with Jay noting that security measures typically require about 1/20th the cost of the risk they mitigate. The discussion also covered how to engage developers who participate in security challenges like CTFs, with some participants preferring to remain hobbyists rather than full-time security professionals.