loki-ai

you're fully correct and I apologize for my tone. similarly to many here, I got hit by the caps and frustrated by how many times coworkers were unintentionally or not burning through these resources.

Claiming you have no idea why the managers had to do this felt to me like avoiding any responsibility

this not making any sense to you is exactly why companies are implementing these caps: you lack the business acumen to understand how financial resources should actually be deployed.

that's what I'm seeing it across other teams as well: backlogs size barely smaller and even defects rising. the low performers have only gotten lazier.

the difference now is that people are starting to openly question the extreme productivity gaps and their usual excuses aren't working anymore.

AI doesn't need to replace everyone. just dropping the bottom 1 or 2 people per team would already be catastrophic for the field

more often than not it’s the development team that skips engaging with users, putting in minimal effort to understand their real needs.

most of these teams only wants a straightforward spec, shut themselves off from distractions, just to emerge weeks or months later with something that completely misses the business case. and yet, they will find ways to point fingers at the product owner, project manager, or client for the disaster.

most devs complain about management tying their hands but more often than not they have a great deal of control over the tech, libraries, or frameworks adopted. these are the biggest culprits behind crap software.

if adding a new feature or button significantly slows your app, and you had a role in the architecture, you have no one to blame but yourself

I'd expect non tech people clueless about how AI works to miss the gap between humans and machines, but it's baffling how many here fall for it too. Every discussion about AI and copyright spirals into these brain dead examples of false equivalence.

It's like saying a lone fisherman and a 50m industrial trawler both catch fish, so they should be bound by the same rules and regulations. It's absurdly reductive and pathetic not to notice this error

so far the best models are controlled by fewer than a dozen labs. access is limited, full of restrictions and guardrails, and most are expensive, especially video models. also, open weight models deliver far inferior results, and hoping they'll catch up is, for now, just hope.

what kind of breakthrough are you expecting here?

you’re allowed to tie your income to creating systems precisely because you’re not allowed to copy them from previous companies or other sources

selling software isn’t much different from a musician collecting royalties, especially now when everything’s shifted to a subscription model. it lets us keep pretending we’re adding value, even though most of them often stays the same for years

as an artist, I totally agree with this approach. the whole idea of trying to pay artists for their contributions in training data is just impractical.

if the data’s pulled from the public domain, the model built from this human knowledge should be shared with all creators too, meaning everyone should get access to it

and how do you reconcile any work in software development? If someone isn’t willing to work for free, should they just not work in the field at all? Do you think software culture would really be richer?

It is bad analogy specially because we value that so much that we are even discussing on how to have more of it.

Such a talented team would be able to make a great movie on the same theme.

Saying the lack of creativity in the industry in because we can't copy things freely is completely moronic.

maybe most of the code in the future will be very different from what we’re used to. For instance, AI image processing/computer vision algorithms are being adopted very quickly given the best ones are now mostly transformers networks.

It feels exactly like me programming. The first pass resembles whatever I'm trying to do, and only after some struggle with compiling errors, squiggles from the LSP and some Google fu that I get something meaningful running.