Cat Hicks
Psychologist for the humans of tech
Evidence strategy for technical teams
The Psychology of Software Teams (July, 2026): https://www.drcathicks.com/#book
Co-host at Change, Technically: https://www.changetechnically.fyi/
Seizing the means of scientific production. "Too much psychology for a software engineering audience" - Reviewer 2
She/her
Founded: Catharsis Consulting, Developer Success Lab, Travrse
Neighborhood Cool Aunt of Science
some candidate pitfalls/fallacies:
-
thinking that just because you reverse a characteristic in the body, the body will just "go back" to the prior state (it has already been through a change that probably changed other things)
-
merging things at inappropriate levels of granularity/scale, like thinking because you know a peptide or such is involved in x, the peptide-or-such "explains x" or "is the sole cause of x"
others you see?
The length of time of that window? We don't know for certain, but the range looks roughly similar to the length of time THESE things take:
- how long it takes most women with these symptoms to get referred to a specialist in the first place
- around the length of time you might spend battling two denials + appeals of a medication (based on my personal experience)
- the time it takes your favorite local psychologist to pitch, draft and publish a book
- the risks of having some very specific mechanistic knowledge of biology but then vastly oversimplying other parts. Interactions between systems are a good example here.