[problem]
You want to write elegant code, which integrates well (pipes) with other UNIX commands.
[/problem]
[solution]
Learn these UNIX Laws, from the inventor of UNIX pipes.
[/solution]
[example]
No examples – see the reference tab.
[/example]
[reference]
1. Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features.
2. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.
3. Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.
4. Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.
– Doug McIlroy, the inventor of Unix pipes and one of the founders of the Unix tradition.
[tags]UNIX Law, UNIX pipes, Unix Coding School[/tags]
[/reference]
If you have found my website useful, please consider buying me a coffee below 😉