Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Great write up. A few things caugyt my eye. You meantioned AI realtime checking code as it is written. IDEs do a pretty good job of that already. To do much better, it would have to know what you want to do. And that seems to be a barrier to how AI is developed today. It doesn't "understand" why.
Now QA is interesting. I wonder if anyone has built a model based entirely on clicks that can predict where a user is going to click. That would be very interesting. It would work really well for testing functionality that is already common on existing sites. Most webapps are made up of a large part of things already done... date chooser, question submitters, and such. Like how many apps out there are for scheduling an appointment. Tons. And so many apps (even mobile games) are just the same thing in a custom facade. In this case I don't think it would replace QA much as places writing that stuff don't test much. But it could speed up developers by reducing the number of customer reported issues in code they wrote months ago.