My idea was a worm that just torrents random shit and dumps it on your desktop like a cat bringing you a dead bat with “I broughted you a pwesent ^w” energy.

As a (non-game) developer, AI isn’t even that great at reducing my burden.

The organization is enthusiastic about AI, so we set up the Gitlab Copilot plugin for our development tools.

Even as “spicy autocomplete” only about one time in 4 or so it makes a useful suggestion.

There’s so much hallucination, trying to guess the next thing I want and usually deciding on something that came out of its shiny metal ass. It actually undermines the tool’s non-AI features, which pre-index the code to reliably complete fields and function names that actually exist.

Also on modern firebreathers.

I like runit better than systemd, the packages are current, and it has most of what I want in the main repos.

I also found the documentation excellent in thst it’s a cohesive list of real-world topics rather than a 500-km-deep wiki or forum archive.

I should try a modern Slackware one day. I loved it back before I had broadband and just ordered a burned CD for each new release, but I should try following -current and the Slackbuilds stuff.

No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

Also add another 6 months to actually get the credentials for the test environment.