ios开发者的未来
As Ballmer put it so energetically in the past, it always comes down to developers. Developers are always at the forefront of technology, but they haven’t always been served directly by technology. The previous paradigm of tech unicorns built their fortune on the backs of developers by convincing them to build within their walled gardens and then taking profits off the top. These tech giants subsidized the tooling as a public good since they reaped most of the value created within their gardens. Developers had plenty free tools to build with, but the experience was always what you’d expect with a public good — sufficiently working, but never mindblowingly good. VCs also hesitated to invest into the space because it’s hard to compete with free, and the value accrued to platforms.
正如鲍尔默(Ballmer)过去那样大力提倡，它总是归结于开发人员。 开发人员始终处在技术的最前沿，但并非总是直接由技术服务。 先前的技术独角兽范例通过说服开发人员在有围墙的花园中进行建造，然后从高层获得利润，从而在开发商的支持下建立了自己的财富。 这些技术巨头将工具作为公共物品进行补贴，因为他们收获了花园中创造的大部分价值。 开发人员可以使用许多免费工具来进行构建，但是对于公共利益而言，体验始终是您所期望的-足够发挥作用，但从不令人惊讶。 风险投资商还犹豫要不要投资于该领域，因为很难与免费竞争，而平台的价值却应运而生。
However, more recently, as developers began to take power back from the walled gardens, some of the most valuable tech companies have won by building directly for developers — from public giants like Atlassian, MongoDB, Splunk, Datadog, Elastic, and Twilio to private unicorns like Stripe, Auth0, HashiCorp, Elastic, Snyk, and Unity. These companies and their peers have already created hundreds of millions of dollars in enterprise value and are still growing quickly. We are seeing an acceleration in the funding and adoption of developer-serving technologies which not only gives developer more superpowers but also has huge implications for businesses and product in the next iteration of the web.
但是，最近，随着开发商开始从围墙花园夺回权力，一些最有价值的科技公司通过直接为开发商建造而赢得了胜利-从Atlassian，MongoDB，Splunk，Datadog，Elastic和Twilio等公共巨头到私人诸如Stripe，Auth0，HashiCorp，Elastic，Snyk和Unity的独角兽。 这些公司及其同行已经创造了数亿美元的企业价值，并且仍在快速增长。 我们看到开发者服务技术的资金和采用正在加速发展，这不仅为开发者提供了更多的超级能力，而且在下一版Web中对企业和产品产生了巨大的影响。
巨大的地震变化创造了新的基石 (Huge seismic shifts creating new building blocks)
One of the reasons we’re seeing more innovation than ever in the developer space is because the existing landscape of software development is undergoing seismic shifts, at a faster pace than ever before. This not creates more opportunities for new products to solve new problems, carving out both wallet-share and mind-share from developers, it also creates new building blocks and dynamic infrastructures for developers to experiment with:
我们在开发人员领域看到比以往任何时候都更多创新的原因之一是，由于软件开发的现有格局正在发生巨变，其发展速度比以往任何时候都要快。 这不会为新产品解决新问题创造更多机会，从而消除了开发人员的钱包份额和头脑份额，它还为开发人员创建了新的构建基块和动态基础架构，以供他们尝试：
1.Breaking down of monolithic applications into microservices adds a lot of devops complexity but also entry & exit points for new software and data feeds. 84% of surveyed mid-to-large organizations have embraced microservices, on average, deploying 180+ microservices each.
1，将单一应用程序分解为微服务会增加很多开发工作的复杂性，还会增加新软件和数据提要的进入和退出点 。 被调查的中型和大型组织中，有84％接受了微服务，平均每个企业都部署了180多种微服务。
2. There are now way more composable building units for developers to build on top of as APIs proliferate, partially due to microservices & popularity of GraphQL. There are more than 50,000 public APIs, and >60% of companies invested in a public-facing API.
2. 现在 ，随着API的激增 ，开发人员可以使用更多可组合的构建单元进行构建，部分原因是微服务和GraphQL的普及。 有超过50,000个公共API ，并且有60％以上的公司投资于面向公共的API。
3. Crypto protocols with native capabilities like payments, compute, identity, and liquidity allows developers to easily build business models into their projects without expending too much capital upfront to build out entire infrastructures to support these.
3.具有支付， 计算 ， 身份和流动性等本机功能的加密协议使开发人员可以轻松地将业务模型构建到其项目中，而无需花费过多的前期资金来构建用于支持这些功能的整个基础架构。
4. Accelerated adoption of containers and Kubernetes means applications are portable across different infrastructures, with ~90% of companies running containers to maintain flexibility, save on infrastructure, and increase developer efficiency.
4. 容器和Kubernetes的加速采用意味着应用程序可以在不同的基础架构中移植 ， 约90％的公司运行容器以保持灵活性，节省基础架构并提高开发人员效率。
5. Great front-end tools maturing to help make software development more accessible for front-end devs and even business users: Javascript is now the most popular programming language in the world, used by 70% of devs. They can access a suite of APIs using GraphQL, used by almost 40% of JS devs. Low/no-code tools like Webflow democratize web development even further to non-devs — more on that later.
5.强大的前端工具日趋成熟，有助于使前端开发人员甚至企业用户更易于访问软件开发 ：Javascript现在是世界上最受欢迎的编程语言 ，被70％的开发人员使用。 他们可以使用GraphQL访问一套API， 几乎有40％的JS开发人员使用过 。 Webflow之类的低代码/无代码工具使Web开发更加向非开发人员民主化-稍后将对此进行更多介绍。
6. Process innovations accelerating as well. Increased CI/CD adoption across enterprises requires new tools and processes across the organization.
6.流程创新也在加速。 企业中越来越多的CI / CD采用率要求企业中使用新的工具和流程 。
7. How companies work with data is changing rapidly with advances in ML, with increasing focus on operationalizing big data and data engineering. 62% of companies are getting ML models deployed into production or have deployed them for already for several years.
7.随着ML的进步， 公司如何处理数据正在Swift变化，并且越来越关注于对大数据和数据工程的操作。 62％的公司正在将ML模型部署到生产中或已经部署了数年。
These shifting landscapes create new complexities but also new building blocks for developers, and the core value prop of the next web is developers building with powerful web functionalities at a fraction of the risk. This will undoubtedly lead to a proliferation of experimentation and innovation.
这些不断变化的格局为开发人员带来了新的复杂性，同时也为他们提供了新的构建基块，下一个Web的核心价值Struts是开发人员使用强大的Web功能进行构建，而风险却很小。 无疑，这将导致实验和创新的泛滥。
从“支持”到“构建”心态 (From a “support” to a “build” mindset)
Meanwhile, as all companies start to become technology companies, business priorities converge with developer priorities, so developers are empowered to build business solutions directly:
同时，随着所有公司开始成为技术公司，业务优先级与开发人员优先级融合，因此开发人员有权直接构建业务解决方案：
There used to be a bifurcation between technology needs and business needs, because technology was seen as efficiency tooling (thus a cost center) for the business functions, but a whole lot was lost in translation between the builders and the users, and you’d end up with systems that looked like this:
过去，技术需求和业务需求之间存在分歧，因为技术被视为业务功能的效率工具(因此是成本中心)，但是建设者和用户之间的转换却损失了很多，您会最终得到如下所示的系统：
This is increasingly no longer the case. As all companies transform into technology companies, technology becomes a core part of the product. It only makes sense that the people building that technology are empowered to make the most important decisions about the products and services the companies use.
情况不再如此。 随着所有公司转变为技术公司，技术成为产品的核心部分。 只有建立技术的人员有权对公司使用的产品和服务做出最重要的决定，这才有意义。
对准 (Alignment)
This is extremely good for enterprises because business priorities can be integrated directly into the developer workflow rather than outsourced to separate, siloed teams. For example, as system performance became increasingly important to software companies, these metrics became integral to the developer workflow rather than outsourced to a separate ops team. Datadog emerged as a unicorn by helping dev teams directly monitor performance for the full stack as enterprise infrastructures shifted to cloud and the processes shifted towards DevOps. Synk similarly helped developers build open source code security into the process itself, allowing its customers to address issues at the root rather than rely on separate processes to find and fix them. We think there is room for many more business priorities to be integrated directly into the development workflow, such as authentication and privacy (Magic.Link, Evervault, Metomic) and cloud optimization (Northflank, Env0, Cloudskiff).
这对企业来说非常好，因为可以将业务优先级直接集成到开发人员工作流中，而不是外包给独立的孤立团队。 例如，随着系统性能对软件公司的重要性日益提高，这些指标已成为开发人员工作流不可或缺的一部分，而不是外包给独立的运营团队。 当企业基础架构转移到云且流程转移到DevOps时， Datadog通过帮助开发团队直接监视整个堆栈的性能而成为独角兽。 Synk同样帮助开发人员在流程本身中构建了开放源代码安全性，从而使客户可以从根本上解决问题，而不必依靠单独的流程来查找和修复问题。 我们认为还有更多的业务优先级可以直接集成到开发工作流中，例如身份验证和隐私( Magic.Link ， Evervault ， Metomic )和云优化( Northflank ， Env0 ， Cloudskiff )。
生产率 (Productivity)
As technology shifts further from a cost center to a profit center, developers can help the whole organization become superusers of technology to ruthlessly optimize productivity. Developers are naturally power users, and translating their processes to the rest of the organization can mean huge productivity gains. This A16Z talk from David Ulevich describes some compelling examples of developers’ typical ways of working which can seem eons ahead of our business processes. For example, developers are used to collaborating asynchronously in a seamless way using tools like Github, and products like Figma and Jam.dev are helping to extend this concepts to the design and product teams, but many business users are still stuck using inefficient naming conventions (v1, v2, vFinal, vFinalFinal, etc.) on static files to keep track of versions and sending them back and forth via email. Developers also prefer to use the most simple method of communication as that is basically what code is, and business users are also starting to catch on to command line communication in tasks like email (Superhuman), notes (Notion), and messaging (Slack).
随着技术从成本中心向利润中心的转变， 开发人员可以帮助整个组织成为技术的超级用户，以无情地优化生产力。 开发人员天生就是高级用户，将其流程转换到组织的其余部分可能意味着巨大的生产力提高。 这A16Z谈话从大卫Ulevich描述了开发者的典型工作能提前似乎我们的业务流程的亿万方式一些引人注目的例子。 例如，开发人员习惯于使用Github之类的工具以一种无缝的方式进行异步协作，而Figma和Jam.dev之类的产品正在帮助将该概念扩展到设计和产品团队，但是许多业务用户仍然使用效率低下的命名约定(v1，v2，vFinal，vFinalFinal等)，以跟踪版本并通过电子邮件来回发送。 开发人员还喜欢使用最简单的通信方法，因为基本上这就是代码的本质，并且业务用户也开始在诸如电子邮件(Superhuman)，便笺(Notion)和消息传递(Slack)等任务中进行命令行通信。 。
研发部 (R&D)
As advances in ML continues to perfect machines’ ability to synthesize what already exists, being on the forefront of what’s new will become one of the most marketable skills. Developers don’t just write code, they hang out on the bleeding edge of technology for fun. While many have enterprise day jobs, they also have nights and weekend projects which are fertile grounds for testing the newest advances in technology, essentially serving as a free R&D product pipeline for enterprises. This is also a sweet spot for many developer-facing companies to address with free or low-cost product. Whereas it may be difficult to convince a fortune 100 to shift to a completely new user authentication tool, it is much easier to convince a developer to use it for his/her nights and weekend project, until there is enough critical mass for the many superusers together to champion the adoption of these new technologies into larger enterprises.
随着ML的不断进步，机器能够完美地综合已存在的功能， 而站在新功能的最前沿将成为最可销售的技能之一。 开发人员不只是编写代码，他们还在技术的最前沿进行娱乐。 尽管许多人从事企业的日常工作，但他们还有夜间和周末的项目，这是测试技术最新进展的沃土，实质上是为企业提供免费的研发产品管道。 对于许多面向开发人员的公司来说，这也是免费或低成本产品解决方案的最佳选择。 尽管说服财富100强企业转换到全新的用户身份验证工具可能很困难，但是说服开发人员将其用于其夜间和周末项目要容易得多，直到有足够的临界数量供许多超级用户使用为止共同倡导将这些新技术引入大型企业。
This kind of technology adoption has two GTM motions — the bottoms up product-driven growth of a consumer-facing product with the potential of achieving virality — and the top down enterprise sales approach with the potential of achieving high ACVs and loyalty. Perfecting this growth strategy is a powerful opportunity for developer facing companies. This leads us to us to our next topic.
这种技术的采用有两个GTM议案-自底向上的产品驱动型面向消费者的产品增长，具有实现病毒性的潜力-和自上而下的企业销售方法，具有实现高ACV和忠诚度的潜力。 对于面向开发人员的公司而言，完善此增长策略是一个强大的机会。 这导致我们进入下一个主题。
考虑销售和产品的新方法 (New ways to think about sales and product)
Developers at the center of businesses have huge implications on marketing and sales, product, and business models. Companies like Asana, Slack, and Figma have already begun to refine these methodologies, but the science area is still nascent compared to traditional enterprise sales. These are just a few non-exhaustive examples:
处于业务中心的开发人员对市场营销，销售，产品和商业模式具有巨大的影响。 像Asana，Slack和Figma这样的公司已经开始改进这些方法，但是与传统企业销售相比，科学领域仍处于起步阶段。 这些只是一些非详尽的示例：
- “Consumery” customer acquisition channels such as digital communities, developer evangelism, conferences / hackathons, great documentation, agency partnerships, etc. with implications on how to measure and refine the funnel and ROI for each. “消费类”客户获取渠道，例如数字社区，开发人员宣讲，会议/黑客马拉松，出色的文档，代理商合作伙伴关系等，对如何衡量和完善渠道和ROI都有影响。
- A single stakeholder (or champion) sale with multiple “checkpoints” baked into the product journey, signaling depth of enterprise penetration, rather than a multi-stakeholder sign-off, all-or-nothing sale. This has implications on which initial stakeholder to target and how to help your champion sell into the enterprise (tiered pricing, documentation, case studies, business cases, etc.). 带有多个“检查点”的单个利益相关者(或冠军)销售进入了产品之旅，表明企业渗透的深度，而不是多个利益相关者的签字，全有或全无的销售。 这涉及到哪个最初的利益相关者作为目标，以及如何帮助您的拥护者向企业推销(分层定价，文档，案例研究，业务案例等)。
- More potential for virality thus a need to better harness it when it happens but also how to precisely layer in the more cadenced, predictable enterprise sales approach once “landed”. 病毒传播的潜力更大，因此需要在病毒发生时更好地加以利用，以及一旦“着陆”后如何精确地采用更加有节奏，更可预测的企业销售方法。
- Developers are the most critical customers, so product experience is really important, much earlier than a traditional enterprise product. The “buttery-smoothness” of a user’s experience, which we often ascribe to consumer products applies much more here, with emphasis on documentation and onboarding. 开发人员是最关键的客户，因此产品体验非常重要，比传统的企业产品要早得多。 我们经常将之归因于消费产品的用户体验的“模糊不清”在这里更为重要，重点是文档和入门。
- More informed and vocal customers as well requiring innovative ways to channel product feedback. Many developer-facing companies include their customers in the product development process as well as roadmap prioritization decisions as a core product feature. This can sometimes be a key reason for adoption because devs, unlike any other enterprise customers, have the option of potentially building it themselves. 消息灵通且忠实的客户，以及需要创新方式来传达产品反馈的客户。 许多面向开发人员的公司将其客户包括在产品开发过程中，并将路线图优先级决策作为核心产品功能。 有时这可能是采用的关键原因，因为与其他企业客户不同，开发人员可以选择自行构建它。
- Sales needs to support product. You cannot over-sell and under-deliver for developer-facing products, but there are important applications of the science of enterprise sales to increase ACV once the product has gained a foothold within an organization. 销售需要支持产品。 您不能针对面向开发人员的产品进行超额销售或交付不足，但是一旦产品在组织中立足，企业销售科学的重要应用就会增加ACV。
- Different monetization paths paves the way for more flexibility in the business models and a reduction in risks overall. From paid APIs, licensing agreements, to crypto tokens, developer-facing companies can price their services in a plethora of ways to carve out value. Companies can also use this to lengthen or shorten the timeline of value realization to make better decisions about how to capitalize the company. 不同的货币化途径为提高业务模型的灵活性和降低总体风险铺平了道路。 从付费API，许可协议到加密令牌，面向开发人员的公司可以通过多种方式对服务定价，以实现价值。 公司还可以使用它来延长或缩短价值实现的时间表，以便就如何利用公司资本制定更好的决策。
软件开发的下一个抽象层次：事半功倍 (The next level of abstraction in software development: doing more with more)
Some may say that the low/no-code movement one day will eliminate the need for developers, and while it is true we are already seeing a blurring of the lines between developer tools and business productivity tools, I highly doubt this will be the case. At the highest level, developer are just experts at abstracting technology tools up a level to help other users use them. The better the tools get, the less work the developer has to do each time. When a business user can leverage basic technology building blocks themselves to achieve their outcomes, the entire organization benefits. Low/no-code platforms help fill the gap in developer resources within an enterprise.
有人可能会说，低代码/无代码移动的一天将消除对开发人员的需求，尽管的确，我们已经看到开发人员工具和业务生产力工具之间的界限越来越模糊，但我高度怀疑情况是否会如此。 在最高级别上，开发人员只是将技术工具抽象到更高级别来帮助其他用户使用它们的专家。 工具越好，开发人员每次要做的工作就越少。 当业务用户可以利用基本技术构建块来实现其成果时，整个组织都将从中受益。 低代码/无代码平台有助于填补企业内开发人员资源的空白 。
Meanwhile, the components making up these building blocks are also getting more complex and powerful, requiring more developers to abstract them up into useful business applications. For example, the level of developer experimentation we’ve already seen with extremely complex open source technologies such as ML (e.g. GPT-3) and Crypto-protocols (e.g. Ethereum) is already staggering, but it will still take a while before an average business user will touch these technologies using low/no-code tools.
同时，构成这些构建模块的组件也变得越来越复杂和强大，需要更多的开发人员将它们抽象为有用的业务应用程序。 例如，我们已经看到开发人员对ML(例如GPT-3)和Crypto-protocols(例如Ethereum)等极其复杂的开源技术的试验水平已经达到惊人的水平，但是要达到平均水平还需要一段时间。商业用户将使用低码/无码工具接触这些技术。
Also, if you think about how much of the world is still unserved by technology, it’s easier to imagine that the no/low-code movement will only create more need for developers. Developers will be the shepherds of technology to the rest of the organization, and these no/low-code platforms will be their collaboration ground.
同样，如果您考虑到技术仍然无法满足世界的需求，那么更容易想到无代码/低代码移动只会给开发人员带来更多需求。 开发人员将成为组织其余部分的技术牧羊人，而这些无/低代码平台将成为他们的协作基础。
Ultimately the venn diagram of creators technology, consumers of technology, and the buyers of technology are converging on developers, a population that is growing in its definition day-by-day. This means the pace of technological innovation should accelerate dramatically in the coming years, in ways we can’t yet envision.
最终，创建者技术的维恩图，技术消费者和技术购买者都聚集在开发人员上，开发人员的定义每天都在增长。 这意味着在未来几年中，技术创新的步伐将以我们无法想象的方式急剧加快。
We have been diving deeply into this space at Northzone and are excited for what’s to come. The future looks bright for devs, and through them, all of us.
我们已经深入北区的这个空间，并对即将发生的事情感到兴奋。 对于开发人员来说，未来是光明的，通过我们，我们所有人。
翻译自: https://medium.com/northzone/the-future-belongs-to-devs-4df5c3a0d929
ios开发者的未来