Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
so, simplified, you have a Gazelle which has a Kill function that returns Meat which is a subclass of FoodIngredient. and you have a Fireplace object which has a Cook function that takes FoodIngredient objects and returns Food objects (which you want). so you figure out that you need to call Kill on the Gazelle, take the Meat return value, put it into Cook function of the Fireplace, take the result, and voilá, you got what you wanted.
which is the core of how the AI can know how to operate/use stuff around it even though you have no datastructures that define the uses and requirements. you just need to structure the code itself correctly. No extra work on top of coding the functionality itself (in the right way). -
@Lucaspar see my comment above this one
-
@MarkoVlaic0 you mean the name or the idea?
just so i know whether my paranoia about someone "stealing" it when i clicked "post" was justified.
you can have the name no prob.
but if...
... then i will find you...
... and i'll use my very particular set of skills on you...
... and it will make you sorry that i ever learned php...
Proper use of object oriented design patterns
Just finished reading this gem from start to end. It is over 20 years old and it is crazy how it is still up t...
...i just remembered why I have a MasturbatorPattern repository on my bitbucket, why is it named that way, and what it does.
It's one of the core abilities of that magical AI i've mentioned in my previous rant. And it's called that way, because of how it works:
The Agent has some objects (as in, class instances) available to it, and wants to get some other kind of object. So it inspects by reflection ("touches") all objects around itself, inspecting their public functions, building up a plan/path/tree of "this function takes the object I have as input, and returns this other object which this other function of other object takes as input and returns this different object, which...." etc, etc, until the final function returns the object the Agent wanted to get in the first place.
And then it goes and "does" all those functions, in that order piping the parameters through.
So first it touches them (second layer of metaphor - linux finger command), and then it does those which output (ejaculate =D) something useful to it.
Therefore, MasturbatorPattern =D
Not sure if my sense of humor is just weird or outright unfunny.
random
funny names
i just realized
design patterns