So I'm pretty sure this is the technology revolution that we're all sleeping on.<p>Like, self-driving cars? VR? Meh.<p>Accessible programming? A safe environment for folks close to a business problem that lets them solve that business problem on their own?! <i>That's</i> cool.<p>Like for me, in my experience as a software engineer, there's basically four types of employees: The tech-naive domain expert, the tech-friendly domain expert, junior coders, and senior engineers.<p>The two ends of the spectrum should stay focused on they're good at: Doing business stuff, or coding on tough problems.<p>It's the two roles in the middle that interest me: Tech-friendly domain experts and junior coders.<p>Right now, in most companies, tech-friendly domain experts could <i>totally</i> figure out a tool like Zapier and do things that they'd normally need an engineer to do. But their company doesn't use something like Zapier, so they can't. They just have to talk to technical people and make them do it. But there lies long debugging loops and, just, slowness.<p>In some companies though, those that have embraced low-code platforms like Tray or Zapier or the product we made (<a href="https://docs.middle.app" rel="nofollow">https://docs.middle.app</a>), they've enabled their tech-friendly domain experts to do tons of stuff they couldn't do before, without bothering people like myself, a more senior coder (I can work on platform things!).<p>ALSO, I've found that junior coders have a special role. We've hired non-programmers and taught them Python JUST so they could code new things in the developer side of our integration platform. It's a sandboxed environment with limited risk; they can go crazy coding whatever connectors or other things that those tech-friendly domain experts need. I don't have to be involved, outside of a code review every now and then. I know that they can't break anything other than the narrow thing they're working on.<p>It's neat. Neat stuff.