Non-Devs Shipping Code: My Take, Featured on Aviator 🎢
Got quoted talking about non-engineers shipping code at Slack — a trend I described as 'a roller coaster: really fun, a little scary, but it's happening.'
Got featured in a piece from Aviator on one of the trends I've had a front-row seat to on Slack's DevXP team: non-engineers shipping code. 🎢
My line that made it in: "non-devs shipping code is like being on a roller coaster — really fun, a little scary, but it's happening." That about sums it up.
What I mean by that: as the cost of actually implementing something drops, the bottleneck shifts. It's no longer "who can write the code" — it's alignment, planning, and knowledge-sharing. Those were never exclusively engineering skills to begin with. We're seeing this play out at Slack as more non-engineers pick up the CLI, get comfortable in a terminal, and start working directly in an IDE. There's real tension in that shift, and I think it's worth naming openly rather than pretending it isn't happening — because it's not just a Slack thing. I'm seeing the same pattern across the industry.
Organizations 🏢
Slack
