我们初创公司的工程师不再开发新功能了。
在我们的初创公司，工程师不再直接构建功能。他们构建的是可以与内部工具（如 Zapier、Make 和 N8n）连接的 API。大多数“功能”，例如运行 SQL 查询或在产品 X 被订购时发送推送通知，都是由运营或产品团队利用这些工具构建的。
如果你有想法，就自己构建并发布。这种方式快速、赋权，并且让工程师专注于构建可靠、可扩展、安全的 API。同时，这也迫使我们编写更好、更简洁的 API，使其保持无状态和专注。调试可能会很困难，有时临时解决方案的逻辑会悄然堆积。
我认为这比传统模式要好，后者往往使工程师成为每个新流程的瓶颈。还有其他人尝试过这种设置吗？它在哪些方面存在问题，还是说这已经成为新常态？
查看原文
At our startup, engineers don't build features anymore. They build APIs that internal tools like Zapier, Make and N8n can connect to. Most "features" like running an SQL query, sending a push notification when product X is ordered gets built by ops or product folks using those tools.<p>If you've got the idea, you build and ship it yourself. It's fast, empowering and it keeps engineers focused on building a reliable, scalable, secure set of APIs. It also forces us to write better, cleaner APIs and the APIs stay stateless and focused. Debugging can be hard and sometimes duct-tape logic quietly piles up.<p>I think it's better than the usual model where eng is the bottleneck for every new flow. Has anyone else tried this kind of setup? Where does it fall down or is it the new normal?