But when you hit that wall, it is hard to stop and convince people to use different patterns and systems. I've seen so many tables go from "it will only be a few thousand rows" to suddenly several TB and then people are looking confused when performance and db admin tasks get really difficult.
I'm working at a scale where almost every day I have to ask people "are you use you need to treat that as relational data? It doesn't seem relational"
> But when you hit that wall, it is hard to stop and convince people to use different patterns and systems. I've seen so many tables go from "it will only be a few thousand rows" to suddenly several TB and then people are looking confused when performance and db admin tasks get really difficult.
It's much, much worse in my experience to have to develop for the opposite -- working on a system that was designed for an imagined "infinite" scale that in reality like 100GB and a few transactions a minute.
I, too, love soldering. I've done it since I was around 6 years old (wood burning before that). It's what I do when I want to zone out and relax. I've found random people at Burning Man and camping events who needed help with electronics, and I was happy to spend my time with an iron helping out - I even carry a butane-powered one on my motorcycle for quick repairs in the field.
Maybe I've just got deep scars from the 90's, where I'd wait 15-25 minutes sometimes to download a single mp3.
I have a FIOS connection here at home, and it seems entirely sufficient. Even AAA steam games, I hit 'download' and go grab a snack in the kitchen and it's done. My server does incremental backups to s3 every night, but its not like i'm sitting there watching it.
I download a new large model maybe once every other week. It takes a few seconds, maybe minutes. I don't really notice either way? 25x faster doesn't seem like it would make any difference.
I could imagine a leadership or viewpoint change in how they reported when/what was down.
I've seen so many times where Company A will complain that their vendors aren't accurate enough about uptime and how Company A notices first that their vendors are down, but then they themselves have a very laggy or inaccurate status page.
We want our vendors to be accurate to the minute on these, but many CTOs don't care to admit when they too have problems.
My first real soldering project (aside from just making cables) was a x0xb0x TB-303 clone. I somehow built it with a $10 radioshack iron and nail-clippers as flush cutters in an un-air conditioned Boston studio apartment over a summer. Probably not the first deep electronics project, but somehow it worked!
I've used it with Claude Code for refactoring and helping write a really in depth D&D campaign. Using frontmatter, I can keep metadata about NPCs and characters synced across all files.
Fixes all the problems I've had about "In what order do I put this data" and flipping back and forth in a huge stack of papers.
reply