Coaster Brake Failure

https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?
--
Andrew Muzi
www.yellowjersey.org/
Open every day since 1 April, 1971

AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.

On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums up
the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in software
design.

--
Regards, Joerg

http://www.analogconsultants.com/

Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums up
the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in software
design.


In Yiddish, it's "farpotchket", which loosely translates to "broken during
the act of fixing it".

On 2019-02-25 10:12, Ralph Barone wrote:
Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums up
the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in software
design.


In Yiddish, it's "farpotchket", which loosely translates to "broken during
the act of fixing it".


That might have the same roots as the German "verpfuscht" or "verpatzt".
When someone tries to design or fix technical stuff and either has no
clue how to go about it, is in a hurry or doesn't really have the budget
for it.

--
Regards, Joerg

http://www.analogconsultants.com/

On Monday, February 25, 2019 at 8:06:33 AM UTC-8, Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket

Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums up
the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in software
design.

--
Regards, Joerg

http://www.analogconsultants.com/

You hit the nail right on the head. For projects that required very fast response from microprocessors I used to use assembly language. Because of that people started to use assembly language in many projects. The trouble is that assembly language is extremely tedious to program. So they would "improve" it by building libraries of assembly language subroutines. Then in order to use these you didn't know exactly what you had to do so you would save all of the registers and branch to the subroutine, save any necessary data from that and then return and retrieve all of the registers and data to use.

This was what higher level languages did but they usually did it more efficiently by only saving the necessary registers and not saving the returned data but simply passing it back.

This put C and C++ into the position that these higher level languages were actually both more memory efficient but also faster in operation.

This is what happens when people improve things that they don't understand.

Though I'm sure that those who don't know anything about this will have plenty of comments about it.

On 2/25/19 5:06 PM, Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket



Mysterious. How the hell did that happen in a design 100+ years
old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums
up the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in
software design.

https://www.youtube.com/watch?v=gp_D8r-2hwk

On 2019-02-25 11:42, Tosspot wrote:
On 2/25/19 5:06 PM, Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket




Mysterious. How the hell did that happen in a design 100+ years
old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums
up the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in
software design.

https://www.youtube.com/watch?v=gp_D8r-2hwk


Sometimes those things happen for reasons Tom mentioned. People using
library modules that others have written, assuming everything in those
we be just fine. And then things aren't.

This is one of the reasons why I prefer gear with the least amount of
electronics and software in there and, for example, will never be caught
with electronic shifters on a bicycle.

I am saying this as an engineer who designs electroncics.

--
Regards, Joerg

http://www.analogconsultants.com/

On Wednesday, February 27, 2019 at 8:09:00 AM UTC-8, Joerg wrote:
On 2019-02-25 11:42, Tosspot wrote:
On 2/25/19 5:06 PM, Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket




Mysterious. How the hell did that happen in a design 100+ years
old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It sums
up the action of "Here we have a working design but let's optimize it
anyhow" and then it all goes to pots. A very common scenario in
software design.

https://www.youtube.com/watch?v=gp_D8r-2hwk


Sometimes those things happen for reasons Tom mentioned. People using
library modules that others have written, assuming everything in those
we be just fine. And then things aren't.

This is one of the reasons why I prefer gear with the least amount of
electronics and software in there and, for example, will never be caught
with electronic shifters on a bicycle.

I am saying this as an engineer who designs electroncics.

I have Ultegra Di2 on my super rain bike Synapse. Works great except that I broke the rear derailleur wire being careless cleaning the bike in a wash stand. I soldered the broken wire and shrink-wrapped it. I also bought a new wire, but the repair seems to be working fine.

The problem with Di2 -- or maybe just 11sp -- is that chain wear beyond .5% but below .75% really degrades shifting. Down-shifts hang up. I threw on a new chain last night, and now it shifts great. I didn't think I had that much mileage on the chain, but I guess I did. I bought a couple $19 11sp 105 chains from Western Bikeworks for back-ups.

The great thing about Western is that if you buy $50, it's free shipping, but if you pick up in store, its $5 off. I can ride to the store on my way home from work and save $5, although not today because it snowed, and I slacked-off and car-pooled with my son.

-- Jay Beattie.

On 2/27/19 5:09 PM, Joerg wrote:
On 2019-02-25 11:42, Tosspot wrote:
On 2/25/19 5:06 PM, Joerg wrote:
On 2019-02-25 07:29, Ralph Barone wrote:
AMuzi wrote:
https://www.bicycleretailer.com/reca...nd-aftermarket






Mysterious. How the hell did that happen in a design 100+
years old?

They must have improved it.


In German there is the inofficial word "verschlimmbessern". It
sums up the action of "Here we have a working design but let's
optimize it anyhow" and then it all goes to pots. A very common
scenario in software design.

https://www.youtube.com/watch?v=gp_D8r-2hwk


Sometimes those things happen for reasons Tom mentioned. People using
library modules that others have written, assuming everything in
those we be just fine. And then things aren't.

https://www.youtube.com/watch?v=kYUrqdUyEpI

This is one of the reasons why I prefer gear with the least amount of
electronics and software in there and, for example, will never be
caught with electronic shifters on a bicycle.

I am saying this as an engineer who designs electroncics.