T
@tante My point is that LLMs 'try' (and very often fail) to solve the wrong problem.
Writing all the boilerplate -> should be solved by better frameworks.
Spell check -> I think this is already invented.
Summarize long texts -> Executive summaries.
Produce (verbose) text -> Writing in my view is as much thinking as it is writing - skipping the thinking part is counter-productive.
@tante I, for one, enjoyed the write-up.
As you, I do plenty of things that I either cannot morally or ethically defend or simply am ignorant of the harms of.
For other technology, I am either pressured to use it (by government or similar institutions) or I can at least use it 'for good' (facilitating some other good - in current case, student administration) and also make a living.
For LLMs, I fail to see the redeeming qualities that make the compromise 'worth it'. It's all nett negatives.
It is a generic ERP-application with an open API - it was bought by EG (sadly VC-backed specialist software house) - they use it as the basis for two or three areas (construction, hairdressers and maybe health care). I left them about two years after the take-over which happened 2017.
The base system is here: https://xena.biz .
@tante My fondest experience in software was building (over ~9 years) an ERP system with the founding principle: "We want it to work for at least 30 years" which had a lot of knock-off effects. We were allowed to improve things that mattered more for maintenance than functionality.
The joy of being able to shift technology on the frontend with little effect to the backend, having response times in single digit ms and so on.
There was plenty to improve, still, but I had pride in my work.
