Zoom | Techlist.io

githubJun 26, 20262 min readCurated summary

Transitioning as a hubber

Arthur Searle describes transitioning at GitHub as a largely smooth experience, enabled by an inclusive, remote-first culture and strong workplace support. Using handles, written communication, flexible avatars, and gender-affirming benefits reduced many common sources of stress. His experience shows that transition can involve both bureaucratic challenges and profound joy when colleagues respond with acceptance and care. ## A Career Built at GitHub - Searle began in IT support and operations before teaching himself to code. - He joined GitHub’s IT Engineering team after a colleague’s referral and moved to Enterprise Security six months later. - His work has included: - Helping migrate GitHub’s main SaaS platform to infrastructure as code. - Speaking at Oxford University about version control. - Throughout his transition, his handle—“gleeblezoid”—remained constant, providing continuity at work. ## How GitHub’s Culture Supported Transition - GitHub’s remote-first structure reduced anxiety around appearance, commuting, and in-person interactions. - Much of Searle’s work happened through written communication in Slack and GitHub, limiting the pressure of speaking while undergoing voice training and hormone-related voice changes. - Employees commonly use handles and informal avatars, making gender assumptions based on appearance less central. - Searle was able to update his name and pronouns in internal systems, with colleagues consistently using them. ## Gender-Affirming Benefits - GitHub covered gender-affirming healthcare for employees. - Benefits included reimbursement for: - Voice training. - Hormone replacement therapy prescriptions. - Therapy. - The main remaining difficulty was ordinary administrative friction, such as changing his legal name in payroll systems. ## Acceptance, Joy, and Belonging - Searle contrasts his experience with people who remain closeted, repeatedly come out to new coworkers, or face extensive bureaucracy. - Colleagues treated his transition as a normal part of his life and expressed genuine happiness for him. - Small gestures had a major emotional impact, including hearing his name and pronouns used at work for the first time and receiving a shaving kit from a teammate. - He emphasizes that being trans is not defined only by hardship; there is also joy in living openly and being supported by others. GitHub’s example suggests that inclusive policies, flexible communication practices, and everyday respect can make workplace transition significantly safer and more affirming. For organizations, support should extend beyond formal benefits to the culture and systems employees use every day.

Read original

Zoom Github Slack Version Control+3

lineApr 8, 20263 min readCurated summary

The Key to AI Utilization Lies in 'Organizational Learning' - The Start of the Orchestration Development Workshop

LY Corporation is moving from simply adopting AI tools to building with AI as a collaborative development partner. Its new Orchestration Development Workshop teaches engineers to coordinate multiple AI systems across coding, testing, reviews, incident analysis, and other workflows. The initiative aims not only to improve efficiency but to free engineers from repetitive work so they can focus on more creative, high-value challenges. ## From AI Adoption to AI Collaboration - AI-assisted development and operations are spreading rapidly across LY Corporation. - Engineers use generative AI for code generation and testing, while combining it with non-generative AI for analysis and operational optimization. - Despite broader adoption, employees differ significantly in how deeply they use AI in their daily work. - The workshop was created to help the organization evolve from “using AI” to “creating alongside AI.” ## Orchestration: Coordinating Multiple AI Systems - “Orchestration” refers to combining multiple AIs, along with human input, to produce a complete outcome. - Example workflows include: - Generating code automatically from a Jira ticket. - Having AI run tests, conduct reviews, and create a pull request. - Analyzing a Slack incident report, estimating the cause, and proposing a fix. - The workshop turns these emerging practices into hands-on learning rather than passive demonstrations. ## A Hands-On, Interactive Learning Model - Participants follow instructors in real time and perform the same tasks themselves. - Zoom conversations and Slack questions create two-way communication during the session. - Instructors and representative participants explore solutions to problems as they arise. - The goal is for attendees to gain skills they can reproduce in their own projects, not merely acquire theoretical knowledge. ## Organization-Wide Support Through Guilds and DevRel - The initiative is designed to avoid depending on individual enthusiasm. - Three complementary functions support continuous growth: - **DevRel:** Drives the program and promotes adoption. - **Guilds:** Contribute practical insights from engineering teams. - **TD:** Helps maintain quality and reproducibility. - This structure supports consistent content quality and enables AI knowledge to spread across the company. ## Beyond Efficiency: Unlocking Engineering Creativity - LY Corporation views AI as more than a way to complete tasks faster. - By delegating repetitive work to AI, engineers can spend more time on creative and strategically valuable activities. - The organization aims to move beyond a model where AI writes code and humans only review it. - Instead, engineers should collaborate with AI from the design stage through implementation. ## Future Direction - LY Corporation plans to share lessons from the workshops through external channels such as its technology blog. - Future topics will include both generative and non-generative AI. - The broader goal is to provide practical guidance for engineers building new workflows with AI. The workshop represents a structured way to turn AI experimentation into repeatable organizational practice, helping engineers coordinate multiple AI tools while preserving human creativity and judgment.

