3 ms·

> This isn't bad advice, but I would add to it. If you're a large organization and building in such a way that large groups need to understand the details of wh

by vageli 8y ago

> This isn't bad advice, but I would add to it. If you're a large organization and building in such a way that large groups need to understand the details of what you're doing, then you're doing it wrong. > Ideally speaking, implementations can be worked through with small groups. Only the interfaces need to be exposed and documented. Unless you're doing something beyond CRUD, drowning teams in unnecessary details often result in distraction. This is assuming that attrition is not a thing. The set of engineers that are on your team is likely smaller than the total number of engineers that will ever work on your project. When people want to know six months from now why you chose RabbitMQ over other tech at the time, having an RFC lets you point to an artifact versus conjecture on past motivations.

toast0 8y ago
Do the reasons for the choice six months ago even matter today? Today you have six months of history of it being a good choice or not. And six months of development assuming it was the choice, that may or may not apply to something else. And the choices available today have likely changed from six months ago, too. (I'm a little concerned about your team that has no connection to decisions from six months ago, but we can adjust the time frame and the rest still applies)
- seb1204 8y ago
  Of course they matter. Ideally the decision that was made 6 months ago under the conditions/restraints was the right one back then. Since then circumstances might have changed that would result in a different decision 6 months ago if you had known. Only if you have a record of some sort (ideally with background information and not just the time of the decision) people will be able to understand and re-evaluate the past. Money and time was invested since then and the decision to keep the course or to change again should consider the history of the decision.

by vageli 8y ago

toast0 8y ago

Do the reasons for the choice six months ago even matter today? Today you have six months of history of it being a good choice or not. And six months of development assuming it was the choice, that may or may not apply to something else. And the choices available today have likely changed from six months ago, too. (I'm a little concerned about your team that has no connection to decisions from six months ago, but we can adjust the time frame and the rest still applies)

seb1204 8y ago
Of course they matter. Ideally the decision that was made 6 months ago under the conditions/restraints was the right one back then. Since then circumstances might have changed that would result in a different decision 6 months ago if you had known. Only if you have a record of some sort (ideally with background information and not just the time of the decision) people will be able to understand and re-evaluate the past. Money and time was invested since then and the decision to keep the course or to change again should consider the history of the decision.