I can see why, but this is doc+patient in collab. And driven by using science in the form of applying llm-as-database-of-symptoms-and-treatments.
Anti-vax otoh is driven by ignorance and failure to trust science in the form of neither doctors, nor new types of science. Plus, anti-vax works like flat earth; a signaling mechanism of poor epostemic judgment."
Ive observed a modern trend of little to no QA. Managers and CTOs insist developers can test their own systems. Maybe this makes more sense in the early phases of product development where I find myself lately? Seems to capture a lot of dev's time.
Love the idea, but whence the training data? Not as readily available as billions of jpegs, lines of code, and audio files. Any clever ideas to source it?
Good question. First start as small as possible. You dont need to design a massive system and burnout is a real possibility... which leads to: find groups already set up around you. We have a local food pantry that also cooks for people. It's ok to test drive various groups until you find good fits. There are various ways. Im helping a group get their non-profit status atm. Not super visible or boots on the ground but needed/useful. Other groups just need people to help reach out on social media.
It's as much a state of mind as physical actions and good for you for starting to see the need and opportunities.
Its not even just Rails ppl. In embedded ive seen so many consultants say things like, "no problem. I just started working on the ultimate, perfect way to set up a state machine." Confidence theater
Anti-vax otoh is driven by ignorance and failure to trust science in the form of neither doctors, nor new types of science. Plus, anti-vax works like flat earth; a signaling mechanism of poor epostemic judgment."
reply