what the hell is all this # Why all this? The honest section. About what happens to companies and roles when work runs through agents. And about why we're scared — and still having fun. ## What's changing — we can already see it Work moves faster. There's more to write down. There's more to keep in your head. And **roles are changing**. Not long ago we had analysts, testers, developers, marketers — like everyone else. Now our structure is flat, and each of us is called an **architect**. An architect is an analyst, a tester, a product manager and a few other people besides. We do completely different kinds of work, and that's fine. The expertise didn't go anywhere — it moved into **skills**. Former analysts write skills for analysis and make sure their colleagues' agents don't mess up. Developers write skills for their own tech stacks. Our development pipeline is a skill too: it takes a task from the request all the way to code, through a spec, a plan, a test plan and a task tree in SKEIN (see the [use case](https://skein.net/case-dev.html)). The owner, of course, sits around picking his nose and tossing out ideas: he has the taste and the feel for the business. **That's how it works for us.** Not a universal recipe. You may have leads, resource managers and quarterly planning — SKEIN fits that too: [here's how](https://skein.net/structure.html). ## The singularity — is it like this for you too? We don't know where this leads. We agree that we're in the singularity. On the one hand, we're scared. On the other, with agents this capable, every day we get the feeling that **we're already late**. We asked around — plenty of people who work with agents feel the same: > “I've never felt this much behind as a programmer.”