@sun@shitposter.world "automatically resets after 20 minutes"
techbros and their understanding of consent
Ignas Kiela
@ignaloidas@not.acu.lt
I do in fact exist
I'm an information sponge, so if you have some question that you think I might have an answer to, feel free to ask! Even if I won't have it off my head, I know how to look up things fast.
Posts
Latest notes
No posts yet.
@feld@friedcheese.us @sun@shitposter.world ok thats bonkers and stupid
Both because it's on oracle, and because SQL is kinda ass for such code volume
@azonenberg@ioc.exchange i don't think ypu can do it (well?) with Vulkan but it is possible to do GPU-side allocation. Not sure if worth tho.
@sun@shitposter.world @feld@friedcheese.us ok, I understand it with oracle because of it's toxic licensing
But like, I've rewritten a whole bunch of stored procedures - e.g. from postgres to mssql and then back to postgres after some changes while it lived in mssql. Was fine.
And yes, if you put all of it in stored procedures, you're gonna have a bad time migrating (guess why oracle wants you to use them so much), but as I said, you should have either small ones for consistency, or large ones for large transformations/analytics. The first case is easy to rewrite because small, the second case is a pain either way because the alternative is just having all of the sql in some script or whatever and you're gonna have to rewrite it either way.
@sun@shitposter.world @feld@friedcheese.us how often you're transitioning between DB vendors anyways?
(also, since writing them is litteraly part of my job, the best use cases I'd say are either small ones for ensuring nore complex consistency terms of the database, or large ones for bulk data transformation and saving.
@sun@shitposter.world depends on the human not having 100% trust for the LLM's results tho, like seemingly a whole bunch of curl's bug bounty reports were humans that just had absolute trust in LLM's results and even tho the talking didn't seem LLM, the arguments and reports did seem to fit a LLM