That's a bit of an overstatement; it's responsible for very few technical decisions in Debian, and doesn't normally have even a theoretical ultimate-decision-maker role of regularly reviewing or steering them. Their only role is technical dispute-resolution, and they are supposed to wade into even that as minimally as possible. Most technical decisions are made by a mixture of individual package maintainers, the Debian Project Leader and release-management team, and informal consensus-building. To the extent there's an "ultimate" technical decision-maker, I would say for the majority of issues, the release team working with the project leader functions in that role.

What does that really mean? Debian is a community project, not a hierarchical organisation with a managerial chain of command.

The Technical Committee seems much more like an advisory board and the forum for and arbiter of the tiny number of contentious issues.

They're not involved in, informed of or responsible for the vast majority of technical decisions.

it would kill redhat too then.

systemd was created by well intentioned people, solving a real issue but being a bit too aggressive and attempting to rewrite everything.

hand waving sure.

And Tollef Fog Heen (partial resignation), but he and Joey were not Technical Committee members.

According to his blog, he didn't resign because of systemd. In fact, he seems to quite like it: https://joeyh.name/blog/entry/a_programmable_alarm_clock_usi...