Swap the ports and see if the problems moved with the module, or stay fixed with a port location. Try on a LiveCD with Linux to rule out the OS. If nothing else - probably MB.
115 karma · joined September 8, 2023
Swap the ports and see if the problems moved with the module, or stay fixed with a port location. Try on a LiveCD with Linux to rule out the OS. If nothing else - probably MB.
It doesn't change the fact though that human drivers don't slam the brakes out of the blue because their "AI" got confused about nothing in particular, and that it is dangerous.
Predictable haters took a bite and there's a flood of self reassuring comments on how Mastodon is great.
There's also problem of incentive. Why would anyone want to run your builds? So you can run theirs? In that case why you won't run yours and their theirs and save the overhead?
Great. An alternative is an honest way to conduct business. We'll take it.
We could get rid of all that click-bait AI-generate crap and not waste everyone's time, among tons of other benefits.
A low complexity org with low complexity tech stack (both good things) can serve a ton users, and don't have much benefit from huge scale, elasticity and features of AWS.
In particular network transfer fees on AWS are ridiculous, IMO.
It's silly. If you can afford not having to worry only about the price, congratulate yourself and enjoy it.
Then, in larger teams, there's some room for HR-like stuff - salary negotiation, personal conflicts, carrier growth opportunities, "how are you feeling" kind of stuff.
The managers should only do the later, but most of the time they completely take over the former, becoming clueless jira ticker shufflers, that multiply like rabbits, because they always think "we need more Managers, because I can't keep up with all the jira shuffling and meetings overheads I created".