4 ms·
> Do you know that keeping your users in a constant state of confusion is not the way to > convince them that you're building a stable and secure product This.
by elfchief 9y ago
> Do you know that keeping your users in a constant state of confusion is not the way to
> convince them that you're building a stable and secure product
This.
I was a very early proponent of docker, and have been using it continuously since the very early versions. I read the release notes and most weeks I read the weekly email newsletter, and I still don't really have a clue where Docker is going, what its current status is (as far as how the various pieces fit together, etc) or what half the new features even do.
The docker team's communication is really poor, and their documentation seems even worse, unless I'm missing some oracle somewhere that fills in all the details that the actual documentation leaves out...
- chii 9y ago> what half the new features even do if you don't currently use any of these new features, and can't work out what they do, perhaps you really don't need them. Therefore, ignoring it and continuing on is the best cause of action. It's not docker team's responsibility to educate you!
- elfchief 9y agoWell, sure, you can make that assertion, but when you have someone that is a) already pretty familiar with the technology, b) continuously keeping track of the product for years, and c) goes out of their way to try to educate themselves... and that person still feels kind of lost... sure, you could put all the blame on them, but that seems a bit disingenuous. (Or you could make the assertion that I'm just an idiot, but my career suggests otherwise.)
- throwaway2048 9y agoActually it is their responsibility to educate you. What do you think documentation does exactly?
- alexktz 9y agoAmen!