cross-posted from: https://lemmy.zip/post/66082776

I never see in public git projects something like a declaration of scope. There's also no convention, unlike a README.md (which rarely contains some sort of scope definition) or LICENSE file.

Is this unusual in open source projects, that you first define what you want and not want in your project and how you want to do it, to combat scope creep and sabotaging yourself?

I'm in a postition in live (short of a burnout) where it's actively a pain to just start things and then wing it; i even add a scope comment to larger shell scripts.
Maybe it's experience, because i already know that i'm then not satisfied afterward or (in case of shell scripts) just create a unfinished mess. Nobody else?

cross-posted from: https://lemmy.world/post/48190865

A very very senior game developer recently told me how he is changing specialization because AI is much better than him at what he does already.

I asked him if it was just the speed and mass of code, to which he replied that Claude 5 Fable/Mythos is just so advanced, it comes up with solutions he would never have thought of, not even requiring good prompts anymore.

He further said in some areas like Unity it's not perfect yet, but improving drastically.

Honestly this is pretty different to what I read in many articles regarding AI code.

They mentioned errors, bad performance & such.

However if it is already used in production and he as a professional evaluating it, is saying it's better than him...

That same day I also talked to somebody that got hired to train an LLM. His interview was with that companies chatbot, that offered him over 120$ per hour, a roughly 500% increase from his previous job 🤣