|
|
|
|
|
by jeremymcanally
1106 days ago
|
|
I have a lot of friends (including my spouse) who are teachers, and I can pretty confidently say that an office environment/culture/work sphere as we as engineers are used to is vastly different than working in a classroom. We don’t often value experience because, you’re right, often times fresh eyes do bring useful insights. But in the case of teaching (and probably many other things), consensus seems to be that experience does vastly affect one’s effectiveness. I applaud the OP for their attempt to bring something new, but I feel like if maybe they’d waited a couple more years they may have an easier time thinking through the problem set and creating a product to fit the need. Perhaps I’m wrong! But that’s just my feeling from the many conversations I’ve had with teacher friends. |
|
This isn’t quite what I’m getting at. Even in an office environment, I bias towards valuing experience over naive and idealistic attempts to fix everything that’s wrong.
My point is closer to: those fresher experiences are ephemeral and also an important signal alongside deeper experience and institutional knowledge.
Office environments are also full of inexperienced people trying to fix systems they don’t understand.
My point is not that inexperienced people should be taking over, but that people in positions to institute change should be listening to newcomers along with seasoned veterans. I don’t see this as an either/or stance.