On the TechWaterloo stage ×1
First seen on the TechWaterloo stage in 2017. Every talk is searchable — ask the archive about Monty ↗
In their words
in the 1950s in Fort Worth um they did a study and they found that no matter how much car infrastructure they added they couldn't relieve congestion
I see it as really a societal change of us going okay that worked for a while
maybe it's not enough anymore to just work in automation and just be, um, a leader or a coder in that capacity, but also to be become an expert on universal basic income at the same time
Around the web ×1
Quick answers
Why was an architect on a Hyperloop team?
Because the pod is a windowless space a person sits inside at very high speed, so how it feels is an engineering requirement rather than decoration. De Luna told TechWaterloo in February 2017 that he joined for the infrastructure argument: adding car lanes never relieved congestion, and the Hyperloop is a bet that the past can be rejected outright.
What was his role on Waterloop?
Architectural lead. He described himself on stage as a master's of architecture student who worked on the pod's design and shell as well as the administrative side — marketing, sponsorship and the team's Kickstarter. The University of Waterloo named him architectural lead in January 2017 after the SpaceX preliminary round.
What is Monty de Luna doing now?
Not established. This page does not publish from LinkedIn or contact-data aggregators.