@realBobbyHealy@stshank I would probably look the other way. Ask it to generate a suite of automated tests, validate them against desired/business outcomes (the hard part), and then generate the code to fit the tests. This would permit hard to read, high perf code and may well be easier for newer devs
@realBobbyHealy@DibsRazell “Now rewrite this code as an educational play where each key part of the code has human-like personality traits and a non-programmer can understand”
@matteocollina Assuming it’s a non-public vuln disclosure *and* the module is popular enough to cause wider impact then I would fix and/or try quietly recruiting a few maintainers from adjacent dependencies. Otherwise ask for PRs, start deprecating and/or find a new owner.
The Battle of Bamber Bridge, 1943.
Racist US military police attacked black US troops on British soil.
US military authorities demanded the town’s pubs impose a colour bar, the local landlords responded with signs that read “Black Troops Only” which pissed them off.
A THREAD
@jessitron@avdi@cvennevik I really love the idea of this, or maybe “full loop development” since it makes me think of making progress with continuous feedback loops. “Going full-circle” can mean *not* making progress in some contexts.
We @GrowRemoteIrl are ambitiously trying to map every remote worker in Ireland - if you are a remote worker and have not already done so, please fill out this survey: https://t.co/TZscV5lk6u and drop your pin in the Remote Worker Map. Thanks to @ESRIDublin for your help.