Read original

Zoom AI Database Design PostgreSQL+4

figmaDec 6, 20232 min readCurated summary

From Slack-lash to Toggle Tax: The New Vernacular of Work | Figma Blog

The article presents a playful glossary for the changing realities of digital and hybrid work. These terms capture common frustrations, habits, and moments in modern workplaces—from endless notifications and multitasking to awkward meetings and collaborative design. Together, they suggest that humor and shared language help people navigate an increasingly virtual work environment. ## Balancing Effort and Iteration - **Fidelity Fluency:** Knowing how polished a project needs to be, and avoiding unnecessary pixel-perfect work when a rough concept is sufficient. - **WIP Waltz:** The continual cycle of revising, tweaking, and rethinking work as it develops. - **Style Guide Safari:** Exploring a design system’s typography, colors, and other visual elements to find the right creative direction. - **UI Lock Ness Monster:** A frequently discussed interface feature that is always expected in a future update but never appears. ## Digital Overload and Distraction - **Keyboard Cardio:** The frantic effort of sending emails and Slack messages, likened to an intense keyboard workout. - **Slack-lash:** The shock of being hit by a sudden flood of Slack notifications and messages. - **Tab Tsunami:** Having so many browser tabs open that the screen—and one’s attention—feels overwhelmed. - **Toggle Tax:** The mental cost of constantly switching between tasks and contexts. - **Workplace Whack-a-Mole:** Repeatedly responding to incoming tasks, alerts, and emails as soon as they appear. ## Virtual Meeting Experiences - **Icebroken:** Oversharing during an icebreaker and turning a friendly introduction into an uncomfortable moment. - **Screenshare Scramble:** Quickly hiding embarrassing or irrelevant browser tabs before sharing a screen. - **Zoombie:** Someone who appears present on a video call but is mentally disengaged. - **Zoom Zen:** The rare, highly effective meeting where the agenda is clear, participation runs smoothly, and the call ends on time. ## Collaboration and Social Validation - **Sudden Heavy Stamping:** Receiving an unexpected rush of positive reactions—such as hearts or “+1” votes—on a collaborative idea. - **Fidelity Fluency** also reflects collaborative judgment: teams must match the level of detail to the project’s actual needs rather than overinvesting in polish. The glossary turns the habits and tensions of modern work into memorable expressions. Recognizing these patterns can make digital collaboration more manageable—and encourage teams to protect focus, communicate intentionally, and find humor in workplace chaos.

Read original

Zoom Figma Design Systems User Interface+3

figmaNov 8, 20212 min readCurated summary

From candidate interviews to developer crits: how Figma engineering uses FigJam to scale | Figma Blog

Figma Engineering uses FigJam as more than a brainstorming tool: it supports team culture, hiring, collaboration, and technical feedback in a rapidly growing, hybrid workplace. By moving activities such as stand-ups and architecture interviews onto a shared digital canvas, the team preserves the spontaneity of in-person collaboration while creating a persistent record of discussions and ideas. ## Supporting Remote Team Culture - Remote stand-ups had become transactional and often ran over time as the team grew. - Engineers now post updates asynchronously in FigJam during a timed, 10-minute session. - Team members can add stickies, photos, reactions, hearts, and comments, making it easier to share personal updates and connect informally. - The shared canvas also encourages playful traditions, such as “20-second animal,” where everyone draws a selected animal at the end of a meeting. ## Scaling Engineering Processes - Figma’s mobile team grew to more than 20 people, creating a need for processes that scale with the organization. - Engineers focus on helping new teammates learn the company’s infrastructure and technology stack. - FigJam provides a shared space for organizing information and maintaining collaboration as teams expand. ## Digital Whiteboarding for Candidate Interviews - Engineering interviews include architecture and system-design exercises designed to reveal how candidates think and collaborate. - When interviews moved online, Figma replaced physical whiteboards with FigJam. - Interviewers share a prompt, observe candidates as they develop a solution, and discuss the design together on the virtual canvas. - Candidates unfamiliar with FigJam receive a brief orientation, and open sessions allow them to participate without creating an account. - The process retains the collaborative nature of in-person whiteboarding while working within Figma’s hybrid model. Figma’s approach demonstrates how a shared, flexible canvas can support both serious technical work and informal team connection. For distributed engineering teams, combining asynchronous updates, collaborative whiteboarding, and lightweight social activities can help preserve culture while processes scale.

Read original

Zoom Figma Figjam Android+2

figmaAug 11, 20203 min readCurated summary

An open letter about my gap year | Figma Blog

