Adam Weisbart

An Accessibility Conformance Report (ACR), more commonly referred to as a VPAT® (Voluntary Product Accessibility Template), is a report that’s typically completed by an Accessibility Professional. It’s an important document to have, and companies should understand what they are and what they are not. https://lnkd.in/e7x5nhgA #Accessibility #A11y #Process

39

1 Comment

SDK documentation is not supplementary material... it is a vital component of the SDK itself. It lets developers harness the SDK's potential by serving as a highly sophisticated technical bridge. However, the tone must be instructional, and the approach must be simple. Here is a quick explainer video on the need for SDK documentation and its essential components.

19

New Cypress blog post showing how to mock the locked down "location.href = ..." assignments in your E2E tests: "Mock The Location Href Property" at https://lnkd.in/eRjSYNfn

11

It took a while but I really wanted to document the build (and also do a little bit of clean up of the code/repo). This is the accompanying article to the last post (the one with the video). In it I share some of the key aspects of building Cuttlefish and how the preso/video was produced - from #contextengineering and #vibetroubleshooting the code to #testplanning and how the automated tests were instrumental in making sure existing code was all good while adding new key features. #AI #AIMakerspace #Jira #softwareengineering #softwaretesting https://lnkd.in/gBEk2B4v

10

1 Comment

I created Conversation Stress Tester to look at how chatbots handle pressure. What sets it apart is that it does not stop at injecting stress into a conversation. It also validates the data, attaches reference responses, and produces HuggingFace - ready datasets with metrics on coverage, diversity, and quality. This system creates end-to-end datasets that can be both tested against and trained on. Still in early testing but This system will be available open source on GitHub next week. #Chatbots #ConversationalAI #MachineLearning #NLP #AIEngineering #AdversarialTesting #OpenSourceAI #HuggingFace

1

1 Comment

"𝗝𝘂𝘀𝘁 𝗱𝗼 𝗶𝘁" 𝗶𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗮 𝘀𝗹𝗼𝗴𝗮𝗻. It’s how I learned to influence without authority As a mid-level QA woman in tech. Waiting for permission wasn’t going to cut it. A colleague who was great at this stuff shared the basics: 🔸 Understand what’s really bugging them 🔸 Bring solutions that help the business 🔸 Show up prepared (always) 🔸 Do what you say you’ll do 🔸 Pick your moments to speak up But here’s what really moved the needle: 𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝗜 𝗻𝗲𝗲𝗱𝗲𝗱 𝘁𝗵𝗲𝗺. Coffee chats with devs. Checking in on product managers’ side projects. Remembering what stressed people out. So when crunch time hit, I wasn’t just “that QA person” I was someone they trusted. And it worked: ✅ I heard about issues early ✅ Devs shifted priorities when I asked ✅ My meetings actually worked because I’d already invested in listening 𝗔𝗻𝗱 𝗵𝗲𝗿𝗲'𝘀 𝘄𝗵𝗲𝗻 𝗶𝘁 𝗮𝗹𝗹 𝗰𝗹𝗶𝗰𝗸𝗲𝗱... A critical customer project. I had to convince leadership to shorten a risky freeze window. They said yes, not because of my job title Because of the trust I'd earned. And because I was clear about the risk and the business impact. 𝗜𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲 𝗶𝘀𝗻’𝘁 𝗮𝗯𝗼𝘂𝘁 𝘆𝗼𝘂𝗿 𝘁𝗶𝘁𝗹𝗲. 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝘁𝗿𝘂𝘀𝘁 𝘆𝗼𝘂’𝘃𝗲 𝗯𝘂𝗶𝗹𝘁. People who influence without authority: 1️⃣ 𝗕𝘂𝗶𝗹𝗱 𝗿𝗲𝗮𝗹 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 – They invest in people, not just projects 2️⃣ 𝗟𝗶𝘀𝘁𝗲𝗻 𝗳𝗶𝗿𝘀𝘁 – They understand what matters to others 3️⃣ 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗲 𝗰𝗹𝗲𝗮𝗿𝗹𝘆 – No jargon, just clarity 4️⃣ 𝗣𝗶𝗰𝗸 𝘁𝗵𝗲𝗶𝗿 𝗯𝗮𝘁𝘁𝗹𝗲𝘀 – They know when to push and when to pause They’re not tricks They’re how real leaders show up. Keep showing up this way, and people will start listening. 𝗪𝗮𝗻𝘁 𝘁𝗼 𝗹𝗲𝗮𝗱 𝗯𝗲𝘆𝗼𝗻𝗱 𝘆𝗼𝘂𝗿 𝗷𝗼𝗯 𝗱𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻? Start with coffee chats - not PowerPoints. Drop a 👍 if you're trying it. Go book that chat this week.

22

23 Comments

I’ve been writing a series of posts on the design principles behind Looping, a product I’m building to help teams run and evolve software over time. These principles shape the architecture underneath and have helped me prioritize clarity, composability, and long-term maintainability from the start. The latest post in the series is about Composable Services. In Looping, every service follows the same interface: it takes a hash of input and returns either Success() or Failure(). That consistency makes services easy to test, reuse, and chain together without resorting to sprawling conditionals or unpredictable side effects. The post walks through the structure, shows real examples, and touches on how it tracks source chains for observability and event logging. https://lnkd.in/ePkn-pF6 #ruby #rails #softwarearchitecture #buildinpublic

7

2 Comments

I'm nearly done listening to L. David Marquet's Leadership Is Language and I can't recommend it highly enough it for anyone moving into an EM role. There are many similarities with Todd Conklin's 5 Principles of Human Performance and the values that were expressed in the Agile Manifesto. What sets Leadership as Language apart is that he provides both the framing (eg: Collaborate, not Coerce) and specific, concrete linguistic expressions to manifest those outcomes. For instance, there are many studies that speak to the importance of psychological safety, but very few that provide specific guidance on exactly how to foster that outcome. This book is overflowing with specific linguistic recommendations. Rather than phrasing like X, phrase instead as Y. This actionable guidance is sadly missing in many leadership books. It's a great book and definitely demands an even deeper second reading. (Links in the comment)

11

7 Comments

"Isn't that the role of an architect?" A senior leader asked me this when I was talking about platform product management. It's a fair question and I have heard it before. Platform systems can be incredibly technical, but they need someone to champion the user perspective — to bridge what's technically possible with what users actually need. In some aspects, it's harder to grasp compared to user-facing products. IMO, Here's what makes Platform PMs unique: * Deeply technical system and users * Tough to imagine the product design * Guardrails as core construct * Adoption through alignment * Impact beyond revenue There's an interesting story about how this played out during a critical system failure, and how Platform PM plays a critical role in stability and scale of systems. Give it a read, and let me know your thoughts. https://lnkd.in/gAhRpD-C #Platforms #PlatformProductManagement #DataPlatform #ProductDesign

58

6 Comments