Cayde-6
The vast majority of playgrounds are entirely unsheltered.
What we actually learned from those lessons was that English/literature class was a waste of time and how to craft complete bullshit that sounds deep, which I guess is a useful skill.
On top of those broader measures listed and the general level of public cleaning/maintenance, there’s reporting of every dengue infection diagnosed along with the individual’s home address and particulars to the National Environmental Agency. Cases and trends are monitored for developing clusters, publicly publishing up-to-date findings and exact numbers. Where a cluster is found, they do additional anti-mosquito fogging and significantly increase the local public awareness campaign (huge banners, posters in every elevator, distribute leaflets, etc).
They then send agents unannounced to inspect inside every home/unit in the area for any potential breeding grounds. Everything is checked from potted plant trays to dish drying racks to toilet bowl scrubber holders. If any breeding is found, there’s fines in the thousands of dollars. The agents are empowered to enter without a warrant; it’s taken THAT seriously.
The NEA also monitors and takes appropriate action against non-residential areas like construction sites, where standing water is hard to eliminate unless it’s a priority.
A while back I worked at a consultancy that typically billed using a 15-minute granularity during standard office hours, reasonably rounded up/down. Unless otherwise contracted, outside of office hours the granularity increased to 1 hour rounded up. A 5 minute fix would be billed as an hour, a 65 minute fix as 2 hours, etc. It was also only undertaken for emergencies; general work requests would be done the next business day.
Generally all contracts were budgeted some number of hours per billing cycle per service. N full-time engineers would be converted to an equivalent amount of hours for the budget.
The result was that overtime was used judiciously and clients were rarely insisted on pushing big changes near the end of a day or on Fridays.
I absolutely love A, B, C; they're critical to my project, the maintainers put pour their own time and effort in, and I want to make sure they get my support. Dep D is pretty good and I wouldn't mind throwing a bit their way too. E is some wrapper lib (or maybe a company-backed package) that I don't care to support monetarily.
Since I want to support 60-80% of my deps, something like StackAid sounds attractive; I don't have to set up and maintain individual (potentially recurring) donations to each. I set up $100/mo to be distributed, feel good about doing my part, and go back to work.
Turns out, only E is collecting their StackAid, for whatever reason. My $100/mo is all going to them. Nothing is going to any of the others, let alone the packages I definitely wanted to support in the first place. I think I've donated, so I don't think to seek projects' alternative donation channels to get the money into their pockets, so they don't see a dime.
The only solution is to go through all of my dependencies to see which ones are actively using StackAid and decide if it's a sufficient set before donating through them.
Make an effort to connect with coworkers in person whenever there's a business or on-site trip. See if the company has any hosted events, holiday parties, or other in-person meetups (and if not, suggest some). If there's any coworkers that live nearby, suggest meeting up for lunch or after-work drinks occasionally.
Beyond that, as others have mentioned, you can seek out local social organizations and clubs, or even just try to interact with your neighbors more.
To someone in the same domain, all of those caveats are commonly accepted/implied, so they become tiresome and muddy the points being made.
To someone outside the domain, it unnecessarily erodes confidence in the supposed domain-expert speaker's abilities and recommendations. It's even worse when put up against someone else does speak with confidence. I've lost count how many times I've seen that leading to stakeholders accepting a suboptimal solution.