原文 · 未翻译
What if you could remove the struggle of context switching across several apps, bringing them together into one place?
Meet Brittany Ellich, Staff Software Engineer, and the productivity tool she built to streamline her work. We sat down with Brittany to learn about this project–what she built, how she did it, and how AI supported the development process from ideation to implementation. Brittany created a visual home that fits how she learns and thinks, all inspired by the GitHub Copilot CLI.
Visual learner? Watch the video above!
Q & A
What is your role at GitHub?
I’m a staff software engineer on the billing team at GitHub. My day-to-day work mostly consists of working on metered billing, so things like keeping records of Actions minutes, storage amounts, and copilot usage. I passionately dogfood everything that comes out of the Copilot org. I’m also an open source contributor to ATProto projects and built Open Social for applications built on the AT Protocol.
What did you build?
I built a personal organization command center to solve a simple problem: digital fragmentation. My goal was to take everything scattered across a dozen different apps and unify them into one calm, central space.
How long did v1 take to make?
I use a plan-then-implement workflow when building systems, leveraging AI for planning and Copilot for implementation. For v1, this approach let me move from idea to a working tool in a single day alongside my other regular work.
While planning, I have Copilot interview me with questions about how something should work until we have a plan that I think is adequate. That way, there’s less guesswork about what I want done and implementation goes more smoothly. Copilot will implement the work based on the plan that we put together.
What’s your favorite tool stack to build with?
I like working in agent mode in VS Code for synchronous development, typically with up to 2 non-competing agent workflows going at a time, and Copilot Cloud Agent for asynchronous development. I typically try to keep a few asynchronous tasks flowing with Copilot Cloud Agent, like bug fixes or tech debt changes that have been well-scoped, while I’m focusing on the work that needs more oversight in VS Code.
Follow-up loaded question: Do you care what tech stack your apps use now?
Not really. I’ve always wanted to build an Electron app and this is technically my first one, but I can’t say I learned a ton about Electron during this process since it was almost completely built by Agent Mode. That said, I went in and simplified the repo significantly to make it publicly accessible which required a lot more hands-on work (agents seem to like adding code but are much less enthusiastic about removing code) and felt pretty comfortable reading through the repo and making changes despite not having a ton of familiarity with Electron apps.