4,932 karma · joined December 1, 2020
email: contact at robbyzambito.me
bksy: @zambyte.robbyzambito.me
zambyte.at.hn
LLMs are deterministic. They are chaotic, which people confuse for non-deterministic.
Now, my entire programming flow does not even include an editor. The tools I use are: pi.dev to write and implement openspec specifications, herdr to manage many pi instances, and ollama to run qwen 3.8 27b on my single 7900 XTX.
Writing good specifications is the key detail here. I will often iterate on a spec for hours until I am happy with it all of the details. Once I am happy with the spec, I can be quite confident that when I tell pi to apply the spec, the changes that I want will be done, and done how I want them, when I come back to check when it reports itself as done.
The landscale is fundamentally different from what it was. Feel free to ignore it, but you can absolutely generate high quality code if you know what you're doing.
Edit: this is obviously assuming they literally meant robots.txt, but from a qyick skim of the site, it doesn't look like that was mentioned at least. I guess you meant it metaphorically :P
Luckily, AGI is pretty boring. It's a tool that does it's job. It seems like very wishful thinking to expect the same of ASI.
Trains need infrastructure, but a lot of the train infrastructure is already there, it just needs to be repaired and modernized. The USA freight network is one of the most comprehensive train networks in the world. The problem is that is has gone through decades of neglect, and trains are required to crawl through a large portion of the network so as to not derail. Urgent modernization of the rail network could happen in years instead of decades.
I'm sorry to shatter the dreams of most Americans, but the world has finite resources. Buying a car when you're poor is hard, because cars are expensive, because they are extremely resource demanding. Even with all the subsidies drivers receive, they still usually struggle with the cost.
By the way, you don't have to look at public transit schedules when your public transit works. I recommend visiting countries outside the US that have functional infrastructure.
Early programming in assembly mostly involved telling the computer how to do things that you want it to do. You instruct it in terms of the mechanical capabilities of the machine.
Compilers and interpreters came along and raised the layer of abstraction that programmers work on from the "how" domain to the "what" domain. Instead of saying how to move bits around to solve problems, we tell the computer what to do, and it would do it. Even languages like C in which programs seem like a description of how to compute something, they are more of a vague suggestion to the compiler, which will do what you told it to do, how it wants to do it.
Now in the era of agentic programming, the "what" isn't even the domain that programmers are operating in, it's "why". Why should we use these technologies? Why should certain architectural decisions be made to support future development? Why should protocols have or not have certain information in them? The relevant "what" questions are handled by the LLM, just like the "how" is handled by the compiler.
I really like using spec-driven development to capture the "why" as artifacts. I personally use the tool openspec, and I like it because it explicitly captures my reasoning in the documents it produces, but I'm sure there are other solutions. I also have a prompt that will generate a commit message for a change that captures "why" instead of "what", based on the conversation history. This is better than just describing what changed, because the diff already does that, and if you're looking at a commit to understand it, generally you'll be confused by the "why".
No matter how you do it, find some way to capture "why" as a material artifact. The "what" is the code that basically anyone can make now. Why will maintain your purpose.
https://en.wikipedia.org/wiki/World_War_II_casualties
https://www.academia.edu/115164883/Car_harm_A_global_review_...