meltedcheese

joined 3 years ago
[–] meltedcheese@c.im 4 points 1 week ago

@festus @selfhosted Excellent examples. What the tag [AI] conveys is not what you really need to know, which is the quality of the code (component/unit), unit testing, and so forth. I assume there is some acceptance testing done at the project level. The human who submits the code must understand that flaws in their code is their responsibility, just as those who contribute/maintain the project are responsible at the system level. It is both an objective and reputational process. Does it really matter what tools are used if the work product passes the test, verification and validation criteria? Sloppy code is not unique to AI tools.

[–] meltedcheese@c.im 0 points 1 month ago (2 children)

@Architeuthis That’s crazy. What’s the crime?

[–] meltedcheese@c.im 0 points 1 month ago (9 children)

@lurker I don’t understand what “target” means in this context. Is there a crime to be investigated? As far as I know, you can’t be prosecuted for beliefs.

[–] meltedcheese@c.im 7 points 1 month ago (1 children)

@irmadlad This is such a great idea. I sometimes tell my rack, “you are my everything” and I give it whatever it wants. I’m about to reposition some of the equipment. That is plenty intimate enough to play Barry White.

[–] meltedcheese@c.im 1 points 1 month ago (1 children)

@Zeoic You are both correct. Chess was chosen as an early problem domain for work on first-order logic-based programming. That certainly was considered AI. People really interested in chess later abandoned logic programming in favor of brute-force, highly parallel special purpose hardware. That was not AI.

“Expert systems” (I hate that term) are application area of “Pattern-Directed Inference Systems” (PDIS). Rule-based systems are just one type of PDIS. For example, “Constraint Satisfaction” is another powerful AI technique often used in resource optimization and scheduling systems.

[–] meltedcheese@c.im 1 points 1 month ago

@Blue_Morpho @selfhosted Thanks for posting this. Some interesting articles that I didn’t know about. The Wikipedia article on expert systems needs some work. Apart from editing, the content is fine but incomplete, and the citations are not the best. I may take a crack at contributing, or I might take a nap. The 80s-90s were my prime years as a developer of intelligent systems, including but not limited to knowledge based expert systems. One of the most successful AI tools I co-invented was SHINE, still in use today.

https://en.wikipedia.org/wiki/SHINE/_Expert/_System

[–] meltedcheese@c.im 1 points 1 month ago

@Kaes3kuch3n @androidul This looks great! Thanks for posting.

[–] meltedcheese@c.im 2 points 1 month ago

@mko I have one. Lots of fun. Made with a Raspberry Pi 0. Lots of plans online. It sits on my windowsill. Tiny! It feeds those two commercial flight tracking sites as well as others. Here is a link to the software for web interface to your ADSB receiver.

https://github.com/wiedehopf/tar1090

[–] meltedcheese@c.im 1 points 1 month ago

@guynamedzero Bulletin Board System (BBS)

[–] meltedcheese@c.im 1 points 2 months ago

@fccview I don’t have that skill.

[–] meltedcheese@c.im 1 points 2 months ago (2 children)

@fccview I wasn’t really joking. I was hearing it.

[–] meltedcheese@c.im 1 points 2 months ago (4 children)

@fccview Vroom! Power tools!

That gives me an idea.You know what a grinder sounds like, and a drill, and a chainsaw. Why don’t OUR power tools have a distinctive sound? Or the code itself? It would be faster to hear a card deck shuffled, in various ways, and know an algorithm is, than to read the documentation or the source code.
Source code = math = music. We could probably pick out AI Slop instantly.

view more: next ›