| As a matter of principle I don't use any network which is trained on non-consensual data ripped of its source and license information. Other than that, I don't think this is bad tech, however, this brings another slippery slope. Today it's as you say: > I think this process is intended for fixing papercuts rather than building anything involved. It just isn't good enough yet. After sufficient T somebody will rephrase it as: > I think this process is intended for writing small, personal utilities rather than building enterprise software. It just isn't good enough yet. ...and we will iterate from there. So, it looks like I won't touch it for the foreseeable future. Maybe if the ethical problems with training material is solved (i.e. trained with data obtained with consensus and with correct licenses), I can use as alongside other analysis and testing tools I use, for a final pass. AI will never be a core and irreplaceable part of my development workflow. |
Unless AI use becomes a KPI in your annual review.
Duolingo did that just recently, for example.
I am developing serious regrets for conflating "computing as a medium for personal expression" with "computing for livelihood" early on.