crush_robo_1536
Joined 8 years ago
Joined 8 years ago
That being said, QA is definitely an important aspect of software development - regardless of who owns this work. Imo, instead of having a QA engineer per team or a few teams, you should have a QA shape role (similar to AVE you mentioned) that oversees a large area like an Org and pushes hard to make sure quality standards are held high across teams.
It's also trivial for engineers these days to have great e2e automated test coverage with AI. We're actually building getlark.ai that helps engineers with this.
It provides a simple runtime + client layer for controlling agents in a sandbox: - start an agent server inside a sandbox (npx -y runtimeuse@latest) - send prompts, stream outputs, and exchange files over websocket - cancel or manage long-running tasks
By default it runs an OpenAI Agents SDK agent with shell + web search tools. You can switch to Claude code agent with --agent=claude.
A Python client connects to the sandbox and lets you interact with the agent programmatically. Docs and quickstart available at the linked website.
We built this while working on https://getlark.ai/ where agents run in sandbox environments to generate end-to-end tests. Getting the infrastructure right took significant effort, so we extracted and open-sourced the runtime layer.
We’re excited to hear any feedback, thoughts, questions, and concerns in the comments!
There are also tools like https://rockyai.me/ that are making LLMs accessible within your browser so you don't even have to context switch between chat gpt and the tab you are on to ask LLMs questions. I use this all the time when reading engineering blog and I want to dig more into a specific section that I don't understand
- get tldr of a long article
- draft personalized outbound linked messages
- search if a specific company or type of role is posted on a long HN WHO IS HIRING thread
- ask questions when reading research papers on arxiv without context switching into chat gpt, etc