Hi there. I wrote this as a bit of speculation since I'm seeing more and more agent based coding in my consulting.
One thing to say given some of the comments here: in this approach the stuff in /src/md would be treated as well as stuff in /src/java or whatever: it would need to be maintained as precisely as possible, not just be a stream of development record of what has happened.
I'm also happy to consider that Markdown might not be the right format for this, or that the whole thing is a terrible idea. But I see people saving content in other places (linear, etc.) that drive agents and it just seems like maybe we should keep that stuff close to the generated source.
No different than UML diagrams: if you don't compile them to get your executable/binary, then they are out of date within a week. The code is the source of truth. Feel free to put steering in your docs. You can also use AI to make sure the docs still match the code.
No, the theory was based on the idea that money is sterile: it does not in and of itself produce anything, whereas the economy is productive. They were generally not sophisticated enough to understand the exponential curve of compound interest which is obviously incompatible with a finite economy, but long experience showed them that usury lead to wealth concentration and eventual collapse.
Unfortunately today usury is so endemic that people can't see any other way of living, even though debt-free publically issued money is an obvious possible solution to many issues we face today. See social credit (canadian, not chinese)
If you look at the right-hand side of your keyboard you'll see a key called "PgDn". You may use this to scroll through the article. Or, if you're using a fondle slab, just swipe to scroll.
All the money is (or will be) spent on land near other rich people so your kids can have a school peer group with parents who have higher education/wealth/social network achievements, and after that, healthcare, and after that, liability coverage.
If there is money left over, then you decorate. But you’ve probably bought into a new housing development with an HOA that doesn’t allow exterior modifications without approval.
This 1983 paper on ironies of manufacturing engineering was referred to me on twitter, and I think it makes many excellent observations that apply to post-AI coding, e.g.:
> By taking away the easy parts of his task, automation can
make the difficult parts of the human operator's task more
difficult. Several writers (Wiener and Curry, 1980; Rouse, 1981)
point out that the 'Fitts list' approach to automation, assigning to
man and machine the tasks they are best at, is no longer sufficient.
It does not consider the integration of man and computer, nor
how to maintain the effectiveness of the human operator by
supporting his skills and motivation.
I intentionally try to foster friendships with all sort of different people with obviously different political positions. Many of them are very far left and very far right and very far in a third direction i have trouble articulating, in ways that would shock most normal people.
What I have found is that, accepting the inevitable human flaws that we are all prone to, they are all pretty good folks.
One thing to say given some of the comments here: in this approach the stuff in /src/md would be treated as well as stuff in /src/java or whatever: it would need to be maintained as precisely as possible, not just be a stream of development record of what has happened.
I'm also happy to consider that Markdown might not be the right format for this, or that the whole thing is a terrible idea. But I see people saving content in other places (linear, etc.) that drive agents and it just seems like maybe we should keep that stuff close to the generated source.
reply