Kudos to you for undertaking this task. I think a lot of folks would have simply not used their devices for 48 hours rather than learn the assistive tech.
That said, please don't fall into the trap of assuming that your experience is definitive, and of recommending/not recommending things to those of us who may be blind for our entire lives based on your 48 hours of experience. Case in point, I know a number of blind Python developers. I myself did a lot of Python during college, back when Zope was huge and Plone didn't exist. It's no more or less difficult than any other high-level language. Just about every screen reader I've used has the ability to speak line indentation (I.e. "8 spaces def fn(...") and this makes tracking scope easy. Holding a function in your head based on hearing it spoken is a skill that improves with practice. I've coded to varying degrees in every language you've listed, and while some of them do have their unique accessibility challenges (Haskell in particular I find dense because "f . g $ h i" packs a lot of meaning into something with little to break it up) I've learned to audit orally parse them over time.
FWIW, as a blind person, I imagine that coordinating the motion of a 2-ton block of metal and glass, down a strip of asphalt surrounded by a number of other chunks of metal and glass, moving as fast as baseballs and prone to factors like weather and surface conditions,, is a very fragile process that terrifies the hell out of me if I really think about it for any amount of time. I wouldn't not recommend driving to sighted folks just because I can't imagine how it routinely gets solved, though. :)