Clearly a rodent got into the emergency food supplies, ate a mouseful of this Clif bar, and noped out of there. I guess we need to keep the lids on these bins. #preparedness #rodents
It's only "menudo" if you're doing for sport or enlightenment. If you're using it in combat, it's "menujutsu".
Setris - play Tetris with sand!
https://www.freegameplanet.com/setris-downloadable-game/
by #gamedev mslivo #indiedev #indiegames #gaming
Many folks have been taught about “The Tragedy of The Commons” in school. But what most folks don’t know is that it was complete bunk written by a white nationalist and eugenicist to justify colonization and genocide.
Commons can be successful. Many long-standing and successful commons exist. Many were studied by Nobel Prize-winning Political Scientist Elinor Ostram, who codified 8 principles for how commons can be governed sustainably and equitably in a community.
https://www.onthecommons.org/magazine/elinor-ostroms-8-principles-managing-commmons
I’d really like for folks to stop using the term “tragedy of the commons” that assumes inevitable failure, and start calling them what they are. Commons with improper governance or “Failed commons”.
(Adapted from Bond, p. 483.)
Suppose you have a Unity GameObject obj and want to set its x position to 5.
You'd like to say:
obj.transform.position.x = 5;
but this doesn't work!
The reason is that position is a property, so obj.transform.position returns a new Vector3, not the one stored in the transform.
You therefore have to do this:
pos = obj.transform.position;
pos.x = 5;
obj.transform.position = pos;
This bothers me because you can't tell by looking at something whether it's a field or a property. .position is accessing a property, but .x is accessing a field.
I'm new to The Cornell Lab. They sure do have a lot of cool #bird stuff! This morning's discovery was Project FeederWatch. It's a nifty visual database where you can mix and match region, food, and feeder type to figure out what birds you might attract to your yard.
Having gone to the office today (my employer's slowly transitioning away from letting folks work from wherever/whenever), I was late for the train back home, so I took a detour by the river and met this very friendly pair of mallards.
(These are barely-cropped phone shots! Didn't have my camera with me nor a tele lens in my phone – they got really close.)
#birding #birds #birdwatching #birdphotography #birdsofmastodon #photography #wildlife #wildlifephotography #naturephotography
UnityEngine.Random:
Uses nondeterministic properties (?!) instead of methods to return random values.
Does not follow Microsoft's convention for capitalizing property names.
Makes the upper bounds inclusive, unlike just about every other random library, because why the hell not.
People generally seem to agree that C# class names should be PascalCase.
Except for, y'know, the class you'll probably use most often: string.
Capitalization in C# / Unity is an infuriating minefield.
Microsoft and Unity offer slightly different standards and then don't consistently follow them.
There is no entry for "capitalization" in the index for the 1000-page C# 10 in a Nutshell. There is some advice under "identifiers", but it differs from what is given by the previous two sources.
Many sources want to capitalize private and public fields differently. Why would you do that?!
Unity adds spaces and changes the capitalization when displaying class and field names.
If you refactor a name, Unity bloats your code with a FormerlySerializedAs attribute.
#Violet keeps striking adorable poses and them moving as soon as someone gets out a phone. I think she just resents the pupparazzi.
CS professor, game designer, and fire dancer ordinaire.