Microsoft have introduced limits for its engineers AI tools usage
https://www.404media.co/microsoft-tells-engineers-tokenmaxxing-is-not-what-we-are-optimizing-for/
It's not in the article but they've also rolled back their Claude Code rollout too.
All of this is noise to companies that make canned tuna and such btw - you know, companies that actually do stuff and drive the global economy.
They can't afford any of this shit. They can barely afford to upgrade their Windows 10 PCs, which are held together by string.
Microsoft's SLT often thinks their customers are all the DoD and banks. They aren't. They're orgs struggling with real world problems, who can't afford Visio licenses.
@GossiTheDog Reminds me of a call I had today with a real, significant company somewhere in Africa, they are knee-deep in the Microsoft ecosystem, except the latency and bandwidth constraints were making any page load on office365 unbearable, the screenshare was painful to watch.
Maybe they should fix that first instead of spending all their capex on GPUs.
@mathieui @GossiTheDog I'm a firm believer that developers should be forced to use shitty machines on shitty internet connections so they can actually feel the pain they inflict on others.
@datenwolf @mathieui @GossiTheDog I've been slowly cutting down my compute for similar reasons. It makes IDEs and fancy code completion tools almost impossible
@datenwolf @mauve @mathieui @GossiTheDog You are conveniently forgetting that Visual Studio has recommended specs of "64GB RAM" and "16 core CPU" and we often don't just run the client, but an entire backend cluster as well, with a debugger attached. What we definitely shouldn't do though is give the senior devs in charge of architectural decisions overpowered workstations with like 96GB RAM, so they can't say shit like "(this 200-project nightmare solution) builds and runs fine on my end".
@lidsel @datenwolf @mathieui @GossiTheDog That's whack. IMO 32GB is decadent. Consumers are getting by with like 16
@mauve @datenwolf @mathieui @GossiTheDog Note that this is recommended, not required. They list minimum requirements as 4 cores and 4GB (absolute minimum to even run it) or 16GB (reasonable performance) RAM, but that cursed solution I described makes it cry on a laptop with 6 cores and 32GB RAM. I have a lot of strong feelings about the design decisions on that project.
@datenwolf @mauve @mathieui @GossiTheDog
To show my age, I recall (pre Internet) there was a company that provided 286 machines to their support staff rather than current 386/486 PCs.
Maybe Borland?
@mauve This is why I've always kept using the oldest machines and phones I can cope with. It's a helpful barometer.
@mauve @mathieui @GossiTheDog
I've been preaching this for years. Developers should be forced to work and test their software on Celeron, 256MiB RAM, 256MiB swap, 5400 RPM spinning rust 120GB HDDs.
I'm okay with compilation to happen on a beefy iron.
But the actual user experience should be the absolute minimum.