Abstract
Now that we have discussed so many design principles, you may feel that it’s time to get a little bit more practical. You just want to finally start creating wonderful packages and share them with your co-workers, or even with the international open source software audience. I definitely think you should do that. Before you do, I want to give you some last words of advice.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Robert L. Glass, Facts and Fallacies of Software Engineering, Pearson Education, 2003.
- 2.
Robert L. Glass, Facts and Fallacies of Software Engineering, Pearson Education, 2003.
- 3.
Robert L. Glass, Facts and Fallacies of Software Engineering, Pearson Education, 2003.
- 4.
Robert L. Glass, Facts and Fallacies of Software Engineering, Pearson Education, 2003.
- 5.
Robert L. Glass, Facts and Fallacies of Software Engineering, Pearson Education, 2003.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Matthias Noback
About this chapter
Cite this chapter
Noback, M. (2018). Conclusion. In: Principles of Package Design. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4119-6_12
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4119-6_12
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4118-9
Online ISBN: 978-1-4842-4119-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books