The post explores Abigail Africa’s uncertainty about returning to USC during the COVID-19 pandemic and whether taking a gap year would better serve her education, finances, and career. She argues that remote classes cannot fully replace the community, hands-on projects, and extracurricular experiences she planned for her senior year. Her decision is also shaped by family expectations, cultural background, and Silicon Valley’s complicated “dropout” mythology. ## The Case for a Gap Year - Africa had envisioned her final year around a senior capstone involving pitching, running, and growing a startup. - A remote semester would mean losing experiences such as: - Collaborating in makerspaces - Experimenting with hardware - Recording podcasts and producing videos - Building close relationships with classmates and professors - Many students faced different constraints: - Some would attend classes from their childhood bedrooms. - Others questioned paying full tuition for Zoom-based education. - International students risked visa complications if they did not return. - Africa’s reasons for considering time off were: - Waiting to return until she could fully participate in campus life - Working during the pandemic and building savings - Gaining more startup experience before potentially founding a company ## Family Expectations and the Value of Education - Africa’s family worried that a gap year could become permanent and prevent her from finishing her degree. - Her immigrant grandparents sacrificed established careers and worked minimum-wage jobs to support their children’s education. - Her parents similarly prioritized education over luxuries and invested heavily in her schooling. - For Africa’s family, education is the reliable path to success, while gap years and dropping out appear risky and difficult to justify. - Africa recognizes that she does not yet have a convincing answer to the fear that delaying graduation could mean never returning. ## Education, Economics, and Cultural Identity - Students were weighing the practical consequences of enrolling, taking time off, or graduating during an unstable economy. - Key questions included: - How employers would interpret a gap year - What a degree is worth under these circumstances - How losing access to a campus community would affect students - Whether delaying school would create financial advantages - Africa also considers whether these calculations differ for her as a woman of color, particularly in an industry shaped by unequal access and representation. ## Silicon Valley’s Dropout Mythology - Technology culture often celebrates the highly privileged, frequently male, elite-university dropout who becomes a successful founder. - Africa has rarely seen herself represented in that narrative. - Her startup internship gives her hope that the industry may be opening to broader kinds of talent and that meaningful opportunities can exist without a completed degree. - At the same time, she questions whether apparent meritocracy is truly based only on ability, since representation, privilege, and access strongly influence who receives opportunities. Ultimately, Africa presents the gap-year decision as more than an academic or financial calculation. It is also a question of identity, family history, opportunity, and whether traditional educational paths remain the best route during a period of extraordinary disruption.

Read original

Zoom Figma Startups Remote Learning+2

figmaMay 26, 20203 min readCurated summary

The making of Maker Week | Figma Blog

Maker Week is Figma’s twice-yearly company-wide tradition for exploring projects beyond everyday roles. In 2020, the event moved fully online, prompting Figma to prioritize connection, emotional expression, and collaboration over polished results. Its theme, “How to help one another,” shaped both the creative direction and the activities. ## A Company-Wide Creative Tradition - Maker Week is open to everyone, unlike hackathons that typically focus on engineering and design. - Employees pause nonessential meetings and, when possible, interviews to collaborate with people outside their usual teams. - The event is intended to remove day-to-day constraints and encourage experimentation rather than shipping finished products. - Figma continued the tradition because maintaining company culture was especially important during remote work. ## Prioritizing Process Over Output - The 2020 event explicitly discouraged optimizing for productivity or delivering polished work. - The emphasis was on working together, exploring ideas, and creating space for individual circumstances and capacity. - This approach acknowledged the difficulty and uncertainty many employees were experiencing. ## “How to Help One Another” - Earlier Maker Weeks had no central theme beyond making something related to Figma. - The new theme provided a guiding principle while responding to the broader challenges of 2020. - It encouraged projects and interactions centered on support, empathy, and mutual help. ## Designing Space for Vulnerability - Remote work created emotional distance but also offered opportunities for people to share more openly. - Figma’s creative direction aimed to give employees an outlet for whatever they were feeling. - The organizers encouraged vulnerability and treated all emotional responses as valid. ## Mood Characters - Figma created a shared playground file where employees could build “mood characters.” - Characters were assembled from familiar objects found around designers’ home workspaces. - The objects represented the mixed, conflicting, and often confusing emotions of working through a difficult period. - The activity gave everyone a simple way to make and share something, even without the time or energy for a larger project. ## Bringing Maker Week Online - Office-based traditions such as posters, shared breakfasts, and in-person kickoff moments had to be reimagined. - Figma replaced them with digital experiences, including custom Zoom backgrounds. - The company used visual design not only for branding, but also to create energy, delight, and a sense of shared participation remotely. Maker Week’s remote adaptation shows how a company tradition can preserve its purpose by changing its format. By focusing on connection, vulnerability, and low-pressure creativity rather than productivity, Figma made the event relevant to the circumstances of its employees.

Read original

Zoom Figma Graphic Design Remote Work

