Stuff and nonsense
Aug. 8th, 2021 09:43 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
-Love writing for submission calls with big length windows. Like..."I'm somewhere between 50% to 250% done with this piece!" :D
-From exchange chat discord:
-Also me:
Orange jacket guy shakes his head at intermediate Python documentation hyping up "object-oriented programming" by how you can define custom things like "classes" and "subclasses," so you can make Fido as a member of the class Dog which is a subclass of Animal. And you can assign variables to them like legs=4, and functions like woof() which prints "woof woof," because they feel very indirect and strange--like why would you use "self" as a dummy variable when it isn't doing anything?
Orange jacket guy also shakes his head at spreadsheet-based examples. Like if I wanted to make Joe as a member of the class Customer and have things like zip_code = 12345, bill=49.99, I would just use...a spreadsheet, or some other kind of array/matrix storage format, either in Python or something else.
Orange jacket guy, however, nods appreciatively at the idea of using Python classes to simulate complicated card games like Keyforge. To be clear, I am very very far from implementing any actual cards, but I can now see why you would want to have "power," "defense", "damage," "money captured" as variables assigned to Creatures, which is a subclass of Cards, and how you want to dynamically update them over time through functions like reap() (no input variable) and fight(creature in position X in opponent's battleline)!
I'm a nerd of many facets, and sometimes, I really like it.
-From exchange chat discord:
orange jacket guy shakes his head generic rock songs about love
orange jacket guy nods yes angsty rock songs about relativistic time dilation
^ me
-(I am having feelings about '39 in a Crying Suns context. I am having lots of feelings in a Crying Suns context! But between silly exchanges, high-commitment exchanges, and aforementioned submissions calls, it will be a while before I circle back to my non-exchange Crying Suns stuff. There will be plenty of it, however! At some point!)
-Also me:
Orange jacket guy shakes his head at intermediate Python documentation hyping up "object-oriented programming" by how you can define custom things like "classes" and "subclasses," so you can make Fido as a member of the class Dog which is a subclass of Animal. And you can assign variables to them like legs=4, and functions like woof() which prints "woof woof," because they feel very indirect and strange--like why would you use "self" as a dummy variable when it isn't doing anything?
Orange jacket guy also shakes his head at spreadsheet-based examples. Like if I wanted to make Joe as a member of the class Customer and have things like zip_code = 12345, bill=49.99, I would just use...a spreadsheet, or some other kind of array/matrix storage format, either in Python or something else.
Orange jacket guy, however, nods appreciatively at the idea of using Python classes to simulate complicated card games like Keyforge. To be clear, I am very very far from implementing any actual cards, but I can now see why you would want to have "power," "defense", "damage," "money captured" as variables assigned to Creatures, which is a subclass of Cards, and how you want to dynamically update them over time through functions like reap() (no input variable) and fight(creature in position X in opponent's battleline)!
I'm a nerd of many facets, and sometimes, I really like it.