http://rcfox.ca
@RyanFox
- Your comment heavily implied (to me) scaling databases horizontally. Yes, it's not necessarily "Google scale" either, but it's a ton of extra complexity that I'm happy to avoid. But a Google employee is probably going to approach every public-facing project with the assumption of scaling everything horizontally.
With multiple servers talking to a single database, I'd still prefer to let the database handle generating IDs.
- Just following the chat for a few minutes, people posted links to a couple of other locations:
Okaukuejo waterhole in Etosha National Park: https://www.youtube.com/watch?v=AeMUdOPFcXI (at the time of posting, a herd of elephants are enjoying the water)
Kalahari Desert: https://www.youtube.com/watch?v=ME0dPuBtzug
- I worked on creating a card game with a couple of my friends. We kept all of the cards in a Google Sheet, allowing everyone to easily edit or create new cards. Then, I wrote a script to compile the sheet into a card atlas so that it could be consumed by Tabletop Simulator. It worked amazingly well.
The only issue was that I had to run the script myself, since my friends were less technical. I'd probably see if I could setup a workflow in Github Actions to do it for me if I were to do this again.
- In Python, every variable is either defined or imported in the file in which it's used, so you always know where to find it. (Assuming you don't do `from foo import *`, which is frowned upon.)
In C++, a variable might be defined in a header or in a parent class somewhere else, and there's no indication of where it came from.
- With Typescript, I find it pretty eager to just try `(foo as any).bar` when it gets the initial typing wrong. It also likes to redefine types in every file they're used instead of importing.
It will fix those if you catch them, but I haven't been able to figure out a prompt that prevents this in the first place.
- I graduated 15 years ago, so who know if my advice is worth anything anymore...
I think the best part of my computer engineering program at the University of Waterloo was the integrated co-op system. (Basically, internships.) It meant my degree was 5 years instead of 4, but I got work experience and professional connections at several companies and came out with a slight profit instead of a ton of debt. I even turned my last internship into a full-time job after I graduated.
- Seems like a good use case for a subagent. https://docs.anthropic.com/en/docs/claude-code/sub-agents
- Back before ChatGPT was publicly available, there was AI Dungeon. It was such a yes-man though. You could be in a scene with a king and a princess, then write "I eat the demon", and it would just invent a demon in the scene, and then describe how you unhinge your jaw and gobble it down.
- As far as radiation treatment software bugs go, it could be far worse... https://en.wikipedia.org/wiki/Therac-25
- My friend got his pilot's license somewhat recently and I went on a $100 hamburger run with him. It was a lot of fun! I studied gliders when I was in air cadets as a teen, so I knew a little bit about what was going on, and he let me take control for a few minutes (both seats had controls), but I was too nervous to do very much.
- Usually you would do it in your main function, or a code path starting from there. Executing code with non-local side effects during import is generally frowned upon. Maybe it's fine for a project-local module that won't be shared, but it's a bad habit and can make it had to track down.
Are the major distros shipping packages with tree-sitter support yet?