惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Microsoft Security Blog
Microsoft Security Blog
S
Secure Thoughts
酷 壳 – CoolShell
酷 壳 – CoolShell
S
SegmentFault 最新的问题
WordPress大学
WordPress大学
Hugging Face - Blog
Hugging Face - Blog
人人都是产品经理
人人都是产品经理
美团技术团队
博客园 - 三生石上(FineUI控件)
Jina AI
Jina AI
V
Visual Studio Blog
腾讯CDC
小众软件
小众软件
有赞技术团队
有赞技术团队
博客园 - 聂微东
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
IT之家
IT之家
C
CERT Recently Published Vulnerability Notes
大猫的无限游戏
大猫的无限游戏
T
Threat Research - Cisco Blogs
SecWiki News
SecWiki News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Hacker News
The Hacker News
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
Troy Hunt's Blog
月光博客
月光博客
雷峰网
雷峰网
T
Tor Project blog
I
Intezer
S
Securelist
罗磊的独立博客
The Register - Security
The Register - Security
H
Hackread – Cybersecurity News, Data Breaches, AI and More
NISL@THU
NISL@THU
Google Online Security Blog
Google Online Security Blog
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Cisco Talos Blog
Cisco Talos Blog
云风的 BLOG
云风的 BLOG
www.infosecurity-magazine.com
www.infosecurity-magazine.com
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
L
Lohrmann on Cybersecurity
The Cloudflare Blog
Attack and Defense Labs
Attack and Defense Labs
P
Privacy International News Feed
W
WeLiveSecurity
Forbes - Security
Forbes - Security
量子位
Last Week in AI
Last Week in AI

Pierce Freeman

A browser for agents | Pierce Freeman The grey market of podcast appearances The way I travel | Pierce Freeman Fixing slow AWS uploads | Pierce Freeman Local tools should still use vaults We solved scratch content first Starting a podcast in 2025 Being late but still being early Automating our home video imports Adding my parents to tailscale A deep dive on agent sandboxes Language servers for AI | Pierce Freeman My simple home podcast studio We need centralized infrastructure | Pierce Freeman Coercing agents to follow conventions using AST validation My unified theory of social selling My personal backup strategy | Pierce Freeman July updates to the homelab How the KV Cache works httpx is the right way to do web requests in Python Reputation is becoming everything | Pierce Freeman Building a (kind of) invisible mac app Updated knowledge in language models Making an ascii animation | Pierce Freeman How speculative decoding works | Pierce Freeman Under the hood of Claude Code Doing things because they're easy, not hard Speeding up sideeffects with JIT in mountaineer Firehot for hot reloading in Python Misadventures in Python hot reloading How text diffusion works | Pierce Freeman The tenacity of modern LLMs The ergonomics of rails | Pierce Freeman How language servers work | Pierce Freeman Just add eggs | Pierce Freeman Unfortunately SEO still matters | Pierce Freeman The futility of human-only web requirements Setting up Input Leap | Pierce Freeman Checking in on Waymo | Pierce Freeman The react revolution | Pierce Freeman Speeding up many small transfers to a unifi nas Quick notes on swift libraries AI engineering is a different animal San Francisco | Pierce Freeman Debugging a mountaineer rendering segfault Local network config on macOS Building our home network | Pierce Freeman Introducing Envelope.dev | Pierce Freeman Legacy code and AI copilots Typehinting from day-zero | Pierce Freeman Generating database migrations with acyclic graphs Lofoten | Pierce Freeman Mountaineer v0.1: Webapps in Python and React Constraining LLM Outputs | Pierce Freeman Passthrough above all | Pierce Freeman Accuracy in kudos | Pierce Freeman How quick we are to adapt The curious case of LM repetition Costa Rica | Pierce Freeman Debugging chrome extensions with system-level logging Speeding up runpod | Pierce Freeman Inline footnotes with html templates Parsing Common Crawl in a day for $60 An era of rich CLI All or nothing with remote work Adding wheels to flash-attention | Pierce Freeman LLMs as interdisciplinary agents | Pierce Freeman New Zealand | Pierce Freeman Representations in autoregressive models | Pierce Freeman Let's talk about Siri | Pierce Freeman Minimum viable public infrastructure | Pierce Freeman Reasoning vs. Memorization in LLMs Automatically migrate enums in alembic Greater sequence lengths will set us free On learning to ski | Pierce Freeman Dolomites | Pierce Freeman Using grpc with node and typescript Opportunity years | Pierce Freeman Buzzword peaks and valleys | Pierce Freeman Buenos Aires | Pierce Freeman Network routing interaction on MacOS Independent work: November recap | Pierce Freeman Debugging slow pytorch training performance The provenance of copy and paste Debugging tips for neural network training Patagonia | Pierce Freeman Santiago | Pierce Freeman My 2022 digital travel kit AWS vs GCP - GPU Availability V2 Independent work: October recap | Pierce Freeman Planning Patagonia | Pierce Freeman Relationship modeling | Pierce Freeman The power of status updates A new chapter | Pierce Freeman Give my library a coffee shop AWS vs GCP - GPU Availability V1 Switzerland | Pierce Freeman Headfull browsers beat headless | Pierce Freeman Webcrawling tradeoffs | Pierce Freeman Copenhagen | Pierce Freeman
The Next 10 Years | Pierce Freeman
Code authoring & testing · 2023-08-24 · via Pierce Freeman

