Virtual HLF 2020 – Scientific Dialogue: Sir C. Antony R. Hoare/Leslie Lamport
604 karma · joined July 14, 2011
Contact info on my website
https://ontouchstart.github.io
Virtual HLF 2020 – Scientific Dialogue: Sir C. Antony R. Hoare/Leslie Lamport
Even for computer science, take a look at Turing Award from 1966 [0], we will see how short sighted we are if we only follow the trend. Time will tell and smart people will find new path.
I only got to the point of having code and data as \verbatim in \LaTeX. Next step is CWEB.
Here is an example (with C and Rust code in \verbatim)
https://ontouchstart.github.io/rabbit-holes/llm_rabbit_hole_...
The ultimate goal is machine and human readable proofs on algorithms.
https://news.ycombinator.com/item?id=47280645
It is more about LLMs helping me understand the problem than giving me over engineered cookie cutter solutions.
https://gist.github.com/ontouchstart/bc301a60067f687b65dad64...
(This is an ongoing experiment, it doesn't matter what model I use.)
Instead of asking for answers, I ask for specific files to read or specific command line tools with specific options. I pipe the results to a file and then load it into the CLI session. Then I turn these commands into my own scripts and documentation (in Makefile).
I forbid the model wandering around to give me tons of irrelevant markdown text or generated scripts.
I ask straight questions and look for straight answers. One line at a time, one file at a time.
This gives me plenty of room to think what I want and how I get what I want.
Learning what we want and what we need to do to achieve it is the precious learning experience that we don’t want to offload to the machine.
https://ontouchstart.github.io/rabbit-holes/tex_rabbit_hole_...
FORTRAN, COBOL, PASCAL, C, Java, C++, Perl, PHP, Python, Ruby, JS, TS, and now Rust…
The only thing matters is people pay attention to them and then have to use them because their job requires them.
AI would not change it.
We are slaves of the trend.
https://simonwillison.net/guides/agentic-engineering-pattern...
https://gist.github.com/ontouchstart/bcffb186a753c5b75522fc8...
[1] https://docs.github.com/en/get-started/writing-on-github/wor...
https://ontouchstart.github.io/rabbit-holes/llm_rabbit_hole_...
Time to sit down, read, digest and understand it without the help of LLM.
> The above tools could theoretically be used to compile, build, and bootstrap an entire FreeBSD, Linux, or other similar operating system kernel onto MMIX hardware, were such hardware to exist.
https://man7.org/linux/man-pages/man2/dup.2.html
and
https://man.archlinux.org/man/dup2.2.en
A lot of bots are reading this. Amazing.
REDIRECTION Before a command is executed, its input and output may be redirected using a special notation interpreted by the shell. Redirection may also be used to open and close files for the current shell execution environment. The following redirection operators may precede or appear anywhere within a simple command or may follow a command. Redirections are processed in the order they appear, from left to right.
In the following descriptions, if the file descriptor number is
omitted, and the first character of the redirection operator is <, the
redirection refers to the standard input (file descriptor 0). If the
first character of the redirection operator is >, the redirection
refers to the standard output (file descriptor 1).
The word following the redirection operator in the following
descriptions, unless otherwise noted, is subjected to brace expansion,
tilde expansion, parameter expansion, command substitution, arithmetic
expansion, quote removal, pathname expansion, and word splitting. If
it expands to more than one word, bash reports an error.
Note that the order of redirections is significant. For example, the
command
ls > dirlist 2>&1
directs both standard output and standard error to the file dirlist,
while the command
ls 2>&1 > dirlist
directs only the standard output to file dirlist, because the standard
error was duplicated as standard output before the standard output was
redirected to dirlist.
...I know GNU -> Google -> SO -> LLM is a culture shift, this is how human attention goes. The search engine and LLM only capture the latest group attention and we have short memory. That is why reading is a critical skill for us as human beings, we can't afford to outsource that to machine. (Same with writing.)
https://www.gnu.org/software/bash/manual/html_node/Redirecti...
https://info.cern.ch/hypertext/WWW/DesignIssues/Overview.htm...
Allen Newell, 1975 ACM A. M. Turing Award Recipient: “Desires and Diversions”
https://www.youtube.com/watch?v=hCe0ZPGap_k
Wisdom from the previous AI era.
https://www.youtube.com/playlist?list=PLn0nrSd4xjjaSLBSzmno-...
Two decades of Git: A conversation with creator Linus Torvalds
https://www.youtube.com/watch?v=sCr_gb8rdEI
I was surprised that he only spent four months on it as a maintainer. What a great piece of work by a great software developer.
I do think your point is valid. The trend in the industry is putting emphasis on cosmetic qualities (format, workflow, testing), producing huge amount of metadata that consumes huge amount of human and machine energy for the peace of mind.
Complexity, maintainability, modularity have more to do with thinking about the problems at proper abstraction levels.
It seems we ended up spending more time on tools like writers spending more time on sharpening pencils or playing with fonts than writing something meaningful.
A low quality software can have beautiful code just like a low quality book has beautiful fonts.
Later I got my own IBM 386 and installed Linux on it and started to program in Perl …
I am a big fan of Jon’s YouTube videos on Rust and I started to use Rust in non conventional ways.
I am going to follow this lecture series and “port” them to rustdoc and see how it goes.
Another rabbit hole to fall down, it is going to be fun.
Then I fell down the rabbit holes of uv, rust and C++ and forgot about LLMs. Today after I saw this announcement and answered someone’s question about how to set it up, when I got home, I decided play with llama.cpp again.
I was surprised and impressed:
https://ontouchstart.github.io/rabbit-holes/llama.cpp/
I am not going to use mlx-lm or lmstudio anymore. llama.cpp is so much fun.