pbrumm

I have been programming with rails since the beginning and it annoys me that nothing to this day solves any of the problems that made me jump to it back then. And this obviously just rhymes with Rails.

- Convention over configuration - db migrations - one way to do something - easy to pick up someone else's project and make progress - great for Jrs to build and be productive - enjoyable to maintain apps for decades - consoles that let me fix and explore - ...

I still use it every day solving problems for customers that pay me to make their lives better.

If an AI slop startup comes to me for help I will direct them to a rails rewrite if they have paying customers and my hourly rate will be based on current 128 ddr5 ram prices.

I used these for years and really enjoyed the typing experience. Fond memories of pinching to paste without having to reach down to the trackpad.

If they are confident in their discovery they should pay some scientists to start making this and testing it out.

I think they should acknowledge that they are liable for damage done now and in the future by their servers

Publish all their external ips and if hacking is attempted through them have easy and strict monetary payout with independent review process. Model it after the CMS IDR process

If they are caught using proxies 10x the fines

Limit their GPU quantities and force them to be more efficient with their resources.

Enforce attribution on their results

So google is accusing an AI company that has a customer who is paying them money to develop software that caused damages. Sounds like the AI company could be liable?

If I am paid by someone to create an exploit that caused damages wouldn't I be liable? Or could I avoid it by making my client sign a terms of service agreement to not use it that way?

Who created the model and who helped with GPU power to run the model to create the export and should they be doing more.

There is wal-g that moves the wal files to s3 and you can spin up any number of instances off of that. Works great for catching up secondary servers

Have you tried switching it to a job queue where the GPU instances try to keep themselves busy. That way you can auto scale the gpus based on utilization. I find it easier to tune and you can monitor latency and backlogs easier. It does require some async mechanisms to the client but I have found it easier to maintain

I wonder how many audio conversations were overheard and uploaded during that moment.

Seems like an attack vector for forcing your devices to start recording the mic and transmitting it.

Even if it just takes down the wifi through maxing out internet connection or cellular network. Play a couple seconds of audio and gigabytes get uploaded.

If you have optimized your math heavy code and it is already in a typed language and you need it to be faster, then you think about the GPU options

In my experience you can roughly get 8x speed improvement.

Turning a 4 second web response into half a second can be game changing. But it is a lot easier to use a web socket and put a spinner or cache result in background.

Running a GPU in the cloud is expensive

I think it is somewhat like git's creation story. Sometimes a senior dev sees a tool that is close to ideal but needs to work a little differently than what the industry has built.

Databases are up there with encryption. Don't roll your own... mentality.

But sometimes they don't fit the problem your solving. Sometimes the data never changes so why have infrastructure for updates.

Having a big DB running all the time could be too expensive for your business model

Also it is good to be curious about "what is an index" and how does a parquet file look in hex editor. Why can't I write the underlying db table outside of postgres. Why are joins hard..

And then you discover your tools give you a competitive edge

Most of the time there are existing tools, but sometimes they don't.

I enjoy being lefty. My grandfather was trained into being righty except for golf, so I noticed early on how things were not made for me and I had to do extra work. My father uses a lot of power tools and the extra dangers were apparent there as well.

Overall it has probably helped my programming as I had been thinking outside the box for longer than the righties.

sounds like we could use this for user attestation.

And be protected from DNS or BGP hijacking