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

推荐订阅源

V
Visual Studio Blog
月光博客
月光博客
T
Tailwind CSS Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
量子位
人人都是产品经理
人人都是产品经理
IT之家
IT之家
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
博客园 - 三生石上(FineUI控件)
有赞技术团队
有赞技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园_首页
Apple Machine Learning Research
Apple Machine Learning Research
博客园 - Franky
The Cloudflare Blog
博客园 - 【当耐特】
Hugging Face - Blog
Hugging Face - Blog
大猫的无限游戏
大猫的无限游戏
S
SegmentFault 最新的问题
Jina AI
Jina AI
阮一峰的网络日志
阮一峰的网络日志
小众软件
小众软件
Last Week in AI
Last Week in AI

jola.dev

Migrating your Bluesky account the hard way | jola.dev Cluster singleton pattern | jola.dev cove.town, atproto self-hosted self-hosting | jola.dev Speeding up a Phoenix LiveView web app with a CDN | jola.dev Self-hosting an atproto container registry | jola.dev Migrating to the new Tangled knot2 | jola.dev Self-hosting and Tangled | jola.dev Self-hosting your PDS | jola.dev Taking control of your atproto account | jola.dev Latch - an Elixir atproto OAuth library | jola.dev Limited output is a feature | jola.dev Distributed rate limiter with HRW in Elixir | jola.dev A computer can never be held accountable | jola.dev Elixir Cluster 101 | jola.dev How to stop Claude from saying load-bearing | jola.dev Let libraries be libraries | jola.dev CI workflows on Tangled for Elixir | jola.dev Automatically syncing your blog to atproto and standard.site | jola.dev Appreciation for the small web | jola.dev Treating LLMs as programming books Publishing your blog to standard.site in Elixir Generating OG images in Elixir The social contract of writing Highest Random Weight in Elixir bunnyx: a bunny.net Elixir client library Building for the joy of building Running local models on an M4 with 24GB memory How to hit your Claude weekly limit so you can go outside and touch grass Dropping Cloudflare for bunny.net Building a blog with Elixir and Phoenix
No cost, no value | jola.dev
https://jola.dev/about · 2026-08-11 · via jola.dev

“The value of a thing sometimes lies not in what one attains with it, but in what one pays for it - what it costs us." - Friedrich Nietzsche

LLMs are incredible tools for generating code, and the frontier models can often build complete end to end apps with very little direction. We can have all kinds of conversations about whether the software they create is good, and what the definition of good is. But it is a fact that today software can be mass-produced by paying for tokens. You don’t really need to invest anything at all into it. You can just pay for a subscription, install the software, and start asking for things. LLMs make it trivial to build all kinds of apps, handle all kinds of tasks, do all kinds of work for you. They’re sold as something that removes toil. But we also lose something in the process.

The value of things

Things you create can have value in different ways. If you create something that is useful to other people, that save them time or bring them joy, then you create a form of value that’s extrinsically validated. This is the case for much of the software we use on a day to day basis, but also true for many of the things around us. Google’s search engine has value (although less and less so every day), so does your refrigerator and your sofa.

But things can also have value because of what they cost you to attain. Not for what they actually do for you, but because of the effort you put into them. When you say “make me a Twitter” to an LLM the output may be working software, but it has very little value. It’s probably not even worth the tokens you spent on it. You’ve recreated a billion dollar product, but it’s worthless. The same is true for whatever thing you have an LLM generate for you. You can clone just about any existing software and all you get at the end is a bill and a slightly janky version of it, that has no value. It has no value to anyone else because they could just generate their own. It has no value to you, because you did not invest anything into it.

We’re already seeing this. An incredible churn of vibe coded projects and libraries that are dead on arrival. There’s no investment behind them, no community. The person who generated the code has no reason to stick around, they’re just going to go generate the next thing. Github is turning into an massive pile of instantly abandoned code.

Do it the hard way

This means that you can choose to do the opposite. You can choose to do it the hard way. You can choose to toil and in that toil create value. Read the original spec yourself. Type out every line of code in your project by hand. Spend a week writing intricate product specifications. Don’t give in to the temptation of sending the LLM off to do it for you. Don’t turn away from the toil. Choose to write your library by hand and spend weeks doing something that an LLM could do in an hour. Create things that have real value, at least to you, because that’s worth doing. Because you grow as a person doing that. Because it brings meaning. Because you get something out of it that has value.

I want to clarify that I’m not saying you can’t be invested in a project where LLMs were used. There are many ways to invest your time and energy into building something, not just writing the code. But I believe that sometimes LLMs take something away from you, something valuable. They take away toil, but we lose meaning. They make it too easy to not engage, to not learn, to not struggle.

So go find the things that you think are worth investing your time and energy into. Create genuine software by not taking shortcuts. Go talk to some humans, draw some diagrams, and type out a whole lot of code. Go have fun!