4,416 karma · joined May 9, 2025
And also we do worry, but not in "replacement" way but just "using AI to create bad code with no proper oversight". It's absolutely enabling clueless to develop crap apps
Instead, it is all dumped in one big pool and distributed by total listens.
Which means, if you listen to more songs, you have more "voting power" on who gets the money. Absolutely asinine system.
They basically put all the revenue into one pot, then divide it by the songs play count.
Which means that account that streams 10 000 plays, have more "voting power" on the revenue that one that just listens "normally"
It's bizzare to see people that made clown issues (not enough detail etc.) suddenly start writing detailed prompts just because it is AI that will do the task and not the human on the other side.
And a lot of "wishing up a feature", I was using it to explore solutions for a given problem in too I didn't knew 100% and it pretty much came to same solution I wanted to do but... the capabilities were not there in the tool so it just started making up probable config clauses, and of course, it didn't work.
Even on simpler stuff there were traps, for example in middle of debug session I asked it to modify Gitlab config to add request duration logging, so it added correct config format to a flag that didn't exist (option was there, just under different name), because it didn't bother to read the docs (since then I generally link it the docs first so it doesn't try to remember and get it wrong).
All of that is both very dangerous, and also easily fixed by just having competent operator there. And as a tool it's great, as replacement it is just AI bros delusion
Of course it did. Because reviewing code thoroughly is harder than writing it.
Writing only consists of "making sure it does the task", reviewer have to understand code first, check if it does the task, then check whether it doesn't affect something else negatively (and it can be meta things like "doesn't adhere to project style", even if technical side is correct)
No idea why they thought they can compete with frontier AI labs on that, it's entirely waste of money
They also tried to push AI feature set as a separate subscription which is just insane in current tooling market.
All users wanted is good integration of multi-AI providers in their base offering. I think they are slowly shifting to that but that's a lot of money wasted already
Yeah, no, vast majority just want to pick a AI vendor and integrate it into their IDEA or CLion or whatever other editor they were already using. Pushing into entirely different subscription was dead on arrival.
They figured that out and started integrating it into main tooling (https://plugins.jetbrains.com/plugin/33314-air), but they definitely wasted a bunch of resources on something nobody really wanted.
IDEA already have small LLM for one line code completion IIRC.
But the gain people want from LLM is generally "here, add this entire feature" or "here, go thru every dependency's changelog and update code to work with latest version". Those are not small LLM tasks
Like, if app in wild gets hacked, you kinda already are screwed, even if the hack is contained to the box (whether VM or container) app runs in, you still get whatever app keys app used, and you still get whatever visibility to internal network the app had. https://xkcd.com/1200/ basically.
If your app server gets hacked, all user data leaks anyway. If you divide everything to microservices so they see minimum required amount of data, attacker can still see everything that goes thru it
The current models intelligence depends on massive training dataset of essentially stolen data
My setup is Syncthing + restic for backups history. I have VM "in the cloud" that act as extra node/shit hits the fan plan too
Like, you can do the same with any distro and say Puppet or Ansible but only to within that distro packages, any 3rd party stuff (and people use more and more stuff that's 3rd party to the distro) might just have dead link for the download.
Also, plain restore from backup is still faster
Traditional data centers have far smaller power density per rack and thus cooling requirements than AI datacenters; if you can use closed loop system without evaporation, water usage is very small. Difference is around order of magnitude
But if you want to fit maximum amount of compute in the space and need to dissipate it, evaporative based system will be far more effective space wise; especially if also for some reason you built it in hot place, rather than somewhere in the north