Really happy to see this starting and eager to learn how I can help. Looking forward to talking soon at EAG.
I resonate with your pitfall statement. Although I haven’t been actively exploring the non-SW engineering space in EA for very long, it does seem that there is a scarcity of technical information publicly available about where and what the specific needs are from a ME, EE, CE, MatSci, robotics, systems, manufacturing, or other non-SW perspective on a variety of problems.
For example, take the biosecurity cause area needing more materials science expertise for better PPE. Intuitively there is a core MatSci aspect to this most people can easily recognize, but there are 1) probably a lot more types of challenges you would discover once you dig into the details of the problem or begin basic conceptual synthesis, and 2) even the MatSci-specific aspects of this problem are hard to find without actually just digging into the decades-long literature on the general topic of PPE. And I think this might be generally true across domains, though I haven’t tried looking exhaustively yet.
Having dashboard-like visibility (whether it’s a literal SW-enable dashboard or not) into the technical problem landscape across disciplines and across cause areas sounds like the holy grail to me, which is obviously a lot to ask for at the moment, but that’s the general direction I personally hope for.
Thanks Vlad! We spoke at EAG SF but wanted to put a comment here for anyone interested in contributing to or viewing of the map of the technical problem landscape to reach out to me or Vlad :) we will have updates soon so keep posted!
Really happy to see this starting and eager to learn how I can help. Looking forward to talking soon at EAG.
I resonate with your pitfall statement. Although I haven’t been actively exploring the non-SW engineering space in EA for very long, it does seem that there is a scarcity of technical information publicly available about where and what the specific needs are from a ME, EE, CE, MatSci, robotics, systems, manufacturing, or other non-SW perspective on a variety of problems.
For example, take the biosecurity cause area needing more materials science expertise for better PPE. Intuitively there is a core MatSci aspect to this most people can easily recognize, but there are 1) probably a lot more types of challenges you would discover once you dig into the details of the problem or begin basic conceptual synthesis, and 2) even the MatSci-specific aspects of this problem are hard to find without actually just digging into the decades-long literature on the general topic of PPE. And I think this might be generally true across domains, though I haven’t tried looking exhaustively yet.
Having dashboard-like visibility (whether it’s a literal SW-enable dashboard or not) into the technical problem landscape across disciplines and across cause areas sounds like the holy grail to me, which is obviously a lot to ask for at the moment, but that’s the general direction I personally hope for.
Kudos to you all for starting this.
Thanks Vlad! We spoke at EAG SF but wanted to put a comment here for anyone interested in contributing to or viewing of the map of the technical problem landscape to reach out to me or Vlad :) we will have updates soon so keep posted!