✳flâneur — a map of the web's best reading

Time to Wall - by Julian Warszawski - Hundred Mondays

hundredmondays.substack.com · 970 words · saved by 1 readers

Here is my observation after 2 years of applying AI to assist in coding: the more convoluted the input codebase is, the less likely an LLM is to produce a satisfying result. It is hardly a revelation. They have been using the expression “Garbage in, garbage out” in the 60s already. The Sixties! I don’t think people realize the implications of of it though. Programming is a generational process. Output of one iteration is an input to the next one. The progress of those generations - the evolution of the codebase and it’s speed has been naturally limited by the speed at which an engineer or a team of engineers can produce code. With LLMs at our disposal, that limit is gone and it is the best thing that could happen to devs… who know their shit. All the rest might not be so lucky. Why do systems rot? Common sense would suggest codebases should only get better in time. There is no physical factor to contribute to their decay. No mold, rust, bacteria, winds or rains. The rotting does not ta

Time to Wall Why do systems rot? Julian Warszawski Apr 13, 2025 4 1 Share Here is my observation after 2 years of applying AI to assist in coding: the more convoluted the input codebase is, the less likely an LLM is to produce a satisfying result. It is hardly a revelation. They have been using the expression “Garbage in, garbage out” in the 60s already. The Sixties! I don’t think people realize the implications of of it though. Programming is a generational process. Output of one iteration is an input to the next one. The progress of those generations - the evolution of the codebase and it’s

Explore this link on the map →

saved by

related reading