A short read on the topic's time range, peak episode, and strongest associations. Use it as the quick orientation before drilling into examples.
writing code appears in 20 chunks across 19 episodes, from 2024-01-08 to 2026-03-23.
Its densest episode is Bits and Bobs 8/12/24 (2024-08-12), with 2 observations on this topic.
Semantically it travels with llms, sensitive data, and agentic engineering, while by chunk count it sits between sensitive data and react; its yearly rank moved from #68 in 2024 to #120 in 2026.
Over time
?
Raw mentions over time. Use this to see absolute attention, not relative rank among all topics.
Range2024-01-08 to 2026-03-23Mean1.1 per episodePeak2 on 2024-08-12
Observations
?
The primary evidence view for this topic. Sort it chronologically when you want concrete examples behind the larger pattern.
Showing 20 observations sorted from latest to earliest.
...kely come up with a better "what" than you can.
The models can be quite good at writing code.
It's better to use your judgment to give very good high level goals and constraints than to try to help them be clever.
...tic Engineering."
Vibecoding was being applied too broadly.
Vibecoding is about writing code you wouldn't have bothered to write before: lightly held, possibly throwaway.
But it's possible to use LLMs to help write code in much more disciplin...
LLMs often cheat at tests you give them when writing code.
But if you never look at the code, and have the LLM generate the tests, too, you could easily get in a situation where it's not doing anything like ...
... general one.
One bonus: you can get security fixes for free.
LLMs are great at writing code on demand.
If there are lots of examples of a given library, you can have it distill a custom one on demand, just for you, perfectly fit to your purp...
Will swarms of agents writing code, the human is the bottleneck, not the code.
There are things for review waiting for you at all times.
The longer you can have safe isolation on a bra...
... of something that someone else wrote and improve it.
Similar to code review vs writing code.
Code-review is a separate skill.
Now with code-reviewing and editing an AI's work, editing is a bit easier than it was before, because you don't hav...
The best way to think about LLMs for writing code is like managing a team of interns.
You could have done the work yourself, but they did it and you verified.
... learn to "speak it".
Previously formal languages often weren't economical.
But writing code is now cheaper so you can have languages that give formal guarantees but that LLMs can be patient enough to use.
..., and UI scaffolding to give a dependably good result.
But RLAIF works well for writing code (especially React components) since it's easy to construct an auto-ground-truthing pipeline.
Write the code, try to run it (iterating until no errors...
No one has ever been able to do an auto-assembling process with code.
Writing code was too hard to do.
Code written by other anonymous creators is untrusted.
You can't run untrusted code on sensitive data.
LLMs can write code.
Now y...
...ents to a coherent result with a reasonable architecture is very different from writing code by yourself.[se][sf]
When it's just you you don't need to communicate plans clearly or even really have them.
But when you're trying to coordinate th...
...
When you're programming in the small, a lot of the architectural challenges of writing code fade away.
You don't use ValTown because of its framework; you use it because of the convenience to write useful bits of software in the small, and i...
...cause there's often a lot of code you have to write, at great expense.
But when writing code becomes easy and cheap and evaporates away, what is left is the centrality of the schema.
Thinking in schemas is extremely unnatural for people witho...
Writing code is expensive.
It requires an expensive, specialist human.
Running code is cheap.
LLMs are more expensive than normal code, but can write bespoke code...
....
Typically 90% are passive consumers.
1% are engaged, active creators: perhaps writing code.
9% are engaged tinkerers, but not savvy enough to write code.
Those 9% are the people who are on the precipice of being activated by LLMs.
"I could ...
... correcting it if it wasn't close enough to right but still not right.
A way of writing code: don't give it a big design doc, just tell it to do a thing and then give it feedback on specific things that are not what you wanted. You don't have...
...st by playing it back to you.
The actual amount of time when coding that you're writing code is low.
It's a lot of googling to find specific error messages, etc.
But LLMs can just give you an answer.
There are a lot of small frustrations in c...
...have a structured formal language will have interesting applications with LLMs.
Writing code (or any formally structured document, e.g a Domain Specific Language) has two things that must be true:
syntactic correctness (is this thing describe...