My only holdup is I’ve used this Google account for over a decade, and I have very little understanding of what in my life will break when it will no longer oauth against Google, and what deep Google features I’ve used this to login with as opposed to my old Gmail account. They make this very hard to understand on purpose.
My friends who have spent a lifetime learning how to make stable change on critical systems will be forced to adapt to help stabilize the tools that lost them their jobs.
Some of them will find a way through, some of them will join the Cobal programmers I have met in other industries throughout the world.
They have told me they were let go because they were getting old, or didn’t want to change. I wonder if it was a similar hype cycle that I was too new or young to see.
CEOs “any advancement in efficiency will reduce the need for jobs”
I’ve never seen so many of my friends out of work on the promise of efficiency. I’ve never seen so many forced to work on fulfilling that promise. I’ve never seen so many people out of work.
The jobs are in “ai” and they are not good jobs, they are not stable jobs, they don’t pay enough money, they pay with “promise”.
When you’re young or new, every technology is new, it’s hard to see the difference. You play along with wonder instead of fear, you feel valued, you haven’t seen the cycle before.
I’m tagging these posts so people who filter them out or subscribe can see them or not. I’m also calling LLMs AI because we’ve publicly lost that distinction but I’m honestly referring to this new product or feature category rather than a particular technology.
We have CEOs telling junior developers to not bother learning how to code, try to vibe code. That’s scary! You don’t learn much with vibe coding. Learning is the best part of the job!
I tell my junior engineers to not outsource their learning. AI can’t do the modeling, the architecture, the understanding. Can it do boilerplate? Sorta! But the job isn’t writing boiler plate.
We knew this way back with the no silver bullets essay on incidental vs necessary complexity.
When this bubble bursts, and the fraction of software that was created during it that remains useful will need stabilization. At some point the infrastructure that hasn’t been maintained will need rebuilding. Many engineers will be hired back again. But the people with the skills will be fewer and older.
Well... so far not that different as a consumer (I've never moderated a host, lots to look at in that area)
Here are some random notes; - SQLite by default - Full search - one process - WASM embedded FFMPEG!? https://codeberg.org/gruf/go-ffmpreg - 1gb of ram, rpi is a target - Does not support more than one app host, says scales to about 20 users
I wonder if we have a lightweight mastodon server that runs on sqlite with search on a single process server. I'll allow nginx in front of it for caching.
People keep complaining about how big mastodon is! I know stuff like gotosocial is a bit different, but how different?
- Half the buildings get destroyed because the Japanese accessibility standards never considered Kaiju. Godzilla is just trying to get around. - The breadth of plots, monsters and alliances means you can pretend to be any Kaiju with anyone being a friend or enemy however you like it. - I cannot imagine what it feels like to pretend to be Godzilla when you are young and small. It must be amazing. 🤩
I’ve heard it’s to do with a classical style of Japanese play that exaggerates a lot of elements. (Probably https://en.wikipedia.org/wiki/Noh Ty @wohali!) The craft of the masks and puppets were the show, it wasn’t suppose to be realistic.
A big part of the earlier movies are the craft. Nothing like this had ever been done before. Sure they could have used b-roll of real tanks but creating dozens of rc tanks with fireworks, or an entire city to be destroyed was a different class of artistry and devotion.
I mean look at this from 1993. It’s less than half of a highly detailed city to be destroyed. That sky scraper on the left doesn’t last long and it’s marvelous.
And then there are the tropes that persist through the dozens of movies. The very first Godzilla (Gojira) used radio announcers and scientists talking to reporters as exposition. It was repeated constantly in so many movies even today.
Much of the Godzilla movies in the 1990s are watching destruction on closed-circuit television in a control room. Can’t fathom why a fight is happening? They’ll be sure to tell you back at HQ.
I’m not gonna do any long #monsterdon threads but my kids fascination with #godzilla movies is so much fun. These wild plots, the contrived fights, the surprise twists, and the unknown motivations and allegiance of Godzilla itself. Oh it’s so juicy.
Godzilla commonly has two motivations : - Why did you wake me up!? - I’m the baddest monster
Sometimes it likes humans even, but often it dngaf.
Open source 🐛🧲- Maintains http://SerialPort.io & helped found Nodebots- Never graduating from @recursecenter - I write about the internet I wish we had and other silly things- I love to make things- Used to build and ship custom Mac servers to Microsoft/GitHub