I think we need a "slow software" movement.
We can look to slow food, Cittaslow (slow city), and other slow efforts.
We need to look "Generative AI" squarely in the eye, and run—not walk—the opposite direction.
We need to teach and advocate for software development practices which are *intentionally* easy to learn and require minimal maintenance.
We need best practices which encourage methodical longevity over quick band-aid fixes.
We need to put artistry over capital.
Will you join me?
@jaredwhite I was with you up until "we need to put artistry over capital".
What your're describing with "intentionally easy to learn and require minimal maintenance" means that making, using and maintaining software is accessible. Making art, by definition, requires a refined and vast skillset!
@jonn I would say you're reading a lot more into that than I intended. 😄
The point is fine craftsmanship and care for ecosystem health and user protections is often jettisoned in the name of short-term profits. Put out crappy solutions now! Fix later! (lol, or not) We need…the opposite of that.
@jaredwhite @jonn The problem here is with "we". There are lots of different stakeholders that shape the incentive landscape.
I would certainly love to take my time to make every project into a best shape it could be. But virtually nobody gonna pay me for *that*.
