|
|
|
|
|
by encyclopedism
169 days ago
|
|
The core issue is that AI is taking away, or will take away, or threatens to take away, experiences and activities that humans would WANT to do. Things that give them meaning and many of these are tied to earning money and producing value for doing just that thing. Software/coding is once of these activities. One can do coding for fun but doing the same coding where it provides value to others/society and financial upkeep for you and your family is far more meaningful. For those who have swallowed the AI panacea hook line and sinker. Those that say it's made me more productive or that I no longer have to do the boring bits and can focus on the interesting parts of coding. I say follow your own line of reasoning through. It demonstrates that AI is not yet powerful enough to NOT need to empower you, to NOT need to make you more productive. You're only ALLOWED to do the 'interesting' parts presently because the AI is deficient. Ultimately AI aims to remove the need for any human intermediary altogether. Everything in between is just a stop along the way and so for those it empowers stop and think a little about the long term implications. It may be that for you right now it is comfortable position financially or socially but your future you in just a few short months from now may be dramatically impacted. As someone said "I want AI to do my laundry and dishes so that I can do art and writing, not for AI to do my art and writing so that I can do my laundry and dishes". I can well imagine the blood draining from peoples faces, the graduate coder who can no longer get on the job ladder. The law secretary whose dream job is being automated away, a dream dreamt from a young age. The journalist whose value has been substituted by a white text box connected to an AI model. I don't have any ideas as to what should be done or more importantly what can be done. Pandora's box has been opened, Humpty Dumpty has fallen and he can't be put back together again. AI feels like it has crossed the rubicon. We must all collectively await to see where the dust settles. |
|
There are infinite analogies for this whole thing, but it mostly distills down to artisans and craftsmen in my mind.
Artisans build one chair to perfection, every joint is meticulously measured and uses traditional handcrafted Japanese joinery, not a single screw or nail is used unless it's absolutely necessary. It takes weeks to build one, each one is an unique work of art.
It also costs 2000€ for a chair.
Craftsmen optimise their process for output, instead of selling one 2000€ chair a month, they'd rather sell a hundred for 20€. They have templates for cutting every piece, jigs for quickly attaching different components, use screws and nails to speed up the process instead of meticulous handcrafted joinery.
It's all about where you get your joy in "software development". Is it solving problems efficiently or crafting a beautiful elegant expressive piece of code?
Neither way is bad, but pre-LLM both people could do the same tasks. I think that's coming to an end in the near future. The difference between craftsmen and artisans is becoming clearer.
There is a place for people who create that beautiful hyper-optimised code, but in many (most) cases just a craftsman with an agentic LLM tool will solve the customer's problem with acceptable performance and quality in a fraction of the time.