90% : Strong Conviction

Personal notes for where we're headed over the next 10 years. While the future is never written in stone, I'm 90% sure of these outcomes. Past a decade, my confidence diminishes significantly.

LLMs will produce most of the functional code that's written in industry. The verification that this code does what users expect / intend is going to become critical. To create good software, it's not enough just to have a specification. You need:

  • Contextual knowledge of the business. The problems, the objectives, the design constraints (financial, engineering, design, etc).
  • The personalities at play. What do they expect it to do? How will they personally benefit from the development?
  • Knowledge of the existing solutions; where data is located, interfaces to existing vendors, what toggles can be modified today?
  • How will users use it? Will they follow the happy path? Does it need to be robust to adversarial inputs from outside?

In complexity theory, the definitions of P/NP distinguish problems that are solvable in polynomial time (P) versus problems that are verifiable in polynomial time (NP) but might be more difficult to solve in the first place. This relationship extends to how engineers write code today: the majority of time is spent writing functional logic instead of writing the tests1. LLMs will flip this relationship. Engineers are going to spend most of their time defining the business objectives and expected handling of workflows (happy paths, edge cases, expected IO relationships) instead of writing the functional code.

Authenticity

Consumers are going to be awash in generated content. This will serve the purpose of private marketing (classic advertising or astroturfing campaigns) and more malicious state-actor attempts to sway public opinion. As a result, people are going to place a much higher emphasis on trust capital online. The value of real, provable, and authentic relationships are going to increase.

  • Some trust might return to established organizations (the media, government, etc) but it just as easily might disseminate to community leaders. These individual leaders take different forms. Some might be known in-person though their local town, others may simply have a cult following of their blog, youtube shows, podcasts, etc.
  • There may be a healthy medium to the size of these followings. Too large and they risk getting tarnished with organizational distrust. Too small, it's difficult to moderate and prove their legitimacy.

Technology can be part of the solution here but only a part. All digital signatures can be forged. Photos purporting to show some international event will have to be verified by people who are there, or journalists from abroad. For us to then trust what they say, we need some notion of identity online.

Governments are really in the best place to ensure this authenticity online, but there's little public appetite for them to do so. The big mainstream platforms are in the second best place - but they themselves show little appetite for doing so. It's likely that developing nations will figure this out before developed ones2.

Market adoption

Most companies have become disillusioned with adopting new software. Managers have overseen one too many digital transformation projects that come in years late, millions of dollars over budget, and leaves the company in effectively the same state as it was before. Literature researches this as the productivity paradox, with some sources affirming and others challenging the conclusion3. Personally, I think this is more of a feeling than a quantifiable judgement.

Despite this trend, AI's biggest benefits can be accrued to companies and personas outside of Silicon Valley. Companies may not have seen much opportunity costs to conservatism in the past 10+ years because software hasn't changed that dramatically. But they will in the next 10. In periods of technical acceleration, the cost of losing out on technical gains becomes that much more pronounced. The opportunity here is in opex triage under the curve of ∫ workplace efficiency. That itself is going to be most highly impacted by technical acceleration.

SaaS software was mostly a focus on:

  • Business model change (flat fee + support to monthly recurring revenue)
  • Consumer-design brought to the enterprise
  • The cloud and continuous integration allowing startups to launch a half-baked offering and quickly improve it

AI SaaS will be governed by:

  • Quantifiable OPEX reduction in business costs
  • Sense of opportunity cost for falling behind
  • Business model change (utilization of models, or outcome driven revenue sharing)

AI has managed to captivate the imagination of people across backgrounds, because AGI feels so close at hand. Whether it is or not matters less than the worry of falling behind. This coupled with early case studies on business outcomes will likely buck historical hesitation to cross the chasm4.

Solved problems in historic ML research

Speech to text, text to speech, named entity recognition, and summarization will be fully solved problems. They already are in large part today. But we can assume that these primitives will be as stable as working with deterministic APIs will be today.

  • When you increase the input space of software / businesses to anything that's text based, you also open yourself up to more unintended consequences. Realistic input fuzzing for these pipelines is going to become important to combat adversarial attacks. A whole new wave of SecOps is going to be focused on these attack vectors; especially once the first big hacks become public.

50-90% : Medium Conviction

Cheap capital will not return

