Edit - Bicycles Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

4

This may depend on the descent. The context implies that this was a relatively short and shallow one where it’s feasible and arguably preferred to stay together. For an extended and/or steep descent, I’d agree.
– Weiwen Ng
Commented Jun 16, 2022 at 15:43
4

Rider A should have stayed where they were and let whoever wanted to go faster pass them on the left. Won't work in a paceline situation, and being in a descent doesn't matter. No one is a paceline is looking to move left until they get to the front, do their pull, and roll off. Stay where you are, let the faster riders go around you OH HELL NO. No one will ever be expecting someone at the front of a paceline to just slow down and not roll off. That's downright dangerous advice, and very likely to be the direct cause of a multi-bike crash at speed.
– Andrew Henle
Commented Jun 16, 2022 at 18:22
@WeiwenNg But that will work only after it's downright obvious to everyone that the paceline has broken up. And the rider on the front is going to be the last to know.
– Andrew Henle
Commented Jun 16, 2022 at 18:27
1

@AndrewHenle Which is precisely why you don't try to run pacelines on a descent.
– Mohair
Commented Jun 16, 2022 at 18:45
1

@Mohair When you get a UCI-sanctioned cycling license and actually do mass-start races THEN you can lecture about the "reality" of riding fast in groups. Until then, you are giving DANGEROUS advise because, frankly, you don't know what the hell you're talking about.
– Andrew Henle
Commented Jun 16, 2022 at 21:11

| Show 2 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »