Perhaps we should stop running things on clouds to begin with. Localstack's main point was that AWS cannot be run locally. Nobody seems to have a problem with that here, which is the bigger problem.
I considered this with my OS, and ultimately decided it was indeed the wrong approach. Really cool to see someone experimenting with these ideas nonetheless.
Wow this looks like an incredible set of features this release. Jump over and schematic grouping will be super useful, and I didn't even know they were working on reusable design blocks. Kicad feels like the next blender in that it's really getting a lot of treatment. Congrats!
Quasi-related but I did the same thing at RadioShack for inventory. It was a long process of scanning each product, looking at the scanner and manually verifying the price on the tag.
The tags had a barcode on the back with the SKU and the price that had been printed, but naturally the scanner didn't support that format.
So I brought in my own scanner, scanned all of those into a spreadsheet, then ran a script that checked the same inventory panel that had the updated prices, and printed out a new sheet with just the barcodes that differed to run "inventory" against. Saved us hours per day.
Corporate got pissed (understandably) and shut it down real quick.
I was running scripts on their PoS (EDIT: point of sale) terminals to hit an internal service. If I were the sysadmin at corporate, people like me would make me nervous too (even though I wasn't doing anything nefarious).
Hard disagree. Drive by's were the easiest to deal with, and the most welcome. Especially when the community tilted more to the side of non-amateurs and passionate people.
Low effort drive-bys were easy to spot because the amount of code was minimal, documentation was nonexistent, they didn’t use the idioms and existing code effectively, etc. Low-skill drive-bys were easy to spot because the structure was a mess, the docs explain language features while ignoring important structural information, and other newbie gaffes.
One latent effect of LLMs in general is multiplying the damage of low-effort contributions. They not only swell the ranks of unknowingly under-qualified contributors, but dramatically increase the effort of filtering them out. And though I see people argue against this assertion all the time, they make more verbose code. Regardless of whether it’s the fault of the software or the people using it, at the end of the day, the effect is more code in front of people that have to revise code, nonetheless. Additionally, by design, it makes these things plausible looking enough to require significantly more investigation.
Now, someone with little experience or little interest in the wellbeing of the code base can spit out 10 modules with hundreds of tests and thousands of words of documentation that all sorta look reasonable at first blush.
