MagosInformaticus

It's the parts of a program's concepts, rules and behaviours that are specific to the program's task. For instance

• Items, a shopping cart and the conversion of such a cart into an order at checkout in an e-commerce application.
• Clips of video and audio, static images etc. and the compiling of these into a single output video for a video editor.
• Vertices, triangles, meshes, animation rigs etc. for a 3d editing program.
• Accounting standards and tax laws for an accounting system.

When developing software you deal both with these kinds of specifics and generically reusable concepts that are more purely computational science, so a term to distinguish them is handy.

I think this is partly about giving yourself an out for liking childish things as a near- or young-adult. Kids shows commonly do include some Parental Bonus but extending that idea specifically to dark undercurrent plots that you have to read between the lines of the text seems like a way to feel "in the know" about something adult in the work while still consuming something you feel society expects you to have grown out of.
Then with a bit more maturing than that, you can hopefully just embrace childish joys earnestly, because joys are precious.

It depends a bit on what you want to optimize for, as there's drawbacks to all the major methods:

• Ultrasonic sprayers are decently efficient but spread any contaminants around your home, potentially still biologically active. Dissolved trace minerals will turn into fine dust, affecting cleaning needs.
• Boiling for humidification is energy intensive because of water's heat capacity.
• Air forced wicks are by default great habitat for mold and similar, so they need regular care and replacement.

It really is a fascinating game, and as odd as the volume view is when you're new to it, it's extremely helpful to be able to orient yourself.

::: late game The 5D courses were a nice surprise as well. :::

"Have they no refuge or resource?" cried Scrooge.
"Are there no prisons?" said the Spirit, turning on him for the last time with his own words. "Are there no workhouses?"

Some computing problems are "easy"* to solve. We call these P.
Some problems let us easily check a proposed solution if we're given one. We call these NP.
All problems in P are also in NP, since checking a solution proposal works is never harder than solving the problem starting from nothing.
We suspect but can't prove that some problems in NP are not in P.

It turns out that it's possible to translate any problem in NP into the boolean satisfiability problem (SAT) using an easy algorithm, so this problem effectively is an upper bound on how hard it could be to solve problems in NP - we could always translate them into SAT and solve that instead if that sequence is easier.
We call SAT, and any problem that it can be translated into easily in the same way, the problem class NP-hard.
NP-complete is just those NP-hard problems which are also in NP, which is many but not all of them.

*: require asymptotically polynomial running time

Bugsnax also does this a bit with creatures like the Fryder.

The use of "alumni" in the singular. A person is an alumnus or an alumna, the alumni are always a group. Seems to be a very American usage, and I don't know why it feels aggravating where other Americanisms like positive anymore don't.

Shapez 2 is a very worthy sequel, IMO. Adding logistics beyond conveyor belts is quite nice, and 3 levels of height give quite a bit more options when building. You do often benefit from a build staying at one level since it makes platform blueprints that consume 12n belts of input to make 12 belts of output quite a bit easier, but several buildings are intentionally impossible to do that with for challenge.

The difficulty levels are also pretty well done - I got some fun learning moments out of Insane in particular. Hexagonal mode is also interesting.

I very much lean towards the microfactory approach - locate a cluster of resources within reasonable belting/piping distances, design a factory which can consume the cluster's entire production of the limiting resource (clocking others to match) to make 1 output or maybe 2, then provide that output to the rail network. Some production chains make it easier to have certain inputs taken from the rail network.

Within one of these factories, items are refined further for each floor they ascend but I rarely enforce a 1 product/floor rule - in particular I find it convenient with many Assembler/Manufacturer recipes to have an input that is directly fed from a single Constructor using clock speed to match production with consumption. This usually means each microfactory underclocks its most power hungry buildings a fair bit which keeps their consumption moderate. Each microfactory ideally has a single priority power switch to turn off its entire production chain if its consumption is becoming a problem and I set up a priority sequence for them.

Federal election times are set by 2 U.S. Code § 7 as 1 day after the 1st Monday in November (of even numbered years). The law is from 1875 and from what I can tell is indeed nominally motivated by the voters' need to first observe rest day on Sunday and then travel to their polling place. Keeping it and not having a federal holiday coinciding with it is largely aimed at keeping voter turnout low.

It's also my favourite place to kill monsters, take their stuff and use it to get better at killing monsters and taking their stuff. I do feel like it has so much build space to explore I find building without some reference to a guide frustrating, but it manages that progression well and the atlas passive trees are a neat way to let you customize what content you want to engage with.