Catastrophic interference is also a favorite Wikipedia page and concept. The thing is, it doesnโt only happen to artificial neural networks, Iโve had it happen to me a few times. Especially with pin numbers, newer pins overwriting old ones and Iโm always scared when Iโm having hard time remembering something that this catastrophic interference applied and now the information is gone from my brain.
There are two kinds of suffering. One which you run from, and it follows you everywhere. And there is suffering you face directly, and in doing so become free.
- Ajahn Chah
So damn insightful.
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
I don't see much point in trying to build software at a "higher level", like whole products and services. I'm going to go down low and train myself on the fundamentals. Hopefully in time I'll be able to contribute to the foundational bits.
You're right, it does get exhausting. At some point you just want to rebuild everything, which is not possible.
I'm going to go down low and train myself on the fundamentals.
When I wrote an HTTP sever (albeit HTTP/1.1), I learned how primitive the HTTP protocol its magic became a skill. It is freeing understanding how things work and allows me to choose where to spend time with more intention.
Last year I wasn't feeling too good.
I turned forty, waited for surgery, and was hurt by my own colleagues. So I dealt with things. Maybe not so well, but to the best of my ability.
One of the consequences was that I got a bit heavy. My body changed, and I didn't feel like myself. It was a problem for future me. So now I am here with this little belly of mine. We're not enemies, but I decided it's time to part ways.
So I count calories. Maybe not so well, but to the best of my ability.
Thank you! Almost back to baseline now, after a few months.
trigger warning, eating disorders:
I sometimes forget to log what I eat in my app of course, but what is perhaps slightly nore disturbing is the fact that I sometimes log stuff and then forget to actually eat them. Some sort of Baudrillardian simulacrum of eating.
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.
I think you're right but executing on that idea requires a lot of care. It's similar to how functional programmers pathologically fear state; sometimes coupling/state are a necessary evil in order to keep the theory simple.
true! i might have been wiser to say: code quality is about managing coupling across the whole system. extracting a coupling sometimes requires you to introduce complexity beyond that which the extraction reduces.
Iโve had quite the successful day cooking today: make a Dutch baby for breakfast with blueberries, a bean stew for lunch using up all the weekโs odds and ends, make a coffee and walnut cake, and barbecued/slightly smoked a whole spatchcocked chicken for the first time!
Iโm an insane person who built their own coding harness, in Rust. Iโve called it Rho. Please forgive this landing page: https://rho-code.dev I just wanted an easy central spot.
Not insane at all. People should build their own instead of using other people's agents. It's easy to do and the results can be great for you. I've built several; one that is effectively "stuck" in Kakoune: youtube.com/โฆ/playlistYouTubeLLMs stuck in Kakoune
Yeah. It's a very large project with lots of dependencies. <The system prompt is long and wastes tokens. If you have ideas for tools (or automations like the agents.sh "loop" I wrote) it's easier if you understand the harness.
I am a remote worker, and has been for 4 years now. It works great. But the owner of the office I've been renting have sold the building, and the new owner has different visions. I could work from home, but my 3 month daughter is a screamer. I had a great, cheap deal. All alternatives I find is like 3x the price.