https://gist.github.com/ontouchstart/b6a08b068cf863f0523bbd8...

``` nix run nixpkgs#llama-cpp -- server --models-dir models -m models/gemma-4-12B-it-Q8_0.gguf --port 8080 ```

open http://localhost:8080.

I also run pi in a docker container to do some vibe agentic coding. But I prefer `cat flake.nix | pbcopy` and paste into the browser. Then I can export the jsonl files and use tools to convert them to md and push to GitHub Pages.

I can do most of AI sessions off-line and only need hotspot to sync with GitHub.

My main use case is to learn and hack nix on Mac. It is fun.

Ignoring the implementation details, if we treat the whole global technology world as one single AI system made up of AI companies, independent developers/researchers, and end users, what would be the training goal and evaluation?

Fighting over engineering is hard. But it is also one of the opportunities for us humans in the era of abundance.

I did learn a lot about the ecosystem and myself from this experience.

https://en.wikipedia.org/wiki/Hello,_world

It is hard to find communities where people are not evangelical and soon you become an evangelist.

I am using LLMs to build my own graph of thoughts and try my best to follow them with critical eyes. Do not want to be influenced by or influence others.

Understanding is about analyzing and we still have some tools to help us, such as type checking, testing, etc. To some extent this can be automated but needs to be maintained automatically to match the flood of synthetic artifacts.

“Synthetic analysis” is an oxymoron and could lead to hallucinations and irrelevance.

The correlation between cost and value can be very complicated, especially in the chaotic world (or chaotic situation).

https://live.lean-lang.org/#codez=CYUwZgBAhgdgzgdxAJwgLgLwQC...

(I am fscking physics major! ;-)

This is a very important point, especially when the output is from a non-deterministic random walk with some unknown probability distribution.

> There is an old adage (e.g., Zen) to the effect that we become what we perceive. In computer terms, our (human) outputs become identified with our inputs. Computer technology is exceedingly habit forming, and our civilization seems to be becoming more computer-like, in the name of "progress". Many people tend to identify with their computers, while others become more computer-dependent, willingly or unwillingly. In addition, the so-called "factory experience" has an antihuman element to it. Although it could indeed help to reduce repetitiveness, it must also allow a suitable role for creativity. (In the spirit of this paper we note that unbridled attempts at creativity can often be detrimental, resulting in obfuscational terminology that masks an absence of novelty, or the reinvention of suboptimal or intermediate steps that have previously been discarded by others for subtle reasons not perceived by the "reinventor".) Thus, it is incumbent on system designers and system development managers to understand the negative effects of the use of computers, and to attempt to minimize those negative effects. In this way, it should be possible to increase incentives, challenges, and satisfaction, to reduce boredom, burnout, and laziness, and generally to increase the effectiveness of computer developers and users.

I will think “Agentic Engineering” is the “time-sharing” of our time. Embrace it.

https://dl.acm.org/doi/pdf/10.1145/1005937.1005938

It is very inspiring.

One example of teamwork is how the programmers and researchers worked together to build the UNIX SYSTEM (https://www.cs.dartmouth.edu/~doug/reader.pdf). It is not a product but an environment optimized for building tools and solving practical problems with tools written in C (while BBMs were busy with Lisp in Boston .;-)

C++ is a totally different story and you need an IDE for that.

On the other hand, there was lot of disruptive work did survive, or we can call them “hallucinations”.

Hindsight is 20/20.

I can see the potential of doing some implementation of APL/J/K at levels even lower than C, like how those guys did APL\360 using assembly language. It is going to be super fun in the era of everyone using LLM to pump out verbose Python/TS/Rust code with context windows bigger than the whole operating system.

I made a self documented (all the related links are in the file) single makefile (https://gist.github.com/ontouchstart/d3ad8e4d0adf63532303a90...) so that anyone can build ymawky from scratch and dig deeper by tinkering.