|
|
|
|
|
by onetoo
972 days ago
|
|
FWIW the (seemingly?) complete lack of bikeshedding makes it a lot easier to approach Go over Python wrt. tooling. IME it feels impossible to make an informed decision without already being knee-deep in the ecosystem, and yet new developers are forced to decide as part of their IDE setup. It's just plain cruel. I say every language should standardize on an extremely opinionated formatting tool, whatever those opinions happen to be. To the point where source code should be considered to have a canonical representation. Get rid of the sheds and bikes. Unfortunately, there are often 14 competing standards... |
|
Bike shedding is when people spend too much time discussing trivial issues, like what color to paint a bike shed, instead of focusing on more important matters. It happens when it's easier to have an opinion on simple, minor issues than on complex, major ones.
Yak shaving is when you find yourself doing a series of unexpected tasks just to solve an original, simple problem. Imagine wanting to fix a leaky faucet, but you end up needing to buy a new wrench, then fix your car to go to the store, and so on—like a chain reaction of tasks just to get back to fixing the faucet.
TL;DR: bike shedding is fussing too much over small details, while yak shaving is getting sidetracked by a chain of tasks that are needed to solve your main problem.