! n
Any conversation
A thing I've been doing lately is trying to come to the same conclusions others have without looking their the direct techniques and code. Last night I tried to figure out why people do vector based retrieval for RAG and ended up running these experiments: n0tls.com/โฆ/2026-09-03-i-think-โฆrag-with-grep.html
I'm still going to do an explore agent.
&
โโโโโโโโโโโโโโโโโโโโโ
โโโโโโโฃโฒ โ โฑโ โโโโโโ
โ โ โฒ โ โฑ โ โ
โ โ โฒ โ โฑ โ โ
โ โ โโโโฒโโโโโโชโโโโโโฑโโโโฃ โ
โ โ โฒ โ โฑ โ โ
โ โ โฒ โ โฑ โ โ
=โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ=
โ โ โฑ โ โฒ โ โ
โ โ โฑ โ โฒ โ โ
โ โ โโโโฑโโโโโโชโโโโโโฒโโโโฃ โ
โ โ โฑ โ โฒ โ โ
โ โ โฑ โ โฒ โ โ
โโโโโโโฃโฑ โ โฒโ โโโโโโ
โโโโโโโโโโโโโโโโโโโโโ
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
time.fyi/timezones is the most intuitive interface to working with different time zones I have used.
Judgement, taste and quality were always precious skills. In the world of , I have become more aware of the fact that it is often hard to put in words why something is good, great or amazing - or just looks good, but is average.
A lot of the professional content I see feels like most Netflix series. They have all the elements - but the overall experience is still meh.
Quality is still hard to achieve.
my wife is concerned that my job search will not be fruitful due to my use of ai to build and orchestrate my json and latex resume and cover letter build pipeline. it has not changed much since I initially built it almost 20 years ago. there are only so many ways that the core metadata can be assembled for presentation, yes?


