> "It takes about three generations for people to forget. Those that experience the disaster themselves pass it to their children and their grandchildren, but then the memory fades,"
Some similarities to lessons from the 1918 flu epidemic that we relearned in 2020. We should build some "COVID stones" so we don't forget.
Yeah, I've gotten sucked into those stories before too and some are just too fanciful to believe. The AI being trained on Reddit data is going to do more than hallucinate...
This is an easily solvable problem. Make crypto-bros subsidize the electric generation they consume. Levy a tax on bitcoin mining and use that to build more power stations.
I threw out my 2 A500's into the electronics recycling when I moved houses 15 years ago. I wish I had kept them now that I have the space. I didn't have a monitor though since my 1084s was busted so I never used the computers.
It's too bad they didn't delve into the technical details of why the processes were pegging the CPU. Would have loved to see that level of Linux debugging narrated.
Meh... keep your passwords in an offline password manager and generated for each site. Don't store payment info anywhere, but if you do, make sure it's a generated CC number. Never link your checking or savings account to anything. Sure you'll miss out on some convenience, but you'll have your money and sanity.
Man, what an experience! I got goosebumps just reading that. So much history you could have learned. It's a shame you only got one evening with them. I mean you were with the pioneers of our field. It's like if you just happened to go out to dinner with a bunch of old men and they casually reveal, yes we played baseball too back in NY in 1932, hi, my name is George...
I used to love doing experiments like this. I was afforded that luxury as a tech lead back when I was at Cisco setting up Kubernetes on bare metal and getting to play with setting up GlusterFS and Ceph just to learn and see which was better. This was back in 2017/2018 if I recall. Good ole days. Loved this writeup!
Interesting! I really need a cheap way to spin up an Apple Silicon container to create binaries for an open source project on GitHub. I don't want to spend money on an Apple Silicon runner in GitHub and I also don't want to run the build directly on my M2 MacBook Pro along with my other development work.
Who owns the source code if AI is helping you write it? Is this a concern for companies that are copyrighting their code? What if multiple companies use this AI tool to implement an algorithm and then copyright it?
This is where the sales team hands it over to the consulting arm. You charge for that as well as the licensing. It's why companies like IBM are still around :)
As someone who evaluated software in the CI/CD realm for years working at an enterprisey company, not have an on-prem solution immediately disqualified you. We had to go through so much more red-tape to allow a SaaS offering in the enterprise it just wasnt' worth it. Yes, that's the enterprise for you. It's been a while since I've done that, so hopefully they've gotten better about it.
Are there concerns for earthquakes similar to how "fracking" used by the oil and gas industry has caused earthquakes? From the article:
>To generate geoethermal energy there, Fervo had to drill two horizontal wells through which it pumps water. Fervo pushes cold water through fractures in the rock, which heats it up so it can generate steam back at the surface.
paper or whiteboard for me too. I sometimes find paper too messy and too "constrained" I guess is the right word. A largish personal whiteboard in my cubicle was perfect for algorithm development or just putting down the flow of a app I was writing.
I wasn't in the "ORMs suck" mindset, but rather I just didn't want to take the time to integrate it since it was "just a small little project for a few people". But as word got around, more people got interested in it and wanted their own fields and data added. It was a case where premature optimizing would have been a good idea.
Back in my Java days a long time ago, I too preferred just writing prepared statements and then copying the data to my POJOs. Until I thought about it and decided to use reflection to do the heavy lifting after modifying the code every sprint to deal with new requirements. Then I added the ability for my POJOs to be annotated so I could define the table and columns it belonged to. It didn't hit me until near the end that I had reinvented Hibernate without all of the rest of its features.
I would venture to say that most non-tech startup companies are not equipped with the knowledge, the hardware, or the political fortitude to do something like that. Especially when it's customer's money at stake. It's one thing if Joe Schmo can't watch the latest Great British Baking Show. It's another matter entirely if Joe's paycheck is missing.
We used to do this for some large Artifactory clusters (~1bn artifacts) we ran on both the east and west coast of the US. Failing over to our DR cluster and our (internal) global DNS load balancer handled it just fine. Made upgrading those clusters seamless for the most part. Gave me confidence we could continue development in the event our main site fell into the ocean for some reason.