|
|
|
|
|
by nathants
955 days ago
|
|
the issue is collaboration on software implementation. this is extremely hard to do well, think lkml. the typical collaborative implementation environment is a disaster. we are baking a cake, slowly over weeks and months. we aren’t sure why or who’s at fault, but we are absolutely sure it looks awful and tastes worse. the only silver lining is that the solution to this disaster is hiring more collaborators. jobs and ubi all around. microservices obviously didn’t quite work, but were an idea in the right direction. we need to collaborate at a higher level than code. we need to work in a bakery together, but each bake alone. then we can easily evaluate the quality and pace of each other. there is no ambiguity of individual responsibility. when my cake is bad, i should feel bad. i should look around the kitchen for better cakes, and ask their baker what they do that i don’t. when my cake is bad and i don’t care, my boss should move me to less important cakes, or out of baking all together. |
|