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.
Incremental games are a bit of an “I know it when I see it” grouping, but two typical characteristics are progression systems nested within each other and game loops that start simple but “flower” into a number of more detailed and mutually interacting ones over the course of play.
Universal Paperclips is a nice example, casting you as a newly built AI with the goal of making as many paperclips as you can. You start out able to make paperclips and sell them to humans for funds you can then use to invest in more capabilities. You work on building trust with the humans so they’ll let you do more things, and on making more clips faster, and there is a lot of escalation from these humble beginnings.
Some other good ones are Cookie Clicker and, if you’re into programming puzzles, Bitburner.
This is definitely important in making the very most engaging base-builders - a pleasing mixture of longer term goals (manufacture this piece that I can eventually put in a future science pack or whatnot) and under-performing pieces of your older infrastructure that you have to scale up or re-plan is just so helpful for getting you into that flow state.
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.