I'm trying to construct an argument that LLMs are like a chess engine. People still play chess. But somehow this falls short.
Any conversation
🐉
let N=6,D0=[0,1,0,-1],D1=[1,0,-1,0],s=[],g={},d=x=y=xa=xb=ya=yb=0;
for(let n=0;n<N;n++){s=s.concat([1]).concat(s.map(x=>!x).reverse())}
for(let i=0;i<s.length;i++) {
x<xa && (xa=x);y<ya && (ya=y);x>xb && (xb=x);y>yb && (yb=y);
let t=s[i]?1:-1,e=(d+t+4)%4;
g[x]||(g[x]={});
g[x][y]=g[x][y]?"┼":"┌┐└┘"[(t*(D0[d]+D0[e])>0?0:2)+(t*(D1[d]+D1[e])>0?0:1)];
x+=D0[e];y+=D1[e];d=e;
}
for(j=yb;j>=ya;j--) {
let u=""; for(i=xa;i<=xb;i++){u+=(g[i][j]||"·")} console.log(u);
}·┌┐┌┐·······
┌┘└┼┘····┌┐·
└··└┐┌┐···└┐
···┌┼┼┘···┌┘
···└┼┼┐┌┐┌┼┐
···┌┼┘└┼┼┘└┘
···└┼┐·└┼┐··
····└┘··└┘··WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
I notice that language models are much better at programming than at writing. This is largely because, in programming, they have a closed feedback loop that allows them to find errors. Writing is much more complicated because the feedback is much more diffuse and delayed over time. In fact, it is often not well-defined.
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
It will become increasingly harder to find niche markets for software when those people can just build it themselves exactly how they want it. In the end, people want to accomplish tasks, and the AI is going to be building the software on-the-fly exactly for that task, why do we need generic software that may or may not be a fit?
Yeah. It makes me think that protocols for exchanging data between apps will become even more important in that landscape. But maybe, not - maybe each exchange is another bespoke AI-driven implementation?
Protocols, infrastructure, containers, those kinds of things. I was actually playing around with an idea for a minimal markup language + runtime that can be utilized by AI to spin up apps more easily, and brainstorming it with ChatGPT, I have a feeling something like that will appear soon to complement MCP.
I was curious of testing the Omarchy distribution this week just because I had some free time to work on it. I saw a lot of hate around it and kind of get the point but so far at least for what I have been doing it wasn't terrible (at least at the point of writing this) although I am not trying to convince anybody to use it. But it just remember me how much do I hate MS.