kukkeliskuu
Joined 7 years ago
Joined 7 years ago
While we all have all of the sides, for such a person, other sides are atrophied from under-utilization, while mind is hyper-trophied from overuse for for things it is not so good at. The primary obstacle for a person like that is to start developing the atrophied sides.
If this is the case, the best way to start is with the simplest possible partner dance, because mind-oriented people naturally approach learning complex body movements through mind, which is exactly the opposite you need to be doing.
So something where steps are one step per beat, like Swedish bugg.
The site https://tanssi.io
When the LLM writes a description of a codebase, you are doing transformation from more semantic meaning to less semantic meaning, and you by definition lose some details.
When you go from requirements to code, transformation is from from less semantic meaning to more semantic meaning. The the missing semantic meaning has to be invented. When inventing the missing semantic meaning, the success depends on what the LLM has trained on.
For me, one of the most important aspects of leadership is having a long-term vision, and being able to communicate it. In other words, it answers the question of WHAT.
One of the most important aspects of management is being able to organize resources to materialize that vision. In other words, it answers the questions of WHO and WHEN.
We still need to answer the question of HOW -- which require the expertise -- architecture and implementation.
All of these elements are necessary when doing anything -- even by myself -- but become even more important when using many external resources to do it -- be it a team of people or a team of LLMs.
There could be open source tooling to create custom private "closednets", with
- trust ring mechanism to allow invitations, flagging, banning, and banning those that invite people who were banned
- the rules of the closednet
- search engine with opt-in scraping
- portal (remember the 80s?) with all the registered nodes, perhaps by service category such as public git repo hosts, web sites etc.
etc.
The first closednet could be Hacker News.
Related to this, I created a tool for situations where you want to compare COBOL code with Java code. It includes a preprocessing step where IMS etc. calls are converted to mocks that return JSON (from file), and also use JSON for input/output, and GnuCOBOL to run the program. More a proof-of-concept than production, but here is a link if somebody finds it helpful.
Intermediate representations are often used to keep the architecture more manageable -- in compilers, for example. But these internal representations appear to increase expressability, which goes beyond the architecture.
For example, software development development cycle has several transformations: from requirements to user stories to design, and then to code. The stages are getting a revival, because they appear to be helpful when working with LLMs.
If we think LLMs as transformation machines, the transformation is reliable to the extent the source internal representation can capture the explicit semantics. The less LLM needs to make up in the content, the more reliable the end result.
This is close to how LISPers approach coding: invent a DSL for what you want to do, implement it in your DSL, and then implement the DSL. This approach seems to work well when creating systems that use LLMs.
You are not suggesting it, but as some might, I want to emphasize that I think it is, really, really, really bad idea to argue for limiting exposure of the bad practices because the papers may be useful even when not following good practices.
The science can work only when we can trust that the foundation it has been built on, including previous research, is solid.
The trust is partly based on the fact that science is self-correcting. As we know from charge of electron measurements, the existing narrative can work against the self-correction, even when everybody is trying to be as truthful as possible.
My impression is that to a large extend, on many fields, publication numbers (and money) have become so important that self-correction process may have become broken.