My basic argument: US debt load increasing will eventually need to print more dollars to cover payments to creditors. This results in more US denominated spending where other countries will spend dollars outside of debt instruments. They'll use returns for construction or their own economic stimulus projects. The Fed will have to keep interest rates high enough to keep larger inflation under control.

Some challenges to this:

The US benefits from issuing debt in its own currency. This position affords it greater leeway in managing debt without resorting to the printing press, especially if debt growth is matched by GDP growth.

  • I assume the US Dollar will remain the world's default reserve currency well into the next 10 years, but just because it has a preferable debt agreement does not free it from servicing its obligations. 5

The assumption that creditors will spend US dollars, thus potentially fueling inflation, does not account for the possibility that they might instead reinvest in more US assets, including debt securities. This reinvestment can actually fund the deficit without necessarily increasing the money supply or spending in the US economy.

  • This is a fair challenge. I imagine this will come down to the specific state of each economy. Current indications in 2023 looking at international markets that are facing debt squeezes don't paint a particularly rosy picture for re-investment.

Labor movements

Growing worry among some jobs that they might be replaced or already are. I've heard this specifically from designers, copywriters, and executive coaches. In some cases the results are quantifiably lower quality but they're still "good enough" to get the job done. This might encourage a resurrection of unions and labor movements that push for limits on AI in industry, or some financial profit sharing for companies where they are affected. See dockworkers during containerized shipping or car manufacturing for similar historical examples6.

There might also be a sense of inevitability with these changes, so people are proactively encouraged to learn new skills, go into training the models explicitly, or something else.

Interdisciplinary understanding

A big missing skillset in the market will be looking at business problems and actually determining how they can be refactored into an ML suitable problem. The tighter the IO contract on tasks, the easier we can benchmark and evaluate different models and approaches. We need bounds on performance of these systems before deploying in the wild, so we need to featurize it somehow to a binary outcome.

This knowledge might come:

  • Internally, via a new generation of workers that intuitively understands what LLMs/ML are good at and where they fall flat.
  • Via new job placement, where companies want in-house expertise to develop these skills.
  • External contractors, who define some of these problems and point to internal/external vendors that can help solve them.
  • External businesses, who can sell a solution to a problem that they know likely exists.
    • This change-management hurtle to enterprise sales will likely remain similar to today. They'll need to convince companies to modify processes, whereas companies might be motivated to just automate their existing workflows.

Building software remains easier than building things

Our software world is going to look dramatically different than it does today: more personalization, more delegation of tasks. This is going to be true in a world where things still look mostly the same. Buildings are going to be built in the same way as they are today, with similar designs and similar materials. Self driving cars might occupy some of the lanes, but they'll be a minority. AI isn't going to dramatically morph the layout of the physical world on this time horizon.

Compiled languages

Over the last 10 years, we've seen a surge in the industrial adoption of Python and Node. I suspect this is due to their simpler syntax, robust library support, and being pretty quick for POCs7. Compiled languages are going to see a resurgence in the next 10. We want to have systems that will throw errors early - so LLMs can quickly get feedback, modify their approach. Even better will be compiled languages that can yield problems at different levels of abstraction; syntax on the line, thematic flows in the large application, etc.

This trend is coupled with decreasing cross-language barriers. All languages are Turing complete; their main difference is in the syntax and in the libraries. When libraries can be automatically rewritten into another language, and the syntax becomes less important as people write less code, the best language will be the one with highest performance and the most robust compiler error handling.

<50% : Low Conviction

Low conviction things here could go either way. I imagine them being trends but I'm not sure which way things will tilt.

A lull in AI adoption

Achieving the last ~20% of ML performance is always the most difficult. And meaningful AI accelerants take time, especially when core research must be scaled up iteratively to training tasks that cost hundreds of millions of dollars. Discussion of AI has reached such a fever pitch - alongside with an overestimation of what it's currently capable of - we could risk seeing a corporate backlash and more caution around adoption.

  1. TDD purports to put a heavy emphasis on writing and defining tests, but in practice, this writing>testing relationship still holds. ↩

  2. See: Privacy regulations in Europe, India's Aadhaar biometric scanner, adoption of WorldCoin in other countries. ↩

  3. http://ccs.mit.edu/papers/CCSWP130/ccswp130.html; https://ideas.repec.org/a/sls/ipmsls/v25y20133.html

  4. Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers, Geoffrey Moore ↩

  5. Past reserve currencies (Dutch guilder, Spanish silver dollar, British pound sterling, French franc) have not remained this way into perpetuity. For each of these previous cases, increasing debt load and unpairing from the gold standard did eventually force the printing presses. ↩

  6. The Box: How the Shipping Container Made the World Smaller and the World Economy Bigger, Marc Levinson ↩

  7. Lack of typing makes it easy to move quickly initially, and only bites you once you get to a certain size. ↩