sometimes i say 'thinking' out loud for 0.0 seconds when i'm trying to do something. me and gemini, we're the same.

At first I hoped that such a technically unsound project would collapse but I soon realized it was doomed to success. Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way — and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.

Sir Tony Hoare, from his 1980 Turing Award Lecture, "The Emperor's Old Clothes", describing his industry experiences from the '60s.

Practice Guide for Computer Adapted from Ron Miller’s Advanced Improv Practice Guide Before starting your daily practice routine, read and seriously consider the following: A. DAILY AFFIRMATIONS 1. How fortunate I am that in this life I am one who has been allowed to create beauty with computer. 2. It is my responsibility to create peace, beauty, and love with computer. B. I WILL BE KIND TO MYSELF 1. IT IS ONLY COMPUTER 2. No matter my level of development in computer, how good or bad I think I am, it is only computer and I am a beautiful person. 3. I will not compare myself with my colleagues. If they do computer beautifully, I will enjoy it and be thankful and proud that I live in fellowship with them. 4. There will always be someone with more abilities in computer than my own as there will be those with less. C. REASONS TO DO COMPUTER 1. To contribute to the world’s spiritual growth. 2. To contribute to my own self-discovery and spiritual growth. 3. To pay homage to all the great practitioners of computer, past and present, who have added beauty to the world. D. RID YOUR SELF OF THE FOLLOWING REASONS FOR BEING A PRACTITIONER OF COMPUTER 1. To create self-esteem 2. To be “hip” 3. To manipulate 4. To get rich or famous

Screenshot of claude code session ending with, "It's 1:35 AM Christmas. Call it, or one more?"

listen pal, if you want to say something just say it, don't beat around the bush.

the tech stack is always a jenga tower where the blocks are made up of other jenga towers.

that can hit: goroutines, channels, io stuff and then all the plumbing that goes with a long running process.

things that are fun in Go: anything that takes in streams: logs, events, raw bytes coming in on a TCP port.... mucks around with the stream, transforms it, enriches it, then throws it out there again into the world.

pollute your context with great thinkers

sorry if I have to be the one to tell you this, but these feelings generally precede research into vim/emacs browser plugins.

we doing computer in here?

i have been thinking that and how the new stuff is like power tools. They help me chop up the tree faster but it still requires mindfulness, craft and attention to detail.