4,197 karma · joined March 1, 2008
https://www.reddit.com/r/applesucks/comments/1k6m2fi/why_do_...
First they came for the Communists
And I did not speak out
Because I was not a Communist
Then they came for the Socialists
And I did not speak out
Because I was not a Socialist
Then they came for the trade unionists
And I did not speak out
Because I was not a trade unionist
Then they came for the Jews
And I did not speak out
Because I was not a Jew
Then they came for me
And there was no one left
To speak out for me
https://www.mckinsey.com/industries/technology-media-and-tel...
And I did not speak out
Because I was not an artist
[1] Only creatures that felt the irrational drive to stay alive and procreate despite the odds and difficulties, did. All the sensible animals opted out. AI holds up a mirror that removes the illusion, and is inevitably developed by all sentient creatures.
(The really dark version would be the AI looking at each other and going: “Creatures are so dumb. This works in every galaxy. Let’s party.”)
For the first decade I wanted nothing to do with DB’s aside from places to store data. One day I saw a few things that made a massive difference and then went wild on learning how to speed things up. It’s fantastic and because few devs know this stuff well, it becomes a superpower. You wouldn’t believe what you can squeeze out of modern SQL DB’s and hardware, without touching any kind of optimised solutions. Which I love too but that’s a different post.
Maybe ask the DBA’s a few questions and see if that triggers any interest for you. Look at query plans and how many rows are processed for a query. How many columns. What is being locked. Can you remove locks when you’re just running a query and how much does that speed things up. There are queries for all sorts of metrics, eg which indexes are huge but never used. The DB can often suggest indexes, but don’t just use add the suggestions. Use them as a starting point to reason about your own. Try get down to low millisecond queries for really frequent stuff, because it’ll make them fast and means less time locking the DB, less RAM, less temp table storage.
All my other skills have aged. Fundamental database knowledge lasts.
TL;DR: you don’t need a world class jet when you trust your partner 100%. Anything less than 100, collaborate fast to overcome the limitation.
My intuition is that we moved through the hype cycle far faster than mainstream. When execs were still peaking, we were at disillusionment.
I suppose the issue would be media. Faster to load locally than push it out. Could be semi solved with typical web caching approaches.
A friend’s dad only knows assembly. He’s the ceo of his company and they do hardware, and he’s close to retirement now, but he finds this newfangled C and C++ stuff a little too abstract. He sadly needs to trust “these people” but really he prefers being on the metal.
Only weird thing is that they sometimes need to be put into the charger and taken out again to for one to connect. It just seems they should be able to reset without the ceremony.
Basically we compete more until everything costs more. Now we need multiple salaries because everyone we’re competing against is a highly paid couple. Rinse and repeat so everything of value is too expensive for “average people”.
An LLM is primarily trying to generate content. It’ll throw the best tokens in there but it won’t lose any sleep if they’re suboptimal. It just doesn’t seek. It won’t come back an hour later and say “you know, I was thinking…”
I had one frustrating conversation with ChatGPT where I kept asking it to remove a tie from a picture it generated. It kept saying “done, here’s the picture without the tie”, but the tie was still there. Repeatedly. Or it’ll generate a reference or number that is untrue but looks approximately correct. If you did that you’d be absolutely mortified and you’d never do it again. You’d feel shame and a deep desire to be seen as someone who does it properly. It doesn’t have any such drive. Zero fucks given, training finished months ago.
I don’t “trust” it in the way I’d trust a smart colleague. We know how this works: use it for info that has a lot of results, or ask it to ground itself if it’s eg new info and you can’t rely on training memory. Asking it about esoteric languages or algo’s or numbers will just make you sad. It will generate 1000 confident tokens. But if you told me to lose Google or ChatGPT+Claude, Google is getting dumped instantly.