Explore >> Select a destination
|
You are here 
|
www.tedinski.com | ||
| | | | |
chipnetics.com
|
|
| | | | | An entry-level article for developers to share with their non-programmer colleagues in a corporate environment, as both a tutorial and learning experience. In particular, I intended it for developers who wish to adopt usage of their CLI (command-line interface) programs amongst end-users, but require their end-users to have some pre-requisite knowledge. | |
| | | | |
lambdaland.org
|
|
| | | | | Wikipedia1 cites a few different sources on what "Unix Philosophy" is. Peter Salus summarizes it as: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface. That second bullet point is my favorite: making composable programs rather than monolithic systems. In this way, Unix is designed to be a forge for easily building new tools. The first rule-writing programs that do one thing well-is largely a means... | |
| | | | |
dave.cheney.net
|
|
| | | | | ||
| | | | |
builtin.com
|
|
| | | What is software engineering? It is a field directly related to computer science, where engineers apply systematic and disciplined methods to the development, operation and maintenance of software. | ||
