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

About ICE negotiation

Disclaimer: I wrote this article on March 2022 while working with Subspace, and the original link is here:  https://subspace.com/resources/ice-negotiation . This post in my personal blog is a way to ensure it doesn't get lost. There is nothing service-specific in it, I've made only minor edits and I hope it can be a good technical reference on the topic. WebRTC is a set of protocols that allow applications, typically running on Web browsers, to exchange media (audio, video, data) with other entities. Before media can flow, however, the WebRTC entities need to discover what type of connection is possible, and among the possible connections, what’s the best to be used. This needs to happen as fast as possible, so that users can perceive the service as instantaneous as possible. WebRTC includes protocols like STUN and TURN that are designed to facilitate the establishment of connections when a direct connection is not possible. The typical case is a computer inside a home or o...
Read more

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

debian - Managing maintainer scripts for packages with multple .debs

If you've ever installed a package from command line on Linux, you must have noticed two main prompts related to package configuration: one asking what to do with installed configuration files with local changes, and one providing feedback right after the installation/upgrade/removal/purge has completed. Under Debian the latter was most probably the postinst script, one of the Package Maintainer Scripts which is executed after installation and configuration. These diagrams are very useful to understand what happens to the Maintainer Scripts in different circumstances: first installation, upgrade, removal, purge. Their name is probably self-explanatory: preinst , postinst , prerm , postrm . Each of them takes zero or more arguments depending on the scenario. It can help to understand that those are really just scripts executed by dpkg - and typically they are shell scripts, sometimes with interactive prompts. If you're building your own packages, you surely already h...
Read more