Someone who has been in a role for years has often absorbed the issues and found ways to navigate around the biggest pain points (the upside of this is a deeper understanding of the environment). But someone who just joined can often see some issues more clearly than anyone else, and someone who is just finding their stride is in a sweet spot for delivering useful feedback.
I’m not claiming to know the ins/outs of classrooms, nor do I know enough about this person to pass judgement, but disdain seems rather misplaced and counterproductive.
Neither should all decisions about improving the system fall on newcomers, but they will have extremely important and valuable feedback. This seems like unnecessary gatekeeping if not tempered by reasonable policies that seek feedback from numerous sources, especially at a time when classrooms are in crisis and improvement is critical.
Blanket disdain is always a red flag.
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.
I’ve been in tech for ~20 years, and if there’s one thing that never changes, it’s that newcomers are eager to tell me how to do my job.
Fresh grads come in convinced it’s their time to shake things up.
Management brings in consultants to tell me how to do my job.
The new SVP comes in and tells me how to do my job despite not understanding the environment, etc.
Over the years I’ve found it far more useful to frame this kind of feedback as just another signal among a myriad of signals, which collectively can be quite valuable.
It seems common to any human organization, especially those that rely on specialized skills, and I’d argue that the outcome is similar: just as experience and deep understanding can be important for stability, questioning the status quo can be just as critical for navigating societal change and long term success.
I’m here to argue against the binary position, not to claim that newcomers should be running the show.
Edit: I don’t mean to be dismissive of the submitter. You very well may have a unique insight into CS instruction based on your time in the classroom. I would just caution that - from a marketing point of view - two years in the classroom is not going to instill confidence in your expertise with long term educators (so avoid making it a selling point as such).
Imagine if we talked about people learning programming the same way?
I have a general disdain for anyone who programs for 2 years and then thinks they have learned enough to teach anyone or improve the system in any way. 2 years is how long it takes just to learn git, let alone be comfortable teaching it. You better wait awhile, chief. Programming is the most important, most hardest, most critical thing in the world. Imagine thinking you could just stroll into MY world and make a possible difference in somebody's life with your abysmal and inexperienced self. The hubris! Y'know what? Go to the principle's office. This will be on your permanent record.
my wife is a HS teacher of about 15 years, truer words have never been said.