figmaApr 7, 20202 min readCurated summary

Keeping that tight-knit feeling, at a distance | Figma Blog

Figma argues that remote work requires more than moving meetings online: teams must intentionally recreate the informal interactions that build trust and community. Its approach combines aligned leadership, recurring social rituals, playful meeting practices, and collaborative activities in Figma. The goal is to preserve connection and morale even when colleagues cannot share an office. ## Keeping the Team Close - Remote work removes spontaneous interactions such as coffee breaks, shared meals, and hallway conversations. - Teams should preserve these moments deliberately rather than treating them as unnecessary. - Meetings that could be replaced by email or Slack can still provide valuable opportunities to check in socially. ## Coordinating Leaders - Figma’s CEO brought managers together to brainstorm ways to maintain team cohesion. - Leaders shared practices such as daily morning check-ins and virtual coffees. - A dedicated Slack channel lets managers exchange ideas, articles, and resources. - Individual teams can choose different approaches while maintaining a shared sense of collective responsibility. ## Creating Moments of Joy - Figma organizes optional workouts, pet-owner meetups, and other informal gatherings. - Zoom chat is used to applaud presenters, add comments, and ask questions. - All Hands meetings end with everyone briefly turning on video to see one another. - Biweekly “Show and Tell” sessions let employees share work, stories, or personal interests. - The company introduced playful elements such as sharing favorite Zoom backgrounds. - Daily Slack prompts encourage upbeat conversation, including recommendations for weekend television. - Donut pairs employees with one or two random colleagues for informal conversations. - Coworkers have adapted walking one-on-ones into Zoom or FaceTime walks. ## Collaborative Activities in Figma - **Figma Tennis:** Participants volley images back and forth, building on each other’s designs. - **Trash Dinosaur:** Teams collaboratively assemble a dinosaur from five virtual pieces of trash. - **Virtual bookshelf:** Colleagues display favorite or currently read books. - **Word-guessing game:** A Pictionary-style activity tests drawing and guessing skills. - These activities can stand alone or be used as short, energizing additions to regular meetings. Teams working remotely should intentionally schedule informal connection, support leaders in sharing successful practices, and make room for playful collaborative experiences—not just task-focused calls.

Read original

Zoom Figma Slack Remote Collaboration+2

figmaMar 30, 20203 min readCurated summary

How to run a remote brainstorm | Figma Blog

Figma argues that remote brainstorming requires more deliberate structure than in-person sessions, especially when teams can no longer rely on spontaneous huddles or whiteboards. Clear goals, shared tools, advance preparation, and smaller breakout groups help remote participants contribute more comfortably and creatively. The central recommendation is to preserve space for ideas while adding enough organization to keep the session focused. ## Why Remote Brainstorms Are Different - Fully distributed teams lose many informal collaboration habits, such as quick conference-room discussions. - Brainstorms require more creative energy than routine status meetings. - Uncertainty and remote-work challenges can make it harder for people to generate and share ideas. - Remote sessions therefore need both structure and room for exploration. ## Preparing the Session ### Define the Goal - Decide whether the session should produce many new ideas or refine a few existing options. - Tailor the level and type of input requested to the project’s current phase. - Communicate the goal clearly so participants understand how they can contribute. ### Set Up the Tools - **Video conferencing:** Put the call link in the calendar invite and encourage cameras where possible to create stronger personal connection. - **Shared Figma file:** Create one central workspace with edit access for all participants. - Use separate pages or frames for different themes. - Share a dedicated brainstorming file rather than relying on scattered documents. - **Chat channel:** For ongoing work, create a Slack channel for updates, notes, and follow-up feedback. - Add the working-document link to the channel topic for easy access. ### Share Materials in Advance - Send the brainstorming file the night before or the morning of the session. - Explain what the group should accomplish. - Add initial ideas or questions for participants to review and develop. - Allow people to ask questions privately or leave comments in the file before the meeting. ## Running the Brainstorm ### Start with Context and Guardrails - Restate the goal and explain what kind of help is needed. - Expect the conversation to go off track; enthusiasm can be a positive sign. - Create a “Parking lot” in the shared document for relevant but out-of-scope ideas to revisit later. ### Use Structured Exercises and Small Groups - Structured activities are generally more effective than completely freeform discussion when everyone is remote. - Divide participants into groups of two or three during video calls. - Smaller groups make it easier for quieter people to participate. - They also reduce technical and communication problems. - In each group, appoint a lead to report key takeaways to the wider team. - Share the Figma file on screen or have participants follow along using Observation mode. - Use video-conferencing breakout rooms when available. A successful remote brainstorm combines thoughtful preparation with a collaborative shared workspace. Teams should define the desired outcome, distribute materials early, use small-group exercises, and capture tangential ideas without letting them derail the main discussion.

Read original

Zoom Figma Slack Remote Collaboration+2