I consider myself the latter who just hasn’t had the time to look into Rust or Zig extensively. But also, I work in safety critical application and it would be hard to shift the organization over to Rust for a lot of reasons, both technological and political.
I was in high school in the late nineties and I was looking forward to some nostalgia but this is hard to watch. I had kinda blocked from my memory that most people felt they needed a computer but didn’t know why. The internet was so new, it wasn’t essential yet. We still used the phone book as a primary source. Most people’s internet was through America Online and you stayed in their walled garden. They still bought computers out of fear of getting left behind. I did a lot of free IT work for friend’s parents in those days.
So, I’m a first-level manager and we basically run an ad-hoc for our team that looks like a blend of spiral and milestones.
For me, the problems arise when methodologies intended for large-scale are applied at a small scale.
What’s a methodology for anyways? To help communicate and to reason-at-scale. If you can’t communicate or reason with a single team, process isn’t going to help. But once you have 200+, then you need process!
And my larger organization does have process, it looks waterfallish repeated every six months. I just don’t apply it to my team.
Personally, I think we do our entire species a disservice if students can’t access free math education up through Calculus. Where it gets muddy for me is how much should be compulsory, especially if it generates math anxiety. I don’t have a good answer.
Good luck designing your system! Sorry I don't have any advice.