Skip to main content

It's not a sprint

You’ve surely heard at least once in your life somebody saying “Calm down: it’s not a sprint, it’s a marathon”.


People use this phrase to try and slow things down, but it misses the point.


The first misconception is that a marathon is something you do slowly. A marathon is fast; it’s just as fast as possible for that athlete in that moment.

Most people couldn’t hold an elite marathoner’s pace for even 100 meters. It’s a marathon, but it’s not slow.


It’s easy to make a point that running a marathon is tough, not just for the distance but for the speed you try to keep.


What’s maybe harder to see is that a marathon is much easier than many life challenges.


You can simply prepare for a marathon. You get to the starting line with months or years of preparation. You tried progressively longer and tougher sessions, simulating the marathon effort. That’s a privilege. Many hurdles you’ll face in life will just appear in front of you while you were thinking of something else.


A marathon has a fixed length and a fixed course that’s known in advance. Life challenges are typically faced only once, making you very unprepared.


You can run the same marathon many years in a row, each time learning something more about that specific event. In life, it’s never clear when a challenge will end. Or if it will end.


Nobody tries to make you fail at completing a marathon, apart, I guess, very rare exceptions. That’s not the case for many life endeavours.


You can quit a marathon. Nobody will blame you for it. There’s basically no risk that somebody will be harmed if you fail.


If you try to run in the wrong direction, somebody will likely tell you and help you get back on track. In life, you’d be lucky if somebody even notices. And the ones who notice may just stay quiet.


And finally the only way a marathon can disappoint you is if you have unrealistic expectations. People can disappoint you even if the expectations are modest.


So maybe next time somebody will tell you “Calm down: it’s not a sprint, it’s a marathon” you’ll want to answer “You wish”.


Labels:

Popular posts from this blog

Troubleshooting TURN

  WebRTC applications use the ICE negotiation to discovery the best way to communicate with a remote party. I t dynamically finds a pair of candidates (IP address, port and transport, also known as “transport address”) suitable for exchanging media and data. The most important aspect of this is “dynamically”: a local and a remote transport address are found based on the network conditions at the time of establishing a session. For example, a WebRTC client that normally uses a server reflexive transport address to communicate with an SFU. when running inside the home office, may use a relay transport address over TCP when running inside an office network which limits remote UDP targets. The same configuration (defined as “iceServers” when creating an RTCPeerConnection will work in both cases, producing different outcomes.
Read more

Extracting RTP streams from network captures

I needed an efficient way to programmatically extract RTP streams from a network capture. In addition I wanted to: save each stream into a separate pcap file. extract SRTP-negotiated keys if present and available in the trace, associating them to the related RTP (or SRTP if the negotiation succeeded) stream. Some caveats: In normal conditions the negotiation of SRTP sessions happens via a secure transport, typically SIP over TLS, so the exchanged crypto information may not be available from a simple network capture. There are ways to extract RTP streams using Wireshark or tcpdump; it’s not necessary to do it programmatically. All this said I wrote a small tool ( https://github.com/giavac/pcap_tool ) that parses a network capture and tries to interpret each packet as either RTP/SRTP or SIP, and does two main things: save each detected RTP/SRTP stream into a dedicated pcap file, which name contains the related SSRC. print a summary of the crypto information exchanged, if available. With ...
Read more

Testing SIP platforms and pjsip

There are various levels of testing, from unit to component, from integration to end-to-end, not to mention performance testing and fuzzing. When developing or maintaining Real Time Communications (RTC or VoIP) systems,  all these levels (with the exclusion maybe of unit testing) are made easier by applications explicitly designed for this, like sipp . sipp has a deep focus on performance testing, or using a simpler term, load testing. Some of its features allow to fine tune properties like call rate, call duration, simulate packet loss, ramp up traffic, etc. In practical terms though once you have the flexibility to generate SIP signalling to negotiate sessions and RTP streams, you can use sipp for functional testing too. sipp can act as an entity generating a call, or receiving a call, which makes it suitable to surround the system under test and simulate its interactions with the real world. What sipp does can be generalised: we want to be able to simulate the real world tha...
Read more