I think that to some extent, ignorance of the field can sometimes be a blessing. When you know what the hard things are (or think you know, at least), you might be hesitant to do things that will be too hard. But if you come at it with no experience, and know knowledge of where the limits might be, you might inspire someone to think outside the limits, approach the problem from a new direction, and end up doing something cool.
I used to work for a company building software for mobile phones. They were pretty weak devices at that time, with no GPUs, and battery life was valued above almost everything else. The engineering teams had told the UI teams that animation was impossible. They said it would take too much CPU, use too much battery, and would never look smooth. But one day, a group of developers who hadn’t been told about these limitations decided to build a small app with some cool-looking animations.
It worked! It animated at about 30 fps, and since it was used judiciously, the battery drain was minimal.
There’s a similar story from Apple, when Jobs was given an early version of the iPod to look at. He complained it was too big. The engineers of course explained that they had done everything they could to shrink it down, including inventing new assembly methods to get it as small as possible. In response, Jobs dropped the prototype in a fish tank. Pointing to the air bubbles, he said “See, there’s still space in there.”
It’s probably very useful to understand how engineers work, but be careful if they tell you something is hard or impossible. Those barriers may not be as solid as they seem.