Eventually, you reach this list’s conclusion, which lies in an unassuming technical question about the trains themselves. After you have figured out what they will look like, and how fast they will run, you need to give signal engineers two facts about them: how fast they can accelerate, and how quickly they can stop. And you need to make sure that your car equipment engineers keep those values the same until you replace the signal system. Remember, the whole point of having signals is keeping a train going at any given location’s maximum possible speed enough braking distance from its leader to prevent a collision. If your gain acceleration performance or lose braking power without rebuilding your signal system, the whole pyramid of assumptions comes crashing down.
How We Slowed the Subway Down
from ~ uday schultz
Filed under:
Same Source
Related Notes
- Deep and shallow modules: The best modules are deep: they allow a ...from John Ousterhout
- It is far easier to collaborate on a first principle model. At this...from sirupsen.com
- If you are designing for 8 demands it’s likely that 6 are easy, 7 r...from sirupsen.com
- Good architecture is built incrementally, but **not** designed incr...from sirupsen.com
- If all the burghers of Small Town USA get together and say “we want...from Matt Levine
- The only good advice I have here is to re-evaluate your metrics oft...from ferd.ca
- Organizing into services taught teams not to trust each other in mo...from gist.github.com
- This, from last week, is [one of the best stories you’ll ever read]...from Matt Levine