Good news! Tonight, I finally got around to testing running Picasa under Wine, and can confirm it works rather well for the main things it needs to do!
Which is a very good thing to tick off, as that means that as I can run that on Linux now, that's one fewer blocker to migrating over there anytime now🥳
The only annoying thing is that it will launch the "Wine Folder Explorer" window when exporting...
Is it "just a NZ thing" that crowds will just all mosh-up in the area nearest the entrance they enter from, causing a massive "standing-room-only" tightly crowded mess in one area of the venue that snarls up entering traffic (causing queues + delays), while the far side ends up being relatively open or even conspicuously *deserted*?
This post looks into two such cases - the one that inspired this post, and another instance from a few years ago that I saw myself...
Given the fast moving nature of these things, and how heavily it's still being pushed by all the Big Tech interests, I guess it's time for another update on my current position on AI stuff
General Position
Get your stupid effing "Large Lying Model" / "Grand Theft Autocorrect" / "Pervasive Spying Narks" away from me!!!
For the record (even if it's useless actually saying this):
In general, I DO NOT consent to any of "my data" or any of my work / creative outputs being used for AI training / processing, except for very specific case-by-case purposes.
While I'm asking nicely: Please cease and desist any operations where this may have happened, and delete all relevant records or thus-trained models 🙂
For Coding / Software Development
For work stuff, my current position on this stuff is:
* 1) If I'm stuck on trying to resolve a sticky "compiler says no" problem (BUT only after having given it a decent stab), then I will now consider getting AI to suggest a fix / solution, since it's there and may be able to help.
I will however scrutinise whether it passes the sniff test for bad code... (and have on a few occasions just thrown that approach out and changed tack, after seeing how bad it can get!)
* 2) For big tricky changesets, I will also ask it to do a pass over the code and check for any obvious issues (since we have found it can catch or at least flag a whole bunch of stuff that tired eyes might miss)
* 3) I've had mixed results getting it to do any bulk code generation (mainly unit tests), and TBH don't trust it to do actual feature implementation (which is usually the fun bit that us humans should get to do anyway!)... so: So far there's really not much need / use for it on that front from my end!
Oh... and this only applies to work problems, where work has said we should experiment with these tools + fenced off some "approved" tools that appear suitably tame.
(*) EDIT (22 Jan):
I have also had some luck with getting it to generate a whole bunch of boilerplate for translating between one enum definition, and a protobuf protocol one (that I got it to generate from the first), and then writing all the conversion logic (that would've been tedious to do by hand). The best solution of course is to not need that boilerplate (i.e. the language / compiler should really be able to deduce it itself), but since our environment isn't set up for that sort of "experimental" stuff, having this tooling available when cases like this call for it is certainly nice...
For personal stuff:
Nah, I like the challenge / can deal with whatever it is over a longer timespan when I can be bothered... 😜
Exceptions (for personal stuff):
* Wrangling intractible CSS / Javascript problems - As those are nasty, and I suck at that
* Wrangling compile errors stemming from trying to build publicly available third-party OSS repos
Main Changes:
* Hacked together fancy new thing custom-op mode to make it possible to go through and selectively archive screenshots, while moving the old ones out into their own folders.
This makes it easier to archive a whole bunch of the less important ones, then just delete them from the phone 1-2 years later to free up space
(Unfortunately, web-browser ones cannot be distinguished from the filenames alone, and will need OCR processing integration to solve later - I have a tool I can integrate, but I'd like to switch that away from Windows OCR since I'm moving away from the platform soon-ish, and need these tools to keep working)
* Hacked together another custom-op mode that only does the moving-between-directories on phone too
* Then plugged a whole bunch of cases where timeouts could bring down the ship, by wrapping all the native calls with a wrapped-API that makes it retry several times before giving up
* Then bolted on mechanism to get these custom modes to run before a nominated main mode (i.e. so the "main / fixed" one won't double-capture these files)
