So who will be doing upkeep and maintenance of the project, will developers who worked on this project need to learn Rust to be able to work with the codebase and be able to have correct judgement about changes done by LLM? If yes then will junior Rust developers be able to correctly assess PR's generated by LLM? Or developers will be fired and new team with Rust expertise will be responsible for the project now?
I wondering about other thing - I'm assuming that publishers are now using LLM's en-masse to "proofread", do initial evaluation, do editorial work etc.
So if an author abstained from using LLM in the writing process - isn't then new, original, not yet on the market book ending up in the LLM training data corpus even before it hits the market?
In my case it's less about actual "rotting" and more about the feeling that any mine attempts to write code are futile and meaningless - if my LLM limits are exhausted it's actually more productive to go do something else (or write specs on how it should be done) and return back later and do LLM assisted coding than coding without it because in literally minutes I can then produce equivalent of hours-long "manual" coding session.
It's the South Korea model and road, people are working hard to chase constantly and quickly moving goal of securing extremely expensive home, basic setup for having the family. But process itself is exhausting and depleting.
That's completely and absolutely fine, if you are millionaire and/or have other well paid job then.. well done, congratulations and enjoy your newly found hobby.
BUT - I'm capable to tinker with my car a bit, to service and repair my bike, to bake a bread - BUT I'm not visiting mechanic shops, bike service shops and bakeries in my city telling owners that they should work for free and give away results of their work.
Yes that's correct, but in doing so remember that only person that cares most about you and your health is YOU - doctor cares about you for 10-15min, then next patient is waiting, and the level of doctor's care is inversely proportional to the level of burnout.
Yes, that's another issue - CS/IT seems to be unique that sharing knowledge and openly discussing problems is the norm, in other professions you can get finger wagging and some general "advice"
This is actually business opportunity for WP/Automattic - they could introduce vetted plugins where plugin author and/or consumer pays for review service.
Now only thing missing is leadership, development and active maintenance of the project for at least 5+ years - and keeping it and ecosystem around it fair and open (to some degree at least) because that whats allows WP to last for so long, it's not zero sum game.
For such rich and resourceful corp like Cloudflare surely this isn't a problem and they are going to overview, maintain and steward the project for a long, long time. Surely.
> Are there more people whose work on a project has been taken away by AI bots?
Of course, what worked me and what allows me to keep my sanity in my case of project owner coming in and remodeling half of the codebase over the weekend with CC is that I mentally ceded "ownership" of the project code, that is, I'm no longer feeling that I'm responsible for what is there and how it is structured. And there are tests.
Apart from that I can say that I empathize with you because I know that initially it feels awful, like loosing some part of agency and also to some degree humiliating when looking that something carefully and meticulously designed is restructured, replaced or thrown away so quickly and carelessly.
What also helps is changing mental model and perceiving oneself as controller who overviews process of "shaping" code as whole, in its big mass, to behave in certain way instead of keeping mentally attached to some part of it because "I designed it".
Recently after noticing how quickly limits are consumed and reading others complaints about same issue on reddit I was wondering how much about this is real error or bug hidden somewhere and how much it's about testing what threshold of constraining limits will be tolerated without cancelling accounts. Eventually, in case of "shit hits the fan" situation it can be always dismissed by waving hands and apologizing (or not) about some abstract "bug".
The lack of transparency and accountability behind all of this is incredible in my perception.
Welcome to Amazon playbook replayed again, most useful, profitable and popular use-cases will implemented by platform - and they will do it ruthlessly and quickly as money needs to be recouped.