1,094 karma · joined July 28, 2013
GitHub: https://github.com/astockwell
Twitter: https://twitter.com/astockwell
Site: http://astockwell.com
Damn. Doesn’t that just sum up so many interactions (and sadly, relationships) in life.
Also, track your time during the work. And keep all correspondance. Paper trail, paper trail, paper trail.
History books on 1945 aggressive monetary policy change: "The public didn't like it"
History books on 2025 aggressive monetary policy change: "The public went frigging bananas, doxxed their leaders, coordinated widespread disobediance on the scale of GME, etc"
(Granted I live in the US, and that's putting it mildly how the US would react)
Couple this with decreasing costs of storage (and ideally compute), and it doesn't matter if the data model is garbage, people can still get something workable that's better than the awful Excel files they curate now. It will still make errors, but eventually fewer than their spreadsheets.
This was in the early '00s, and hand-over-heart, there was less than 10 pages _on the internet_ about Reinhardt. The collegiate library was not much more help.
> The most common chemical sunscreen ingredients cause cancer themselves
Both of these statements are out-of-date.
Recent studies show two different histological subtypes of melanoma for young adults vs older adults, each following a different common mode of presentation [1]. Melanoma in younger adults tends to present on the long limbs and is thought to have different contributing factors.
Also "common chemical sunscreen ingredients cause cancer" is a common FUD trope. Sunscreen reduces cancer mortality, full stop. Each person's circumstances vary based on their daily habits, geography, and personal/familial history.
I would have thought this thread was overblown had I not inadvertently done that a few weeks ago. But it was truly surprising just how awful the “untailored” ads were.
“Come back to the office”
“We’ll be resuming periodic Active Shooter drills”
I’ve been on several teams that consistently endeavor to keep the knowledge of a code base shared, but every time the code base reaches a certain size, the Bus Factor creeps right back in, but this time for “modules” or areas of the broader code base.
Combine a large code base, 4-8 engineers making constant changes all over, and it becomes a real struggle to keep everyone “up” on the whole thing.
Has anyone seen a workable strategy for this?
Can recommend.